No login possible after "full-harddisc" - crash

[jonaswagner]

IHi there,
my scalix crashes, because the harddisk went full.
After expending the harddisk- space for my var- directory, scalix behave strange:
- no login possible in webmail/ Outlook, because scalix says, it cannot recognize the user/ passwort
- no login possible sac, because the login- page doesn't completely load
- I am using scalix 10 CE, suse 10 and all scalix / Scalix- tomcat- threads seem to be running correctly.
- Except the full harddisk- problem, i have done no changes to the system.
- Any suggestions?

Thanks, Jonas

[jonaswagner]

Sorry for the bad English above - it was dictated via a friend, becaus I was on the road.

The Problem mentioned above is now a little bit smaller. I can at least acces the sac with my admin-account and password. But trying to acces webmail with the same user-data I get the response "Der Benutzer konnte nicht gefunden werden oder das eingegebene Passwort ist falsch. ..." (The User could not be found or the typed password is wrong).

I entered the user-data correctly, but the webmail-acces (and the Outlooc-Connect-Access too) wont let me in.

I would be very pleased for any ideas or solutions.

Thanks, Jonas

[kanderson]

if you go to a command line, and type omstat -s and then omstat -a, which services are in a state other than started or enabled. (Item Structure Server doesn't matter).

My first guess would be that Remote Client Interface isn't running.

If that's correct, type

omoff -d 0 rci
omreset -o off rci
omon rci

that should restart it for you.

Kev.

[jonaswagner]

Hi kanderson,

and thanks for your reply. After typing omstat -a the Remote Client Interface didnt even show up in the list. But the Item structure server was stopped. so I translated your suggestions from rci to iss. This is what i got:

mts-oxserver:~ # omstat -a
PC Monitor Started NON-STOP 0
Directory Relay Server Started 16:16:31
Notification Server Started 16:16:31 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
Database Monitor Started 16:16:32
Licence Monitor Daemon Started NON-STOP
LDAP Daemon Started 16:16:32
Queue Manager Started NON-STOP
Item Delete Daemon Started NON-STOP
IMAP Server Daemon Started 16:16:32
SMTP Relay Started 16:16:32
Mime Browser Controller Started 16:16:32
mts-oxserver:~ # omoff -d 0 iss
omoff : [OM 4835] Subsystem Item Structure Server is already off.
mts-oxserver:~ # omreset -o off iss
Service Item Structure Server forced to state 0
mts-oxserver:~ # omon iss
Enabling 1 subsystem(s).
mts-oxserver:~ # omstat -a
PC Monitor Started NON-STOP 0
Directory Relay Server Started 16:16:31
Notification Server Started 16:16:31 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 Started 18:35:50
Database Monitor Started 16:16:32
Licence Monitor Daemon Started NON-STOP
LDAP Daemon Started 16:16:32
Queue Manager Started NON-STOP
Item Delete Daemon Started NON-STOP
IMAP Server Daemon Started 16:16:32
SMTP Relay Started 16:16:32
Mime Browser Controller Started 16:16:32
mts-oxserver:~ #

After the Procedure the Item Structure Server is running, but the problem when trying to access webmail, still remains the same: "The User could not be found or the typed password is wrong". I dont see any real mistakes since all services are running and I can access the sac (where I can manage all my existing users). And the system was running well before the harddisk-Problem.

After restarting the scalix-services the Item structure Server is again set to stopped.

In the meantime I expanded the Space for my Var-Directoy, so it cant be anything with too less harddisk-space.

Very strange, but I hope anybody can help me,
Jonas

[kanderson]

The Item Structure Server doesn't matter. It'll likely be off by now again anyway. Which is fine.

You did use omstat -a, but what about omstat -s

Can you please post the output from omstat -s?

Thanks
Kev.

[jonaswagner]

Hi kanderson,

firstly thanks for your help. Here is the omstat -s:

mts-oxserver:~ # omstat -s
Service Router Started 10.11.06 0
Local Delivery Started 10.11.06 0
Internet Mail Gateway Started 10.11.06 0
Local Client Interface Enabled 10.11.06 0
Remote Client Interface Enabled 10.11.06 0
Test Server Started 10.11.06 0
Request Server Started 10.11.06 0
Print Server Started 10.11.06 0
Bulletin Board Server Started 10.11.06 0
Background Search Service Started 10.11.06 0
CDA Server Started 10.11.06 0
POP3 interface Started 10.11.06 0
Omscan Server Started 10.11.06 0
Archiver Started 10.11.06 0
mts-oxserver:~ #

Everything seems to be running, or it is not listed. Is there a special log-File, which content would help to resolve the problem?

Thanks,

Jonas

[jonaswagner]

And more input:
I tried to shut down scalix using the omshut-command and it tells me scalix is running and I have use omshut. Doing this, it says:

mts-oxserver:~ # omshut
omoff : [OM 4835] Subsystem Application Link Server is already off.
Disabling 14 subsystem(s).
omoff : [OM 4835] Subsystem Item Structure Server is already off.
Disabling 7 subsystem(s).

Now trying to restart scalix using omrc -n there are some Compyright-things folowed by:

Enabling 7 subsystem(s).
[OM 10440] /opt/scalix/bin/omrc : Service startup has been disabled.
Scalix services NOT started.

But I can login to sac and can see the login-page of my webmail though a login is not possible with the same problem remaining.

Another strange thing is, that accessing the sac/webmail via Internet from my home the pages are coming up a lot faster than from inside the network.

Jonas

[jonaswagner]

Update 2:
Trying "omtidyu -B -u "Jonas Wagner" -M" I get the message:

Scalix-Benutzerschnittstelle ist nicht aktiviert. (scalix-userinterface is not active).

What is the User-interface-service called and how can I enable it?

J.

[jonaswagner]

Finally, I fixed it:

I checked all file-permissions with omcheck -s -d >/tmp/omcheck.out , made this file an executable and executed it. After this, I stopped scalix (/etc/init.d/scalix stop) and tried ompatchom and then restarted scalix (/etc/init.d/scalix start). And to my surprise - it worked. Another reboot of the whole server confirmed, that everything is runing fine again.

Thanks for your help and your suggestions and enjoy the rest of this wonderful sunday,

Jonas