Re: [Koha-devel] Major surprise - "automatic" upgrade
At 12:08 PM 4/30/2013 +1200, Chris Cormack wrote: [big snip]
But as Jared says it will not do this without you entering your database user and password, and explicitly clicking to tell it to upgrade. It will give you the page, but it won't upgrade until you tell it.
The only automatic thing is it telling you you need to upgrade your database
Thanks Chris (and Jared, Marcel and Mason.) That was my understanding and it functioned as expected: it "upgraded the *database* from 3.8.5 to 3.8.10" the first time after I ran './cleanup_database.pl --zebraqueue -v' -- at this point I could not log in on the staff page as "paul" (or any other staff-user), had to log in as "koha" and got: Web installer Step 3 We are upgrading from Koha 3.08.05.000 to 3.08.10.000, you must update your database Update report : Upgrade to 3.08.06.000 (3.8.6 release) done / .. / Upgrade to 3.08.10.000 (3.8.9 release) done Everything went OK, update done. Continue to log in to Koha The "worrisome mystery" is why the "upgrading from Koha 3.08.05.000 to 3.08.10.000" took place at all! Let me be clear, it took place without my knowledge and without my "informed" consent. I say "informed" because, when I ran './cleanup_database.pl --zebraqueue -v' I was obviously logged in as user=koha, but the '-v' verbose gave me no warning whatsoever that it had found either the tarred 3.8.10 on the root of the server or the untarred 3.8.10 at /home/paul/ -- but equally obviously user=koha has the necessary permissions to carry out the "system upgrade." It is obvious that the 'cleanup' Perl script provoked the system upgrade which took a couple of hours (no CLI messages whatsoever), as the database upgrade took just a couple of seconds. This is reproducible: I restored the 3.8.5 from backup, and can confirm the update to 3.8.10. after running './cleanup_database.pl --zebraqueue -v'. The other elements of the same script - logs, mail, import and sessions do not provoke the system upgrade. I will now restore the backup again, delete the tarred and untarred 3.8.10s and expect no upgrade :=) The mystery remains ... Thanks and regards all round, Paul --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>
On 2013-05-1, at 6:41 AM, Paul wrote:
At 12:08 PM 4/30/2013 +1200, Chris Cormack wrote: [big snip]
But as Jared says it will not do this without you entering your database user and password, and explicitly clicking to tell it to upgrade. It will give you the page, but it won't upgrade until you tell it.
The only automatic thing is it telling you you need to upgrade your database
Thanks Chris (and Jared, Marcel and Mason.) That was my understanding and it functioned as expected: it "upgraded the *database* from 3.8.5 to 3.8.10" the first time after I ran './cleanup_database.pl --zebraqueue -v' -- at this point I could not log in on the staff page as "paul" (or any other staff-user), had to log in as "koha" and got: Web installer › Step 3 We are upgrading from Koha 3.08.05.000 to 3.08.10.000, you must update your database Update report : Upgrade to 3.08.06.000 (3.8.6 release) done / .. / Upgrade to 3.08.10.000 (3.8.9 release) done Everything went OK, update done. Continue to log in to Koha
The "worrisome mystery" is why the "upgrading from Koha 3.08.05.000 to 3.08.10.000" took place at all! Let me be clear, it took place without my knowledge and without my "informed" consent.
The mystery remains …
take a look at the timestamp of any file in the codebase, it will give you, at least, the timestamp of when the 'upgrade' occurred # ls -l /usr/share/koha/intranet/cgi-bin/kohaversion.pl -rw-r--r-- 1 root root 693 Mar 25 14:56 /usr/share/koha/intranet/cgi-bin/kohaversion.pl fyi, if you genuinely believe that neither you (or your workmates) upgraded your Koha, i think you should consider your system hacked/rooted
participants (2)
-
Mason James -
Paul