Linux Servers not saving new setting.

[VMhomebox]

So, my last post never got any kind of responces, so here I am back again.

Please note, that I have an old server and a new one I am going to be replacing.

My old Proxmox server is 5.0-30, while my new server is 8.0.3

So, on my old Server I am having issues with updating settings with Open Media Vault, where I can not run updates, change web interface settings or change the password.

And with my new box, I have been trying to install Smooth Wall Express 3.1 SP4, this will not keep the network card settings apon reboot, I have tried setting up both OS's on bare metail and I do not have these issue.

Any idea from anyone on here, as to what might ben going on?

I'll link my other post here

**Update**

So anyone coming across this, no this iusse has not been fixed and as to what is going on.

No idea.

 

[LnxBil]

In one image, there is "no space left on the device" displayed, maybe check this.

 

[VMhomebox]

In one image, there is "no space left on the device" displayed, maybe check this.

I have done yes, please see attached.

With OMV the OS only has 8GB while all the 'data' is kept on a second disk image, that is always fine.

I should had that both VM are having the same issue, both do not allow for changes to the OS.

 

[LnxBil]

I should had that both VM are having the same issue, both do not allow for changes to the OS.

It's clear if the disk is full and you df states exactly this.

 

[VMhomebox]

It's clear if the disk is full and you df states exactly this.

That would answer it on the old server, but what about my new one, where I am getting similar behavior.

 

[LnxBil]

That would answer it on the old server, but what about my new one, where I am getting similar behavior.

Post df of the new server, and we'll see if the problem is the same.

 

[VMhomebox]

Post df of the new server, and we'll see if the problem is the same.

By all means, take a look below.

 

[LnxBil]

So, it's not the space. Now we need error messages on the new system where you want to change a setting.

 

[VMhomebox]

So, it's not the space. Now we need error messages on the new system where you want to change a setting.

Look at the last two images from my first post.

 

[LnxBil]

Sorry, that's not enough.

 

[VMhomebox]

Sorry, that's not enough.

What else do you need?

 

[LnxBil]

What else do you need?

Anything useful. Just a screenshot with an error message is simply not enough.

Try to set something in the system via a cli way so we have a command and the corresponding error message.

All screenshots look like a very old linux and on their webpage, the last version is from 2014, is this correct? I cannot recommend running such an old software especially for security purposes.

 

[VMhomebox]

Anything useful. Just a screenshot with an error message is simply not enough.

Try to set something in the system via a cli way so we have a command and the corresponding error message.

All screenshots look like a very old linux and on their webpage, the last version is from 2014, is this correct? I cannot recommend running such an old software especially for security purposes.

As said in my first post, I am using SmoothWall Express 3.1, I have tried both the base and the latest SP4 Build.

All have the same reaction, I go through setup, reboot and I get that nic error. I find I have to reapply the network card settings and then its all good.

I have tried that cli command and all I get is an error.

Also 2018, however once I can get red working, the follow up update will go as high as 2020.

-

So, I have attached the log files, now this is in a fresh install and I have rebooted the system once and had to do the network card settings. And yes I have gotten the same error as before.

The Smoothwall 5 error file from my first post.

 

[LnxBil]

There is no error reported there, but shown that this software should never be used for something security related, it's just too darn old.

 

[VMhomebox]

There is no error reported there, but shown that this software should never be used for something security related, it's just too darn old.

Well as I said before, on bare metail this works just fine, that includes running updates, however trying to run it on a VM, nope.