Re: [Koha-devel] 3.8.4 interim [was: koha-zebra-daemon not starting]
[sending again to the LIST - apologies, only went to Robert yesterday] At 08:31 PM 8/24/2012 +0000, Robert Williams wrote:
Paul:
I'm wondering if you could have the staffClientBaseURL system preference set (not changed after loading the database from the production server)? If so, logging in to the staff interface on the test server may be "sending" you to the production server?
Robert, Many thanks for the suggestion. The 'staffClientBaseURL' was indeed blank ... I filled it in with the test server url, and it's still saving to the production machine (different url, different db name, ...) Best - Paul
--Robert
********************************************* Robert L. Williams Manager, Open Source ILS Services Amigos Library Services, Inc. 14400 Midway Road Dallas, TX 75244-3509 800-843-8482, x2870 972-340-2870 (direct) 972-991-6061 (fax)
-----Original Message----- From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] On Behalf Of Paul Sent: Friday, August 24, 2012 12:38 PM To: Koha Devel Cc: Koha Devel Subject: Re: [Koha-devel] 3.8.4 interim [was: koha-zebra-daemon not starting]
At 01:50 PM 8/23/2012 +1200, Mason James wrote:
paul@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
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
--- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>
Paul: <newbie-alert status="I'm still learning!"> You wrote:
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).
I've thought of and rejected several ideas. I'm thinking that, outside of the "BaseURL" sys pref settings, if it was an entry in the MySQL db or in a problem with the underlying Koha code, the dump/transfer/reload cycle would commonly end in problems for everyone. So I'm thinking it's likely a system setup thing. It seems to me most likely to be related to a domain name lookup problem (DNS issue/hosts issue?). But it possibly could be on the client side rather than the server side. Since your URLs do not correspond to your machine (host) names, the client's DNS lookup could be involved. You might try flushing the Firefox cache, flushing the local OS's DNS cache (ipconfig /flushdns on Windows clients, run with admin privileges), and then pinging the koha-admin, koha-admin3 names from the client command line and see what you get. Or alternatively, just check the local hosts file on the client, or the DNS server for your local network if implemented, and make sure there are not errors. If you change the Apache configuration to use the IP addresses and port numbers (and access the sites by the direct IP address temporarily), you can determine if it's actually a DNS issue or not. Don't know that this will be helpful, but it sounds from your message like something different than what you've already tried. Here's hoping it helps. </newbie-alert> --Robert ________________________________________ From: koha-devel-bounces@lists.koha-community.org [koha-devel-bounces@lists.koha-community.org] on behalf of Paul [paul.a@aandc.org] Sent: Saturday, August 25, 2012 7:30 AM To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] 3.8.4 interim [was: koha-zebra-daemon not starting] [sending again to the LIST - apologies, only went to Robert yesterday] At 08:31 PM 8/24/2012 +0000, Robert Williams wrote:
Paul:
I'm wondering if you could have the staffClientBaseURL system preference set (not changed after loading the database from the production server)? If so, logging in to the staff interface on the test server may be "sending" you to the production server?
Robert, Many thanks for the suggestion. The 'staffClientBaseURL' was indeed blank ... I filled it in with the test server url, and it's still saving to the production machine (different url, different db name, ...) Best - Paul
--Robert
********************************************* Robert L. Williams Manager, Open Source ILS Services Amigos Library Services, Inc. 14400 Midway Road Dallas, TX 75244-3509 800-843-8482, x2870 972-340-2870 (direct) 972-991-6061 (fax)
-----Original Message----- From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] On Behalf Of Paul Sent: Friday, August 24, 2012 12:38 PM To: Koha Devel Cc: Koha Devel Subject: Re: [Koha-devel] 3.8.4 interim [was: koha-zebra-daemon not starting]
At 01:50 PM 8/23/2012 +1200, Mason James wrote:
paul@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
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
--- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca> _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Paul: Sorry, upon further reflection after sending another response, I think I've debunked my DNS thoughts (my brain's too dead to be thinking :-) ). They might play a part, but they don't seem to address the fact that one form submission succeeds in reaching the correct server/database. It'll be interesting to hear what actually resolves the problem! Sorry for the noise. --Robert ________________________________________ From: koha-devel-bounces@lists.koha-community.org [koha-devel-bounces@lists.koha-community.org] on behalf of Robert Williams [williams@amigos.org] Sent: Saturday, August 25, 2012 1:09 PM To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] 3.8.4 interim [was: koha-zebra-daemon not starting] Paul: <newbie-alert status="I'm still learning!"> You wrote:
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).
I've thought of and rejected several ideas. I'm thinking that, outside of the "BaseURL" sys pref settings, if it was an entry in the MySQL db or in a problem with the underlying Koha code, the dump/transfer/reload cycle would commonly end in problems for everyone. So I'm thinking it's likely a system setup thing. It seems to me most likely to be related to a domain name lookup problem (DNS issue/hosts issue?). But it possibly could be on the client side rather than the server side. Since your URLs do not correspond to your machine (host) names, the client's DNS lookup could be involved. You might try flushing the Firefox cache, flushing the local OS's DNS cache (ipconfig /flushdns on Windows clients, run with admin privileges), and then pinging the koha-admin, koha-admin3 names from the client command line and see what you get. Or alternatively, just check the local hosts file on the client, or the DNS server for your local network if implemented, and make sure there are not errors. If you change the Apache configuration to use the IP addresses and port numbers (and access the sites by the direct IP address temporarily), you can determine if it's actually a DNS issue or not. Don't know that this will be helpful, but it sounds from your message like something different than what you've already tried. Here's hoping it helps. </newbie-alert> --Robert ________________________________________ From: koha-devel-bounces@lists.koha-community.org [koha-devel-bounces@lists.koha-community.org] on behalf of Paul [paul.a@aandc.org] Sent: Saturday, August 25, 2012 7:30 AM To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] 3.8.4 interim [was: koha-zebra-daemon not starting] [sending again to the LIST - apologies, only went to Robert yesterday] At 08:31 PM 8/24/2012 +0000, Robert Williams wrote:
Paul:
I'm wondering if you could have the staffClientBaseURL system preference set (not changed after loading the database from the production server)? If so, logging in to the staff interface on the test server may be "sending" you to the production server?
Robert, Many thanks for the suggestion. The 'staffClientBaseURL' was indeed blank ... I filled it in with the test server url, and it's still saving to the production machine (different url, different db name, ...) Best - Paul
--Robert
********************************************* Robert L. Williams Manager, Open Source ILS Services Amigos Library Services, Inc. 14400 Midway Road Dallas, TX 75244-3509 800-843-8482, x2870 972-340-2870 (direct) 972-991-6061 (fax)
-----Original Message----- From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] On Behalf Of Paul Sent: Friday, August 24, 2012 12:38 PM To: Koha Devel Cc: Koha Devel Subject: Re: [Koha-devel] 3.8.4 interim [was: koha-zebra-daemon not starting]
At 01:50 PM 8/23/2012 +1200, Mason James wrote:
paul@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
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
--- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca> _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
participants (2)
-
Paul -
Robert Williams