Hello,
I've a 3.0.10 that did run well. Starting from yesterday, nobody cannot log on the system from Web dashboard.
The logon process is working, because if you insert a wrong password it reports that. But if you insert the right password, it show always the logon page and doesn't enter the dashboard.
We didn't apply any change or update, it simply did start to have this behavior.
In log I can see that logon was ok, but the next line reports
table "./otrs/sessions" is marked as crashed and should be repaired
Any idea?
thanks
Unable to logon
Moderator: crythias
-
- Znuny ninja
- Posts: 1029
- Joined: 13 Apr 2009, 12:26
- Znuny / OTRS Version: 6.0.13
- Real Name: Wolfgang Fürtbauer
- Company: PBS Logitek GmbH
- Location: Pinsdorf
Re: Unable to logon
you need to user mysql client and repair the table, egIn log I can see that logon was ok, but the next line reports
table "./otrs/sessions" is marked as crashed and should be repaired
Code: Select all
mysql> repair table sessions;
+---------------+--------+----------+----------+
| Table | Op | Msg_type | Msg_text |
+---------------+--------+----------+----------+
| otrs.sessions | repair | status | OK |
+---------------+--------+----------+----------+
1 row in set (0.04 sec)
Produktiv:
OTRS 6.0.13/ ITSM 6.0.13
OS: SUSE Linux (SLES 12, Leap), MySql 5.5.x, 5.6.x
Windows 2012 AD Integration (agents and customers), Nagios integration (incidents, CMDB), Survey, TimeAccounting
OTRS 6.0.13/ ITSM 6.0.13
OS: SUSE Linux (SLES 12, Leap), MySql 5.5.x, 5.6.x
Windows 2012 AD Integration (agents and customers), Nagios integration (incidents, CMDB), Survey, TimeAccounting
Re: Unable to logon
it did work, thank you!
But.. how is it possible that a table was corrupted without any "event" (power failure, at least a reboot, ...)?
thanks
But.. how is it possible that a table was corrupted without any "event" (power failure, at least a reboot, ...)?
thanks