Re: [Koha-devel] 3.8.4 interim [was: koha-zebra-daemon not starting]
A tad of clarification. I had written:
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).
From the install log of the production machine (passwords snipped): # This file contains settings used # during the installation of Koha. # It is meant for use during future # upgrades of Koha, and should not # be edited. KOHA_INSTALLED_VERSION=3.06.01.000 LOG_DIR=/var/log/koha DB_TYPE=mysql DB_NAME=koha306 DB_HOST=localhost DB_USER=koha WEBMASTER_EMAIL=webmaster@nelson WEBSERVER_DOMAIN=nelson WEBSERVER_HOST=nelson The same from the test machine: # This file contains settings used # during the installation of Koha. # It is meant for use during future # upgrades of Koha, and should not # be edited. KOHA_INSTALLED_VERSION=3.08.04.000 LOG_DIR=/var/log/koha DB_TYPE=mysql DB_NAME=koha384 DB_HOST=localhost DB_USER=koha WEBMASTER_EMAIL=webmaster@server WEBSERVER_DOMAIN=server WEBSERVER_HOST=server 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
Did you miss Robert's reply? Chris On Aug 25, 2012 1:22 PM, "Paul" <paul.a@aandc.org> wrote:
A tad of clarification. I had written:
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).
From the install log of the production machine (passwords snipped):
# This file contains settings used # during the installation of Koha. # It is meant for use during future # upgrades of Koha, and should not # be edited. KOHA_INSTALLED_VERSION=3.06.**01.000 LOG_DIR=/var/log/koha DB_TYPE=mysql DB_NAME=koha306 DB_HOST=localhost DB_USER=koha WEBMASTER_EMAIL=webmaster@**nelson WEBSERVER_DOMAIN=nelson WEBSERVER_HOST=nelson
The same from the test machine:
# This file contains settings used # during the installation of Koha. # It is meant for use during future # upgrades of Koha, and should not # be edited. KOHA_INSTALLED_VERSION=3.08.**04.000 LOG_DIR=/var/log/koha DB_TYPE=mysql DB_NAME=koha384 DB_HOST=localhost DB_USER=koha WEBMASTER_EMAIL=webmaster@**server WEBSERVER_DOMAIN=server WEBSERVER_HOST=server
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<Koha-devel@lists.koha-community.org> http://lists.koha-community.**org/cgi-bin/mailman/listinfo/**koha-devel<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/ <http://bugs.koha-community.org/>
Op 25-08-12 03:22, Paul schreef:
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).
Can you confirm that you are checking both search results and details? I'm wondering if both instances are pointing to the same zebra server. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
At 10:45 AM 8/27/2012 +0200, Robin Sheat wrote:
Op 25-08-12 03:22, Paul schreef:
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).
Robin - thanks. It's all a bit moot now as the test server has been successfully (and totally) rebuilt (using the new " .1 " version of the ISO, see my email to this list yesterday Sun, 26 Aug 2012 12:39:27 -0400), but:
Can you confirm that you are checking both search results and details?
['are' ==> 'was'] yes
I'm wondering if both instances are pointing to the same zebra server.
This was not a case of sebra|search, the records were being *saved* to a differently named mysql/innodb on a differently IP'd machine. After saving a new Z39.50 biblio on the test server and shutting it down, the new record was on the production server and found by the zebra on the production server. I'm pretty certain from all my notes that both servers had separate zebra servers indexing separate sql db's. I even went as far as shutdown -h of the production server; 3.8.4 on the test server still appeared (i.e. no errors) to save new records, but they went nowhere -- and could not be found by either zebra server on either the production (after restarting) or the test box. While it's quite possible I screwed something up, the new LTS distro has made a number of fundamental changes concerning 'cloud' networking (OpenStack, MAAS, Keystone) which just possibly could have had some impact on our LAN (I have no proof of this, and our static IP LAN seems perfect after numerous "every-which-way" verifications.) Also, the older distro had a few ugly points in handling i386 modules if it couldn't find AMD64, but again, I could find no reason for this to account for my dilemma. Again thanks and br, Paul
On Mon, Aug 27, 2012 at 10:36 AM, Paul <paul.a@aandc.org> wrote:
While it's quite possible I screwed something up, the new LTS distro has made a number of fundamental changes concerning 'cloud' networking (OpenStack, MAAS, Keystone) which just possibly could have had some impact on our LAN (I have no proof of this, and our static IP LAN seems perfect after numerous "every-which-way" verifications.) Also, the older distro had a few ugly points in handling i386 modules if it couldn't find AMD64, but again, I could find no reason for this to account for my dilemma.
We use and used 12.04 since its release in several production servers and didn't have any problem. I even managed to do a: Koha 3.0.x + Ubuntu 10.04 => Koha 3.8.x + Ubuntu 12.04 migration a while ago without issues. The only problem we had to solve, had to do with a bug in Xen and Ubuntu using submenues in grub2, which were ok but old Xen didn't handle well (SuSE Dom0). The cloud stuff is not installed by default thou, unless you're using MASS images. Regards To+
participants (4)
-
Chris Cormack -
Paul -
Robin Sheat -
Tomas Cohen Arazi