Re: [Koha] hourly fines not calculating

2023-07-04 Thread Hector Gonzalez Jaime
Tom, you should check your circulation rules, and verify "overdue fines 
cap" is not zero (the default), as it would limit your fines to nothing.


Make sure you have "CalculateFinesOnReturn" on, and "FinesMode" set to 
"Calculate and Charge"


On 7/4/23 10:24, Tom Obrien wrote:

Hi all,
I installed koha 22 on ubuntu 22. Everything works except that Koha is not
calculating hourly fines. The long loan is working very well.
Kindly assist.
Tom
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Fwd: Koha 22.11.05 released

2023-05-29 Thread Hector Gonzalez Jaime

I see this behavior in two unrelated installations.  Both with overdues.

On 5/27/23 17:47, Tomas Cohen Arazi wrote:

Update using the packages.

El sáb, 27 may 2023 16:37, Hector Gonzalez Jaime  
escribió:


Sorry, I didn't copy the list:

Hi, it is strange, I was testing in english, anyway,
koha-translate does
not list english as it is the default language, and doesn't let me
update it.

The system also had another language, which was updated but it still
gives the same set of errors for both:

[Sat May 27 13:27:32.849826 2023] [cgi:error] [pid 6125] [client
192.168.1.1:50078 <http://192.168.1.1:50078>] AH01215: Template
process failed: undef error - :
filter not found at /usr/share/koha/lib/C4/Templates.pm line 127.:
/usr/share/koha/intranet/cgi-bin/circ/branchoverdues.pl
<http://branchoverdues.pl>, referer:
http://bibliotecacho-intra.locales/cgi-bin/koha/circ/circulation-home.pl
[Sat May 27 13:27:32.902038 2023] [cgi:error] [pid 6125] [client
192.168.1.1:50078 <http://192.168.1.1:50078>] End of script output
before headers:
branchoverdues.pl <http://branchoverdues.pl>, referer:
http://bibliotecacho-intra.locales/cgi-bin/koha/circ/circulation-home.pl

This is a test system, so I'm certain there are no other missing
messages in the logs.

I'll try deleting koha and installing it without an upgrade to see if
this still is a problem or if it needs overdue fines to be triggered.


On 5/27/23 01:06, Mason James wrote:
> hi Hector
>
> this problem tests OK for me, on a 22.11.06 KTD instance
>
>
> some suggestions...
>
> 1/ switch your language to 'en', and test problem again
>
> 2/ manually rebuild your koha languages, and test problem again
>
>
>   $ sudo koha-translate --list
>   en
>   fr-FR
>
>
>   $ sudo koha-translate -v --update en
>   $ sudo koha-translate -v --update fr-FR
>
>
>
> On 27/05/23 5:27 am, Hector Gonzalez Jaime wrote:
>> Hello, thanks for all the hard work!
>>
>> I just tried this version on a development server, and get a 500
>> error trying to check overdue fines, this is in the logs:
>>
>> "GET /intranet/circ/branchoverdues.pl
<http://branchoverdues.pl> HTTP/1.1" 500
>>
>> Template process failed: undef error - : filter not found at
>> /usr/share/koha/lib/C4/Templates.pm line 127.
>>
>> It worked well with 22.11.05, and got broken with 22.11.06
>>
>>
>> On 5/26/23 09:00, Renvoize, Martin wrote:
>>> Hello, Bonjour, Kia ora,
>>>
>>> The Koha community is pleased to announce the release of version
>>> 22.11.05.
>>>
>>> This is a security and bugfix maintenance release, including 160
>>> bugfixes!
>>>
>>> Full release notes are available here:
>>> https://koha-community.org/koha-22-11-06-released/
>>>
>>> This is our last release as the stable branch maintainers,
with the
>>> community heading into the next cycle imminently. However,
22.11.x
>>> will be
>>> in the capable hands of Pedro and Matt for the next cycle having
>>> been voted
>>> in as the oldstable maintainers 
>>>
>>> Thanks to anybody involved! 
>>>
>>>
>>> Martin Renvoize, MPhys (Hons)
>>>
>>> Head of Development and Community Engagement
>>>
>>>
>>>
>>> E: martin.renvo...@ptfs-europe.com
>>>
>>> P: +44 (0) 1483 378728
>>>
>>> M: +44 (0) 7725 985636
>>>
>>> www.ptfs-europe.com <http://www.ptfs-europe.com>
>>> ___
>>>
>>> Koha mailing list http://koha-community.org
>>> Koha@lists.katipo.co.nz
>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>>
>
-- 
Hector Gonzalez

ca...@genac.org

___

Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


--
Hector Gonzalez
ca...@genac.org
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Fwd: Koha 22.11.05 released

2023-05-29 Thread Hector Gonzalez Jaime

I have updated with the packages, it's now on 22.11.06-3

It only fails if there are pending fines, I removed the pending fines, 
and it shows the page.  But that page is only for showing overdues.  Do 
you have overdues in your test system?



On 5/27/23 17:47, Tomas Cohen Arazi wrote:

Update using the packages.

El sáb, 27 may 2023 16:37, Hector Gonzalez Jaime  
escribió:


Sorry, I didn't copy the list:

Hi, it is strange, I was testing in english, anyway,
koha-translate does
not list english as it is the default language, and doesn't let me
update it.

The system also had another language, which was updated but it still
gives the same set of errors for both:

[Sat May 27 13:27:32.849826 2023] [cgi:error] [pid 6125] [client
192.168.1.1:50078 <http://192.168.1.1:50078>] AH01215: Template
process failed: undef error - :
filter not found at /usr/share/koha/lib/C4/Templates.pm line 127.:
/usr/share/koha/intranet/cgi-bin/circ/branchoverdues.pl
<http://branchoverdues.pl>, referer:
http://bibliotecacho-intra.locales/cgi-bin/koha/circ/circulation-home.pl
[Sat May 27 13:27:32.902038 2023] [cgi:error] [pid 6125] [client
192.168.1.1:50078 <http://192.168.1.1:50078>] End of script output
before headers:
branchoverdues.pl <http://branchoverdues.pl>, referer:
http://bibliotecacho-intra.locales/cgi-bin/koha/circ/circulation-home.pl

This is a test system, so I'm certain there are no other missing
messages in the logs.

I'll try deleting koha and installing it without an upgrade to see if
this still is a problem or if it needs overdue fines to be triggered.


On 5/27/23 01:06, Mason James wrote:
> hi Hector
>
> this problem tests OK for me, on a 22.11.06 KTD instance
>
>
> some suggestions...
>
> 1/ switch your language to 'en', and test problem again
>
> 2/ manually rebuild your koha languages, and test problem again
>
>
>   $ sudo koha-translate --list
>   en
>   fr-FR
>
>
>   $ sudo koha-translate -v --update en
>   $ sudo koha-translate -v --update fr-FR
>
>
>
> On 27/05/23 5:27 am, Hector Gonzalez Jaime wrote:
>> Hello, thanks for all the hard work!
>>
>> I just tried this version on a development server, and get a 500
>> error trying to check overdue fines, this is in the logs:
>>
>> "GET /intranet/circ/branchoverdues.pl
<http://branchoverdues.pl> HTTP/1.1" 500
>>
>> Template process failed: undef error - : filter not found at
>> /usr/share/koha/lib/C4/Templates.pm line 127.
>>
>> It worked well with 22.11.05, and got broken with 22.11.06
>>
>>
>> On 5/26/23 09:00, Renvoize, Martin wrote:
>>> Hello, Bonjour, Kia ora,
>>>
>>> The Koha community is pleased to announce the release of version
>>> 22.11.05.
>>>
>>> This is a security and bugfix maintenance release, including 160
>>> bugfixes!
>>>
>>> Full release notes are available here:
>>> https://koha-community.org/koha-22-11-06-released/
>>>
>>> This is our last release as the stable branch maintainers,
with the
>>> community heading into the next cycle imminently. However,
22.11.x
>>> will be
>>> in the capable hands of Pedro and Matt for the next cycle having
>>> been voted
>>> in as the oldstable maintainers 
>>>
>>> Thanks to anybody involved! 
>>>
>>>
>>> Martin Renvoize, MPhys (Hons)
>>>
>>> Head of Development and Community Engagement
>>>
>>>
>>>
>>> E: martin.renvo...@ptfs-europe.com
>>>
>>> P: +44 (0) 1483 378728
>>>
>>> M: +44 (0) 7725 985636
>>>
>>> www.ptfs-europe.com <http://www.ptfs-europe.com>
>>> ___
>>>
>>> Koha mailing list http://koha-community.org
>>> Koha@lists.katipo.co.nz
>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
>>
>
-- 
Hector Gonzalez

ca...@genac.org

___

Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


--
Hector Gonzalez
ca...@genac.org
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] Fwd: Koha 22.11.05 released

2023-05-27 Thread Hector Gonzalez Jaime

Sorry, I didn't copy the list:

Hi, it is strange, I was testing in english, anyway, koha-translate does 
not list english as it is the default language, and doesn't let me 
update it.


The system also had another language, which was updated but it still 
gives the same set of errors for both:


[Sat May 27 13:27:32.849826 2023] [cgi:error] [pid 6125] [client 
192.168.1.1:50078] AH01215: Template process failed: undef error - : 
filter not found at /usr/share/koha/lib/C4/Templates.pm line 127.: 
/usr/share/koha/intranet/cgi-bin/circ/branchoverdues.pl, referer: 
http://bibliotecacho-intra.locales/cgi-bin/koha/circ/circulation-home.pl
[Sat May 27 13:27:32.902038 2023] [cgi:error] [pid 6125] [client 
192.168.1.1:50078] End of script output before headers: 
branchoverdues.pl, referer: 
http://bibliotecacho-intra.locales/cgi-bin/koha/circ/circulation-home.pl


This is a test system, so I'm certain there are no other missing 
messages in the logs.


I'll try deleting koha and installing it without an upgrade to see if 
this still is a problem or if it needs overdue fines to be triggered.



On 5/27/23 01:06, Mason James wrote:

hi Hector

this problem tests OK for me, on a 22.11.06 KTD instance


some suggestions...

1/ switch your language to 'en', and test problem again

2/ manually rebuild your koha languages, and test problem again


  $ sudo koha-translate --list
  en
  fr-FR


  $ sudo koha-translate -v --update en
  $ sudo koha-translate -v --update fr-FR



On 27/05/23 5:27 am, Hector Gonzalez Jaime wrote:

Hello, thanks for all the hard work!

I just tried this version on a development server, and get a 500 
error trying to check overdue fines, this is in the logs:


"GET /intranet/circ/branchoverdues.pl HTTP/1.1" 500

Template process failed: undef error - : filter not found at 
/usr/share/koha/lib/C4/Templates.pm line 127.


It worked well with 22.11.05, and got broken with 22.11.06


On 5/26/23 09:00, Renvoize, Martin wrote:

Hello, Bonjour, Kia ora,

The Koha community is pleased to announce the release of version 
22.11.05.


This is a security and bugfix maintenance release, including 160 
bugfixes!


Full release notes are available here:
https://koha-community.org/koha-22-11-06-released/

This is our last release as the stable branch maintainers, with the
community heading into the next cycle imminently. However, 22.11.x 
will be
in the capable hands of Pedro and Matt for the next cycle having 
been voted

in as the oldstable maintainers 

Thanks to anybody involved! 


Martin Renvoize, MPhys (Hons)

Head of Development and Community Engagement



E: martin.renvo...@ptfs-europe.com

P: +44 (0) 1483 378728

M: +44 (0) 7725 985636

www.ptfs-europe.com
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha





--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Koha 22.11.05 released

2023-05-26 Thread Hector Gonzalez Jaime
Your problem looks like koha-plack is not running, you should try 
restarting it.


On 5/26/23 13:02, Thomas Sycko-Miller wrote:

I'm getting a similar error when trying to view biblio details in staff
client:

[Fri May 26 13:54:25.843357 2023] [proxy:error] [pid 2474] (2)No such file
or directory: AH02454: http: attempt to connect to Unix domain socket
/var/run/koha/library/plack.sock (localhost) failed
[Fri May 26 13:54:25.843460 2023] [proxy_http:error] [pid 2474] [client
999.999.999.999:55178] AH01114: HTTP: failed to make connection to backend:
httpd-UDS

--


On Fri, May 26, 2023 at 1:28 PM Hector Gonzalez Jaime 
wrote:


Hello, thanks for all the hard work!

I just tried this version on a development server, and get a 500 error
trying to check overdue fines, this is in the logs:

"GET /intranet/circ/branchoverdues.pl HTTP/1.1" 500

Template process failed: undef error - : filter not found at
/usr/share/koha/lib/C4/Templates.pm line 127.

It worked well with 22.11.05, and got broken with 22.11.06


On 5/26/23 09:00, Renvoize, Martin wrote:

Hello, Bonjour, Kia ora,

The Koha community is pleased to announce the release of version

22.11.05.

This is a security and bugfix maintenance release, including 160

bugfixes!

Full release notes are available here:
https://koha-community.org/koha-22-11-06-released/

This is our last release as the stable branch maintainers, with the
community heading into the next cycle imminently. However, 22.11.x will

be

in the capable hands of Pedro and Matt for the next cycle having been

voted

in as the oldstable maintainers 

Thanks to anybody involved! 


Martin Renvoize, MPhys (Hons)

Head of Development and Community Engagement



E: martin.renvo...@ptfs-europe.com

P: +44 (0) 1483 378728

M: +44 (0) 7725 985636

www.ptfs-europe.com
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Koha 22.11.05 released

2023-05-26 Thread Hector Gonzalez Jaime

Hello, thanks for all the hard work!

I just tried this version on a development server, and get a 500 error 
trying to check overdue fines, this is in the logs:


"GET /intranet/circ/branchoverdues.pl HTTP/1.1" 500

Template process failed: undef error - : filter not found at 
/usr/share/koha/lib/C4/Templates.pm line 127.


It worked well with 22.11.05, and got broken with 22.11.06


On 5/26/23 09:00, Renvoize, Martin wrote:

Hello, Bonjour, Kia ora,

The Koha community is pleased to announce the release of version 22.11.05.

This is a security and bugfix maintenance release, including 160 bugfixes!

Full release notes are available here:
https://koha-community.org/koha-22-11-06-released/

This is our last release as the stable branch maintainers, with the
community heading into the next cycle imminently. However, 22.11.x will be
in the capable hands of Pedro and Matt for the next cycle having been voted
in as the oldstable maintainers 

Thanks to anybody involved! 


Martin Renvoize, MPhys (Hons)

Head of Development and Community Engagement



E: martin.renvo...@ptfs-europe.com

P: +44 (0) 1483 378728

M: +44 (0) 7725 985636

www.ptfs-europe.com
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Fwd: Dead Koha Resuscitation

2023-05-19 Thread Hector Gonzalez Jaime


On 5/18/23 20:46, Bruce A. Metcalf wrote:

On 5/18/23 21:35, Hector Gonzalez Jaime wrote:


What does sudo koha-plack --start instancename Do?


root@store:/usr/sbin# koha-plack --start library bash: koha-plack:
command not found

Which seems even more weird. Are the permissions wrong?


You are still missing /usr/sbin in your PATH variable.



That's been added.

It mighty not have been added permanently.  start-stop-daemon is at 
/sbin, which means that one is missing from your PATH.


to verify what is on your path, you can type:  echo $PATH

if it is missing any of the directorios, add it with: 
PATH=/sbin:/usr/sbin:$PATH, followed by export PATH


it might be part of .bashrc, but if you are editing root's one, you 
might want to check your regular user's .bashrc first.





The command would have run if you had typed:

/usr/sbin/koha-plack --start library



Let me try:

root@store:/usr/sbin# /usr/sbin/koha-plack --start library
/usr/share/koha/bin/koha-functions.sh: line 285: start-stop-daemon: 
command not found

[ ok ] Starting Plack daemon for library:.

Okay, a step forward, but a new challenge. (Been a lot of that in this 
project!)


Line 285 is:

if start-stop-daemon --pidfile 
"/var/run/koha/${instancename}/plack.pid" \


File /var/run/koha/library/plack.pid does exist. It contains a 
five-digit number only.


Okay, I'm stuck again!

Thanks again for all the help.

Regards,
/ Bruce /
Bruce A. Metcalf, Librarian
The Augustan Library


your system seems to be in a strange situation, you might want to 
uninstall koha, remove all dependencies, and install it again:


apt-get remove koha-common <- this does not affect your database
or configuration files. apt-get autoremove <- this
deletes every dependency that is no longer needed, which should be a
ton of perl libraries. apt-get install koha-common  <- this
should reinstall koha, and every one of its dependencies.  If your
system has problems, this command would eventually fail.

If this last command fails, I'd like to see the contents of your 
/etc/apt/sources.list file and every file at /etc/apt/sources.list.d




Regards, / Bruce / Bruce A. Metcalf, Librarian The Augustan
Library ___

Koha mailing list  http://koha-community.org Koha@lists.katipo.co.nz 
Unsubscribe:

https://lists.katipo.co.nz/mailman/listinfo/koha



___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Fwd: Dead Koha Resuscitation

2023-05-18 Thread Hector Gonzalez Jaime


On 5/18/23 19:18, Bruce A. Metcalf wrote:

On 5/18/23 17:35, Chris Cormack wrote:


What does
sudo koha-plack --start instancename
Do?



root@store:/home/bruce# koha-plack --start library
bash: koha-plack: command not found

Which I thought was pretty odd, so I went to the /usr/sbin directory, 
and:


root@store:/usr/sbin# ls -l koha-p*
-rwxr-xr-x 1 root root 13538 May 13 23:26 koha-plack

then

root@store:/usr/sbin# koha-plack --start library
bash: koha-plack: command not found

Which seems even more weird. Are the permissions wrong?
You are still missing /usr/sbin in your PATH variable.  You seem to be 
running bash:


export PATH=/sbin:/usr/sbin:$PATH

(bash can do this in one line).  Copy the command exactly, CAPS are 
important here.  Linux does not have the current directory in your PATH, 
which means it will not run a command from the directory you are at 
(this may feel strange if you come from a windows environment, but is 
normal)  The command would have run if you had typed:


/usr/sbin/koha-plack --start library

your system seems to be in a strange situation, you might want to 
uninstall koha, remove all dependencies, and install it again:


apt-get remove koha-common <- this does not affect your database or 
configuration files.
apt-get autoremove <- this deletes every dependency that is 
no longer needed, which should be a ton of perl libraries.
apt-get install koha-common  <- this should reinstall koha, and 
every one of its dependencies.  If your system has problems, this 
command would eventually fail.


If this last command fails, I'd like to see the contents of your 
/etc/apt/sources.list file and every file at /etc/apt/sources.list.d




Regards,
/ Bruce /
Bruce A. Metcalf, Librarian
The Augustan Library
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Fwd: Dead Koha Resuscitation

2023-05-18 Thread Hector Gonzalez Jaime


On 5/18/23 13:46, Bruce A. Metcalf wrote:

On 5/18/23 14:52, David Liddle wrote:

Hello, Bruce. You've been good about chasing down the information 
folks have asked for. I'm sorry that we haven't brought you closer

to a solution.



I'm no less appreciative of your efforts for that.



I have some follow-up questions:

1.a. Database. Once you listed the databases, did you exit the mysql 
prompt and back up the koha_library database with the mysqldump command?



Yes, and it appeared to work. I have a 450MB file called backup.sql.



1.b.Can you use an FTP client such as FileZilla to download such files?



I assume so.



2.a. Path. What is the result of this command? env | grep -i 'path'



root@store:/# env | grep -i 'path'
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

I am aware that the path should contain several sbin directories, but I
don't know how to add them.


with these commands:

PATH=/sbin:/usr/sbin:$PATH
export PATH

Assuming you are using some variant of /bin/sh

You might edit your .bashrc and add that at the end of the file, and 
login again, or use "source ~/.bashrc " to process the file in your session.





2.b. Path. Did you already establish that the Koha commands are or 
are not installed? ls /usr/sbin/koha*



Yes, the usual list of commands is there. This suggests to me that the
inadequate PATH command is at least part of my problem.


3. Repository and deb. Did you run "apt update" before running 
"apt-get install --reinstall koha-common"?



Yes. The resultant is:

root@store:/# apt-get update && apt-get install --reinstall koha-common
[some lines skipped]
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 koha-common : Depends: libtest-dbix-class-perl but it is not going to
be installed
E: Unable to correct problems, you have held broken packages.




You should try:  apt-get dist-upgrade which would install the 
missing dependencies.  Also apt-get -f install should fix that too.




The current version is 21.11.20.



Right, but I haven't been able to employ any earlier version, either.


Yes, koha-common appears to be running, though maybe I'm reading it 
wrong. Have you checked the Apache config file for your instance, 
probably /etc/apache2/sites-available/library.conf



There are two links in that file, one for the OPAC and one for admin 
access.




SSL Certificate information will be important.



There is no mention of SSL Certificates in the file.


There are also Apache-related config files in /etc/koha, which I 
think could have been overwritten in the upgrade; that may or may

not be important.



There are such files. I don't know what to make of them.



5. This situation is a good opportunity to research and document the
elements on the server that you need to back up manually and download
in the event that you need to rebuild the server from scratch. I'm
guessing you don't do this work full-time, but having this
information written will save you and/or your successor a lot of time
when that day comes.



Yeah, I should be so lucky as to have someone take over for me!  
The organization is a non-profit with declining participation.




Is this hosted server just running: 1. the main website (what
platform or site-building tool?), 2. a wiki (MediaWiki?), and 3.
Koha? That backup will probably come down to the databases you've
listed and one or more directories for each service.



The virtual server is running an Online Store, a Wiki, and Koha. Minor 
file storage is all else that's there.



What I suspect at this point is that I need to add the sbin 
directories to the PATH. Can someone point me to a tutorial?


Regards,
/ Bruce /
Bruce A. Metcalf, Librarian
The Augustan Library
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Fwd: Dead Koha Resuscitation

2023-05-16 Thread Hector Gonzalez Jaime


On 5/16/23 10:51, Bruce A. Metcalf wrote:

On 5/15/23 16:41, Galen Charlton wrote:


3. Can I install a new instance in the same virtual machine and
transfer the settings and data?


Almost everything worth permanently keeping in a typical Koha system
is stored in the database. Is MySQL/MariaDB running and can you get a
 mysqldump?



I'm not sure. How can one tell? There is a MySQL instance running, but 
I suspect that may be for one of the other servers. There is no 
MariaDB running, which I recall having switched to some time back.


Can I buy a clue about how to run mysqldump?


MariaDB's process name is mysql, it doesn't matter much which you are using.

you can make a backup wich mysqldump like this:

mysqldump -u root -p --all-databases > backup.sql

you should run this command from a directory with enough space to hold a 
backup of your database.


you can reinstall koha-common by issuing this command:

sudo apt-get install --reinstall koha-common

it should pull any missing dependencies.

Have you tried to backup your koha instance with "koha_dump" ? if your 
library instance is called "thisone", use:  sudo koha_dump thisone


it should put the backup on /var/spool/koha/thisone/

This process creates a mysqldump backup of just your database, and 
copies the rest of your koha files to a tar file.  Those files can be 
used with koha_restore but if they can be made, your koha should be good 
enough for you to repair it.






If not, are there at least database files present in /var/lib/mysql?



If /var/lib/mysql/ibdata1 is the right file, then yes. It's almost a 
GB in size, which seems reasonable for the library's data.




A current copy of the database could be imported into a fresh install
of Koha (either in a new VM or after a wipe and recreation of the
existing one - though if you do a wipe, triple-check that your
database export is good!).



Right. Tried to delete Koha and reinstall, but there was no change in 
the resultant. Wiping the whole VM is impractical due to the other 
servers on it, though that may prove necessary.


I continue to suspect that the problem lies with the upgrades from 
Debian 9 to 10 and Koha 21.05 to 21.11. Something didn't upgrade 
correctly, or there's a hidden incompatibility, that's stopping work.


Thanks for the ideas.

Respectfully,
/ Bruce /
Bruce A. Metcalf, Librarian
The Augustan Library
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Koha mysql DBMS fix

2023-03-22 Thread Hector Gonzalez Jaime
You need to add a line to one of mysql's configuration files, you may 
create one just for this, the complete file would look like:


[mysqld]
init-file = /var/lib/mysql/init-file_library.sql

you may change "library" with your own libraries name.

And you must create that file, with the sql from the wiki.

from the error message, my guess is your sysadmin put this line outside 
the scope of a [mysqld] section.  [mysql] is not good enough, as it 
refers to mysql's CLIENT program, not your database server.



On 3/21/23 20:59, Decka David wrote:

Dear Koha Community,

Here is a problem that someone here in this community might come across or
know to share how to solve this problem; I talked with my ICT administrator
to solve this issue to have access to the koha mysql but was unable to do
so to fix the DBMS auto increment problem. The issue  of the "unknown
variable" in the script is;

*mysql: [ERROR] unknown variable
'init-file=/var/lib/mysql/init-file_koha_library.sql'*

I can do the mysqldump and run the backup on the test server but on the
production server, I have no access at all.
Looking into the past forum emails, wikis there is not much help.

Thanking everyone here in advance for their invaluable insight and pointing
me towards solving the problem.

Kind regards



*Decka David*
Matheson Librarian | PNG University of Technology | PMB | Lae, 411 | Morobe
Province | PAPUA NEW GUINEA
Alternate E: decka.da...@gmail.com | P: 657 4734353 <%28657%29%20473-4353> |
F: 675 4374363
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] cron problem with automatic_checkin after update to 22.05

2023-03-01 Thread Hector Gonzalez Jaime

Thank you, the script found a lot of those.

On 3/1/23 03:44, Jonathan Druart wrote:
Make sure you have an item type for all your items. There is a script 
that can help you to catch them: 
misc/maintenance/search_for_data_inconsistencies.pl 
<http://search_for_data_inconsistencies.pl>


Le mar. 28 févr. 2023 à 22:36, Hector Gonzalez Jaime  
a écrit :


Hi, we recently updated our system to 22.05 and since then we
receive this error from cron:

/etc/cron.hourly/koha-common:
Can't call method "automatic_checkin" on an undefined value at
/usr/share/koha/lib/Koha/Checkouts.pm line 85.
kamoxtin: 11 status returned by
"/usr/share/koha/bin/cronjobs/automatic_checkin.pl
<http://automatic_checkin.pl>"

both files seem to be up to date.  Is this a known issue?  I can't
find any reference to it or reported bugs.

-- 
Hector Gonzalez

ca...@genac.org

___

Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] cron problem with automatic_checkin after update to 22.05

2023-02-28 Thread Hector Gonzalez Jaime

Hi, we recently updated our system to 22.05 and since then we receive this 
error from cron:

/etc/cron.hourly/koha-common:
Can't call method "automatic_checkin" on an undefined value at 
/usr/share/koha/lib/Koha/Checkouts.pm line 85.
kamoxtin: 11 status returned by 
"/usr/share/koha/bin/cronjobs/automatic_checkin.pl"

both files seem to be up to date.  Is this a known issue?  I can't find any 
reference to it or reported bugs.

--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] difficulties authenticating after samba/openldap -> samba4 AD migration with koha

2021-12-13 Thread Hector Gonzalez Jaime

Try removing id="dc1" from the ldapserver line, so it looks like this:




On 12/12/21 10:53 AM, Web Developer wrote:

help me to solve this.

On Sat, 11 Dec 2021 at 22:23, Web Developer  wrote:


Hello Team,


I am trying to authenticate samba4/AD to koha LDAP but I am getting the
following error.


However, I can't login, koha OPAC log says  : LDAP search failed to return
object : 2020: Operation unavailable without authentication at
/usr/share/test_koha/lib/C4/Auth_with_ldap.pm line 98.


So, before I start doing bigger things (like updating koha, which has
always been running fine) I'd like to know if I'm missing something
obvious? I'm sure many people here are using (native) active directory
to authenticate to? Any tips..?

Here is my AD samba4 config:

   
  dc1.my.domain
  CN=Users,DC=samba,DC=my,DC=domain
  username
 password

  1
  1
  1

CN=%s,CN=Users,DC=samba,DC=my,DC=domain

  


  


Regards,
Amar


___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] LDAP changes from 19.xx to 21.05 ?

2021-10-12 Thread Hector Gonzalez Jaime
I'm using the debian package, and upgraded with  apt-get update; apt-get 
dist-upgrade.  Just ran them again now and it doesn't update 
koha-common, so I should be at the last 21.05.xx version, dpkg reports 
it is: 21.05.04-1


The upgrade itself didn't show any errors, but plack-error.log was 
filled with that one about ldapserver, so I created a new koha site, and 
used that configuration file to adapt our old configuration to the new 
koha version, but just copied the LDAP part over as it was untouched.


After reading the bug report I removed id="ldapserver" and 
listenref="ldapserver" from my configuration and it works now.



On 10/12/21 2:31 AM, Jonathan Druart wrote:

Looks like you hit bug 28385, but it's supposed to be fixed on 21.05.
Are you using the debian package? How did you upgrade?

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28385

Le mar. 12 oct. 2021 à 02:17, Hector Gonzalez Jaime  a écrit :

Hello, we recently tried to update our development server to 21.05, and
it mostly works, but it does not like our LDAP setup, which is unchanged.

plack-error.log is filled with errors from this one:

Error while loading /etc/koha/plack.psgi: No ldapserver "hostname"
defined in KOHA_CONF: /etc/koha/sites/clavius/koha-conf.xml at
/usr/share/koha/lib/C4/Auth_with_ldap.pm line 58,  line 755.

Now, we did not touch our LDAP configuration, which was correct and
working with 19.11.  Can somebody help find out what changed? Our ldap
configuration is like this now:


   
  ip.address.for.server
  ou=users,dc=domain,dc=example,dc=org
  1
  1   
  1
uid=%s,ou=users,dc=domain,dc=example,dc=org
   



Tijuana, BCN

TJNA




STUDENT
    1
  
    

Thanks.

--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] LDAP changes from 19.xx to 21.05 ?

2021-10-11 Thread Hector Gonzalez Jaime
Hello, we recently tried to update our development server to 21.05, and 
it mostly works, but it does not like our LDAP setup, which is unchanged.


plack-error.log is filled with errors from this one:

Error while loading /etc/koha/plack.psgi: No ldapserver "hostname" 
defined in KOHA_CONF: /etc/koha/sites/clavius/koha-conf.xml at 
/usr/share/koha/lib/C4/Auth_with_ldap.pm line 58,  line 755.


Now, we did not touch our LDAP configuration, which was correct and 
working with 19.11.  Can somebody help find out what changed? Our ldap 
configuration is like this now:



 
    ip.address.for.server
    ou=users,dc=domain,dc=example,dc=org
    1
    1   
    1
uid=%s,ou=users,dc=domain,dc=example,dc=org
     

  
  
  
  Tijuana, BCN
  
  TJNA
  
  
  
  
  STUDENT
  1
    
  

Thanks.

--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] How to Update and Upgrade Koha

2021-09-22 Thread Hector Gonzalez Jaime
Hi, I'd like to, but I didn't have an account for the wiki, so I'm 
waiting for it to be enabled.


On 9/20/21 4:47 AM, Jonathan Druart wrote:

Hi Hector, Well detailed instructions, it would help to have them on
the wiki page :)
Would you mind updating the existing section?
https://wiki.koha-community.org/wiki/Koha_on_Debian#Upgrade


--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] How to Update and Upgrade Koha

2021-09-15 Thread Hector Gonzalez Jaime
I forgot something, if koha requires additional software to be 
installed, when you run apt-get upgrade it will say something like this:


The following packages have been kept back:
  koha-common

In this case, you will need to do:

apt-get dist-upgrade

which will install the needed packages and then it will upgrade koha.


On 9/15/21 6:25 PM, Hector Gonzalez Jaime wrote:
Hi, as with anything else, you should first have a good (tested) 
backup of everything.  Koha, server software, and database.


Then, if you used the debian packages, you should check which version 
you are "tracking", something like:


grep -Ri koha /etc/apt/*

would return something like:

/etc/apt/sources.list.d/koha.list:deb 
http://debian.koha-community.org/koha 19.11 main


That means there is a file /etc/apt/sources.list.d/koha.list which you 
should edit and change to the version you want to track now. The 
content of the file would be:


deb http://debian.koha-community.org/koha 21.05 main

if you want to track koha 21.05

Then you would:

apt-get update
apt-get upgrade

and it should do the upgrade.  With the following exception, if 
apt-get upgrade says it would need to update mariadb-server or 
mysql-server, then you should upgrade that first and separately, like 
this:


apt-get update
apt-get install mariadb-server-10.3
apt-get upgrade

If you don't upgrade mariadb first, it will be DOWN when koha wants to 
upgrade the database, leaving you with a half upgraded system.  (And 
using that backup).


Hope this helps.

On 9/15/21 6:04 PM, Charles Kelley wrote:

Hi, all!

 I think I have asked about this before, but I don't recall 
getting a

definitive answer. But it's awhile, so here goes.

 I have seen announcements about updates and upgrades to Koha. 
("Come

and get it!") Alas, I don't find instructions for installing updates and
upgrades. There are initial installation instructions aplenty, but 
alas, if

there are ones for updates and upgrades, I don't see them. So I ask:

 How does one update or upgrades Koha?

 Thanks for your help, everyone.


--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] How to Update and Upgrade Koha

2021-09-15 Thread Hector Gonzalez Jaime
Hi, as with anything else, you should first have a good (tested) backup 
of everything.  Koha, server software, and database.


Then, if you used the debian packages, you should check which version 
you are "tracking", something like:


grep -Ri koha /etc/apt/*

would return something like:

/etc/apt/sources.list.d/koha.list:deb 
http://debian.koha-community.org/koha 19.11 main


That means there is a file /etc/apt/sources.list.d/koha.list which you 
should edit and change to the version you want to track now.  The 
content of the file would be:


deb http://debian.koha-community.org/koha 21.05 main

if you want to track koha 21.05

Then you would:

apt-get update
apt-get upgrade

and it should do the upgrade.  With the following exception, if apt-get 
upgrade says it would need to update mariadb-server or mysql-server, 
then you should upgrade that first and separately, like this:


apt-get update
apt-get install mariadb-server-10.3
apt-get upgrade

If you don't upgrade mariadb first, it will be DOWN when koha wants to 
upgrade the database, leaving you with a half upgraded system.  (And 
using that backup).


Hope this helps.

On 9/15/21 6:04 PM, Charles Kelley wrote:

Hi, all!

 I think I have asked about this before, but I don't recall getting a
definitive answer. But it's awhile, so here goes.

 I have seen announcements about updates and upgrades to Koha. ("Come
and get it!") Alas, I don't find instructions for installing updates and
upgrades. There are initial installation instructions aplenty, but alas, if
there are ones for updates and upgrades, I don't see them. So I ask:

 How does one update or upgrades Koha?

 Thanks for your help, everyone.


--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Connection to memcached servers failed after update to 19.11.04

2020-04-07 Thread Hector Gonzalez Jaime

Alvaro, this happens during upgrades, It doesn´t seem to be a problem.

The upgrade uses koha-conf-site.xml.in   instead of your own files, 
which remain correct after the upgrade.


--
Hector Gonzalez

On 04/04/20 14:34, Alvaro Cornejo wrote:

Hi

I have just updated koha from 19.11.02 to 19.11.04 and got the following
erors during update.

Upgrade to 19.11.04.000 done (19.11.04 release)

Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are the
unix  socket permissions set properly? Is the host
reachable?
If you ignore this warning, you will face performance issues

Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are the
unix  socket permissions set properly? Is the host
reachable?
If you ignore this warning, you will face performance issues
Updated the es-ES translations.

Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are the
unix  socket permissions set properly? Is the host
reachable?
If you ignore this warning, you will face performance issues

Connection to the memcached servers '__MEMCACHED_SERVERS__' failed. Are the
unix  socket permissions set properly? Is the host
reachable?
If you ignore this warning, you will face performance issues
Updated the fr-FR translations.

An process check shows:
ps -ef |grep memcach
memcache   676 1  0 Apr02 ?00:03:10 /usr/bin/memcached -m 64 -p
11211 -u memcache -l 127.0.0.1 -P /var/run/memcached/memcached.pid

Koha about page shows Memcached is working. Can I safely ignore those erors?

Koha version: 19.11.04.000
PSGI: Plack (deployment)
Memcached: Servers: 127.0.0.1:11211 | Namespace: koha_library | Status:
running. | Config read from: koha-conf.xml



Regards,

Alvaro

||
*7* Switch off as you go / Apaga lo que no usas /  Débranchez au fur et à
mesure.
  *q *Recycle always / Recicla siempre / Recyclez toujours
  P Print only if absolutely necessary / Imprime solo si es necesario /
Imprimez seulement si nécessaire
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] koha 19.05 uninitialized string problems.

2019-07-03 Thread Hector Gonzalez
Hi, we recently updated to 19.05 and now see a very big number of these errors 
in plack-error.log, it happens with two very different systems at different 
libraries.

Is this a known problem for 19.05?

Use of uninitialized value in concatenation (.) or string at 
/usr/share/koha/lib/Koha/Biblio.pm line 578.
Use of uninitialized value in concatenation (.) or string at 
/usr/share/koha/lib/C4/Auth.pm line 584.

This is a count of the most relevant in the last couple days:

Times_seen - Error message
608 - Use of uninitialized value in string eq at 
/usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line 797.
608 - Use of uninitialized value in string eq at 
/usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line 798.
802 - Use of uninitialized value in string ne at 
/usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line 905.
896 - Use of uninitialized value in string eq at 
/usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line 801.
896 - Use of uninitialized value in string eq at 
/usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line 802.
   1234 - Use of uninitialized value in string ne at 
/usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line 794.
   1723 - Use of uninitialized value in string ne at 
/usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line 909.
   2468 - Use of uninitialized value in string ne at 
/usr/share/koha/intranet/cgi-bin/cataloguing/additem.pl line 798.
   5973 - Use of uninitialized value in concatenation (.) or string at 
/usr/share/koha/lib/Koha/Biblio.pm line 578.
  19001 - Use of uninitialized value in concatenation (.) or string at 
/usr/share/koha/lib/C4/Auth.pm line 584.
9018495 - Use of uninitialized value in join or string at 
/usr/share/koha/intranet/cgi-bin/reports/guided_reports.pl line 899.


--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Koha Ldap Auth

2019-06-25 Thread Hector Gonzalez


> On Jun 25, 2019, at 8:28 AM, Daniele Piccoli  
> wrote:
> 
> Il 24/06/19 21:30, Hector Gonzalez ha scritto:
>> Hi Daniele
> 
> Hi
> 
>>> On Jun 24, 2019, at 4:22 AM, Daniele Piccoli  
>>> wrote:
>>> 
>>> Software error:
>>> Error reading file /etc/koha/sites/biblioname/koha-conf.xml.
>>> Try running this again as the koha instance user (or use the koha-shell
>>> command in debian)
>> 
>> 
>> Is the file readable by koha?  Permissions should be 640, with user root and 
>> biblioname-koha as the group (if that is the group that owns koha).
> 
> The file is readable by Koha and in fact it has the correct permission
> as you said.

Ok, then try making these changes:


*IP-OF-DC* >
ou=Users,dc=*sub*,dc=*domain*,dc=*tld*
1
1
1
0
uid=%s@*sub*.*domain*.*tld*
 record field names -->
  
  
  
  YOURLIBRARYCODEinKoha
STUDENT
 


1. change the hostname to the actual hostname of the ldap server, if it is 
using ldaps, it might want to check the certificate, and that is based on the 
name.
2. remove the  and  tags, as you are using auth_by_bind.  (I don´t 
know if they are needed for  so you might want to leave that there).
3. Add a line that says: 0  which is needed 
with AD logins when you are using auth_by_bind  (sounds weird, but it works 
that way)
4. Change principal_name, the format is 
%s@*your.domain.name* which is needed with AD 
too.  It looks like an email address.
5. Add a mapping for "categorycode" with the text of the main user category 
(staff, students, faculty...)  It IS required for login, and is assigned to the 
user automatically.
6. Add the branchcode for the library.

Also, I would change the userid mapping to   which is a unique name for every user with AD.
If it still gives you trouble, check the tags above and below your ldap 
configuration, and be sure those were not affected by editing the file.

>> 
> 
> Daniele
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Koha Ldap Auth

2019-06-24 Thread Hector Gonzalez
Hi Daniele

> On Jun 24, 2019, at 4:22 AM, Daniele Piccoli  
> wrote:
> 
> Software error:
> Error reading file /etc/koha/sites/biblioname/koha-conf.xml.
> Try running this again as the koha instance user (or use the koha-shell
> command in debian)


Is the file readable by koha?  Permissions should be 640, with user root and 
biblioname-koha as the group (if that is the group that owns koha).


--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] (no subject)

2019-06-11 Thread Hector Gonzalez


> On Jun 5, 2019, at 11:02 PM, Charles Kelley  wrote:
> 
> $ sudo koha-remove mylibrary
> 
>The report was
> 
> ERROR 1133 (28000) at line 1: Can’t find any matching row in the user table
> 
>Any other suggestions?
> 
I recently had to do this again for an upgrade, and found this exact error.  It 
means the mysql user koha_mylibrary exists, but does not have a password 
assigned, so it can´t be found and erased properly.

you can add a password (it doesn´t matter which you use, it will be removed 
with koha-remove mylibrary), from mysql, with: 

grant all on koha_mylibrary.* to koha_mylibrary@localhost identified with 
'thispasswordwillberemovedbykoha-remove';

then koha-remove should be able to work.


>Hope all are well and all is well.
> 
>— Charles.
> 
>Charles Kelley
>PSC 704 Box 1029
>APO AP 96338
> 
>011-81-80-4714-5490 [JPN cell]
> 
>mnogoja...@aol.com 
>cmkelley...@gmail.com 
> 
>www.linkedin.com/in/cmkelleymls 
>Meeting Your Information Needs. Virtually.

--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] (no subject)

2019-06-06 Thread Hector Gonzalez

> On Jun 5, 2019, at 11:02 PM, Charles Kelley  wrote:
> 
> Hello, all
> 
>In our latest exchange, on June 6, 2019, at 9:00 AM, Héctor González wrote:
> 
>> Not so grand!  This means the user it is trying to create to grant database 
>> privileges is already there, and it won´t continue.  You should first make 
>> sure everything is clean of your previous attempts, or it will not proceed.
>> 
>> You should check mysql, and drop the user and the database if they exist 
>> before running that command again.
>> 
>> koha-remove can help you remove a previous installation attempt.
> 
>Sorry but this did not help. I typed in the terminal
> 
> $ sudo koha-remove mylibrary
> 
>The report was
> 
> ERROR 1133 (28000) at line 1: Can’t find any matching row in the user table
> 
>Any other suggestions?

Try sudo koha-remove --keep-mysql mylibrary  
so it doesn´t try to remove the mysql part, then check mysql, and see if the 
database is there or not.  If it is there, drop it, and then start again.  

The message indicates that the mysql user koha creates is not there, so this 
part is already done, and should be skipped.

The original message your system showed was about the linux user, which should 
also be deleted to proceed.

Your koha looks like it is in a half installed state, so you need to try and 
make it clean again.  You could also change the name of the library 
configuration, but the old files would be left there.

If this is just a development server, the fastest route might be to do:

sudo koha-create --create-db myotherlibrary


> 
>Hope all are well and all is well.
> 
>— Charles.
> 
>Charles Kelley
>PSC 704 Box 1029
>APO AP 96338
> 
>011-81-80-4714-5490 [JPN cell]
> 
>mnogoja...@aol.com
>cmkelley...@gmail.com
> 
>www.linkedin.com/in/cmkelleymls
>Meeting Your Information Needs. Virtually.
> 
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] User MyLibrary Already Exists

2019-06-05 Thread Hector Gonzalez


> On Jun 4, 2019, at 9:47 PM, Charles Kelley  wrote:
> 
> Hello, all
> 
>My new library is thinking of migrating to Koha and I am installing it on 
> a development machine before installing it on the production machine. I have 
> reached this stage in the installation instructions, to wit:
> 
> $ sudo koha-create --create-db mylibrary
> 
>The response is 
> 
> User mylibrary-koha already exists.
> 
>Grand! I proceed to the next instruction, to wit:

Not so grand!  This means the user it is trying to create to grant database 
privileges is already there, and it won´t continue.  You should first make sure 
everything is clean of your previous attempts, or it will not proceed.

You should check mysql, and drop the user and the database if they exist before 
running that command again.

koha-remove can help you remove a previous installation attempt.


> 
> Retrieve the admin username and password from 
> /etc/koha/sites/mylibrary/koha-conf.xml
> 
>So I look for the username and password in that file. A directory 
> /etc/koha/sites/mylibrary does indeed exist; but mylibrary turns out to be 
> devoid of all files, and koha-conf.xml consequently nonexistent. What went 
> wrong? How does one fix this?
> 
>Thank you for the help.
> 
>— Charles.
> 
>Charles Kelley
>PSC 704 Box 1029
>APO AP 96338
> 
>011-81-80-4714-5490 [JPN cell]
> 
>mnogoja...@aol.com
>cmkelley...@gmail.com
> 
>www.linkedin.com/in/cmkelleymls
>Meeting Your Information Needs. Virtually.
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Upgrading from Koha 17.11 to 18.11 --- anything to watch out for?

2019-04-01 Thread Hector Gonzalez
Hello, you should have a complete backup that you trust and know how to 
restore.  Both the database and the host files.

Also, if the upgrade includes your database server, the upgrade may fail, as 
the upgrade might turn mysql off and leave it off while other packages -like 
koha-common- get upgraded, and koha-common requires mysql to be up, in order to 
upgrade your database schema.  Make sure your mysql/mariadb packages are 
upgraded before letting koha upgrade.

Other than that, it should be that simple.

Hector Gonzalez.

> On Mar 31, 2019, at 1:09 PM, Chris Brown  wrote:
> 
> Hello,
> 
> We are currently running Koha 17.11 (installed from Debian packages) on
> Debian 9.3, and we want to upgrade to Koha 18.11
> 
> Is it really as simple as:
> 
> sudo apt-get update
> sudo apt-get upgrade
> 
> or is there anything else I need to watch out for? For example, do I need
> to take action to update the database schema?
> 
> Best Regards,
> 
> Chris Brown
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha


___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] LDAP authentication problem

2019-03-19 Thread Hector Gonzalez

> On Mar 18, 2019, at 9:55 AM, Lichtsteiner Patric (lici)  wrote:
> 
> Hi all,
> 
> We are currently evaluating koha for our university.
> 
> Right now, I’m trying to configure ldap authentication. I followed the 
> following guides:
> https://openschoolsolutions.org/koha-ldap-setup/
> https://perldoc.koha-community.org/C4/Auth_with_ldap.html
> 
> I did the following configuration in /etc/koha/sites/ name>/koha-conf.xml
> 
> 1
> 
>   ldap://ldap.domain.ch
>   ou=users,DC=domain,DC=ch
>   CN=srvc-koha,OU=unit,DC=domain,DC=ch
>   somepass
>   1   
>   1 
>   1 

You seem to be using AD (you have a principal_name setup), and using 
auth_by_bind, you might need to add this: 

0

It seems redundant, but recent versions of koha seem to not be able to find the 
user if this is not also set with auth_by_bind.


>   %s...@domain.ch
>   0
>
>  
>  
>  
>  
>  
>   
> 
> 
> I’m trying to login to OPAC, but get the error message "You entered an 
> incorrect username or password.” and the log file
> /var/log/koha//opac-error.log 
> is still empty.
> 
> How can I debug the ldap authentication in koha?
> 
> Best,
> Patric
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] [MariaDB] installing version 10.3

2019-03-06 Thread Hector Gonzalez
> But Koha>About still shows:
> 
>MySQL version: mysql Ver 15.1 Distrib 10.2.22-MariaDB, for 
> debian-linux-gnu (x86_64) using readline 5.2
> 
> I am running Koha 18.11.03.000 on Debian 9 Stretch.

You may need to restart memcached and koha-common.  The mariadb
 upgrade would not do that.

> Any ideas?
> 
> Thank you,
> 
> Father Vlasie
> 
> IT Director
> St. Photios Orthodox Theological Seminary
> 510 Collier Way, Etna, CA 96027, U.S.A.
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Send all notices to all available eMail addresses

2018-08-24 Thread Hector Gonzalez
If the comma doesn´t do the trick, you might have a chat with your sysadmin, 
and make mail aliases in a local mail server, say "thiskid@parents.yourdomain 
" would resend its messages to 
"parentofthiskid@theirmailserver, otherparentofthiskid@theirothermailserver, 
thiskid@whenkidgetsanemail"

It´s not simple, but it may work for you.  With postfix this could be done with 
alias tables, within a file or a database.

Cacho.

> On Aug 24, 2018, at 10:52 AM, Paul Hoffman  wrote:
> 
> Have you tried a comma?  That's the standard, not a semicolon.  The
> people who developed Outlook, etc. don't particularly seem to care about
> standards (pet peeve #9,037).
> 
> Paul.
> 
> On Fri, Aug 24, 2018 at 01:49:00PM +, Boettcher, Uwe wrote:
>> Hi Alvaro,
>> 
>> thanks a lot for your feedback.
>> 
>> Indeed, we already have tried to enter more than just one email address into 
>> the address field. Unfortunately, as you already assumed, Koha comes up with 
>> an error message, claiming the email address not to be correct. We have 
>> tried several combinations of blank and semicolon, but none was accepted.
>> 
>> Best
>> 
>> Uwe
>> 
>> Von: Alvaro Cornejo [mailto:cornejo.alv...@gmail.com]
>> Gesendet: Freitag, 24. August 2018 15:24
>> An: Boettcher, Uwe 
>> Cc: zefanja ; koha@lists.katipo.co.nz
>> Betreff: Re: [Koha] Send all notices to all available eMail addresses
>> 
>> Hi,
>> 
>> Haven't tested on Koha but in other applications, the workaround I use is to 
>> enter both email addresses on the same field separated by a semi-colon (;) 
>> something like "ema...@domain.com; 
>> ema...@domain2.com"
>> 
>> Koha might not allow the ; and space as valid characters on the email 
>> address and the email process might also fail. You can also try with a 
>> semicolon only (no space).
>> 
>> Regards,
>> 
>> Alvaro
>> 
>> |-|
>> Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier 
>> celular y Nextel
>> en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y 
>> GPRS online
>>  Visitenos en www.perusms.com
>> 
>> 2018-08-24 5:52 GMT-05:00 Boettcher, Uwe 
>> mailto:uwe.boettc...@whu.edu>>:
>> Dear all,
>> 
>> we have the same problem, just with professors and personal assistants, and 
>> would be happy to learn about a way to send notices to more than just one 
>> e-mail address derived from a patrons' account.
>> 
>> Many thanks in advance, and kind regards
>> 
>> Uwe
>> --
>> (Mr.) Uwe Boettcher
>> WHU - Otto Beisheim School of Management
>> Vallendar, Germany
>> 
>> -Ursprüngliche Nachricht-
>> Von: Koha 
>> [mailto:koha-boun...@lists.katipo.co.nz]
>>  Im Auftrag von zefanja
>> Gesendet: Freitag, 24. August 2018 12:10
>> An: koha@lists.katipo.co.nz
>> Betreff: [Koha] Send all notices to all available eMail addresses
>> 
>> Hi all,
>> 
>> we are using Koha in our school library and we have the following
>> "problem". We checkout books to all of our students starting from
>> preschool. Especially the younger once don't have a personal eMail
>> address. So we like to send notices (checkouts, checkins, overdues...)
>> to both parents. As far as I understand Koha it send the notices only to
>> one address. We could put in one of the parent's email, but we like to
>> inform both.
>> 
>> I've read that overdue_notices.pl has an 
>> repeatable --email parameter.
>> Where can I change it to send the notice to both parents?
>> 
>> Are there other ways to solve this problem or is it just not possible?
>> 
>> I'm thankful for any hints.
>> 
>> Regards,
>> Stephan
>> ___
>> Koha mailing list  http://koha-community.org
>> Koha@lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha
>> ___
>> Koha mailing list  http://koha-community.org
>> Koha@lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha
>> 
>> ___
>> Koha mailing list  http://koha-community.org
>> Koha@lists.katipo.co.nz
>> https://lists.katipo.co.nz/mailman/listinfo/koha
> 
> -- 
> Paul Hoffman 
> Systems Librarian
> Fenway Libraries Online
> c/o Wentworth Institute of Technology
> 550 Huntington Ave.
> Boston, MA 02115
> (617) 442-2384 (FLO main number)
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha

--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org

Re: [Koha] 18.05.00 - do not upgrade if itemtype defined at biblio level

2018-05-28 Thread Hector Gonzalez
Hi Michael, I have this as biblio record, can I change it to "specific 
item"?  Is there a procedure to do that?


I don't remember changing this preference, is it the default?


On 05/28/2018 10:17 AM, Michael Kuhn wrote:

Hi Narcis

Am 28.05.2018 um 17:11 schrieb Narcis Garcia:
> How can I check if my Koha instance is affected?

Check if your Koha system preference "item-level_itypes" is set to 
"biblio record" (affected) or "specific item" (not affected).


Hope this helps.

Best wishes: Michael


--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] How do I change an item's type?

2018-05-22 Thread Hector Gonzalez
Thank you, it seems this is a mixture of all that.  We have both 
items.itype, and biblioitems.itemtype set, but with different values, 
one is VM, whichdoes not exist, and the other is PELIC, which is 
"movie", so it seems the modification is happening, but is not 
readable.  I'll make a backup, and change the nonexisten item types with 
SQL and see ifthis helps.


The test system is in english, but the install was made in spanish, and 
the framework is in spanish, that's why I see that form translated.  I 
removed the language, but the translations are part of the database now.


Thanks for your help.


On 05/22/2018 03:13 PM, Jonathan Druart wrote:

Sorry, my previous answer was completely off topic.

You should try with the English interface (not translated).
If it works, it means there is a translation issue, if it still does 
not work it is certainly a data problem, double check the value  in 
your database (items.itype or biblioitems.itemtype, depending on the 
pref).

I have tested on 17.05.11 with the sample data and it seems ok.

On Tue, 22 May 2018 at 16:55 Hector Gonzalez <ca...@genac.org 
<mailto:ca...@genac.org>> wrote:


No, what I'm trying to do is to change the type of an existing
item, that was catalogued as a book, and it should be a movie now.

I search for the item, click on edit, change "y - tipo de item
Koha"  (I have the interface set to english, but this form is
shown in spanish)  it also does not show the original value, it is
blank.  I change it to "Movie", and click save.

The item type remains unchanged.


On 05/22/2018 01:53 PM, Jonathan Druart wrote:

On /admin/itemtypes.pl?op=add_form=BK
<http://itemtypes.pl?op=add_form=BK>
I changed the description from "Book" to "Movie" and it is saved
correctly.
    Is it what you are trying to do?

On Tue, 22 May 2018 at 15:47 Hector Gonzalez <ca...@genac.org
<mailto:ca...@genac.org>> wrote:

Sorry, I did not copy to the list:

Yes there are some lines in the logs, but I don't know what
to make of
them, these are the messages when I click save:

==> plack-error.log <==
DBIx::Class::Storage::DBI::select_single(): Query returned
more than one
row.  SQL that returns multiple rows is DEPRECATED for ->find
and
->single at /usr/share/koha/lib/Koha/Objects.pm line 92

==> plack.log <==
192.168.10.54 - - [22/May/2018:13:33:56 -0500] "POST
/intranet/cataloguing/additem.pl <http://additem.pl>
HTTP/1.1" 200 78332

"https://library-intra.example.com/cgi-bin/koha/cataloguing/additem.pl?op=edititem=36948=51602=;

"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
like Gecko)
Chrome/65.0.3325.183 Safari/537.36 Vivaldi/1.96.1147.36"

==> intranet-access.log <==
192.168.10.54 - - [22/May/2018:13:33:55 -0500] "POST
/cgi-bin/koha/cataloguing/additem.pl <http://additem.pl>
HTTP/1.1" 200 11789

And I messed the version, is 17.05.11  But I also tested this
with
17.11.05 (a full copy of the catalog), and it shows nearly
the same, the
intranet-access.log is missing there.

thanks.

    On 05/22/2018 09:34 AM, Jonathan Druart wrote:
> Do you see something in the logs?
>
> On Mon, 21 May 2018 at 20:03 Hector Gonzalez
<ca...@genac.org <mailto:ca...@genac.org>
> <mailto:ca...@genac.org <mailto:ca...@genac.org>>> wrote:
>
>     Hi, I'm trying to change an items type, from "Book" to
"Movie",
>     but Koha
>     won't do it.
>
>     This is with koha 17.11.05, running on debian stretch
with mariadb,
>     plack and memcached.  It doesn't show any error
messages, it just
>     ignores the action.
>
>     Is this a known bug?
>
>     --
>     Héctor González
> ca...@genac.org <mailto:ca...@genac.org>
<mailto:ca...@genac.org <mailto:ca...@genac.org>>
>
>  ___
>     Koha mailing list http://koha-community.org
> Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz>
<mailto:Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz>>
> https://lists.katipo.co.nz/mailman/listinfo/koha
>

-- 
Héctor González

ca...@genac.org <mailto:ca...@genac.org>

___
Koha mailing list http://koha-community.org
Koha@lists.ka

Re: [Koha] How do I change an item's type?

2018-05-22 Thread Hector Gonzalez
No, what I'm trying to do is to change the type of an existing item, 
that was catalogued as a book, and it should be a movie now.


I search for the item, click on edit, change "y - tipo de item Koha"  (I 
have the interface set to english, but this form is shown in spanish)  
it also does not show the original value, it is blank.  I change it to 
"Movie", and click save.


The item type remains unchanged.


On 05/22/2018 01:53 PM, Jonathan Druart wrote:
On /admin/itemtypes.pl?op=add_form=BK 
<http://itemtypes.pl?op=add_form=BK>
I changed the description from "Book" to "Movie" and it is saved 
correctly.

Is it what you are trying to do?

On Tue, 22 May 2018 at 15:47 Hector Gonzalez <ca...@genac.org 
<mailto:ca...@genac.org>> wrote:


Sorry, I did not copy to the list:

Yes there are some lines in the logs, but I don't know what to
make of
them, these are the messages when I click save:

==> plack-error.log <==
DBIx::Class::Storage::DBI::select_single(): Query returned more
than one
row.  SQL that returns multiple rows is DEPRECATED for ->find and
->single at /usr/share/koha/lib/Koha/Objects.pm line 92

==> plack.log <==
192.168.10.54 - - [22/May/2018:13:33:56 -0500] "POST
/intranet/cataloguing/additem.pl <http://additem.pl> HTTP/1.1" 200
78332

"https://library-intra.example.com/cgi-bin/koha/cataloguing/additem.pl?op=edititem=36948=51602=;

"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like
Gecko)
Chrome/65.0.3325.183 Safari/537.36 Vivaldi/1.96.1147.36"

==> intranet-access.log <==
192.168.10.54 - - [22/May/2018:13:33:55 -0500] "POST
/cgi-bin/koha/cataloguing/additem.pl <http://additem.pl> HTTP/1.1"
200 11789

And I messed the version, is 17.05.11  But I also tested this with
17.11.05 (a full copy of the catalog), and it shows nearly the
same, the
intranet-access.log is missing there.

thanks.

    On 05/22/2018 09:34 AM, Jonathan Druart wrote:
> Do you see something in the logs?
>
> On Mon, 21 May 2018 at 20:03 Hector Gonzalez <ca...@genac.org
<mailto:ca...@genac.org>
> <mailto:ca...@genac.org <mailto:ca...@genac.org>>> wrote:
>
>     Hi, I'm trying to change an items type, from "Book" to "Movie",
>     but Koha
>     won't do it.
>
>     This is with koha 17.11.05, running on debian stretch with
mariadb,
>     plack and memcached.  It doesn't show any error messages, it
just
>     ignores the action.
>
>     Is this a known bug?
>
>     --
>     Héctor González
> ca...@genac.org <mailto:ca...@genac.org> <mailto:ca...@genac.org
<mailto:ca...@genac.org>>
>
>     ___
>     Koha mailing list http://koha-community.org
> Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz>
<mailto:Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz>>
> https://lists.katipo.co.nz/mailman/listinfo/koha
>

-- 
Héctor González

ca...@genac.org <mailto:ca...@genac.org>

___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz>
https://lists.katipo.co.nz/mailman/listinfo/koha



--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] How do I change an item's type?

2018-05-22 Thread Hector Gonzalez

Sorry, I did not copy to the list:

Yes there are some lines in the logs, but I don't know what to make of 
them, these are the messages when I click save:


==> plack-error.log <==
DBIx::Class::Storage::DBI::select_single(): Query returned more than one 
row.  SQL that returns multiple rows is DEPRECATED for ->find and 
->single at /usr/share/koha/lib/Koha/Objects.pm line 92


==> plack.log <==
192.168.10.54 - - [22/May/2018:13:33:56 -0500] "POST 
/intranet/cataloguing/additem.pl HTTP/1.1" 200 78332 
"https://library-intra.example.com/cgi-bin/koha/cataloguing/additem.pl?op=edititem=36948=51602=; 
"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) 
Chrome/65.0.3325.183 Safari/537.36 Vivaldi/1.96.1147.36"


==> intranet-access.log <==
192.168.10.54 - - [22/May/2018:13:33:55 -0500] "POST 
/cgi-bin/koha/cataloguing/additem.pl HTTP/1.1" 200 11789


And I messed the version, is 17.05.11  But I also tested this with 
17.11.05 (a full copy of the catalog), and it shows nearly the same, the 
intranet-access.log is missing there.


thanks.

On 05/22/2018 09:34 AM, Jonathan Druart wrote:

Do you see something in the logs?

On Mon, 21 May 2018 at 20:03 Hector Gonzalez <ca...@genac.org 
<mailto:ca...@genac.org>> wrote:


Hi, I'm trying to change an items type, from "Book" to "Movie",
but Koha
won't do it.

This is with koha 17.11.05, running on debian stretch with mariadb,
plack and memcached.  It doesn't show any error messages, it just
ignores the action.

Is this a known bug?

-- 
Héctor González

ca...@genac.org <mailto:ca...@genac.org>

___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz>
https://lists.katipo.co.nz/mailman/listinfo/koha



--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] How do I change an item's type?

2018-05-21 Thread Hector Gonzalez
Hi, I'm trying to change an items type, from "Book" to "Movie", but Koha 
won't do it.


This is with koha 17.11.05, running on debian stretch with mariadb, 
plack and memcached.  It doesn't show any error messages, it just 
ignores the action.


Is this a known bug?

--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Need help Setting up MTA for Koha email

2018-02-20 Thread Hector Gonzalez
You should focus on configuring postfix tosend its mail with a remote 
host with user and password, here is a howto on that:


https://www.freelock.com/kb/postfix-relayhost

What you are looking for is best searched for with this: "postfix 
relayhost authentication" google that and you'll see lots of samples.



On 02/20/2018 09:10 AM, Hughes Dimka wrote:

Hello Chris,

I have a major problem, i have been trying to setup mta on koha 17.11
installed package with ubuntu 16.04. i have seen alot of instructions on
setting up emails using gmail and postfix but none on if you have a domain
name that is hosted on the web  wih a user  account like
hdi...@hopewell.com.ng.

I have been delaying a library from launching their koha for over two
months now and still yet am not able to configure the email sending for
their patrons.

I would really need your help and direction on how to configure MTA  it to
work for sending emails , as on the koha 17.11 manual their is no guide on
how to set-up email using MTA.


--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Koha 17.11.01 released

2018-01-08 Thread Hector Gonzalez

Try this: apt-get install koha-common

It should mark it as "to be installed", try to resolve its dependencies, 
and upgrade it to the latest version.  It looks like it is marked to be 
removed, and this it should be corrected.



On 01/08/2018 09:36 AM, Bruce A. Metcalf wrote:

On 01/04/2018 01:55 PM, Chris Cormack wrote:

* Chris Cormack (chr...@catalyst.net.nz) wrote:
That usually means an unmet dependency. Definitely don't remove it. 
I'll look into it soon and see if I can spot what the issue is


Hmm, I just tried at work and the 17.11.00 to 17.11.01 worked fine

Can you paste exactly what it is saying when you upgrade (don't choose
yes to remove though)


This system has just had "apt-get update && apt-get upgrade" run, with 
no new packages suggested.

When I try to upgrade:

==
root# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... The following packages were automatically 
installed and are no longer required:
 at autopoint daemon docbook-xml docbook-xsl gettext idzebra-2.0 
idzebra-2.0-common idzebra-2.0-doc idzebra-2.0-utils 
libalgorithm-checkdigits-perl libanyevent-http-perl libanyevent-perl 
libappconfig-perl libarchive-zip-perl libauthen-cas-client-perl 
libbarcode-code128-perl libbiblio-endnotestyle-perl libbit-vector-perl 
libbusiness-isbn-data-perl libbusiness-isbn-perl 
libcache-fastmmap-perl libcache-memcached-fast-perl 
libcache-memcached-perl libcache-perl libcarp-assert-more-perl 
libcarp-assert-perl libcarp-clan-perl libcgi-compile-perl 
libcgi-emulate-psgi-perl libcgi-session-driver-memcached-perl 
libcgi-session-perl libcgi-session-serialize-yaml-perl 
libclass-accessor-chained-perl libclass-accessor-grouped-perl 
libclass-accessor-perl libclass-adapter-perl 
libclass-c3-componentised-perl libclass-data-inheritable-perl 
libclass-factory-util-perl libclass-makemethods-perl libclass-mix-perl 
libclass-returnvalue-perl libclass-singleton-perl libclass-unload-perl 
libcontext-preserve-perl libconvert-basen-perl 
libcrypt-eksblowfish-perl libcrypt-gcrypt-perl 
libdata-dumper-concise-perl libdata-ical-perl libdata-page-perl 
libdate-calc-perl libdate-manip-perl libdatetime-event-ical-perl 
libdatetime-event-recurrence-perl libdatetime-format-builder-perl 
libdatetime-format-ical-perl libdatetime-format-mail-perl 
libdatetime-format-mysql-perl libdatetime-format-strptime-perl 
libdatetime-format-w3cdtf-perl libdatetime-locale-perl 
libdatetime-perl libdatetime-set-perl libdatetime-timezone-perl 
libdbd-mock-perl libdbd-sqlite2-perl libdbix-class-perl 
libdbix-class-schema-loader-perl libdbix-runsql-perl 
libdevel-cover-perl libdevel-stacktrace-ashtml-perl 
libdevel-symdump-perl libemail-abstract-perl libemail-date-perl 
libemail-simple-perl libemail-valid-perl libexception-class-perl 
libfile-nfslock-perl libfile-pushd-perl libfile-sharedir-perl 
libfile-slurp-perl libfilesys-notify-simple-perl libfont-ttf-perl 
libgd-barcode-perl libgraph-perl libgraphics-colornames-perl 
libgraphics-magick-perl libgraphicsmagick3 libgraphviz-perl 
libgravatar-url-perl libhash-multivalue-perl libheap-perl 
libhtml-scrubber-perl libhtml-tidy-perl libhttp-body-perl 
libhttp-oai-perl libhttp-parser-xs-perl libhttp-server-simple-perl 
libidzebra-2.0-0 libidzebra-2.0-dev libidzebra-2.0-mod-alvis 
libidzebra-2.0-mod-dom libidzebra-2.0-mod-grs-marc 
libidzebra-2.0-mod-grs-regx libidzebra-2.0-mod-grs-xml 
libidzebra-2.0-mod-text libidzebra-2.0-modules libimage-size-perl 
libio-multiplex-perl libio-pty-perl libipc-run-perl 
libipc-shareable-perl libjcode-pm-perl libjson-validator-perl 
liblibrary-callnumber-lc-perl liblingua-ispell-perl 
liblingua-stem-snowball-perl liblocale-currency-format-perl 
liblocale-maketext-lexicon-perl liblocale-po-perl liblog-dispatch-perl 
liblog-log4perl-perl libmail-sendmail-perl libmarc-charset-perl 
libmarc-record-perl libmarc-xml-perl libmath-base36-perl 
libmodern-perl-perl libmodule-bundled-files-perl libmodule-find-perl 
libmodule-refresh-perl libmojolicious-plugin-openapi-perl 
libnet-cidr-perl libnet-domain-tld-perl libnet-server-perl 
libnet-sftp-foreign-perl libnet-z3950-zoom-perl libnumber-format-perl 
libole-storage-lite-perl libopenoffice-oodoc-perl 
libparse-recdescent-perl libpath-class-perl libpdf-api2-perl 
libpdf-api2-simple-perl libpdf-fromhtml-perl libpdf-reuse-barcode-perl 
libpdf-reuse-perl libpdf-table-perl libpdf-writer-perl 
libplack-middleware-reverseproxy-perl libplack-perl 
libpod-coverage-perl libreadonly-perl libreadonly-xs-perl 
libschedule-at-perl libset-infinite-perl libsms-send-perl 
libspreadsheet-parseexcel-perl libspreadsheet-writeexcel-perl 
libsql-abstract-perl libsql-translator-perl libstring-crc32-perl 
libstring-random-perl libsub-uplevel-perl libswagger2-perl 
libtemplate-perl libtemplate-plugin-htmltotext-perl 
libtemplate-plugin-json-escape-perl libtemplate-plugin-stash-perl 
libtest-deep-perl libtest-longstring-perl libtest-mockmodule-perl 

Re: [Koha] Koha 17.11.01 released

2018-01-04 Thread Hector Gonzalez
Try apt-get dist-upgrade, there is a new dependency in 17.11 that was 
not there with 17.05. If you don't want to dist-upgrade, you can answer 
no to the prompt, but it will tell you what is blocking the upgrade.


You may then install the dependency (in my case it was 
libmojolicious-plugin-openapi-perl ) and then apt-get upgrade will proceed.



On 01/04/2018 12:26 PM, Chris Cormack wrote:

Hi Bruce

That usually means an unmet dependency. Definitely don't remove it. I'll look 
into it soon and see if I can spot what the issue is

Chris

On January 5, 2018 5:35:09 AM GMT+13:00, "Bruce A. Metcalf"  
wrote:

On 01/03/2018 12:25 PM, Jonathan Druart wrote:


The Koha community is proud to announce the release of Koha  >

17.11.01. Packages are also available.

When I attempt to upgrade using apt-get, the system proposes to remove
koha-common, but not to replace or upgrade it. This is not how previous

upgrades have been done. Is this correct?

Koha 17.05.05 installed via packages under Debian Squeeze.

Regards,
/ Bruce /
Bruce A. Metcalf, FAS
Augustan Society Library


___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Broken packages, Unmet dependencies

2017-12-21 Thread Hector Gonzalez

Use:  dpkg --configure -a

when it finishes, you should be able to run apt-get again.


On 12/20/2017 08:22 PM, Javed Sahil wrote:

Hi jonathan,
I have used
apt-get install -f

And

aptitude install

Also not worked
It also not worked.



On Dec 21, 2017 12:37 AM, "Jonathan Druart" <
jonathan.dru...@bugs.koha-community.org> wrote:


apt-get install -f?

On Wed, 20 Dec 2017 at 15:17 Javed Sahil  wrote:


Hi All,
  I removed libsasl2-2,
sudo apt-get remove libsasl2-2
It started removing other packages too, i was shaked, hurriedly i pressed
ctrl + x, ctrl + c,
then i saw error messag something like this:
The process was intrupted.

Now i have lost the following:

Gnome ubuntu destop
access to Koha opac and Koha staff client

And packages Like libreoffice, gnome, gdm3, apache2, and many more

If i try to install them error shows;

You have held broken packages,
sometimes says already installed
could not be installed, it has unmet dependencies.
when try to remove any package  it says,;
not intalled.
i am stucked
how to get rid of unmet dependeCies and broken packages,

I have tried,
sudo su
clean
autoclean
autoremove
apt-get clean
apt-get autoclean
apt-get autoremove
apt-get update
apt-get upgrade

nothing worked.

Help plz

Javed.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Problems with MARC framework test.

2017-10-10 Thread Hector Gonzalez

On 10/10/2017 05:58 PM, Hector Gonzalez wrote:
Hi, I recently installed a new koha server, with version 17.05.04, and 
was trying it out, but found this, I have no idea why this would be 
wrong (I have not edited the framework):


Ignore my previous message, testing the queries checkmarc.pl uses, I 
found the FA framework caused the errors and deleted it.

I hope it is not required

--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] Problems with MARC framework test.

2017-10-10 Thread Hector Gonzalez
Hi, I recently installed a new koha server, with version 17.05.04, and 
was trying it out, but found this, I have no idea why this would be 
wrong (I have not edited the framework):



 MARC bibliographic framework test

TestResult
itemnum 

 * The field itemnum MUST be mapped
 * The corresponding subfield MUST be in with -1 (ignore) tab

item fields ALL items fields MUST :

 * be mapped to the same tag,
 * and they must all be in the 10 (items) tab

OK  Only 1 MARC tag mapped to items
OK  biblioitems.itemtype defined
homebranch NOT mapped   the items.homebranch field MUST :

 * be mapped to a MARC subfield,
 * the corresponding subfield MUST have "Authorized value" set to
   "branches"

holdingbranch NOT mappedthe items.holdingbranch field MUST :

 * be mapped to a MARC subfield,
 * the corresponding subfield MUST have "Authorized value" set to
   "branches"

OK  at least 1 item type defined
OK  at least 1 library defined
biblio and biblionumber 	The biblio.biblionumber and 
biblioitems.biblioitemnumber fields be mapped to a MARC subfield,

OK  no NULL value in frameworkcode
OK  all subfields for each tag are in the same tab (or ignored)
OK  all authority types used in the frameworks are defined
OK  items.permanent_location is not mapped on the frameworks
TOTAL 	You have 5 error(s) in your MARC configuration. Please fix them 
before using Koha


I can't find the errors, or where the errors are.
do you have any suggestions?
Thanks in advance.

--
Héctor González
ca...@genac.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Bulk Patron Image upload zip file giving Error 500

2017-07-21 Thread Hector Gonzalez
The problem is with the headers, the header names have whitespace before 
the text, and that became a problem after debian fixed a security bug 
related to this.


More information: https://blog.tigertech.net/posts/apache-cve-2016-8743/

Debian's fix: https://www.debian.org/security/2017/dsa-3796

In particular, the texts " extracting"  and "   inflating" have extra 
spaces before the header names.


can you check with Koha 17?

On 07/20/2017 11:29 PM, Sunil Sharma wrote:

Hello Friends,

If someone faced the problem mentioned in my previous mail attached below
and having any solution, please guide.

I am using Koha 16.05.12 with Debian 8.3 OS on my cloud server.

Currently, I am facing a very strange problem while uploading a single
patron image via Koha Bulk Patron image upload tool, the image file is
uploading fine. But When I tried using *zip file* of all patron images with
a mapped text file named as IDLINK.TXT, As soon as I browse the zip file
and try to upload the images, the images are uploaded but instead of result
page, the page will through error 500.

I had checked many Koha versions i.e. Koha 3.22.x, Koha 16.05.x, Koha
16.11.x but same *error 500* will be the result.

To troubleshoot the problem I had tested the same Koha versions with same
zip file at my local virtual machine but the strange problem which I found,
that* all Koha* versions with bulk patron upload feature *worked fine on
Debian 8.2 *but *through error 500 with Debian 8.3 and onwards i.e. 8.4,
8.8 etc. *

I had tested with different Apache versions but on Debian 8.2 all things
worked fine, but on Debian 8.3 no success (may be any security fetch or
something wrong is there)

As there are a lot of other application are running on my cloud server so I
can't change the OS. Please guide me what will I do?

The Koha error logs are as given below:





*[Thu Jul 12 13:43:02.2017] [http:error] [pid 16357] [client x.x.x.x]
AH02429: Response header name ' extracting' contains invalid characters,
aborting request, referer:
http://example.com/cgi-bin/koha/tools/picture-upload.pl
[Thu Jul 12
13:50:38.2017] [http:error] [pid 14327] [client x.x.x.x] AH02429: Response
header name '  inflating' contains invalid characters, aborting request,
referer: http://example.com/cgi-bin/koha/tools/picture-upload.pl
[Thu Jul 12
13:59:27.2017] [http:error] [pid 25507] [client x.x.x.x] AH02429: Response
header name '  inflating' contains invalid characters, aborting request,
referer: http://example.com/cgi-bin/koha/tools/picture-upload.pl
*


Any pointers would be of help.


On Fri, Jul 14, 2017 at 3:19 PM, Sunil Sharma 
wrote:


Hi Ian Bays,

Thank you very much for the valuable input.

I had checked and you are right that all patron images are uploading
correctly but was failing when trying to show the results page with the
error 500 as you observed.

Now, it is confirmed with your mail that something is wrong. Please guide
if you will find any solution for this problem.

If someone else faced this problem and having solution, please guide.



On Fri, Jul 14, 2017 at 2:19 PM, Ian Bays 
wrote:


Hello,

I have noticed the same problem uploading a zip file of patron images and
saw similar messages in the log file.

However on checking the patron records saw the images so I concluded that
the upload was working correctly but was failing when trying to show the
results page with the error 500.

There is definitely something wrong but you might like to check to see if
the upload actually worked OK.

Best regards.
Ian

On 13/07/2017 06:32, Sunil Sharma wrote:


Hello Friends,

I am using Koha 16.05.12 with Debian 8.3 OS on my cloud server.

Currently, I am facing a very strange problem while uploading a single
patron image via Koha Bulk Patron image upload tool, the image file is
uploading fine. But When I tried using *zip file* of all patron images
with
a mapped text file named as IDLINK.TXT, As soon as I browse the zip file
and try to upload the file, the page will through error 500.

I had checked many Koha versions i.e. Koha 3.22.x, Koha 16.05.x, Koha
16.11.x but same *error 500* will be the result.

To troubleshoot the problem I had tested the same Koha versions with same
zip file at my local virtual machine but the strange problem which I
found,
that* all Koha* versions with bulk patron upload feature *worked fine on
Debian 8.2 *but *through error 500 with Debian 8.3 *

I had tested with different Apache versions but on Debian 8.2 all things
worked fine, but on Debian 8.3 no success (may be any security fetch or
something wrong is there)

As there are a lot of other application are running on my cloud server
so I
can't change the OS. Please guide me what will I do?

The Koha error logs are as given below:





*[Thu Jul 12 13:43:02.2017]