Cant log into SAC

[rex007can]

First, I downloaded glibc-2.3.2-95.44.i686.rpm, but that's the package I already had installed, and is the latest available for RHEL3. Apparently, RHEL3 doesn't support ntpl. Hell doing a search for all packages with NTPL at RedHat returns nothing.

So I cheated and downloaded glibc-2.3.4-2.25.i686.rpm for RHEL4.
It needed a few other packages updated with it, but didn't give me any errors while installing.

I know, I know, technically shouldn't install packages from 2 versions like that, but it's all I could come up with short of uninstalling it and reinstalling it from source with all the work that this would entail. I'm planning to update the OS to RHEL4 in a few weeks anyhow (To also update to Scalix 11.0.2.1), so I will deal with other problems it may bring (if any) until then.

[LHD-Tech]

Should I be disappointed in the support I'm getting now?
My Admin console's been down for over a week. I was expecting more...

Should I be disappointed that you jacked my thread and got help before i did?

Well, my SAC still doesnt work...

I ran:

Code: Select all

getconf GNU_LIBPTHREAD_VERSION

And got:

Code: Select all

NPTL 2.3.4

... <sigh> ....

now when i try to log into SAC i get the error of:

Could Not Login
Check the Login ID and password.
You might have forgotten to include the domain name as part of your Login ID
(e.g. 'yourID@yourDomain.com')

And I know I have the user name and password correct because I just changed it.

[mito]

I too have been getting the exact same problem. I've just now noticed this thread however, and have been posting my problems and reports in this thread.

I am running RHEL4 (actually CentOS 4.4) and have the correct responses to the commands listed in this thread.

Note, I was having this problem BEFORE updating the tzdata package (updated the package late...). As noted in the other thread, I never had this problem while using my old server (FC4) but it appeared after migrating to the CentOS4.4 server.

Code: Select all

# rpm -qa|grep glibc
glibc-2.3.4-2.25
glibc-common-2.3.4-2.25
glibc-kernheaders-2.4-9.1.98.EL
glibc-devel-2.3.4-2.25
glibc-headers-2.3.4-2.25

# getconf GNU_LIBPTHREAD_VERSION
NPTL 2.3.4

Note: I'm not trying to jack this thread, just trying to help add clues to the puzzle to help us all get fixed.

Mito

[LHD-Tech]

Note: I'm not trying to jack this thread, just trying to help add clues to the puzzle to help us all get fixed.
Mito

hehe. I was more upset that he was giving the support guys a hard time about getting FREE help. I just want to get my problem fixed...

[rex007can]

hehe. I was more upset that he was giving the support guys a hard time about getting FREE help.

Look. I bough my licenses for corporate 9.2. I bought the licensing again to go to 10.0. I also intend to stay licensed to go to 11.0.2. It's not like I'm a freeloader here.
I've always run it on a supported OS. I update 2 packages and a major part of the system stops working. And there's nothing on their website about it anywhere except a possibility here. I have to wait over a week to get one guy to give me a command to run, one simple check, to get it fixed.

You bet I get frustrated, because when I spend nearly 10K$ on software, I expect it to work...and keep working. And if it breaks through absolutely no fault of my own, I also expect the provider of that software to do something about it. And if I have to highjack a thread and complain to get it done...so be it.

I've payed for support when I needed something done that I couldn't figure out properly from instructions myself. But if it breaks, I at LEAST expect instructions.

Sorry if that "upset" you.

[mito]

Just as a reference, I (finally) successfully upgraded to 11.0.2.1 today. Only 7 hours after the upgrade was finished however, I am again struck with this same error.

Has anyone found where this problem is being registered in the logs? I haven't even found a log showing a problem yet.

Again, SAC is giving a problem, SWA works perfectly.

[mito]

[support@scalix support]$ getconf GNU_LIBPTHREAD_VERSION
linuxthreads-0.10

This is the cause of the problem. That command should report NPTL.

Sorry if this has been asked before, what OS and kernel version are you running ?

Cheers

Dave

Dave,

Any help / hope for those of us that replied that we do get the proper NPTL response? I'm getting in trouble for not being able to solve this problem yet... I was hoping it would be fixed in my upgrade from 10.0.5 to 11.0.2.1 but I am still getting the errors. Note that webmail works forever, but SAC gives the error:

Code: Select all

Could Not Login
Could not fetch configuration information.
Possible problem with administration server

Thanks for any help and advice you can give us!

Mito

[patrick88296]

Hi all

I have here the same Problem on a Ubuntu Server 6.06 LTS running SCALIX 11,0.2.23

Installation done using the Wiki Manual installation, Everything worked like in descrition,

My getconf GNU_LIPTHREAD_VERSION

NTPL 2.3.6

Webmail works fine but logon to sac says:
"Anmeldung konnte nicht durchgeführt werden Überprüfen Sie Benutzername und Kennwort. Ihre Email-Domäne....."

Any sugestions. Better use ist with CentOS?

Thank you for this great Software!

Patrick

[mito]

Any sugestions. Better use ist with CentOS?

This is off topic, but I have had, other than this problem in this thread, no problems with running Scalix on CentOS. I have also documented my process of getting it up and running, even the process of migration from an existing server, onto CentOS on my website if you want to give it a try.

[dkelly]

The first thing to check is that you've got the correct password configured for the sxqueryadmin user. This is what SAC uses in te background to talk to each Scalix server. You will have been prompted for this during an upgrade.

The file is /var/opt/scalix/NN/caa/scalix.res/config/psdata where NN is the first and last characters of your hostname.

Using that password, run the command:

Code: Select all

ldapsearch -xh your.host.name -D "cn=sxqueryadmin" -w password

If you get something back, the password is correct and we need to look elsewhere.
If you get an error, the password is incorrect and you need to change it. Either set the correctf password in the psdata file or change the sxqueryadmin user password to match the current value

Code: Select all

ommodu -o sxqueryadmin -p newpassword

Cheers

Dave

[mito]

Thanks for the response Dave!

I'm not sure about the other guys, but for me, this is the only server I have. The password in that file is correct, but when I run the ldapsearch program to find out what the password it is using it is, I get the error:

Code: Select all

-bash: ldapsearch: command not found

Which, obviously, means I don't have such a command. Is ldap connectivity required for Scalix 11? Is it possible that scalix didn't discover it as a possible problem because I upgraded from 10.0.5 and didn't install fresh?

I did recently change the root password on the server (which used to match the password in the above file), and it was changed before the upgrade to Scalix 11, but I was having this problem way before the password change.

Just for fun, I reset the password anyways, and it said that the password was reset successfully. I will just have to wait and see how things go.

Also, I thought of it late yesterday. Since the upgrade to Scalix 11, all I have to do to fix the error is restart the scalix-tomcat service (in Scalix 10 that didn't work). So, I added the command 'service scalix-tomcat resart' to the ommaint-daily process so that I can at least access SAC in the mornings... this might help others temporarily be able to work around this problem...

Mito

[dkelly]

You don't necessarily need ldapsearch for Scalix but it's useful. However, we have our own LDAP equivalents. You can run

Code: Select all

omldapsearch -h your.host.name -D "cn=sxqueryadmin" -w password objectclass=*

to get the same result.

Given that this is working after you restart tomcat, I'm suspecting that it's not the password

The next step is to enable logging for the SAC service. Edit the file /var/opt/scalix/NN/caa/config/log4j.properties and change the word INFO to DEBUG. You're going to need to restart tomcat for this change to be picked up.

This will give us more verbose logging during the login session that should help to pinpoint th e problem. The file that this gets logged to is /var/opt/scalix/NN/tomcat/logs/scalix-caal.log

Cheers

Dave

[mito]

The next step is to enable logging for the SAC service. Edit the file /var/opt/scalix/NN/caa/config/log4j.properties and change the word INFO to DEBUG. You're going to need to restart tomcat for this change to be picked up.

This will give us more verbose logging during the login session that should help to pinpoint th e problem. The file that this gets logged to is /var/opt/scalix/NN/tomcat/logs/scalix-caal.log

Cheers

Dave

Perfect! That's why I wasn't able to find any relevant logs. I changed it, and will wait until tomorrow to check in on it, as restarting scalix-tomcat in the middle of the day is a good way to get my users to yell at me...

Thanks for your help!

[LHD-Tech]

The first thing to check is that you've got the correct password configured for the sxqueryadmin user. This is what SAC uses in te background to talk to each Scalix server. You will have been prompted for this during an upgrade.

The file is /var/opt/scalix/NN/caa/scalix.res/config/psdata where NN is the first and last characters of your hostname.

Using that password, run the command:

Code: Select all

ldapsearch -xh your.host.name -D "cn=sxqueryadmin" -w password

If you get something back, the password is correct and we need to look elsewhere.
If you get an error, the password is incorrect and you need to change it. Either set the correctf password in the psdata file or change the sxqueryadmin user password to match the current value

Code: Select all

ommodu -o sxqueryadmin -p newpassword

Cheers

Dave

Thanks Dave, you may have helped me solve this problem.

When I run this, I get the correct password but when I run

Code: Select all

ommodu -o sxqueryadmin -p newpassword

I get a message that says:

ommodu : [OM 8040] The user can't be found, or has been deleted.

So this could be the reason why I cant connect to SAC? do I add a sxqueryadmin user just like i add any other user but give it admin rights?

[LHD-Tech]

So I fixed the problem...
I ran:
omaddu -n sxqueryadmin/<mailnode> --class limited -c admin -p <passwd> sxqueryadmin@<fqdn>

Everything in bold was my settings... after I added the sxqueryadmin account (I have no clue how or why it was deleted) I tried to log into SAC and it worked. Yay!

Thanks again to all who helped on this!!