Koozali.org: home of the SME Server
Legacy Forums => Experienced User Forum => Topic started by: fitzrik on November 20, 2005, 01:39:54 AM
-
My sme-server is set to yum update which it seems to do every morning. (It had been upgraded previously to beta 6 by cd)
Today I noticed I couldn't login to email usin the web interface on either of to accounts. One being admin. I can access fine using imap.
Only details I have are this email
/etc/cron.daily/yum.cron:
warning: /home/httpd/html/horde/config/mime_drivers.php saved as /home/httpd/html/horde/config/mime_drivers.php.rpmsave
warning: /home/httpd/html/horde/config/prefs.php saved as /home/httpd/html/horde/config/prefs.php.rpmsave
warning: /home/httpd/html/horde/config/registry.php saved as /home/httpd/html/horde/config/registry.php.rpmsave
warning: /home/httpd/html/horde/turba/config/sources.php saved as /home/httpd/html/horde/turba/config/sources.php.rpmsave
warning: /home/httpd/html/horde/imp/config/prefs.php saved as /home/httpd/html/horde/imp/config/prefs.php.rpmsave
warning: /home/httpd/html/horde/imp/config/servers.php saved as /home/httpd/html/horde/imp/config/servers.php.rpmsave
warning: /home/httpd/html/horde/ingo/config/backends.php saved as /home/httpd/html/horde/ingo/config/backends.php.rpmsave
Incidentally I tried logging on to sourceforge to log this but couldn't get to the project after I logged in.
Richard
-
Please try again to submit a bug report.
http://sourceforge.net/account/login.php?return_to=/tracker?func=add&group_id=96750&atid=615772
-
I too have the same problem with webmail after the latest yum-update. I also cannot access the server-manager page from my web browser. Everything else seems to work OK.
I have submitted a bug-report, as I could not find one already there.
Mudra
-
Hello,
I had the same problem after yum updated horde. I restarted the server and all was good again? I suspected there were files in use or needed to be replaced.
Stephan.
-
I had the same problem after yum updated horde. I restarted the server and all was good again? I suspected there were files in use or needed to be replaced.
Some templates needed to be expanded after the package updates.
Go to the Shutdown and Reboot panel and choose "Reconfigure". This is a new option which performs a "post-upgrade/reboot".
If you do the yum update from the command line, follow it with "signal-event post-upgrade" and then "signal-event reboot"
We are working on making this smoother, but for now, please ensure that you do one of these options if you have issues after updates. In most cases it's overkill, but it will ensure everything is expanded and restarted.