[Koha-devel] Immediate logout in Koha 21.05.02 (03?)
dcook at prosentient.com.au
dcook at prosentient.com.au
Mon Sep 6 01:42:55 CEST 2021
What's your base URL system preferences? If they're HTTPS, then a Secure Cookie should be set I think, which won't be sent over a HTTP connection.
That kind of sounds like what is going on.
David Cook
Senior Software Engineer
Prosentient Systems
Suite 7.03
6a Glen St
Milsons Point NSW 2061
Australia
Office: 02 9212 0899
Online: 02 8005 0595
-----Original Message-----
From: Koha-devel <koha-devel-bounces at lists.koha-community.org> On Behalf Of Michael Kuhn
Sent: Saturday, 4 September 2021 7:59 PM
To: Michael Hafen (TECH) <michael.hafen at washk12.org>
Cc: Koha-devel <koha-devel at lists.koha-community.org>
Subject: Re: [Koha-devel] Immediate logout in Koha 21.05.02 (03?)
Hi Michael
You wrote:
> Seems to be a problem with the session. Do you know what the session > store sys pref (SessionStorage) is set to? If not you can get that > from the database in the systempreferences table.
> If it's "tmp", then I would suggest deleting all the files in the > session store directory > (/var/lib/koha/[instance]/tmp/cgisess_koha_[instance]/)
> If it's "mysql", then you should be able to delete everything from the > session table.
>
> That's something to try anyway.
The preference was set to "Memcached server". I have now changed that to "MySQL database" but the problem persists. However, there was no such problem as long as the Koha 21.05 database was empty - it only appears since I loaded the Koha 18.11 database and updated it to Koha 21.05.
> System Preferences can be changed in the database too, when the Staff > interface isn't working; like in this case. You will need to restart > the memcached service to flush the changed sys pref. Might need to > "koha-plack --restart [instance]" as well.
This didn't change anything.
However, the login process was somewhat complicated (but originally did work). I had to open an SSH tunnel as follows:
ssh -p 33 -t root at host1 ssh -C -g -L 10080:kohahost:80 -L
18080:kohahost:8080 -J root at host2 koha at kohahost
Like this access via http://host1:8080 was possible (but was looging me out after every click on a link as described).
The system administrator now opened the firewall and gave me direct access to the staff client, now access via http://kohahost:8080 is possible and it works as expected.
Best wishes & thanks for your hints: Michael
--
Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik at adminkuhn.ch · W www.adminkuhn.ch
> On Thu, Sep 2, 2021 at 7:22 AM Michael Kuhn <mik at adminkuhn.ch
> <mailto:mik at adminkuhn.ch>> wrote:
>
> Hi
>
> As written on this list on 26 August I tried to install Koha 21.05.03
> but after the installation Koha said the installed version was
> "21.05.02.003". Jonathan Druart wrote this comes from
>
> commit 8ea80995c590dad86c43df636456640d3aa84bab
> Increment version for 21.05.03 release
>
> -$VERSION = "21.05.02.002";
> +$VERSION = "21.05.02.003";
>
> Today I updated a Koha 18.11.05 database into this Koha 21.05.02.003
> installation. After restarting memcached I executed "sudo
> koha-upgrade-schema instancename" - the output looked OK and ended with
> the following lines:
>
> Upgrade to 21.05.02.000 done [12:15:20]: Koha 21.05.02 release
> Upgrade to 21.05.02.001 done [12:15:20]: Bug 28567 - Set to NULL
> empty
> branches fields
> Upgrade to 21.05.02.002 done [12:15:20]: Bug 28813 - Update
> delivery_note to failure_code in message_queue
> Upgrade to 21.05.02.003 done [12:15:20]: Bug 28872 - Update syspref
> values from on and off to 1 and 0
>
> It seems even if I installed Koha 21.05.03 it only upgraded to Koha
> 21.05.02.
>
> I don't know if there is any connection but whatever, I was able to
> open
> the staff client and to login - but as soon as I click on any link I'm
> logged out immediately. I am able to login again and then advance to
> the
> next link but then I'm logged out again etc ad infinitum. It is not
> possible to change any system preference (internal server error) or
> search for any users.
>
> File "plack-error.log" sometimes tells me, without a timestamp:
>
> new(): failed: query object HASH(0x555f47cfad30) does not support
> cookie() and param() methods: Can't call method "cookie" on unblessed
> reference at /usr/share/perl5/CGI/Session.pm line 707.
>
> File "plack-intranet-error.log" says:
>
> [2021/09/02 13:33:36] [WARN] Odd number of elements in anonymous
> hash
> at /usr/share/koha/intranet/cgi-bin/catalogue/search.pl
> <http://search.pl> line 577.
>
> Can anyone please give me a hint how to solve this problem?
>
> Best wishes: Michael
> --
> Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis
> Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz
> T 0041 (0)61 261 55 61 · E mik at adminkuhn.ch
> <mailto:mik at adminkuhn.ch> · W www.adminkuhn.ch <http://www.adminkuhn.ch>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> <mailto:Koha-devel at lists.koha-community.org>
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> <https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
> website : https://www.koha-community.org/
> <https://www.koha-community.org/>
> git : https://git.koha-community.org/ <https://git.koha-community.org/>
> bugs : https://bugs.koha-community.org/
> <https://bugs.koha-community.org/>
>
>
>
> --
> Michael Hafen
> Washington County School District Technology Department Systems
> Analyst
>
_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/
More information about the Koha-devel
mailing list