[horde] grandchild failed in cron

Jan Schneider jan at horde.org
Fri Mar 23 10:09:59 UTC 2012


Zitat von Andreas Mauser <andreas at mauser.info>:

> Hi,
>
> ----- Nachricht von Andreas Mauser <andreas at mauser.info> ---------
>   Datum: Thu, 15 Mar 2012 09:11:54 +0100
>     Von: Andreas Mauser <andreas at mauser.info>
> Betreff: Re: [horde] grandchild failed in cron
>      An: horde at lists.horde.org
>
>
>> Hi,
>>
>> ----- Nachricht von Andreas Mauser <andreas at mauser.info> ---------
>>  Datum: Mon, 12 Mar 2012 15:36:29 +0100
>>    Von: Andreas Mauser <andreas at mauser.info>
>> Betreff: Re: [horde] grandchild failed in cron
>>     An: horde at lists.horde.org
>>
>>
>>> Hi,
>>>
>>> ----- Nachricht von Jan Schneider <jan at horde.org> ---------
>>> Datum: Mon, 12 Mar 2012 13:46:19 +0100
>>>   Von: Jan Schneider <jan at horde.org>
>>> Betreff: Re: [horde] grandchild failed in cron
>>>    An: horde at lists.horde.org
>>>
>>>
>>>> Zitat von Andreas Mauser <andreas at mauser.info>:
>>>>
>>>>> Hi,
>>>>>
>>>>> ----- Nachricht von Andreas Mauser <andreas at mauser.info> ---------
>>>>> Datum: Mon, 05 Mar 2012 15:14:12 +0100
>>>>> Von: Andreas Mauser <andreas at mauser.info>
>>>>> Betreff: Re: [horde] grandchild failed in cron
>>>>>  An: horde at lists.horde.org
>>>>>
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> ----- Nachricht von Jan Schneider <jan at horde.org> ---------
>>>>>> Datum: Mon, 05 Mar 2012 14:01:45 +0100
>>>>>> Von: Jan Schneider <jan at horde.org>
>>>>>> Betreff: Re: [horde] grandchild failed in cron
>>>>>> An: horde at lists.horde.org
>>>>>>
>>>>>>
>>>>>>> Zitat von Andreas Mauser <andreas at mauser.info>:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> ----- Nachricht von Andreas Mauser <andreas at mauser.info> ---------
>>>>>>>> Datum: Mon, 05 Mar 2012 13:32:55 +0100
>>>>>>>> Von: Andreas Mauser <andreas at mauser.info>
>>>>>>>> Betreff: Re: [horde] grandchild failed in cron
>>>>>>>> An: Reindl Harald <h.reindl at thelounge.net>
>>>>>>>> Cc: horde at lists.horde.org
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> ----- Nachricht von Reindl Harald <h.reindl at thelounge.net> ---------
>>>>>>>>> Datum: Mon, 05 Mar 2012 13:08:49 +0100
>>>>>>>>> Von: Reindl Harald <h.reindl at thelounge.net>
>>>>>>>>> Betreff: Re: [horde] grandchild failed in cron
>>>>>>>>> An: Andreas Mauser <andreas at mauser.info>
>>>>>>>>> Cc: horde at lists.horde.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Am 05.03.2012 12:56, schrieb Andreas Mauser:
>>>>>>>>>>> In crontab I have:
>>>>>>>>>>>
>>>>>>>>>>> */5 * * * * root  
>>>>>>>>>>> PHP_PEAR_SYSCONF_DIR=/var/www/mauser.info/mailoffice
>>>>>>>>>>> php -d include_path=/var/www/mauser.info/mailoffice/pear/php
>>>>>>>>>>> /var/www/mauser.info/mailoffice/pear/horde-alarms
>>>>>>>>>>>
>>>>>>>>>>> and I get a:
>>>>>>>>>>>
>>>>>>>>>>> /USR/SBIN/CRON[4915]: (CRON) error (grandchild #4916  
>>>>>>>>>>> failed with exit
>>>>>>>>>>> status 127)
>>>>>>>>>>> and:
>>>>>>>>>>> /bin/sh: root: not found
>>>>>>>>>>>
>>>>>>>>>>> Removing 'root' at the line beginning I get:
>>>>>>>>>>> PHP Fatal error:  Call to a member function setObs() on a  
>>>>>>>>>>> non-object in
>>>>>>>>>>>
>>>>>>>>>>> Anything to fix that?
>>>>>>>>
>>>>>>>> Sorry I didnt give you the full error message:
>>>>>>>>
>>>>>>>> Removing 'root' at the line beginning I get:
>>>>>>>> PHP Fatal error:  Call to a member function setObs() on a  
>>>>>>>> non-object in /PATH/SQL.php in line 130
>>>>>>>>
>>>>>>>> Does that help some more?
>>>>>>>
>>>>>>> If it's really SQL.php (and not Sql.php), that's not even Horde 4 code.
>>>>>>>
>>>>>>
>>>>>> Sorry about that, I wrote the last words by myself because I  
>>>>>> already closed the console window.
>>>>>>
>>>>>> PHP Fatal error:  Call to a member function setObs() on a  
>>>>>> non-object in  
>>>>>> /var/www/mauser.info/mailoffice/pear/php/Horde/Perms/Sql.php on  
>>>>>> line 130
>>>>>>
>>>>>> In fact you are right, it is Sql.php and because it is in horde  
>>>>>> directories I assume its a horde part?
>>>>>>
>>>>>> Is that fixable? Because I get hundrets of messages a day in  
>>>>>> the logfile.
>>>>>
>>>>> Is there anything I can do?
>>>>
>>>> This could only happen if the unserialization in the line fails,  
>>>> but you should have that in your logs too. And that could only  
>>>> happen if you have some broken permission object in the cache.
>>>
>>> Ok, I take this as a fact. But what would one do in such a case?
>>
>> A reboot did not help at all.
>
> Anyone who can help? It fills my logs daily with a hundred of messages.

Did you read my reponse? First of all there has to be some error in  
any of the logs about failed unserialization. Is this the case?

And I wrote that this may only happen if a cached value is broken. So  
you need to empty the cache if that's the case.

Jan.

-- 
The Horde Project
http://www.horde.org/




More information about the horde mailing list