Re: [Koha-devel] Major surprise - "automatic" upgrade
At 11:40 AM 5/7/2013 +0000, Marcel de Rooy wrote:
To reproduce upgrade, restore db; sftp [...] koha-3.08.05.tar.gz and koha-3.08.10.tar.gz /home/paul; "untar" koha-3.08.10.tar.gz in /home/paul/; cp koha-3.08.10.tar.gz to /
Hey: untar 3.8.10 and copy 3.8.10 to root ??
koha@hardy:/$ ls -l / drwxrwxr-x 42 koha koha 4096 Feb 23 05:09 koha-3.08.10
Paul: If I read well what you are doing here, you are restoring your database to 3.8.5 and your code to 3.8.10 !!
Marcel - thanks for your comments. The 3.8.10 "code" is the installation tarball -- not a /usr/share/koha functional system.
The 3.8.10 script cleanup_database does not complain about that; it does not really care about the exact version.
There is/was no 3.8.10 script cleanup_database in the tarball. I used /usr/share/koha/bin/cronjobs/cleanup_database.pl in the fully working 3.8.5. Surely this script (no diff, btw, between 3.8.5 and 3.8.10) is created from the tarball during install/upgrade.
It gets a db handle. It runs. But if you go to OPAC or staff, of course Koha will complain. The newer code sees the older database..
Mystery solved?
Respectfully, no. Where did the "newer code" come from without running Makefile.pl, make, make install as a "sudoer"? I was simply running cleanup_database.pl as user=koha without sudo privileges. Again thanks for your interest and best regards, Paul
Paul schreef op di 07-05-2013 om 12:18 [-0400]:
Respectfully, no. Where did the "newer code" come from without running Makefile.pl, make, make install as a "sudoer"? I was simply running cleanup_database.pl as user=koha without sudo privileges.
Out of curiosity, is the code in /usr/share/koha owned by root or by koha? If by root, then this is simply impossible barring a hyuuge security issue in Linux. If by koha, well that's bad configuration, but doesn't address the issue as a whole. In your earlier post, you didn't show us the version immediately before running cleanup, or at least, it was unclear. You showed it, did some other stuff, and then ran clean up. You need to look at kohaversion.pl _immediately_ before, and _immediately_ after. Otherwise any one of the other steps could have been involved. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
At 11:03 AM 5/8/2013 +1200, Robin Sheat wrote:
Paul schreef op di 07-05-2013 om 12:18 [-0400]:
Respectfully, no. Where did the "newer code" come from without running Makefile.pl, make, make install as a "sudoer"? I was simply running cleanup_database.pl as user=koha without sudo privileges.
Out of curiosity, is the code in /usr/share/koha owned by root or by koha? If by root, then this is simply impossible barring a hyuuge security issue in Linux. If by koha, well that's bad configuration, but doesn't address the issue as a whole.
A bit of a mix: drwxr-xr-x 8 koha koha 4096 Oct 11 2012 bin drwxr-xr-x 3 koha koha 4096 Sep 22 2012 doc drwxr-xr-x 5 root root 4096 Sep 22 2012 intranet drwxr-xr-x 4 koha koha 4096 Sep 22 2012 lib drwxr-xr-x 3 koha koha 4096 Sep 22 2012 man drwxr-xr-x 3 koha koha 4096 May 7 14:26 misc drwxr-xr-x 4 root root 4096 Sep 22 2012 opac
In your earlier post, you didn't show us the version immediately before running cleanup, or at least, it was unclear. You showed it, did some other stuff, and then ran clean up. You need to look at kohaversion.pl _immediately_ before, and _immediately_ after. Otherwise any one of the other steps could have been involved.
Agreed ... Over the next few days, I'll restore everything from a previous back up, and do it again. Thanks for the suggestions - best regards - Paul
participants (2)
-
Paul -
Robin Sheat