I am thinking this is not normal. This happens when I try to add permission to read for a group or single back-end user for our entire site and cascade down. The HIPO stays at 0% and seems to time out, then gives me the error.
16:06:04 - 06 Sep
User: Nicholas Hubbard (48)
Level: MySource Warning
(/core/include/locale_manager.inc:505) - A HIPO Job with this code name is currently run by "Root User" (Id: #12)
Raw Entry: . last updated at 31/08/2007 11:01:21 [HIPO0041]
16:06:35 - 06 Sep
User: Nicholas Hubbard (48)
Level: MySource Warning
(/core/hipo/hipo_job.inc:1484) - HIPO Server Error : No TaskID Supplied or invalid TaskID [HIPO0048]
16:06:35 - 06 Sep
User: Nicholas Hubbard (48)
Level: MySource Warning
(/core/hipo/hipo_job.inc:1500) - Forcing Abort of HIPO Job [HIPO0046]
Can you check the error.log directly and see if there are any errors before this? This just looks like the new HIPO error when a Squiz Server process dies. We need to find the error generated by the Squiz Server. Perhaps it ran out of memory or similar.
[2007-09-06 11:10:45][48:Nicholas Hubbard][1024:mysource notice][R] (:) - The Squiz Server reset the running mode to WEB for User ID #48 and Job hipo_job_clone_assets-20b02dc95171540bc52912baf3aa709d
That is the only one that talks about the squiz server, but that was from this morning. Do you want me to post the contents of error.log?
That error indicates that the job died while running on the Squiz Server. Disable the Squiz Server and try again. If everything works without it, you may need to upgrade your Squiz Server.
Ok, I turned off the Squiz Server and it seems to be working now. Taking forever, but it got past the point where it failed getting the locks. It is now in the process of changing the permissions (which it never reached previously) so this is good. Should I keep the server off?
Does this mean I have a problem with the Squiz Server? We are getting the 3.16 upgrade soon, so, would this fix that problem?
If you're running v3.14 you might want to ask Squiz Support to check your Squiz Server version. Make sure that you have the latest version of the Squiz Server (as it was modified to support v3.14 and higher). If you haven't upgraded your Squiz Server since upgrading to v3.14, you need to!
