Hipo problem after upgrade

Squiz Matrix Support
1

I had two users who did not read their email and ignored 75px high red text telling them not to edit the content during a major upgrade (and I failed to check stalled hipo jobs on the 2nd and 3rd upgrades).


So now my hipo herder reads:

Fatal error: Cannot redeclare class HIPO_Job_Acquire_Locks in /data/matrix/core/hipo/jobs/hipo_job_acquire_locks.inc on line 343

Job TypeOwnerLast UpdatedPercent CompleteHIPO Job Acquire LocksGuilty One (Id #1400)5 days, 1 hour, 54 minutes and 1 second ago0%HIPO Job Acquire LocksGuility Two (Id #1542)5 days, 1 hour, 44 minutes and 10 seconds ago0%

Any suggestions on how to fix it?

2

You are going to have to get into the DB and run: TRUNCATE sq_hipo_job

3

[quote]
You are going to have to get into the DB and run: TRUNCATE sq_hipo_job

[/quote]

Thanks Greg, that fixed it

4

[quote]
I had two users who did not read their email and ignored 75px high red text telling them not to edit the content during a major upgrade (and I failed to check stalled hipo jobs on the 2nd and 3rd upgrades).

[/quote]



Hm. Is there a way to lock out users from editing during an upgrade?

5

[quote]
Hm. Is there a way to lock out users from editing during an upgrade?

[/quote]



I change the System Backend Suffix from _admin that makes it hard for them.

6

If you don't mind blocking your own access as well (like when you are running upgrade scripts) you can blank out both the _edit and _admin suffixes in main.inc and nobody will be able to get into the editing interfaces. But really only good for a read-only copy while you upgrade a second copy or while you are running the upgrade steps on the production system.

7

Could you not set all the accounts under construction for the duration and then make them live again when it's over?


I suppose that's easy for me to say since I have no public accounts that may have been suspended; only staff ones so I don't have a risk of reactivating something that shouldn't be.