- Koha - lists.katipo.co.nz

Hi! + a newbie question about nullmailer
by tan chong hui 08 Sep '14

08 Sep '14

Hello! I'm a new user of Koha.A friend needs to use the system at his library and I'm helping with the backend. Glad to join the Koha Community! ********************** I've had the system up and running.So far it's been smooth and fun except for a glitch. nullmailer came to be installed together with Koha and it's been causing mail.log and mail.errto blow up to 10GB in sizes, with lines that typically look like this: Sep 8 04:08:05 klc1 nullmailer[2290]: message repeated 694 times: [ smtp: Failed: Connect failed] I'm not currently sending emails so I removed nullmailer altogether from the system. Did I configure koha incorrectly during installation? ch

2 1

Re: [Koha] (Sip2) couldn't start sip2
by Abdulsalam Yousef 08 Sep '14

08 Sep '14

i've already changed it my real ip # like this port="176.34.249.176:6001/tcp" On Mon, Sep 8, 2014 at 6:47 AM, Chris Cormack <chrisc(a)catalyst.net.nz> wrote: > * Abdulsalam Yousef (ayousef(a)kwareict.com) wrote: > > hi Chris > > I mean i've changed this line > > > > port="127.0.0.01:6001/tcp" > > > > to > > > > port="123.456.7.89:6001/tcp" > > That's not a real ip number, you need to set it to your actual ip number > > Chris > > > > > in my SIPConfig.xml (or in my case SIPServer.xml) > > as you suggested. > > thanks > > _______________________________________________ > > Koha mailing list http://koha-community.org > > Koha(a)lists.katipo.co.nz > > http://lists.katipo.co.nz/mailman/listinfo/koha > > -- > Chris Cormack > Catalyst IT Ltd. > +64 4 803 2238 > PO Box 11-053, Manners St, Wellington 6142, New Zealand >

1 0

Re: [Koha] (Sip2) couldn't start sip2
by Abdulsalam Yousef 08 Sep '14

08 Sep '14

hi Chris I mean i've changed this line port="127.0.0.01:6001/tcp" to port="123.456.7.89:6001/tcp" in my SIPConfig.xml (or in my case SIPServer.xml) as you suggested. thanks

1 0

(Sip2) couldn't start sip2
by Abdulsalam Yousef 07 Sep '14

07 Sep '14

Hello all, We have a problem when trying to run Sip2 using this command perl -I./ ./SIPServer.pm ./SIPServer.xml >~/sip_log.out 2>~/sip_log.err & the log file called sip_log.err shows this error END SIPServer config. Bad arg length for Socket::unpack_sockaddr_in, length is 28, should be 16 at /usr/local/lib/perl/5.14.2/Socket.pm line 830. and running this command perl -d "/usr/share/koha/lib/C4/SIP/SIPServer.pm" "/etc/koha/sites/catalog/SIPconfig.xml" shows this UNIVERSAL->import is deprecated and will be removed in a future perl at /usr/share/koha/lib/C4/SIP/Sip/MsgType.pm line 22. at /usr/share/perl/5.14/UNIVERSAL.pm line 20. UNIVERSAL::import("UNIVERSAL", "can") called at /usr/share/koha/lib/C4/SIP/Sip/MsgType.pm line 22 Sip::MsgType::BEGIN() called at /usr/share/koha/lib/C4/SIP/Sip/MsgType.pm line 22 eval {...} called at /usr/share/koha/lib/C4/SIP/Sip/MsgType.pm line 22 require Sip/MsgType.pm called at /usr/share/koha/lib/C4/SIP/SIPServer.pm line 19 SIPServer::BEGIN() called at /usr/share/koha/lib/C4/SIP/Sip/MsgType.pm line 22 eval {...} called at /usr/share/koha/lib/C4/SIP/Sip/MsgType.pm line 22 SIPServer::(/usr/share/koha/lib/C4/SIP/SIPServer.pm:13): 13: require UNIVERSAL::require; We asking for any solutions that could help us??? thanks

2 1

Re: [Koha] inclusion of a detailed typical cron jobs section in the wiki
by Paul A 06 Sep '14

06 Sep '14

At 05:35 AM 9/6/2014 +0000, Indranil Das Gupta wrote: >I was reading http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_git [snip] >I mean, there are two sides to this - >a) people running a dev install >are expected to know what they are doing; and >b) someone wanting to >get started / simply participate in bug-triaging / patch sign-offs >could benefit from having this info in one place. "someone wanting to get started" should be nowhere near 'git' -- it's a developer's tool and requires a dedicated (non-production) server -- or at least that's the way that Torvalds designed it ten or so years ago. Perhaps this post should have gone to koha-devel? and not the general list. And perhaps the Wiki page might mention that there are other, more suitable, ways for "someone wanting to get started"? It's not very obvious if someone stumbles across the page which could start: "This is for more advanced users who are encouraged to get involved (knowledge, time and budget permitting) in the development of the world's best library cataloguing software." Best -- Paul

1 0

Incremental fine and purchase suggestion restriction
by Vinod Kumar Mishra 06 Sep '14

06 Sep '14

Dear All, Incremental fine and purchase suggestion restriction by category of users is very much needed in my view. Many libraries badly needs this features for proper administration of libraries. Therefore developers may review the above demand for incorporating it in next versions. Thanking You. With regards, Vinod Kumar Mishra, Assistant Librarian, Biju Patnaik Central Library, NIT Rourkela, Mob:91+9439420860 91+6612462103 (O) email: vinod_librarian(a)rediffmail.com : mishravk79(a)gmail.com

3 2

inclusion of a detailed typical cron jobs section in the wiki
by Indranil Das Gupta 06 Sep '14

06 Sep '14

Hi all, I was reading http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_git It seems to me, the wiki page could do well with the inclusion of how to setup up the important cron scripts that are readily available in the package-based installs, i.e. /etc/cron.d/koha-common /etc/cron.hourly/koha-common /etc/cron.daily/koha-common of course, links to the actual scripts and params need to be re-factored for dev install $KOHA_PATH. The info is already available in http://manual.koha-community.org/3.16/en/cronjobsch.html, but not exactly in the HOWTO approach of specific wiki articles. I mean, there are two sides to this - a) people running a dev install are expected to know what they are doing; and b) someone wanting to get started / simply participate in bug-triaging / patch sign-offs could benefit from having this info in one place. how do the devs and documentation manager feel about this? -indra -- Indranil Das Gupta Phone : +91-98300-20971 Blog : http://indradg.randomink.org/blog IRC : indradg on irc://irc.freenode.net Twitter : indradg -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=- Please exchange editable Office documents only in ODF Format. No other format is acceptable. Support Open Standards. For a free editor supporting ODF, please visit LibreOffice - http://www.documentfoundation.org

2 1

Renewal date-time in "issues.lastreneweddate"
by Ramprasad S. Joshi 05 Sep '14

05 Sep '14

Hello, We (at BITS, Pilani - Goa Campus, Goa INDIA) have a problem of reporting renewal date-times on koha 3.14.08.000. I suppose it is there with newer versions as well. 1. *The Problem:* For all renewals, the date-time recorded in "issues. *lastreneweddate*" is the "today" date and *midnight 00:00:00 time* *regardless of the actual time of transaction*. This makes hourly or forenoon-afternoon circulation reports confusing to our library staff when they try to tally the numbers. For fresh issues and clear returns, the issuedate and returndate respectively are the timestamp itself. For renewals, the timestamp is exact but the lastrenewddate is the midnight time of today. 2. *The Source:* I have located the exact source of the problem thus: * In Circulation.pm (in lib/C4): The function AddRenewal takes $lastreneweddate as a last optional parameter. When NULL, the default is (line 2534): DateTime->now(timezone => C4:Context->tz())->ymd(). Thus only the ymd part of now is taken, and the hh:mm:ss become all zero by default. * In renew.pl (in intranet/cgi-bin/circ): at line 79: my $date_due = AddRenewal( undef, $item->itemnumber() ); passes only two parameters, hence lastreneweddate is null and defaults to midnight as above. * A similar story goes with line 90 in renewscript.pl in intranet/cgi-bin/reserve. 3. *A Solution:* I suppose removing the "->ymd()" part in line 2534 in Circulation.pm in lib/C4 will not cause any problem to any other part in koha, in fact it will make it more consistent and more accurate. I hope this simple rectification is incorporated after due examination. Thanks, Ramprasad Joshi CS-IS Dept BITS, Pilani - K K Birla Goa Campus Zuarinagar, GOA INDIA 403726 Phone +91 832 2580 121 Fax +91 832 2557033

2 3

how to modifcate the label in marc modification template
by BOUIS Sonia 05 Sep '14

05 Sep '14

Hello, I can't manage to target the label in the marc modification template. What can I put in « fields » : 000 or LDR... ? If you have any idea, you're welcome. Thank you. Sonia BOUIS Responsable du Système intégré de gestion des bibliothèques bIBLIOTHÈQUES UNIVERSITAIRES Université Jean Moulin Lyon 3 6 Cours Albert Thomas - B.P. 8242 - 69355 Lyon Cedex 08 ligne directe : +33 (0)4 78 78 79 03 | http://scd.univ-lyon3.fr<http://scd.univ-lyon3.fr/> L'Université Jean Moulin est membre fondateur de l'Université de Lyon

2 3

multiple ldap servers (redundancy)
by mourik jan heupink - merit 05 Sep '14

05 Sep '14

Hi, I just found out something by trying, and thought I'd share it on the list, as I've never seen it in any of the examples. We have three samba dc's, and you can configure koha to use all three ldap servers, to gain failover. Do it like this: <ldapserver id="ad"> <hostname>dc1.my.domain</hostname> <hostname>dc2.my.domain</hostname> <hostname>dc3.my.domain</hostname> <base>CN=Users,DC=samba,DC=my,DC=domain</base> ... </ldapserver> It seems to work nicely, and all examples only use one single <hostname>. I hope this info will help someone. Regards, Mourik Jan

1 1