After Upgrade from 3.2 to 3.3 Session/Login Problems

[lordlamer]

Hi,

we have OTRS 3.2 running on a Debian Wheezy System.
I have done the update to version 3.3 and we have some strange problems with the session.

Every Link/Form without the session id does not work. It will show always the login screen.
I does not see any problems in the Logs.
What is wrong here?

Upgrade works fine without any errors.

regards,
Frank

[piotrknysz]

Hello,

I have the same problem. I have done upgrade from 3.0.10 to 3.3.3, every think works fine but otrs add SessionID for each URL.
Problem appears when I changed the default URL from https://otrs_srv/otrs to (https://otrs_srv/agent,https://otrs_srv/user)

I think thet the problem is with storing cookies in webbrowser, but I do not know the cause.

Regards
Piotr Knysz

[lordlamer]

Hi,

no new feedback here.
Should we open a ticket?

Frank

[crythias]

I'm surprised you don't have any errors at all.. even the one that talks about the session should give an error in system log.
Check for crashed session tables.

[lordlamer]

Hi,

i only find this in syslog at update time:
Feb 19 22:18:21 otrs OTRS-DBUpdate-to-3.3-01[19967]: [Error][main::_AddTemplateTypeColumn][Line:422]: Unknown column 'template_type' in 'field list', SQL: 'SELECT template_type FROM standard_template WHERE 1=0 LIMIT 1'
Feb 19 22:18:21 otrs OTRS-DBUpdate-to-3.3-01[19967]: [Error][main::_AddACLTables][Line:310]: Table 'otrs.acl' doesn't exist, SQL: 'SELECT * FROM acl WHERE 1=0 LIMIT 1'

After update is finished i found no new logs and the problem still exists.

Frank

[lordlamer]

Hi,

@piotrknysz:
Did you see the same errors at upgrade time?

No other feedback here.
I think we should open a ticket.

Frank

[crythias]

Those error messages indicate that you didn't upgrade database structure properly.

[lordlamer]

Hi,

as you see the message is at update time and from the script: OTRS-DBUpdate-to-3.3-01
So script i am missing?

Frank

[crythias]

https://github.com/OTRS/otrs/blob/rel-3_3/UPGRADING.md
https://github.com/OTRS/otrs/blob/rel-3 ... ema-update

[lordlamer]

Hi,

ok. Today i found the time to test that again and i got the exact same error as i told.
I will create a ticket now.

Frank

[lordlamer]

ok. Here is the ticket: http://bugs.otrs.org/show_bug.cgi?id=10391

[crythias]

as you see the message is at update time and from the script: OTRS-DBUpdate-to-3.3-01

Did you do the part before that?

[jojo]

I never had this error, so something went wrong during the update via SQL script

[lordlamer]

Hi,

ok. here is the solution for my problem.
I had to set the cookie path in the config.
That works.

Frank

[hlawatsch]

Hi,

ok. here is the solution for my problem.
I had to set the cookie path in the config.
That works.

Frank

Hallo Frank,

I have the same Problem but found no Clue how to set the CookiePath in the Config,
How do you have done it?

BR
Stephan

[Christoph89]

Hi,

I don't know wether this still aplies for current Version but google told me:

The Cookie Path can be set in /opt/otrs/Kernel/cpan-lib/CGI/Cookie.pm
Change here
line no 147 $path ="/"

Edit: File is still there but path variable is set a few lines earlier.

[koshihaku]

Hi,

ok. here is the solution for my problem.
I had to set the cookie path in the config.
That works.

Frank

Hi Frank,

I have a similar problem with your OTRS.
After updating from 3.0 to 3.3, sessionIDs are shown in the URLs.
Can you tell why reset the cookie path can solve this problem?

Koshihaku