[Error] Session invalid. Please log in again / upgrading !

[Lubna]

Hello all ,

I tried to upgrade from otrs 3.0.17 to 3.2.9 , as the following :

Backup process :

1. i dump the otrs DB to otrs.sql
2. i took a copy of config.pm , and others needed files like : generic agent , zzzauto , .. + certificates , bcz i used openssl
3.i export the sysconfig file

Then i un install the previous version and install the new one , i.e. 3.2.9

i did all the above process but in opposit , i import the mysql db , import sysconfig , copy config.pm in the otrs file to suitable location and the same for the others file and i change the location path if it required to be changed specially in config.pm file .

now i notice that every thing was working properly until the last stage in importing the .sql file once i import it and try to log in it gives me this message :

{Session invalid. Please log in again}

but when i try to solve that issue by adding this :

Code: Select all

$Self->{SessionModule} = 'Kernel::System::AuthSession::FS';
#$Self->{SessionModule} = 'Kernel::System::AuthSession::DB'; 

to config.pm i am able to login and use mysql old db which is what i need , but i face another issue i faced after login that when i went to postmaster to delete the old mail that i used to fetch from i wasnt able and it prompt me an error :
Need ID or ldap_folder in mail account is unknown .

How to solve my main issue which is : session invalid . please login again !

Can any one explain to me whats happening and what is the problem exactly ?

Thanks in advanced !

[crythias]

It doesn't appear that you've upgraded per the UPGRADING instructions. Note that you need to upgrade 3.0.x -> 3.1.latest -> 3.2.latest.
and you'll need to apply the database and schema updates for each step.

[Lubna]

Always you are helpful crythias .

Maybe that problem occure because of that !

so i will upgrade it to 3.1.x then do the backup then upgrade it to 3.2.9 .

Thanks again for your fast reply and ur help as well.

Bless u !

[Lubna]

Hello cryth.

you know i did the installation of 3.1.0 & 3.1.17 , but once i run the installer.pl and directly after i'd checked the database and clicking next the bellow error is occured :

Unknown Subaction DBCreate!

Kindly , check the attachment ! and tell me what the mistake that i did !

Regards,

Untitled.png

[crythias]

don't run installer.pl on upgrade unless you want to lose your data (potentially). Read and follow UPGRADING file.

[Lubna]

i told you i faced this issue prev. :

Need ID or ldap_folder in mail account is unknown

I faced it also while upgrading from 3.0.x to 3.1.x ,

but when i create this column in mysql every thing is working properly !! i use this command !

Code: Select all

mysql > ALTER TABLE mail_account ADD imap_folder VARCHAR(60);

and i restore every thing in postmaster email file with no error messages and am able to delete the fetching process inside !! is that way is good !

so after doing that modification can i backup mysql db , otrs , to upgrade to 3.2.x !!

Am i doing right things !!

[crythias]

I don't know what state you're in. There is not enough information to answer your question.

If OTRS runs - you can log in, fetch mail, and there aren't errors, then "Are you doing the right thing"? yes?
If there are errors then no.

[Lubna]

Thank you crythias ,

You make me some how confident about what am doing , and i would like to tell you i upgraded to 3.2.9 with adding to config .pm this line :

Code: Select all

$Self->{SessionModule} = 'Kernel::System::AuthSession::FS';

and am able to login without seeing this error of invalid session . please login again !

if this addition also may case problem for me in my future use or upgrade please advise me !

Thanks again !

[crythias]

FS = FileSystem. Basically, how session authentication is stored -- db or filesystem.
It's not as if there is, necessarily, a right or wrong way to handle this. It could be the session information is handled better, performancewise, in a database. Or not. Or it could be that session information might be faster in a filesystem, but have space issues, or not.

Probably FileSystem is better long term for you and that's all that needs to be said.

It's also *possible* that the table that held the session authentication results is crashed/bad. Can't tell from this. In any case, moving it to filesystem would ignore database table issues.

[Lubna]

Thanks alot crythias for your helpful replies ,

I am really happy that am learning and well understanding new information from you , bcz. that i wish that you'll be patiant to accept my questions bcz. rarelly to find someone to understand from him simply and easily like you !

maybe my last questiones , maybe :/

From time to time i am doing the backing up process and also the upgrading process , so i am wondering if its nessessary to backup the session authentication filesystem or no need bcz. it will be created in each authenticated process will be done in the future, i.e. am i have to back it up otherwise i will lose some data or no need ?

Another question , when i entered the database i saw 3 differant db : information_schema , mysql , otrs (i think this is the one that i restored it) and my question is what is the use for each database ? and when we restored the backedup database can we restore it by appending it to one of the existing DB , am asking this question bcz. i am thinking to create a fresh installation of OTRS system with new otrs DB to re create the crashed tables in the database , so i want at the same time to not loose my original tickets or configurations or data so i was thinking if i can append the old DB to the new created OTRS DB without applying any changes in the new DB tables only it should add the changes in the old one to the new one and avoid the crashed data ! am trying to repair the crashed table in easy way !

And also , is there is any way to backup only the tickets DB , i.e. closed , open , pending , .. tickets only ! so i can restore them after doing fresh installation !? without the need to restore the rest of the database that my contains the crashed tables ?? bcz. the most important things that i dont want to lose in the otrs db is the tickets !

[crythias]

so i am wondering if its nessessary to backup the session authentication filesystem or no need

I don't have any immediate thoughts on why backing up the session authentication filesystem is necessary. At the worst, not having it requires people to log in again. (I know, right?)

3 differant db : information_schema , mysql , otrs (i think this is the one that i restored it) and my question is what is the use for each database ?

The other two are critical to how MySQL works. "mysql" holds your otrs and "root" login information. if you lose it, it's okay, you can create it again, it's just a pain in the longer term. Read MySQL documentation for more information.

and when we restored the backedup database can we restore it by appending it to one of the existing DB

no. I don't really want to get into the particulars of restore in this conversation. There are too many variables and if you don't already know what you're doing, I'll probably have forgotten something critical

And also , is there is any way to backup only the tickets DB , i.e. closed , open , pending , .. tickets only ! so i can restore them after doing fresh installation !?

No, but ... repairing tables that aren't related to those ticket tables isn't going to kill the tickets.
Backup first.

[Lubna]

Thanks alot crythias at least i understand the main thing that i want and really understand what is going on and i wish that even after long term i will see you here and not going somewhere else .

And i want to tell you that i think i know what was the initial mistake that i made !

while i am working i dont know where in otrs exactly , but i got this error message :

mysqldump: Got error: 145: Table '[insert table name]' is marked as crashed , example process_id table

So i think i tried to repair this table by running ( REPAIR TABLE process_id ) in mysql , i thought that i was repairing the table without damaging something else ..

Umm i dont know wether that was an issue , at least now every thing is going as what i want and that session authentication DB is only like what you said if there is a big problem it will be only for relogin again and that is not an issue !

Finally , thanks alot crythias and i dont know how to thank you rather than writting that in words !

Bless u & wish u the best in ur life !

Regards,

[Lubna]

Yes i remeber now when i faced that initial issue !

I post before 1-2 month this ticket : viewtopic.php?f=53&t=21108&p=83511#p83511

so i find that to solve that issue i need to upgrade

so when i try to backup the mysql DB using mysqldump i got that error !

Got error: 145: Table '[insert table name]' is marked as crashed , example process_id table

but i was not able to understand the reason of that crashing so all what i was doing is to repair that crashed table !

thats it