Disk and Network Filesystems/use quotas & Hostname and DNS Client/127.0.0.1 keep reseting

I have noticed this over many weeks/momths. but every time I set quota's up and add 127.0.0.1 to the DNS setting, after reboot, these setting revert back to previous.

Is this meant to happen?

Paul

Status: 
Active

Comments

Howdy -- are you by chance using DHCP for your IP address?

DHCP is capable of altering both your hostname as well as your DNS settings. Using a static IP would resolve that, or you can just tweak your DHCP settings to not modify the hostname and DNS.

I dont think so!! I wouldnt expect a VPS to have that option - is not in VM anywhere is it?

Any thoughts on the quotas issue?

Well, it's not normal for those things to reset on a server after a reboot, if you aren't using DHCP :-) It sounds like something unusual is going on...

A few questions for you --

What kind of VPS are you using?

What are the contents of "/etc/sysconfig/network-scripts/ifcfg-eth0"?

What are the contents of "/etc/fstab" after rebooting?

What kind of VPS are you using? Xen

What are the contents of "/etc/sysconfig/network-scripts/ifcfg-eth0"?

DEVICE=eth0 BOOTPROTO=static ONBOOT=yes IPADDR=95.154.208.51 NETMASK=255.255.255.255

What are the contents of "/etc/fstab" after rebooting?

I was born of XenVZ!

proc /proc proc defaults 0 0 devpts /dev/pts devpts defaults 0 1 /dev/sda2 none swap sw 0 1 /dev/sda1 / ext3 errors=remount-ro 0 1

Hrm, one of the things I notice there is that the usrquota and grpquota settings from your fstab are missing.

So, your fstab is changing, as is your resolv.conf.

Those aren't things that Virtualmin would be changing -- is it possible that your provider is doing that automatically on bootup?

You were spot on!!

When I asked the host, they responded:

"This is because our system automatically writes to these files at power on time to ease administration for most of our client base."

I have switched that process off, however, they warn that it is now even more important to keep the kernel up to date! Is this an automatic process with VM?

I don't believe Virtualmin would perform package updates by default... doing that drives most sysadmins batty :-)

However, you can certainly perform kernel upgrades along with your typical server's package upgrades.

Also, you can configure Virtualmin's behaviour regarding package updates by going into Virtualmin -> System Information, click "Virtualmin packages" in the "System" screen at the top, then scroll all the way to the bottom to tweak how package updates are handled.