[Koha-devel] 3.8.4 interim [was: koha-zebra-daemon not starting]

[Paul]

At 01:50 PM 8/23/2012 +1200, Mason James wrote:
> >> paul at server:~$ sudo /etc/init.d/koha-zebra-daemon start
> >> Starting Zebra Server
> >> /etc/init.d/koha-zebra-daemon: line 73: daemon: command not found
> > $ sudo apt-get install daemon ?

Thanks - that was the problem, and I have no idea why it "went AWOL."

>my other hunch is that you have bunch of __FOO__ stuff in your 
>/etc/init.d/koha-zebra-daemon file

That had installed perfectly, but thanks, it pushed me into doing a lot 
more digging around.  Anyway, as of this morning, Koha 3.8.4 is running on 
AMD64 Ubuntu 12.04 LTS.

However, I have (after asking our staff to try it out), got a very weird 
dilemma: from the new test machine, all NEW records (biblios and items, 
both Z39.50 imports and manual entries) are saving to our *PRODUCTION* 
server (3.6.1) -- all EDITS of existing biblios/items are saving correctly 
to the *TEST* server (3.8.4).

Both servers are on the same LAN, but under different computer names 
'server' and 'nelson', different IPs 192.168.0.91 and .95, different db 
names 'koha' and 'koha384', different URLs 'http://koha' and 
'http://koha-admin' compared to 'http://koha3' and 'http://koha-admin3', 
hosts files all updated, router updated (static, no DHCP).

Similarities are that I restored a mysql dump from production to test and 
therefore users/staff logins/passwords are the same. The test machine is 
saving something: we experimented with entering a new book by an existing 
author; on the "1 tab" when cataloging and checking the "authority" (little 
red box at the end of the 100$a line) it correctly incremented the number 
of times "Used" from 4 to 5 - 6 - 7 each time we saved that book - but a 
subsequent "authority" search only found the 4 again. However, now 
(accidentally) checking the production machine, an "authority" search finds 
all 7  !!!  with the associated biblios and items.

Anyone got any thoughts? Is there something is the mysql "restore" that 
points to the wrong db? [I used 'mysql --user=<me> --password=my_pw koha384 
< /usr/share/koha/koha361dump_1jan12.sql]

I have fairly detailed installation notes if anyone would like them... but 
as I'll probably do another complete reinstall (before upgrading the 
production machine mid-September), I will verify and refine them -- then 
try and assist with the "documentation project."

Thanks - Paul