Thruk cache undefined value

(noone123) #1


i am experiencing very random cache issues with thruk (latest version).
It happens 3 times now in 3 month… so it’s not often. But i have no idea what causes the issue.

Thruk log:

Trace begun at (eval 34) line 1
main::ANON(‘Can’t use an undefined value as a HASH reference at /usr/share/thruk/lib/Thruk/Action/ line 507.^J’) called at /usr/share/thruk/lib/Thruk/Action/ line 506
Thruk::Action::AddDefaults::add_defaults(‘Thruk::Context=HASH(0x7f1e858edb28)’, 2) called at /usr/share/thruk/lib/Thruk/Controller/ line 25
Thruk::Controller::status::index(‘Thruk::Context=HASH(0x7f1e858edb28)’) called at /usr/share/thruk/lib/ line 319
eval {…} at /usr/share/thruk/lib/ line 308
Thruk::_dispatcher(‘HASH(0x7f1e8464cff0)’) called at /usr/share/thruk/script/thruk.psgi line 0
eval {…} at /usr/share/thruk/script/thruk.psgi line 0
main::ANON(‘Can’t use an undefined value as a HASH reference at /usr/share/thruk/lib/Thruk/Utils/ line 34.^J’) called at /usr/share/thruk/templates/ line 1
eval {…} at /usr/share/thruk/templates/ line 18
Template::Provider::ANON(‘Template::Context=HASH(0x40768e0)’) called at /usr/lib/thruk/perl5/x86_64-linux-gnu-thread-multi/Template/ line 163
eval {…} at /usr/lib/thruk/perl5/x86_64-linux-gnu-thread-multi/Template/ line 161
Template::Document::process(‘Template::Document=HASH(0x7f1e844ce5b0)’, ‘Template::Context=HASH(0x40768e0)’) called at /usr/lib/thruk/perl5/x86_64-linux-gnu-thread-multi/Template/ line 351
eval {…} at /usr/lib/thruk/perl5/x86_64-linux-gnu-thread-multi/Template/ line 321
Template::Context::process(‘Template::Context=HASH(0x40768e0)’, ‘’) called at /usr/share/thruk/templates/ line 58
eval {…} at /usr/share/thruk/templates/ line 18

It seems some userdata in the cache stops thruk from working.
The frontend is not reachable while this happends.
Any idea how to debug this and get the missing/wrong value?

(Sven Nierlein) #2

which version is that exactly?

(noone123) #3

oh… it’s still thruk 2.22
btw. removing /var/cache/thruk/* solves the problem.

(noone123) #4

you think upgrading will solve the issue sni?
I also can deliver more debugging information if needed.

(noone123) #5

Hi, unfortunately it happened again.
Both times the last lies in cache contains:



any idea how to solve this problem?

(Sven Nierlein) #6

tbh, i have no idea and never had such issues in any of our or our customer setups. Could you save the cache next time this happens?

(noone123) #7

hi sni,

i have some saved caches with this issue around.
i’ll do some more investigation first and send you the cache then.

Thank you!