SAC The Administration server is not responding

[RnsVI]

Ok, first off let me say I HATE creating new topics, especially for something I have seen multiple other places HOWEVER, most of the other threads I found have all dead ended quite a while ago and deal with older versions of Scalix so I thought I would fire up a new thread with current info and see how it goes. That said:

The background:
Moved from 11.2 to the most recent version of 11.4
Moved from a Fedora Core server to CentOS 5

The Move (simplified)
Installed 11.4 on Cent
Moved Data
re-installed 11.4

The Problem
As the title suggests whenever we go into SAC it says "The Administration Server is not responding"

Now here is what I have done:
-Verified that SXQueryAdmin user's password is in the proper location and matches the the user password. I have done the manual query test with this user and it works.

-Created a new SXAdmin user with the proper permissions and tested its ability to do a command line login, works great.

-Set tomcat logging to DEBUG and checked the log in scalix-caa.log and it has nothing in it except the indication of a successful tomcat start.

-Did the omcheck routine and fixed several file permissions errors. I still get a bunch of files listed in the middle of the check that appear to be warnings but they do not indicate any permissions problems.
Example:

Code: Select all

#Now checking component OM-WEBADM
# Filename: /opt/scalix/access/omsession.cgi ( OpenMail OM-WEBADM )
echo /opt/scalix/access/omsession.cgi: /opt/scalix/access/omsession.cgi: Success


-Made sure tomcat setupd had port 80 as default

-Un-installed and re-installed the management services from the graphical install

-Did an omshowlog -e and I did find one section that peaked my interest and sealed the deal on me putting together this post:

Code: Select all

SERIOUS ERROR                  Administration(Scalix Admin C) 09.02.08 10:45:13
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xb3)[0x97cb33]
/opt/scalix/lib/libom_er.so[0x97ce23]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x97cfaf]
[0xa3b420]
/lib/libc.so.6[0x13eeb8]
/lib/libc.so.6[0x13ee48]
/lib/libc.so.6[0x13ee48]
/lib/libc.so.6[0x13ee48]
/lib/libc.so.6[0x13ee48]
/lib/libc.so.6[0x13ee48]
/lib/libc.so.6[0x13ee48]
/lib/libc.so.6[0x13ee48]
/lib/libc.so.6[0x13ee48]
/lib/libc.so.6[0x13ee48]
/lib/libc.so.6[0x13ee48]
/lib/libc.so.6[0x13ee48]
/lib/libc.so.6(qsort+0x85)[0x13f035]
/opt/scalix/bin/sxmkindex[0x804956c]
/opt/scalix/bin/sxmkindex[0x804a37e]
/opt/scalix/bin/sxmkindex[0x804aa87]
/lib/libc.so.6(__libc_start_main+0xdc)[0x129dec]
/opt/scalix/bin/sxmkindex[0x8049401]


I searched for various lines in that code but found nothing.

If anyone has any other ideas for me I would LOVE to hear them. I am not so much desperate to get into the SAC as I am to just get this resolved in case something does make me desperate to get into the SAC!

Thanks in advance for any help and hopefully this will help somebody else out there pulling their hair out over this!

-Richard

[schmoe90]

Check that sxadmin and sxqueryadmin aren't locked... seen that too many times

[RnsVI]

As I mentioned I did test logins with both accounts and both times was able to successfully complete the login from the command line.

I did an omshowu for sxqueryadmin and sxadmin and both kicked back
Mail Account: Unlocked
I assume this is the attribute I should be looking for? Please let me know if there is something else.

I did a quick search and ran across a post dealing with sxqueryamdin being locked so I did:

1. I changed the sxqueryadmin password to the same as in psdata.
ommodu -o sxqueryadmin -p <mypasswd>

2. I unlocked the sxqueryadmin and configured his password to never expire
ommodu -o sxqueryadmin -E -k

No Change
Still not able to login.

[schmoe90]

Does anything get logged in the tomcat logs when you fail to log in?

[RnsVI]

Nope, no such luck. It is as though we are never making it to the point where tomcat is actually getting info. Its like there is a disconnect between the login page and the underlying services.

Doing another hunt of omshowlog (using omshowlog -s administration) found the following a couple of times:

Code: Select all

ERROR                          Administration(Scalix Admin C) 09.02.08 17:19:38
[SYS 2] No such file or directory
Current errno value: 2
        <- /build/11.4.1/src/lib/ombase/os/os_stat.c:58[1,2]


Not sure if that means anything but it could.
Thanks for the help so for schmoe90.. any other thoughts?

[schmoe90]

Try upping the logging (omconflvl) and seeing what it's missing... SYS 2 means there's a file that it's needing that's not there. Often this is a REPORT, like for mimeout.str and suchlike, but it obviously cares about whatever file it's not seeing here.

omcheck? Reinstall the SAC stuff?

[RnsVI]

Thanks again for your time schmoe90

On the omconflvl command, I am not overly familiar with it, would you by chance have a suggestion for what parameters I should use?

In looking more carefully at the output of omcheck I think I see the problem.
It kicks back 2 sections that look bad
First is:

Code: Select all

#---------------------------------------------------------
#Now checking component OM-EVAL
# Filename: /opt/scalix/lib/libom_lml.so ( OpenMail OM-EVAL )
echo /opt/scalix/lib/libom_lml.so: /opt/scalix/lib/libom_lml.so: Success
#---------------------------------------------------------


This does not really alarm me a whole lot, ran omcheck on my old server and got this as well but please correct me if this is a problem.

Second area (and I think this is where the problem is)

Code: Select all

#---------------------------------------------------------
#Now checking component OM-WEBADM
# Filename: /opt/scalix/access/omsession.cgi ( OpenMail OM-WEBADM )
echo /opt/scalix/access/omsession.cgi: /opt/scalix/access/omsession.cgi: Success
# Filename: /opt/scalix/access/omTclXML.tcl ( OpenMail OM-WEBADM )
echo /opt/scalix/access/omTclXML.tcl: /opt/scalix/access/omTclXML.tcl: Success
# Filename: /opt/scalix/access/omformat.tcl ( OpenMail OM-WEBADM )
echo /opt/scalix/access/omformat.tcl: /opt/scalix/access/omformat.tcl: Success
# Filename: /opt/scalix/access/omLogging.tcl ( OpenMail OM-WEBADM )
echo /opt/scalix/access/omLogging.tcl: /opt/scalix/access/omLogging.tcl: Success
# Filename: /opt/scalix/access/dom.tcl ( OpenMail OM-WEBADM )
echo /opt/scalix/access/dom.tcl: /opt/scalix/access/dom.tcl: Success
# Filename: /opt/scalix/access/xml.tcl ( OpenMail OM-WEBADM )
echo /opt/scalix/access/xml.tcl: /opt/scalix/access/xml.tcl: Success
# Filename: /opt/scalix/access/unixdom.so ( OpenMail OM-WEBADM )
echo /opt/scalix/access/unixdom.so: /opt/scalix/access/unixdom.so: Success
# Filename: /opt/scalix/access/omparse.tcl ( OpenMail OM-WEBADM )
echo /opt/scalix/access/omparse.tcl: /opt/scalix/access/omparse.tcl: Success
# Filename: /opt/scalix/access/README ( OpenMail OM-WEBADM )
echo /opt/scalix/access/README: /opt/scalix/access/README: Success
# Filename: /opt/scalix/access/omsession.user ( OpenMail OM-WEBADM )
echo /opt/scalix/access/omsession.user: /opt/scalix/access/omsession.user: Success
# Filename: /opt/scalix/access/pkgIndex.tcl ( OpenMail OM-WEBADM )
echo /opt/scalix/access/pkgIndex.tcl: /opt/scalix/access/pkgIndex.tcl: Success
# Filename: /opt/scalix/access/sgml.tcl ( OpenMail OM-WEBADM )
echo /opt/scalix/access/sgml.tcl: /opt/scalix/access/sgml.tcl: Success
# Filename: /opt/scalix/template/access/apps/admin/conf.presignon ( OpenMail OM-WEBADM )
echo /opt/scalix/template/access/apps/admin/conf.presignon: /opt/scalix/template/access/apps/admin/conf.presignon: Success
# Filename: /opt/scalix/template/access/apps/admin/do_dSearch.page ( OpenMail OM-WEBADM )
echo /opt/scalix/template/access/apps/admin/do_dSearch.page: /opt/scalix/template/access/apps/admin/do_dSearch.page: Success
# Filename: /opt/scalix/template/access/apps/admin/do_viewUser.page ( OpenMail OM-WEBADM )
echo /opt/scalix/template/access/apps/admin/do_viewUser.page: /opt/scalix/template/access/apps/admin/do_viewUser.page: Success
# Filename: /opt/scalix/template/access/apps/admin/delMailNode.action ( OpenMail OM-WEBADM )


There are lots more lines to that but I did not see the need to post a million lines that all referenced files in the same basic set of directories,

I tried navigating to these folders and they do not appear to exist. I am thinking if omcheck is looking for files there it could mean something is very wrong.

I tried pulling the scalix management agent and management services out and re-installing. It did not solve the problem but it had an interesting side effect. The lines I showed above starting saying "no such file or directory" instead of "Success" at the end. I created the repair script with the omcheck command and ran it, after that it went back tot he same thing I posted above.

So I guess my big question is:
Is there supposed to be a /opt/scalix/access/ and a /opt/scalix/template/access/ diectory or is something pointing at things incorrectly? If these directories are supposed to be there then how would I go about getting them back?

I see a light at the end of the tunnel, just not sure if it is a train.....

[schmoe90]

Code: Select all

omconflvl admin 21


Expect a lot more junk when you use omshowlog <blah> -l 21

The omcheck script output looks fine as long as it's saying Success...

[RnsVI]

So this one is solved.. it was a train at the end of the tunnel but I think I managed to make the best of it. Anyway....

After upping the reporting level and finding little if anything useful I decided to do something crazy and see how it went. I took a snapshot of my server (We run our Cent install with scalix on an ESXi server) and I ripped everything out of the system expect the message stores. This includes all the caches and all the packages.

After the un-install I did a re-boot then I re-installed all the packages and did another re-boot. After a omrc successfully started everything up I was able to get into SAC with the sxadmin user on the first try.

Not sure what was broken where but something deep was broken and only a re-install seemed to be capable of solving things.

Hope something somewhere in this thread helps someone..
Thanks for the help schmoe90 and thanks for a great product Scalix team!

[Axel]

I run into the same trouble. Login to SAC was impossible: "Administrationserver not responding ..."

The reason was a wrong "ubermanager.notification.listener.address"- entry in "/var/opt/scalix/NN/caa/scalix.res/config/ubermanager.properties".

[rpl]

Thanks for this hint.
We changed the IP of our Scalix server last weekend, following the Wiki.
In this instructions they forgot this topic.
The procedure has to be completed with the change of the IP address (why IP is hard coded, not used a hostname or FQDN ?) in this file.