Error messages: WARN: uid is 0 but '/' is owned by 107

1

Hello,

How would I fix these errors. They run when I enter mailinabox.

Initializing system random number generator…
WARN: uid is 0 but ‘/’ is owned by 107
WARN: uid is 0 but ‘/’ is owned by 107
Firewall is active and enabled on system startup
Installing nsd (DNS server)…
WARN: uid is 0 but ‘/’ is owned by 107
Installing Postfix (SMTP server)…
WARN: uid is 0 but ‘/’ is owned by 107
WARN: uid is 0 but ‘/’ is owned by 107
Installing Dovecot (IMAP server)…
WARN: uid is 0 but ‘/’ is owned by 107
WARN: uid is 0 but ‘/’ is owned by 107
WARN: uid is 0 but ‘/’ is owned by 107

2

It seems that your filesystem permissions are broken. Did you run a chown -R somewhere? I would probably reinstall/restore at that point?

I saw in your other topic that you used scp to transfer the files, by default that doesn’t preserve modes. Did you use -p?

-p      Preserves modification times, access times, and modes from the original file.

I prefer to transfer via rsync. This creates an identical structure at the other end as long as the user has the rights to create the files. (So in this case use root)

1 Like
3

I have exact same warning from the daily mail sent from the box:

Subject: Cron <root@box> (cd /root/mailinabox && management/daily_tasks.sh)

WARN: uid is 0 but '/' is owned by 107

I have installed MIB a few days ago, on a new bare Linode with Ubuntu 14.04.

I have not done any chown. Also, user 107 is the Name Server Daemon (NSD).

It seems a bug related to the install.

4

I still have this issue for several months, and yet not resolve until now.

5

What kind of VPS do you have?

6

I’m using Linode VPS.

7

Can you try install on a different VPS provider?

8

@assistance_pls @samask I’m running on Linode, this is not a major issue because it’s just warning message. I’ve fixed this by doing this:

root@box# chown root.root /

I think this is caused by the way Linode image is built and restored on initial setup of the VM.

Regards,

1 Like