Question

Ubuntu 12.04 x64 Server - wrong ownership on /var/log/syslog?

Posted June 13, 2013 9.2k views
on a fresh Ubuntu 12.04 x64 Server droplet /var/log/syslog is empty and no entries are added. file ownership is root.root, after changing this to syslog.adm everything works fine. messages is also owned by root.root. is this a bug? (and is this the correct place for feedback)? also there is a file called "mail.*" (including the asterisk) in /var/log which seems wrong.
Add a comment
gruber
By:
gruber
Add a comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
10 answers
gabrielhpugliese June 22, 2013
This is happening for me too. For all my droplets :(
Reply Report
johan August 5, 2013
This happend to me to, is it Ubuntu or DO that causes the problem?
Reply Report
kamaln7 August 6, 2013
Are you still experiencing this? If so, can you please open up a ticker so we can take a look?
Reply Report
saturlight August 19, 2013
Yes, still a problem.
Droplet was created 8th of August 2013. Ubuntu 12.04.
Reply Report
kamaln7 August 21, 2013
@saturlight: Can you please open up a support ticket? Thanks!
Reply Report
mitayai August 24, 2013
In creating a brand-new Ubuntu 12.04 x64 droplet, my permissions look all fine:

https://www.dropbox.com/s/4isejd8h13tr0j4/log2013082401.txt

-Will
Reply Report
doug.muth October 12, 2013

I created an Ubuntu 12.04 64-bit Droplet the other day (9 Oct 2013) and ran into this problem. 2 days of logs that I needed to consult... never written to disk. WTF?

I had to add the following to my Puppet manifest just to make logging work:

file {"/var/log/messages":
owner => syslog,
group => adm,
mode => 0644,
}

file {"/var/log/debug":
owner => syslog,
group => adm,
mode => 0644,
}

file {"/var/log/syslog":
owner => syslog,
group => adm,
mode => 0644,
}
Reply Report
kamaln7 October 16, 2013
@Douglas: Can you please open up a support ticket?
Reply Report
do160106 December 3, 2013
What was the outcome of this?

I've just gone to check the logs on my droplet for something, and they're empty and haven't been written to since June. The permissions are broken as per the above also.
Reply Report
kamaln7 December 3, 2013
@do: It was resolved. If a new droplet has this issue, please open up a support ticket.
Reply Report
Submit an Answer

Looking for something else?

Ask a new question Search for more help