Scalix Forums

I just spent more time than I care to admit working on an upgrade from 11.0 to 11.4

Everything worked fine before the upgrade; after the upgrade /webmail and /sac gave Apache errors "page not found".

/Scalix/rw worked fine.

Problem was that once upon a time someone had removed the symlink /etc/httpd/conf.d/scalix-web-client.conf -> /opt/scalix/global/httpd/scalix-web-client.conf

They copied scalix-web-client.conf from /opt/scalix/global/httpd to /etc/httpd/conf.d so the file was there but it was a regular file, not a symlink. Thus, the installer upgraded the file but the apache configuration in conf.d never recognized the changes, as it was running off of the old copied file.

Hope this saves someone else some headaches. If all the config stuff looks good, start checking your symlinks. Better yet, don't break them in the first place

Hi,

IMNSHO this is more than worth filing a bug for. If a soft link should be present in /etc/httpd/conf.d, then the installer MUST check that this is indeed the case and create it. If something else than a soft link is present: rename it and create the link.

The first time I had an issue with the upgrade breaking the Apache config (because the installer never did it right) I just manually added everything into the httpd.conf (yes I went through all the /etc/apache2/ stuff and make one big unified httpd.conf file... I like it that way)

nvehommes wrote:IMNSHO this is more than worth filing a bug for.

Bug 17621 has been opened.
I pretty much stole your description, word for word.