Scalix Forums

Ok Long story short: I have my old scalix server, and my new future scalix server. I have latest version of scalix on new machine, I transfered mail stores and ran the checks and scans etc. The only thing that is currently not working is users being able to log into the SWA. When I log into SAC I can see all the users there. I even created a test user, who was also not able to log into the SWA.

In the httpd error_log I receive messages like this: "proxy: AJP: failed to make connection to backend"

and

"proxy: AJP: disabled connection for (hostname)"

I have reinstalled various components more times than I care to, so that does not seem to be the quick simple fix. Does anyone else have any suggestions?

Thanks,
Derek

dpinkston wrote:Ok Long story short: I have my old scalix server, and my new future scalix server. I have latest version of scalix on new machine, I transfered mail stores and ran the checks and scans etc. The only thing that is currently not working is users being able to log into the SWA. When I log into SAC I can see all the users there. I even created a test user, who was also not able to log into the SWA.

In the httpd error_log I receive messages like this: "proxy: AJP: failed to make connection to backend"

and

"proxy: AJP: disabled connection for (hostname)"

I have reinstalled various components more times than I care to, so that does not seem to be the quick simple fix. Does anyone else have any suggestions?

Thanks,
Derek

looks like you have tomcat configuration issues. Check out the virtual host configs in /etc/opt/scalix-tomcat/connector/ajp/instance-<hostname>.conf and /etc/opt/scalix-tomcat/connector/jk/instance-<hostname>.conf

in the latest version tomcat needs to have port 8080 available so make sure apache is not listening on that.

Do the scalix versions match? If they dont this is probably why tomcat is not working after sync. Its always better to install the same version on the new machine, sync and get it working, then upgrade.

les wrote:If they dont this is probably why tomcat is not working after sync. Its always better to install the same version on the new machine, sync and get it working, then upgrade.

Kinda hard to do, when version changes prevent upgrading. For instance, I can not install my old version on the new machine because the old version does not support the OS. Even if the old version did support the OS, I can't get my hands on a copy of the old version. So I am unable to do this "upgrade" that everyone is speaking of.

Now, after uninstalling and deleting all scalix components on the test box I reinstalled everything re transferred the mail stores, ran the checks, patches, scans, etc. Now the exact opposite is true. I can get logged into the webmail flawlessly, but I can not log into sac...

Kinda hard to do, when version changes prevent upgrading. For instance, I can not install my old version on the new machine because the old version does not support the OS. Even if the old version did support the OS, I can't get my hands on a copy of the old version. So I am unable to do this "upgrade" that everyone is speaking of.

depends on what version you were running on what os. There are ways to get the old versions and ways to install on different platforms. So what os and version are you migrating from?

dpinkston wrote:Now, after uninstalling and deleting all scalix components on the test box I reinstalled everything re transferred the mail stores, ran the checks, patches, scans, etc. Now the exact opposite is true. I can get logged into the webmail flawlessly, but I can not log into sac...

Well, that should be easier to fix, but.....we need more info than that. What error messages do you get when you try to login? what account name are you using to login to sac?

Well, that should be easier to fix, but.....we need more info than that. What error messages do you get when you try to login? what account name are you using to login to sac?

I am using my personal account that was setup as admin on the existing server. I have also tried logging in as the admin that was created on the new machine. The error I get is The invalid username and password error that appears below the logon box. The same username and password does work logging into swa. I also did a omshowu with the -a flag and it does show that user as an administrator.

Thanks in Advance!
Derek

dpinkston wrote:

Well, that should be easier to fix, but.....we need more info than that. What error messages do you get when you try to login? what account name are you using to login to sac?

I am using my personal account that was setup as admin on the existing server. I have also tried logging in as the admin that was created on the new machine. The error I get is The invalid username and password error that appears below the logon box. The same username and password does work logging into swa. I also did a omshowu with the -a flag and it does show that user as an administrator.

Thanks in Advance!
Derek

can you use command line to login?

omlogon -h localhost -u sxadmin -p <password>

type in omlogoff afterwards to logout.

are you sure that you dont need to specify the login name as sxadmin@mail.yourdomain.com?

What OS are you on?

are you sure that sac is correctly configured for the different ip/ hostname for the test system? i.e. do a reconfigure from the scalix installer.

Man this is getting frustrating, I seem to be taking one step forward and two steps back. I decided to reload the OS, Scalix, and start from scratch. I install scalix, transfer the store, do the omchecks and om patches, and try to start scalix. now EVERYTIME i get omon permission denied. The file it's self has the right permissions. I only get this message after I transfer the mailstore and check and patch everything. Before that all the scalix service start right up with no problem.

I think I should stop all this trial and error and just go with what works. However I don't know what "just works". I can't get my hands on the install file with the same version I am running on the other server. So, with that being said, what can I do to get this to work right?

Thanks,
Derek

Ok, well I found the older versions. So I am going to start completely from scratch again. Going to install the matching version of scalix on the Centos 5.2 machine. Transfer the mailstore, omcheck everything and hope all goes well with that. Then I will upgrade to the newest version and hope for the best. To me it just sounds like too many point of failure possibilities, bit I will post back with the results.

Still ran into the same problems starting from scratch. However I did get past them. It seems like 99% of my problems have been permission errors. omcheck with the different flags took care of some of the permission problems but not all of them. So I manually adjusted the other permissions. I know the permissions probably wouldn't have been a problem if I would have tar's the mailstore while preserving permissions, but for some reason the tar'd mailstore would error out when transferring to the external HD I was using, when I transferred the mailstores them selves it did not error out, but did lose the permissions.

So Currently my temporary scalix hardware is in place running scalix on VMware. I must say the performance is terrible, and it seems like it's hard drive performance and not the ram, cpu, etc. Whenever there is hard drive activity everything runs very slow on the machine. Hopefully when I get the permanent hardware loaded up and ready for the VM image it will handle it better and wont go to a crawl when there is HD activity.

dpinkston wrote:Still ran into the same problems starting from scratch. However I did get past them. It seems like 99% of my problems have been permission errors. omcheck with the different flags took care of some of the permission problems but not all of them. So I manually adjusted the other permissions. I know the permissions probably wouldn't have been a problem if I would have tar's the mailstore while preserving permissions, but for some reason the tar'd mailstore would error out when transferring to the external HD I was using, when I transferred the mailstores them selves it did not error out, but did lose the permissions.

How did you transfer the mailstore to have such problems with permissions? The normal way is to rsync -avz which will preserve permissions. The only problem you have sometimes is that on the old box the scalix uid and gid could be different to the new one. In my experience however, omcheck has always resolved any permissions issues.

You don't want to know . I tried SCP, several times and it kept erroring out (I don't remember the exact error) So I figured that transfering over the wire wasn't going to work to well. So I copied to an external drive.

dpinkston wrote:You don't want to know . I tried SCP, several times and it kept erroring out (I don't remember the exact error) So I figured that transfering over the wire wasn't going to work to well. So I copied to an external drive.

scp or cp are no good. rsync is the only option to preserve permissions.

I did one the other day, old box centos 4.6, scalix 11.4.0, new box centos 5.3 scalix 11.4.0 with an upgrade to 11.4.3 and everything went fine. 35 gigabyte mailstore.

A rough run down of what i did....

1. move old server to new ip on lan. shutdown all scalix related services.
2. setup new server on original ip. Install virgin scalix 11.4.0. stop scalix and all related services.
3. mkdir /var/opt/scalix.11.4.0.virgin
4. mv /var/opt/scalix/* /var/opt/scalix.11.4.0.virgin/.
5. cd /var/opt/scalix
6. rsync -avz root@oldserver:/var/opt/scalix/* . (rsync ran over ssh)
7. wait 2-3 hours
8. mv postgres to postgres.old (postgres changed from v7 to v8 in centos 5, so the old postgres wont work. It's just indexes so they will be re-created)
9. rsync -av /var/opt/scalix.11.4.0.virgin/??/postgres /var/opt/scalix/??/.
10. ompatchom
11. omcheck -s -d > /tmp/check_file
review the file and then type:
sh /tmp/check_file
12. start all scalix related services and test login to webmail and sac on 11.4.0 - all worked.
Note: scalix uid and gid did end up being different between the two servers, but it didn't cause any issues. omcheck fixed a few things. the new server had the same ip and hostname as the old when i installed scalix.
13. stop scalix again.
14. run a standard upgrade to 11.4.3 on the new server. tested all - worked ok.

That process should work everytime. Hope this helps you out for next time.