Re: [Koha-devel] Koha SIP Server error message
Mark Actually, I should have added more information. It does, in fact, halt the SIP server and disconnect from the mysql server, so I suspect that it's a bug. thanks for replying. Scott ________________________________ From: Mark Tompsett [mtompset@hotmail.com] Sent: Friday, March 29, 2013 11:20 PM To: Scott Kushner Subject: Re: [Koha-devel] Koha SIP Server error message Greetings, I don’t use SIP, but many of the uninitialized variable type errors in other parts of Koha did not affect processing. I suspect this is the same kind of thing. I was told this is not an error but a warning. After all, and error would prevent what you are attempting from actually working. A warning merely indicates less than perfect code which functions. I’m assuming you read the warning message in the error log files and didn’t actually have your SIP check-in failing. As for it’s annoying nature, you are always welcome to submit a patch to fix it. GPML, Mark Tompsett
On 31 March 2013 02:38, Scott Kushner <skushner@mplmain.mtpl.org> wrote:
Mark
Actually, I should have added more information.
It does, in fact, halt the SIP server and disconnect from the mysql server, so I suspect that it's a bug.
The relevant piece of information then is what version are you running? Chris
Chris, I am running Koha vers. 3.08.11.002 ________________________________________ From: Chris Cormack [chris@bigballofwax.co.nz] Sent: Saturday, March 30, 2013 3:16 PM To: Scott Kushner Cc: Mark Tompsett; koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Koha SIP Server error message On 31 March 2013 02:38, Scott Kushner <skushner@mplmain.mtpl.org> wrote:
Mark
Actually, I should have added more information.
It does, in fact, halt the SIP server and disconnect from the mysql server, so I suspect that it's a bug.
The relevant piece of information then is what version are you running? Chris
On 1 April 2013 02:40, Scott Kushner <skushner@mplmain.mtpl.org> wrote:
Chris,
I am running Koha vers. 3.08.11.002
Right so the warning you pasted before is just a warning, and will not be creating the db disconnect, but it may be a symptom that might help us find what is causing the error. my $var=$context->{"activeuser"}; $var is not being set, presumably because activeuser is not being set Can you check your syslog for the lines that occur just before and after this occurs? Chris
participants (2)
-
Chris Cormack -
Scott Kushner