One other change you need to make. You OMNAME appears to still be Scalix. Please change that to be "mail" so it matches the first of OMHOSTNAME=mail.domain.com. Now, restart tomcat. BTW, you really need to get your DNS (both regular and reverse) for your Scalix server setup correctly so it resolves to this host. I know you're still in test mode, but the sooner you get this done, the better.
Thanks,
Rachel
Problems after IP Change
Moderators: ScalixSupport, admin
-
ScalixSupport
- Scalix
- Posts: 5503
- Joined: Thu Mar 25, 2004 8:15 pm
Last edited by ScalixSupport on Tue Jun 20, 2006 6:43 pm, edited 1 time in total.
-
ScalixSupport
- Scalix
- Posts: 5503
- Joined: Thu Mar 25, 2004 8:15 pm
-
mito
- Posts: 194
- Joined: Fri Mar 24, 2006 11:33 am
Code: Select all
[root@Scalix ~]# tail -n 50 /opt/scalix-tomcat/logs/caa.log
2006-06-19 15:41:50,089 DEBUG [NotificationEventListener$WorkerThread.registerRES:154] Named Instance mail.domain.com registered but is not using any secure mode, OK.
2006-06-19 15:41:55,098 INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: register|http://mail.domain.com/res/RESDispatcher|LISTEN|300|mail|mail.domain.com|10.0.1 from host:mail.domain.com
2006-06-19 15:41:55,099 DEBUG [NotificationEventListener$WorkerThread.registerRES:154] Named Instance mail.domain.com registered but is not using any secure mode, OK.
2006-06-19 15:42:00,174 INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://mail.domain.com/res/RESDispatcher|LISTEN|300|mail|mail.domain.com|10.0.1 from host:mail.domain.com
2006-06-19 15:42:46,211 DEBUG [RESMonitor.run:67] There are 1 remote servers registered
2006-06-19 15:42:46,240 INFO [RESMonitor.run:115] Server mail.domain.com up 51 secs
2006-06-19 15:43:00,274 INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://mail.domain.com/res/RESDispatcher|LISTEN|300|mail|mail.domain.com|10.0.1 from host:mail.domain.com
2006-06-19 15:43:09,369 DEBUG [SAAJServlet.doPost:93] ************ Request Start ***************
2006-06-19 15:43:09,370 DEBUG [SAAJServlet.doPost:95] Starting SAAJServlet with POST
2006-06-19 15:43:09,412 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header accept:*/*
2006-06-19 15:43:09,427 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header accept-language:en-us
2006-06-19 15:43:09,428 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header referer:http://mail.anotherdomain.net/sac/AdminApp.jsp
2006-06-19 15:43:09,429 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header content-type:text/xml
2006-06-19 15:43:09,430 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header accept-encoding:gzip, deflate
2006-06-19 15:43:09,431 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header user-agent:Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
2006-06-19 15:43:09,432 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header host:mail.anotherdomain.net
2006-06-19 15:43:09,433 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header content-length:434
2006-06-19 15:43:09,434 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header connection:Keep-Alive
2006-06-19 15:43:09,435 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header Cache-Control:no-cache
2006-06-19 15:43:09,671 DEBUG [SOAPDispatcherServlet.onMessage:158] **** Start of Message Handling ****
2006-06-19 15:43:46,242 DEBUG [RESMonitor.run:67] There are 1 remote servers registered
2006-06-19 15:43:46,243 INFO [RESMonitor.run:115] Server mail.domain.com up 1 mins, 51 secs
2006-06-19 15:44:00,193 INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://mail.domain.com/res/RESDispatcher|LISTEN|300|mail|mail.domain.com|10.0.1 from host:mail.domain.com
2006-06-19 15:44:46,250 DEBUG [RESMonitor.run:67] There are 1 remote servers registered
2006-06-19 15:44:46,251 INFO [RESMonitor.run:115] Server mail.domain.com up 2 mins, 51 secs
2006-06-19 15:45:00,201 INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://mail.domain.com/res/RESDispatcher|LISTEN|300|mail|mail.domain.com|10.0.1 from host:mail.domain.com
2006-06-19 15:45:46,258 DEBUG [RESMonitor.run:67] There are 1 remote servers registered
2006-06-19 15:45:46,259 INFO [RESMonitor.run:115] Server mail.domain.com up 3 mins, 51 secs
2006-06-19 15:46:00,208 INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://mail.domain.com/res/RESDispatcher|LISTEN|300|mail|mail.domain.com|10.0.1 from host:mail.domain.com
2006-06-19 15:46:00,681 DEBUG [SAAJServlet.doPost:93] ************ Request Start ***************
2006-06-19 15:46:00,682 DEBUG [SAAJServlet.doPost:95] Starting SAAJServlet with POST
2006-06-19 15:46:00,684 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header accept:*/*
2006-06-19 15:46:00,684 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header accept-language:en-us
2006-06-19 15:46:00,685 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header referer:http://mail.anotherdomain.net/sac/AdminApp.jsp
2006-06-19 15:46:00,686 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header content-type:text/xml
2006-06-19 15:46:00,687 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header accept-encoding:gzip, deflate
2006-06-19 15:46:00,688 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header user-agent:Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
2006-06-19 15:46:00,689 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header host:mail.anotherdomain.net
2006-06-19 15:46:00,690 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header content-length:434
2006-06-19 15:46:00,691 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header connection:Keep-Alive
2006-06-19 15:46:00,692 DEBUG [SAAJUtils.dumpHeaders:129] -----> Header Cache-Control:no-cache
2006-06-19 15:46:00,693 DEBUG [SOAPDispatcherServlet.onMessage:158] **** Start of Message Handling ****
2006-06-19 15:46:46,266 DEBUG [RESMonitor.run:67] There are 1 remote servers registered
2006-06-19 15:46:46,266 INFO [RESMonitor.run:115] Server mail.domain.com up 4 mins, 51 secs
2006-06-19 15:47:00,216 INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://mail.domain.com/res/RESDispatcher|LISTEN|300|mail|mail.domain.com|10.0.1 from host:mail.domain.com
2006-06-19 15:47:46,274 DEBUG [RESMonitor.run:67] There are 1 remote servers registered
2006-06-19 15:47:46,274 INFO [RESMonitor.run:115] Server mail.domain.com up 5 mins, 51 secs
2006-06-19 15:48:00,224 INFO [NotificationEventListener$WorkerThread.run:50] Event Notification: heartbeat|http://mail.domain.com/res/RESDispatcher|LISTEN|300|mail|mail.domain.com|10.0.1 from host:mail.domain.com
2006-06-19 15:48:46,281 DEBUG [RESMonitor.run:67] There are 1 remote servers registered
2006-06-19 15:48:46,282 INFO [RESMonitor.run:115] Server mail.domain.com up 6 mins, 51 secs
[root@Scalix ~]#
Last edited by mito on Tue Jun 20, 2006 10:31 pm, edited 1 time in total.
-
ScalixSupport
- Scalix
- Posts: 5503
- Joined: Thu Mar 25, 2004 8:15 pm
Are you actually attempting to login to SAC before posting the caa.log snippet? If so, how far are you getting and what error is being returned? What URL are you going to to start SAC? And lastly, what machine is "mail.domain.net"?
Thanks,
Rachel
Thanks,
Rachel
Last edited by ScalixSupport on Tue Jun 20, 2006 2:52 pm, edited 1 time in total.
-
mito
- Posts: 194
- Joined: Fri Mar 24, 2006 11:33 am
Yes I'm trying to login to the SAC, and then grab the caa.log file.
This box is mail.anotherdomain.net (that is a domain that I use for testing different website stuff, this being one of them). I had this server working well, but I wanted a way to actually send and receive real mail from the internet to test it out, so I added a 2nd domain to this scalix server (completely via SAC) and then setup my MX record and my mail. subdomain to point to this server, and it worked perfectly.
Then, after a week or two of problem-free testing, I moved it to this production network, changed the settings in the scalix box for the new IP, change the IP settings for my mail.anotherdomain.net domain, and waited for it to propagate. As soon as it propagated, I was hit in the face with these problems.
As far as how far do I get when I try to login:
When I try to login using Firefox: I get a login screen, type in my username/password, hit login, and then nothing happens, no errors, no nothing.
When I try to login using IE6: I get the login screen, type in my username/password, hit login, and then instantly get a popup error that says "Administration server is not responding. Possible lost connection or server problem"
Yes, i know that there are no dns records etc for anotherdomain.net in the hosts file etc, but as I said, it was working PERFECTLY on the testing-network... even without having those...
This box is mail.anotherdomain.net (that is a domain that I use for testing different website stuff, this being one of them). I had this server working well, but I wanted a way to actually send and receive real mail from the internet to test it out, so I added a 2nd domain to this scalix server (completely via SAC) and then setup my MX record and my mail. subdomain to point to this server, and it worked perfectly.
Then, after a week or two of problem-free testing, I moved it to this production network, changed the settings in the scalix box for the new IP, change the IP settings for my mail.anotherdomain.net domain, and waited for it to propagate. As soon as it propagated, I was hit in the face with these problems.
As far as how far do I get when I try to login:
When I try to login using Firefox: I get a login screen, type in my username/password, hit login, and then nothing happens, no errors, no nothing.
When I try to login using IE6: I get the login screen, type in my username/password, hit login, and then instantly get a popup error that says "Administration server is not responding. Possible lost connection or server problem"
Yes, i know that there are no dns records etc for anotherdomain.net in the hosts file etc, but as I said, it was working PERFECTLY on the testing-network... even without having those...
Last edited by mito on Tue Jun 20, 2006 10:33 pm, edited 1 time in total.
-
ScalixSupport
- Scalix
- Posts: 5503
- Joined: Thu Mar 25, 2004 8:15 pm
Okay, this is where I'm confused. We've been talking about machine.domain.local and mail.domain.com and now there's a third name for the server, mail.anotherdomain.net. Are you going to that URL (i.e. mail.domain.net/sac) to mail.domain.com/sac or ?? Your /etc/hosts on the Scalix server doesn't have that hostname, is it in DNS?
What I need to understand is what should the name of this host be? And, can that hostname be put into DNS so that it points to this server? The caa.log is showing that Apache seems to think it's mail.anotherdomain.net and tomcat thinks it's mail.domain.com so they're not really talking to each other.
Rather than trying to fix all of this after the fact, it may be easier to get the name straightened out in both your /etc/hosts file and DNS, then uninstall and reinstall. When you uninstall, make sure you tell the installer to leave the Scalix database on your server and when you reinstall tell the installer to use the existing database.
Thanks,
Rachel
What I need to understand is what should the name of this host be? And, can that hostname be put into DNS so that it points to this server? The caa.log is showing that Apache seems to think it's mail.anotherdomain.net and tomcat thinks it's mail.domain.com so they're not really talking to each other.
Rather than trying to fix all of this after the fact, it may be easier to get the name straightened out in both your /etc/hosts file and DNS, then uninstall and reinstall. When you uninstall, make sure you tell the installer to leave the Scalix database on your server and when you reinstall tell the installer to use the existing database.
Thanks,
Rachel
Last edited by ScalixSupport on Tue Jun 20, 2006 6:45 pm, edited 2 times in total.
-
mito
- Posts: 194
- Joined: Fri Mar 24, 2006 11:33 am
Ok, here's the story overall (I thought I just said it, but I'll be more precise this time).
I want to set this up for mail.domain.com on a perm basis. I installed the server as such, with the machines hostname actually being Scalix.domain.local (that's the machines hostname, not the FQDN). When I got it all setup and running, I realized that I had no way to test it before I moved over my entire email system to this (I wasn't comfortable just swapping over without it being fully tested). So, at this point, after the server has been installed, and tested internally opperational (I had been able to login to SWA and SAC, create accounts, and send emails internally etc. Even send emails from scalix to outside, but I had no way to test from the outside into scalix at this point).
This is where mail.anotherdomain.net comes in. As I said, it's a domain name that I have that I use for testing purposes. So, I transfered my MX record and my mail. subdomain to this server's old external IP address. I setup scalix via SAC to act as a mail server for this domain. At no time did the linux server's DNS know anything about mail.anotherdomain.net ( I never manually edited a file, not /etc/hosts, not any of those configs, anything). I was then able to access both the webmail and SAC through the mail.anotherdomain.net domain without problems. I tested it for a week or more, even setup some automated scripts that send me emails dailly to use that mailserver so that I could test it's reliability etc. It passed with flying colors, the only time I ever had a problem, I later found out that it was due to a power outage at my server location, and with it being in my test environment, I had neglected to plug it into a UPS (so therefore the problem wasn't anything related to Scalix etc).
So, then I decide that I am happy, and am ready to go into production mode. I physically move the server, and change it's IP address (DNS servers stayed the same, hostnames stayed the same, etc). Changed my mail.anotherdomain.net MX record and subdomain to point to the new external IP address, and as soon as it propagated, I was ready to rock and roll.. or so I thought. I was promptly greeted with this lovely series of errors that have led us here.
So, while I understand where you are coming from, wanting to make sure that all DNS etc knows about all these different domain names etc, I can promise you that it was working perfectly without knowing where they are, so why do they need to know now is my point.
And yes, I am thinking that I will just backup my system as it is right now, and then uninstall/reinstall, keeping the same database, and see how that goes.
But I would still like to know why this happened, and how to fix it in the future, as I do plan to do this more than just this one time!
I want to set this up for mail.domain.com on a perm basis. I installed the server as such, with the machines hostname actually being Scalix.domain.local (that's the machines hostname, not the FQDN). When I got it all setup and running, I realized that I had no way to test it before I moved over my entire email system to this (I wasn't comfortable just swapping over without it being fully tested). So, at this point, after the server has been installed, and tested internally opperational (I had been able to login to SWA and SAC, create accounts, and send emails internally etc. Even send emails from scalix to outside, but I had no way to test from the outside into scalix at this point).
This is where mail.anotherdomain.net comes in. As I said, it's a domain name that I have that I use for testing purposes. So, I transfered my MX record and my mail. subdomain to this server's old external IP address. I setup scalix via SAC to act as a mail server for this domain. At no time did the linux server's DNS know anything about mail.anotherdomain.net ( I never manually edited a file, not /etc/hosts, not any of those configs, anything). I was then able to access both the webmail and SAC through the mail.anotherdomain.net domain without problems. I tested it for a week or more, even setup some automated scripts that send me emails dailly to use that mailserver so that I could test it's reliability etc. It passed with flying colors, the only time I ever had a problem, I later found out that it was due to a power outage at my server location, and with it being in my test environment, I had neglected to plug it into a UPS (so therefore the problem wasn't anything related to Scalix etc).
So, then I decide that I am happy, and am ready to go into production mode. I physically move the server, and change it's IP address (DNS servers stayed the same, hostnames stayed the same, etc). Changed my mail.anotherdomain.net MX record and subdomain to point to the new external IP address, and as soon as it propagated, I was ready to rock and roll.. or so I thought. I was promptly greeted with this lovely series of errors that have led us here.
So, while I understand where you are coming from, wanting to make sure that all DNS etc knows about all these different domain names etc, I can promise you that it was working perfectly without knowing where they are, so why do they need to know now is my point.
And yes, I am thinking that I will just backup my system as it is right now, and then uninstall/reinstall, keeping the same database, and see how that goes.
But I would still like to know why this happened, and how to fix it in the future, as I do plan to do this more than just this one time!
Last edited by mito on Tue Jun 20, 2006 10:36 pm, edited 1 time in total.
-
mito
- Posts: 194
- Joined: Fri Mar 24, 2006 11:33 am
Ok, so now I'm in a bit of a different situation.
I uninstalled, making sure to keep the message store. I then reinstalled, making sure to tell it to use the existing message store. It gets through the installation of the main components, startst he services, asks me for my admin password, and then gives me an error saying "An error occured configuring Web Applications -- Check the log for errors. Click OK to exit Scalix Installer" and the box only has an OK button.
My question here is, where is this log that I need to check? I don't see any logs in the installation source directory...
I uninstalled, making sure to keep the message store. I then reinstalled, making sure to tell it to use the existing message store. It gets through the installation of the main components, startst he services, asks me for my admin password, and then gives me an error saying "An error occured configuring Web Applications -- Check the log for errors. Click OK to exit Scalix Installer" and the box only has an OK button.
My question here is, where is this log that I need to check? I don't see any logs in the installation source directory...
-
ScalixSupport
- Scalix
- Posts: 5503
- Joined: Thu Mar 25, 2004 8:15 pm
The logfile is generated in /var/log, e.g. when you start the installer:
galadriel:/home/ssiekmann # /mnt/iso/scalix-installer
Scalix Installer - extracting archive, please wait...
Scalix Installer - starting version 10.0.1.24...
Scalix Installer - using Python 2.4.1.
Scalix Installer - audit log file is /var/log/scalix-installer-20060620.log
Cheers,
Sascha.
galadriel:/home/ssiekmann # /mnt/iso/scalix-installer
Scalix Installer - extracting archive, please wait...
Scalix Installer - starting version 10.0.1.24...
Scalix Installer - using Python 2.4.1.
Scalix Installer - audit log file is /var/log/scalix-installer-20060620.log
Cheers,
Sascha.
-
mito
- Posts: 194
- Joined: Fri Mar 24, 2006 11:33 am
Ok, so what does this mean?
of course that ID would already be used, as it was already installed once... am I missing something? Did something not get uninstalled correctly?
[root@Scalix log]# tail -n 10 scalix-installer-20060620.log
2006-06-20 00:11:37,454 INFO Creating server Admin Groups on this host on mailnode mail,domain
2006-06-20 00:11:37,455 INFO Configuring / installing SAC
2006-06-20 00:11:38,225 INFO Configuring RES...
2006-06-20 00:11:38,536 INFO Mailnode is mail,domain
2006-06-20 00:11:38,537 INFO Server's existing mailnode is mail,domain
2006-06-20 00:11:38,585 INFO Configuring / installing RES
2006-06-20 00:11:39,035 ERROR Aborting...!
2006-06-20 00:11:39,036 CRITICAL Operation failed: Web apps config function configure_res failed: Failed to add "query admin" user sxqueryadmin@mail.domain.com. /opt/scalix/bin/omaddu reported the following error: omaddu : [OM 8265] Authentication ID sxqueryadmin@mail.domain.com already used..Please check that the domain domain.com is licensed.
2006-06-20 00:11:39,036 ERROR Operation failed: Aborting web apps configuration
2006-06-20 00:17:16,580 INFO Ending Scalix Installer - Msg: An error occurred configuring Web applications!
[root@Scalix log]#
of course that ID would already be used, as it was already installed once... am I missing something? Did something not get uninstalled correctly?
Last edited by mito on Tue Jun 20, 2006 10:37 pm, edited 1 time in total.
-
mito
- Posts: 194
- Joined: Fri Mar 24, 2006 11:33 am
Ok, now I have yet another problem...
I found this post in the forums:
http://www.scalix.com/community/viewtopic.php?t=2460
and ran this code as suggested:
And then uninstalled/reinstalled, and it worked!!!
I was then able to login to the SAC with one of my administration logins from before!
Now, my new problem though... none of the users or groups show up in the user and group lists. I tried to refresh them etc but it didn't help. I then tried to login to the webmail with one of the users, and that worked, and all of my old mail was there. But, this is for a user that doesn't apear in my SAC at all.
How do I refresh my SAC to show my existing users etc?
I found this post in the forums:
http://www.scalix.com/community/viewtopic.php?t=2460
and ran this code as suggested:
Code: Select all
# omstat -a
# omlicmon
# omdelent -e cn=sxqueryadmin
# omdelu sxqueryadmin@host.domain.com
And then uninstalled/reinstalled, and it worked!!!
I was then able to login to the SAC with one of my administration logins from before!
Now, my new problem though... none of the users or groups show up in the user and group lists. I tried to refresh them etc but it didn't help. I then tried to login to the webmail with one of the users, and that worked, and all of my old mail was there. But, this is for a user that doesn't apear in my SAC at all.
How do I refresh my SAC to show my existing users etc?
-
ScalixSupport
- Scalix
- Posts: 5503
- Joined: Thu Mar 25, 2004 8:15 pm
Do this:
omsearch -e cn=sxqueryadmin -m @all-attr@ -v
and look for the host-fqdn value. Now do a:
omsearch -e "cn=your name" -m @all-attr@ -v
and see what your host-fqdn value is. Now type:
sxmodfqdn -o YOUR-HOST-FQDN -n SXQUERYADMIN-HOST-FQDN
where YOUR-HOST-FQDN is the one listed in your omsearch output and SXQUERYADMIN-HOST-FQDN is the one listed in that omsearch. Once done, log back into SAC and you should see your entries again.
Thanks,
Rachel
omsearch -e cn=sxqueryadmin -m @all-attr@ -v
and look for the host-fqdn value. Now do a:
omsearch -e "cn=your name" -m @all-attr@ -v
and see what your host-fqdn value is. Now type:
sxmodfqdn -o YOUR-HOST-FQDN -n SXQUERYADMIN-HOST-FQDN
where YOUR-HOST-FQDN is the one listed in your omsearch output and SXQUERYADMIN-HOST-FQDN is the one listed in that omsearch. Once done, log back into SAC and you should see your entries again.
Thanks,
Rachel
Who is online
Users browsing this forum: No registered users and 4 guests