ISPConfig monitor System Log

Thought I'll open this thread, because I think there is a wrong config variable or? for the syslog log.

On an Ubuntu system 12.04 Server LTS the "system" log is not called "messages" instead they use "syslog"

I might be wrong however once I retrieve the system log file, an error is thrown.

Dunno if this is fixed pointer or if it can be configured to point to /var/log/syslog ?

Just thought I post my thoughts.

Cheers,
Norbert

 

I've added this to our bugtracker, so we will check that.

 

If you have a server like I have and it doesn't work you can make a link and it will work just fine

sudo ln -s /var/log/syslsog /var/log/messages

sudo chown syslog:adm /var/log/messages

This is fix the monitor in Ispconfig3 using ubuntu 12.04LTS and Ver 3.0.4.6

 

Sym Link works

Hi mmidgett,
the work around works fine for my setup.
Could have been my idea , but it wasn't!!!

Thanks,
Norbert

 

I just noticed that syslog must have rotated the log cause the link Is now broken. I wouldnt do my recomendation unless you scripy the deleting of the old links and create new ones. I think It would be better to look through the code and find where it calls it and change it. I will look for It today and post my findings.

 

Not a big deal!

Hi mmidgett,
it's really not a big deal, I can always SSH and read the Syslog directly.

Just had a look at the Monitor within the ISPConfig panel and it still looks alright.
I don't know how often Logrotate does create new logfiles?
Perhaps my system didn't get to that point yet or logrotate isn't involved as much?

On the other hand it seems to be weird that logrotate would break the link.
How does logrotate create new logs, hmmm. Think it stops logging, then renames the old logfiles, if older tar balls them, then creates a new logfile with the name given in /usr/local/ispconfig/server ( sorry just looked at it, this is varable (PHP) so it sits deeper).
I got lost!!! Just finding the relevant part of it is a challenge.

Cheers, and TNX,
Norbert

 

Sorry

I am not rewriting what I just lost.

The board logs you out and on login, destroys whatever you were putting together.

No big deal, on the syslog, I always can check via SSH.

Cheers,
Norbert