Scalix Forums

It appears that none of my users can log into the IMAP server on my new scalix box. The can log in using the outlook connector, and POP3, and SWA, but not IMAP.

I haven't done anything strange on the box (other than changing the IP address after installation, but I'm reasonably sure I did that properly).

It's Scalix 11 Running on Centos 4.

Here is a sample of what I get when testing...

= = = = = = = = = = CUT HERE = = = = = = = = = =
[root@scalix scalix-11.0.3-GA]# telnet 127.0.0.1 143
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
* OK Scalix IMAP server 11.0.3.10719 ready on scalix.sas-sa.co.za
a login jdoller@sas-sa.co.za mypass
a NO LOGIN failure, service unavailable
* BYE IMAP Server not available
Connection closed by foreign host.
= = = = = = = = = = CUT HERE = = = = = = = = = =

omshowlog -p 20 -l 11 gives a LOT of errors, mostly starting with "SERIOUS ERROR", which gives me happy happy joy joy feelings deep within my stomach.

I'm not going to post everything, just the last bit:

= = = = = = = = = = CUT HERE = = = = = = = = = =
SERIOUS ERROR IMAP Server Da(IMAP Server Pr) 05.16.07 17:39:16
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0x48eee6]
/opt/scalix/lib/libom_er.so[0x48f1e6]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x48f38f]
/lib/tls/libpthread.so.0[0x154898]
in.imap41d[0x8086752]
in.imap41d[0x80559db]
in.imap41d[0x80569c0]
in.imap41d[0x8057a34]
in.imap41d[0x8068ece]
in.imap41d[0x8069ae9]
in.imap41d[0x8063b89]
in.imap41d[0x80650bb]
in.imap41d[0x8065a84]
/lib/tls/libc.so.6(__libc_start_main+0xd3)[0xb7bde3]
in.imap41d[0x804e021]
User Name: jason doller / scalix/CN=doller, jason

SERIOUS ERROR IMAP Server Da(IMAP Server Pr) 05.16.07 17:42:47
[OM 10270] Process about to terminate due to error.
Signal (Segmentation Violation) trapped by process 6231
Procedure trace follows:
-> ual_DeleteGetItemFiles
-> ual_GetUserTweak
<- ual_GetUserTweak
<- ual_DeleteGetItemFiles
-> ual_CloseBrowserPipes
<- ual_CloseBrowserPipes
-> ual_CloseBrowserPipes
<- ual_CloseBrowserPipes
<- ual_TidyUp
<- ual_ShutDown
<- ual_RecvReply
<- imapual_finalise
<- imapLogin1
<- imapSatelliteCommand
-> checkNotifications
-> imapual_checkShutdown
User Name: jason doller / scalix/CN=doller, jason


SERIOUS ERROR IMAP Server Da(IMAP Server Pr) 05.16.07 17:42:47
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0x48eee6]
/opt/scalix/lib/libom_er.so[0x48f1e6]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x48f38f]
/lib/tls/libpthread.so.0[0x154898]
in.imap41d[0x8086752]
in.imap41d[0x80559db]
in.imap41d[0x80569c0]
in.imap41d[0x8057a34]
in.imap41d[0x8068ece]
in.imap41d[0x8069ae9]
in.imap41d[0x8063b89]
in.imap41d[0x80650bb]
in.imap41d[0x8065a84]
/lib/tls/libc.so.6(__libc_start_main+0xd3)[0xb7bde3]
in.imap41d[0x804e021]
User Name: jason doller / scalix/CN=doller, jason
= = = = = = = = = = CUT HERE = = = = = = = = = =

Help? Please?

Hi!

I hope you have followed the steps for change of IP address of Scalix Server at:
http://www.scalix.com/wiki/index.php?ti ... s/ChangeIP

To help resolve Serious errors of IMAP, I would request you to omscan for the user(s)
in question, and then would clear the imap-cache.

Run omscan as below:

You need to watch the status of the omscan process using the command:

Wait until you get a message that says "Current server cycle not started; service reset
or delayed".

Now try to fix the mailstore related issues in active mode using the below given
command:

Note: <username> should be the username for the user in question.

Clear imap-cache using steps as below:
Once, omscan gets over, we need to clear the imap cache for this user, follow the
steps below:
1. make sure the user is logged out, i.e.

should not show any more sessions for any user.

2. determine the user folder directory, i.e.

Note: <lastname> should be the lastname of the user in question.

3. Go there (the so-called g-directory of the user)

4. This should have a subdirectory called imap-cache. delete that:

Note: After you execute these commands, all Outlook profiles for users using SmartCache or Offline Working need to be recreated.

5. Now, restart scalix-tomcat service and try accessing the user's mailbox using IMAP
again.

Hope this helps.

Thanks,
Subir

OK, a few keywords for the search engine first:

= = = = = = = = = = SNIP = = = = = = = = = =
Scalix user interface access is disabled
Cannot start up subsystem Remote Client Interface, a shut down is in progress.
Cannot start up subsystem Local Client Interface, a shut down is in progress.
Scalix user interface access is disabled
= = = = = = = = = = SNIP = = = = = = = = = =

OK, seems the problem may have been a power failure. When the box came up again, everything worked (appeared to work?) except IMAP. The next morning, users couldn't log int webmail (Password incorrect messages) and the scalix Outlook COnnector didn't work. Scalix Rules Wizard gave the error "Scalix user interface access is disabled" (which led me to the correct (I sincerely pray) solution).

Strangely enough, POP3 seemed to work just fine.

I could log into SAC, which showed Remote Client Interface as being down.

Running the following:
omreset -o off rci
omon rci
omreset -o off lci
omon lci

Resolved the problem.

What would have caused this problem?

Thanks to Scalix for the forums, BTW. Great support for a product that many (myself included) use as free.

The box lost power due to a power failure again today, and when it came up the problem was back (again).

Any suggestions on why this is happening, and what to do to resolve it?

I've set these commands in /etc/rc.local so that this happens again it should fix itself, but it worries me that it's happening.

Jason

I have just recently began to receive an error very similar to the on described above. However, it is not due to any power failures or changes of IP address, and it doesn't seem to effect the user in any way. The Errors just show up in the log. It is for one specific user only. I have tried the above suggestions, but I am still receiving the error. Are there any ideas on how to fix this.

After further investigating I have determined that the error seems to happen at logout. Which is i guess why there seems to be nothing wrong from the users point of view.


causes



Anyone have any Ideas? This is on CentOS 5 and 11.3.0.77. I will assume that it will happen with any imap client. It does do it with Thunderbird, and Perl-MAil-IMAPClient.

Since nobody has replied, let me ask another question. Would it be possible to just omcpoutu said account, delete account recreate, omcpinu account. If so, would all permissions to shared resources have to be redone. And if possible, is it likely to solve this problem.

kcsc wrote:Since nobody has replied, let me ask another question. Would it be possible to just omcpoutu said account, delete account recreate, omcpinu account. If so, would all permissions to shared resources have to be redone. And if possible, is it likely to solve this problem.

If it is just one user then try clearing the imap cache for that user. Check the scalix wiki for a howto on that.
Make sure there are no hung processes belonging to the user for imap.

If you do export, delete and import use sxmboxexp and sxmboximp, they are better that the old tools. If you use those tools they should, by default export out all ACL's for all folders and import them also. Check the man pages for each.
I don't think you'll need to go that far though.

There is also a script on the wiki to enable full imap logging per user. Set this up and attempt connection then check those log files. They should show the reason for the problems.

You can use sxmboxexp to dump out the users, but I have to think getting a UPS is your #1 priority...

Les,
I have cleared the cache as described above, but I missed the script to clear the cache in the wiki, I will give that a try. I will take a look at the logging as well. Schmoe thanks as well, but as mentioned it is not a power, or change of ip address problem (that was a possible cause of the problem of the OP, my problem has a very similar error message in the log). I agree that power management is very important, which is why I have UPS, and Standby Generators. The server has never lost power and its IP has never been changed.