horde-alarms cronjob fail

[TDannhauer]

horde-alarms cronjob fail:

Fatal Error:
SessionAccessor::current() called before a session has been established.
Guard with hasCurrent() at sites that legitimately run before
SessionLifecycle::start().
In
....horde-deployment/vendor/horde/core/src/Session/Sessio
nAccessor.php on line 62

1. include()
   ....horde-deployment/vendor/bin/horde-alarms:119
2. Horde_Registry::appInit()
   ....horde-deployment/vendor/horde/horde/bin/horde-alarms:
   23
3. Horde_Registry->__construct()
   ....horde-deployment/vendor/horde/core/lib/Horde/Registry
   .php:392
4. Horde_Registry->setLanguageEnvironment()
   ....horde-deployment/vendor/horde/core/lib/Horde/Registry
   .php:647
5. Horde_Registry->setLanguage()
   ....horde-deployment/vendor/horde/core/lib/Horde/Registry
   .php:3200
6. Horde_Registry->preferredLang()
   ....horde-deployment/vendor/horde/core/lib/Horde/Registry
   .php:3143
7. Horde_Registry_Nlsconfig->__get()
   ....horde-deployment/vendor/horde/core/lib/Horde/Registry
   .php:3125
8. Horde\Core\Session\SessionAccessor->hasScoped()
   ....horde-deployment/vendor/horde/core/lib/Horde/Registry
   /Nlsconfig.php:53
9. Horde\Core\Session\SessionAccessor->current()
   ....horde-deployment/vendor/horde/core/src/Session/Sessio
   nAccessor.php:92

[TDannhauer]

.. and tons of HORDE 2026-07-22T18:37:23+02:00 emergency: SessionAccessor::current() called before a session has been established. Guard with hasCurrent() at sites that legitimately run before SessionLifecycle::start(). [pid 3358781 on line 62 of "/var/www/torben/web/horde-deployment/vendor/horde/core/src/Session/SessionAccessor.php"]
in horde.log

no further callstack in horde.log available.

also Activesync is'nt working anymore. Hypothesis:

Today’s Core session refactor (horde/Core#203) switched many consumers from a held HordeSession to SessionAccess / SessionAccessor::current(). That accessor is empty until SessionLifecycle publishes a session.

ActiveSync deliberately boots with session_control = 'none', which uses Horde_Session_Null instead of a normal PHP session. Horde_Session_Null::setup() overrides the parent and never publishes a session to SessionAccessor. After the refactor, bootstrap code (NLS, notifications, prefs cache, …) still calls SessionAccessor::current(), which throws LogicException and aborts the request.

That is the same failure mode as horde-alarms (CLI / no real session), but a different code path: the CLI fix (horde/Core#206 publishInMemory() on Horde_Session::setup(false)) does not cover Horde_Session_Null.

Predicted effect: After Core was updated this afternoon, ActiveSync requests started dying early; devices stopped talking (logs silent from ~17:02); unread badges and other sync state froze even though IMAP itself was fine.

[ralflang]

See revises #206 - should fix both.

[TDannhauer]

Fixed - thanks