[horde] Problem after server's upgrade

Jan Schneider jan at horde.org
Mon Jan 4 12:14:25 UTC 2016


Zitat von Jānis <je at ktf.rtu.lv>:

> Hi!
>
> After upgrading the server running Horde, I suddenly got such error:
>
> Uncaught exception 'Horde_Exception_PushApp' with message ' is not  
> activated.' in /usr/lib64/php/Horde/Registry.php:1522 Stack trace:  
> #0 /usr/lib64/php/Horde/Registry.php(1189):  
> Horde_Registry->pushApp('horde', Array) #1  
> /usr/lib64/php/Horde/Registry.php(2106):  
> Horde_Registry->callAppMethod('horde', 'logout') #2  
> /usr/lib64/php/Horde/ErrorHandler.php(30):  
> Horde_Registry->clearAuthApp('horde') #3 [internal function]:  
> Horde_ErrorHandler::fatal(Object(Horde_Exception_AuthenticationFailure)) #4  
> {main} thrown
>
> 1. Horde_ErrorHandler::catchFatalError()
>
> ErrorException Object
> (
>     [message:protected] => Uncaught exception  
> 'Horde_Exception_PushApp' with message ' is not activated.' in  
> /usr/lib64/php/Horde/Registry.php:1522
> Stack trace:
> #0 /usr/lib64/php/Horde/Registry.php(1189):  
> Horde_Registry->pushApp('horde', Array)
> #1 /usr/lib64/php/Horde/Registry.php(2106):  
> Horde_Registry->callAppMethod('horde', 'logout')
> #2 /usr/lib64/php/Horde/ErrorHandler.php(30):  
> Horde_Registry->clearAuthApp('horde')
> #3 [internal function]:  
> Horde_ErrorHandler::fatal(Object(Horde_Exception_AuthenticationFailure))
> #4 {main}
>   thrown
>     [string:Exception:private] =>
>     [code:protected] => 0
>     [file:protected] => /usr/lib64/php/Horde/Registry.php
>     [line:protected] => 1522
>     [trace:Exception:private] => Array
>         (
>             [0] => Array
>                 (
>                     [function] => catchFatalError
>                     [class] => Horde_ErrorHandler
>                     [type] => ::
>                     [args] => Array
>                         (
>                         )
>                 )
>         )
>
>     [previous:Exception:private] =>
>     [severity:protected] => 1
>     [logged] => 1
> )

These are two problems. The root cause is some authentication failure.  
The next one is some problem while reporting this error. For some  
reason the "name" of the base "horde" application cannot be read.
My guess is that you made some local changes to one of the distributed  
configuration files that are now overwritten during the upgrade. Or  
some other issue with loading configuration files, most probably the  
registry configurations.

> It worked straight away after upgrade but stopped doing it when I  
> updated 4 php modules: imagick, ssh2, lzh and horde_lz4.
>
> server is running MariaDB 5.5.43/PHP 5.5.30.
>
> May be it is due to some strange auth issues with MariaDB? I had  
> notorius: "[Warning] 'user' entry 'hordeuser' has both a password  
> and an authentication plugin specified. The password will be ignored"
> message and had to make some corrections. Now user can login to  
> specific account without problems, but the problem above still  
> remains even after upgrade --force horde/(all installed modules with  
> deps)
>
> It is not possible to to connect to /admin also
>
> Janis
> -- 
> Horde mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org



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



More information about the horde mailing list