Users unable to logon

[trig]

Hello,

Had to re-install a server, following a kernel failure. I managed to take a copy of /var/opt/scalix* using Knoppix

I then re-installed 10.0.0.1 on RHEL4 by putting /var/opt/scalix back and then running the install.
Naturally this would pick up that a message store exists, sort out the permissions and owners and then allow me to install the servers as needed.

Since doing this, users are unable to login. sxdu confirms that users exist and their mailbox sizes (fantastic!). omshowu confirms user exists and password is set. I can login with sxadmin and the original password into SAC, but I cannot login with Webmail/MAPI or IMAP even if I change the password.

This scares me tho

Code: Select all

[root@mail ~]# /etc/init.d/scalix status
/etc/init.d/scalix: line 121: [: missing `]'
*** mail not present
[root@mail ~]


Code: Select all

[root@mail ~]# omstat -a
PC Monitor                    Started        NON-STOP       0
Directory Relay Server        Started        13:19:13
Notification Server           Started        13:19:13       0
Shared memory daemon          Started        NON-STOP
Notification Monitor          Started        NON-STOP
Session Monitor               Started        NON-STOP
Container Access Monitor      Started        NON-STOP
Item Structure Server         Stopped        12:04:56
Database Monitor              Started        13:19:14
Licence Monitor Daemon        Started        NON-STOP
LDAP Daemon                   Started        13:19:14
Queue Manager                 Aborted        NON-STOP
Item Delete Daemon            Aborted        NON-STOP
IMAP Server Daemon            Started        13:19:14
SMTP Relay                    Started        13:19:14
Mime Browser Controller       Started        13:19:14
[root@mail ~]#


Ideas?

[trig]

also when running

/etc/init.d/scalix start

It just says

Starting Scalix services (mail):

[Shredder]

First off is the name of the new server the same as the old one? It has to be exact.

Second, there is probably a permission problem.
Type:

Code: Select all

 omcheckl -s -d > /tmp/script.sh

This will check the permissions on all files and create a script you can run to fix them. It will take some time depending on the size of your mail store.

Try that and see if that helps.

Shredder

[deyjvu]

You said that you restored /var/opt/scalix and then installed Scalix. You should have done this in the reverse. Installed Scalix, then copied /var/opt/scalix over the top of what you installed. Otherwise the install could have written over files like general.cfg, smtpd.cfg etc.

Check the swa.properties file and ensure it has the server name in there - I doubt you would have stored this off and so it would be or could be a clean installed file with no local data in it. This is usually updated during the installation process when you identify the server name domain etc. If you didn' t use the scalix.install script then this would not have been done.

Did you ensure tomcat and httpd were running when you users were trying to connect? This one caught me out recently hence my mentioning it.

You can test if users can logon by doing "omlogon -u name -p password" then do "omlist" and it should list any messages in this accounts inbox. if that works then Scalix is working. If users can't logon from the SWA then it is most likely a Tomcat or httpd problem. Check the logs in the directory where caa.log is situated. See what those log files show.

[trig]

HI,

First off, I ran that omcheck script, and it took some time, as you can imagine (9GB message store).

Secondly

omlogon didnt work

[root@mail tmp]# omlogon -h mail.domain.co.uk -u "Users Name" -p password
A fatal error has occurred - see the system error log
Permission denied

Unable to connect, hostname/username invalid

I can ping mail.domain.co.uk from the local box and it returns the correct IP.

Last 50 lines of 'fatal are

SERIOUS ERROR Bulletin Board(Bulletin Board) Fri Mar 30 09:29:17 2007
[OM 10272] BACKTRACE:
/opt/scalix/lib/libom_er.so(er_add_backtrace+0xc6)[0x832f06]
/opt/scalix/lib/libom_er.so[0x8331d6]
/opt/scalix/lib/libom_er.so(er_DumpProcAndExit+0x1f)[0x83337f]
/lib/tls/libpthread.so.0[0xbab8b8]
/lib/tls/libc.so.6(abort+0x129)[0xa73319]
/lib/tls/libc.so.6[0xaa4f8a]
/lib/tls/libc.so.6[0xaab4f8]
/lib/tls/libc.so.6(__libc_free+0x8a)[0xaabaca]
/opt/scalix/lib/libom_mdc.so(mdc_free+0x21)[0x128991]
/opt/scalix/lib/libom_os.so(os_free+0x1d)[0xe54f4d]
/opt/scalix/lib/libom_bb.so(bb_FreeSyncConfMem+0x91)[0x9f8d8d]
bb.server[0x8058dfe]
/lib/tls/libc.so.6(__libc_start_main+0xe3)[0xa5ee33]
bb.server[0x804c625]
ôï¶
Pid of logging process: 29942
Current errno value: 3


SERIOUS ERROR Service Router(Service Router) Fri Mar 30 09:29:17 2007
[OM.DMON 1013] The queue manager is not running.
Pid of logging process: 29944
Current errno value: 3


SERIOUS ERROR Service Router(Service Router) Fri Mar 30 09:29:17 2007
[OM.DMON 1013] The queue manager is not running.
Pid of logging process: 29945
Current errno value: 3


SERIOUS ERROR Internet Mail (Incoming ) Fri Mar 30 09:29:22 2007
[SYS 2] No such file or directory
File Name: /var/opt/scalix/msgpool/60QP
Pid of logging process: 29960
Current errno value: 2

[trig]

i've taken the decision to run

omcpoutu on the mailboxes and re-install scalix and then re-import them.

thanks for your help guys

[ScalixSupport]

Hi!

Once you have exported the message store for users, create user/group with same user-id
and group-id, make sure you run omcheck to clear permission issues, only then should you
try to upgrade scalix server.

Please feel free to reply if you continue to experience problem.

Thanks,
Subir

[deyjvu]

Just to clarify why the omlogon did not work for you, you have to be root or su to root for om commands to work.

Make sure you have plenty of disk space for your restore of users as you will use up more space when you restore from an omcpoutu. Reason being that previously if a message went to 5 local users then only one copy was kept. With omcpoutu/inu each person then has a copy of the message so 5xoriginal message size. Just a warning.

The other error messages you were see as Serious Errors, you could look them up with omsolve -n DMON 1013 or omsolve -n 10272. If your stars are all aligned right and you hold your tongue in the right tilt... you might be lucky enough to get a response to tell you what to do with these errors.... don't hold your breath!! You never know your luck in the big city though.