Bug 24189 - Can't login to SIP2
Summary: Can't login to SIP2
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: SIP2 (show other bugs)
Version: 18.11
Hardware: HP Linux
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-09 03:05 UTC by ciarebaha
Modified: 2023-06-08 22:26 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Sip testing tool return value '0' which indicate as login failure (59.77 KB, image/jpeg)
2019-12-09 03:05 UTC, ciarebaha
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ciarebaha 2019-12-09 03:05:01 UTC
Created attachment 96081 [details]
Sip testing tool return value '0' which indicate as login failure

This problem occurred when we trying to shut down the server. But then after we start up the server, the SIP2 connection was failed. This is the log from the selfcheck machine after start the server. It's showing that the connection is connected but the login seems failed because of the status indicate as '0'. Please refer attachment for clearer view.

21/11/2019 05:00:05 ILSport Error - The attempt to connect timed out
21/11/2019 05:00:26 ILSport Error - The attempt to connect timed out
21/11/2019 05:00:47 ILSport Error - The attempt to connect timed out
21/11/2019 05:01:08 ILSport Error - The attempt to connect timed out
21/11/2019 05:01:44 ILSport Connected
21/11/2019 05:01:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY0AZF1A5
21/11/2019 05:01:45 From <---- ILS 940AY0AZFDFE
21/11/2019 05:01:45 To-->ILS 9901002.00AY1AZFCA7
21/11/2019 05:01:46 ILSport Disconnected by remote host
21/11/2019 05:03:44 ILSport Connected
21/11/2019 05:03:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY5AZF1A0
21/11/2019 05:03:45 From <---- ILS 940AY5AZFDF
21/11/2019 05:03:45 To-->ILS 9901002.00AY6AZFCA2
21/11/2019 05:03:46 ILSport Disconnected by remote host
21/11/2019 05:05:44 ILSport Connected
21/11/2019 05:05:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY0AZF1A5
21/11/2019 05:05:45 From <---- ILS 940AY0AZFDFE
21/11/2019 05:05:45 To-->ILS 9901002.00AY1AZFCA7
21/11/2019 05:05:46 ILSport Disconnected by remote host
21/11/2019 05:08:05 ILSport Error - The attempt to connect timed out
21/11/2019 05:08:26 ILSport Error - The attempt to connect timed out
21/11/2019 05:08:35 ILSport Error - Connection is forcefully rejected
21/11/2019 05:08:36 ILSport Connected
21/11/2019 05:08:36 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY5AZF1A0
21/11/2019 05:08:38 From <---- ILS 940AY5AZFDF9
21/11/2019 05:08:38 To-->ILS 9901002.00AY6AZFCA2
21/11/2019 05:08:38 ILSport Disconnected by remote host
21/11/2019 05:09:44 ILSport Connected
21/11/2019 05:09:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY0AZF1A5
21/11/2019 05:09:45 From <---- ILS 940AY0AZFDFE
21/11/2019 05:09:45 To-->ILS 9901002.00AY1AZFCA7
21/11/2019 05:09:46 ILSport Disconnected by remote host
21/11/2019 05:11:44 ILSport Connected
21/11/2019 05:11:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY5AZF1A0
21/11/2019 05:11:45 From <---- ILS 940AY5AZFDF9
21/11/2019 05:11:45 To-->ILS 9901002.00AY6AZFCA2
21/11/2019 05:11:46 ILSport Disconnected by remote host
21/11/2019 05:13:44 ILSport Connected
21/11/2019 05:13:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY0AZF1A5
21/11/2019 05:13:45 From <---- ILS 940AY0AZFDFE
21/11/2019 05:13:45 To-->ILS 9901002.00AY1AZFCA7
21/11/2019 05:13:46 ILSport Disconnected by remote host
21/11/2019 05:15:44 ILSport Connected
21/11/2019 05:15:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY5AZF1A0
21/11/2019 05:15:45 From <---- ILS 940AY5AZFDF9
21/11/2019 05:15:45 To-->ILS 9901002.00AY6AZFCA2
21/11/2019 05:15:46 ILSport Disconnected by remote host
21/11/2019 05:17:44 ILSport Connected
21/11/2019 05:17:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY0AZF1A5
21/11/2019 05:17:45 From <---- ILS 940AY0AZFDFE
21/11/2019 05:17:45 To-->ILS 9901002.00AY1AZFCA7
21/11/2019 05:17:46 ILSport Disconnected by remote host
21/11/2019 05:19:44 ILSport Connected
21/11/2019 05:19:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY5AZF1A0
Comment 1 Jonathan Druart 2019-12-10 14:04:59 UTC
Which exact version of Koha are you using?

Does the problem appear after an upgrade? Or is it a fresh installation?
Comment 2 Katrin Fischer 2019-12-11 07:08:57 UTC
Did you set up your SIP user with circulate permissions in Koha and the conf file correctly? (https://koha-community.org/manual/19.11/en/html/apis_protocols.html#sip2)
Comment 3 ciarebaha 2019-12-11 23:28:49 UTC
(In reply to Jonathan Druart from comment #1)
> Which exact version of Koha are you using?
> 
> Does the problem appear after an upgrade? Or is it a fresh installation?

We are using koha version 18.11
It never been upgrade since May 2019
The SIP already running smoothly since September 2019.
However after the event that I mention in 1st post somehow made the SIP failed to operate.
Comment 4 ciarebaha 2019-12-11 23:31:37 UTC
(In reply to Katrin Fischer from comment #2)
> Did you set up your SIP user with circulate permissions in Koha and the conf
> file correctly?
> (https://koha-community.org/manual/19.11/en/html/apis_protocols.html#sip2)

Yes, since this SIP already running since September 2019 & working fine before this, all the login id,password,permission already set up in koha patron & SIPconfig.xml.
Comment 5 Jonathan Druart 2019-12-17 09:27:46 UTC
(In reply to ciarebaha from comment #4)
> (In reply to Katrin Fischer from comment #2)
> > Did you set up your SIP user with circulate permissions in Koha and the conf
> > file correctly?
> > (https://koha-community.org/manual/19.11/en/html/apis_protocols.html#sip2)
> 
> Yes, since this SIP already running since September 2019 & working fine
> before this, all the login id,password,permission already set up in koha
> patron & SIPconfig.xml.

So my guess is that the SIP server is not running, try to start it with:
  % koha-sip --start $INSTANCE
With $INSTANCE the name of you Koha installation.

Lowering severity.
Comment 6 ciarebaha 2020-06-11 04:29:20 UTC
(In reply to Jonathan Druart from comment #5)
> (In reply to ciarebaha from comment #4)
> > (In reply to Katrin Fischer from comment #2)
> > > Did you set up your SIP user with circulate permissions in Koha and the conf
> > > file correctly?
> > > (https://koha-community.org/manual/19.11/en/html/apis_protocols.html#sip2)
> > 
> > Yes, since this SIP already running since September 2019 & working fine
> > before this, all the login id,password,permission already set up in koha
> > patron & SIPconfig.xml.
> 
> So my guess is that the SIP server is not running, try to start it with:
>   % koha-sip --start $INSTANCE
> With $INSTANCE the name of you Koha installation.
> 
> Lowering severity.

The Sip2 service already started but selfcheck cannot established connection with Koha server. It seems failed to login. We got status 940 instead of 941.
Comment 7 Katrin Fischer 2020-06-11 10:22:04 UTC
As you said it worked before: can you check if the user in Koha is still there? Has the right permissions? Is not expired? Password and username correct as defined in your SIP configuration file? Branchcodes correct?
Comment 8 Katrin Fischer 2020-06-11 10:24:22 UTC
We also have 18.11 installations with SIP and so far, the connections work alright. That's why I think this is more a support request, than a bug at this point. You might get more help and ideas bringing this up on the mailing list.