Koozali.org: home of the SME Server
Obsolete Releases => SME Server 9.x => Topic started by: smiit on May 30, 2016, 09:09:51 PM
-
We held off running yum update for several weeks until the Samba issue got resolved. Posters appeared to be confirming resolution in recent days so yum update.
After signal-event post-upgrade and reboot the web server-manager still gives the "Warning: a reconfigure and reboot is required .." message.
Default Server Manager landing for View log files arrives at ConsoleKit/history instead of /var/log/messages/current
Did some Alpha 10 packages get pushed through by mistake?
Should I file a bug?
-
Default Server Manager landing for View log files arrives at ConsoleKit/history instead of /var/log/messages/current
/var/log/messages is a file, not a directory, and therefore there is (and can be) no /var/log/messages/current. But with that said, my system has all the new updates installed, and though ConsoleKit/history appears in the list (and at the top of the list), the drop-down still defaults to messages (on Firefox 46/Ubuntu 16.04).
I don't think any SME10 packages got pushed through, but if your system is behaving in an unexpected way, filing a bug is usually a good idea.
-
Thank you for correcting my sloppy way of referring to the messages log.
My system appears to have righted itself -- I believe the behavior it was exhibiting is due to running a very aggressive Fail2Ban jail to fight spam and it writes to the syslog so frequently it likely took a while to catch up after reboot.