-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Business processes now unreliable #1322
Comments
You seem to use the packages from the nightly/testing repository. Could you by chance update to the lastet daily pkg and see if it's gone already or if the line number changes. |
Hi Sven
So the repo source is this one ...
name=Naemon (AlmaLinux_9)type=rpm-md
baseurl=https://download.opensuse.org/repositories/home:/naemon/AlmaLinux_9/
gpgcheck=1
gpgkey=https://download.opensuse.org/repositories/home:/naemon/AlmaLinux_9/repodata/repomd.xml.
key
enabled=1
libthruk-3.00-17.17.x86_64thruk-base-3.10-36.2.x86_64
thruk-plugin-reporting-3.10-36.2.x86_64
thruk-3.10-36.2.x86_64
naemon-thruk-1.4.1-13.18.noarch
I ran "yum update thruk* but there was no new packages.
I've refreshed the BP jobs but they are still going to state UNKNOWN
[2023/12/01 13:01:02][vuh-lb-mgp009.herts.ac.uk][ERROR] [cron] Thruk::BP::Components::BP::update_status(Thruk::BP::Components::BP=HASH(0x7febc8026698), Thruk::Context=HASH(0x5637621d65e0))called at /etc/thruk/plugins//plugins-enabled/business_process/lib/Thruk/Utils/CLI/Bp.pm line 210 thread 6
[2023/12/01 13:01:02][vuh-lb-mgp009.herts.ac.uk][ERROR] [cron] eval {...} called at /etc/thruk/plugins//plugins-enabled/business_process/lib/Thruk/Utils/CLI/Bp.pm line 209 thread 6
[2023/12/01 13:01:02][vuh-lb-mgp009.herts.ac.uk][ERROR] [cron] Thruk::Utils::CLI::Bp::__ANON__(21) called at /usr/share/thruk/lib/Thruk/Pool/Simple.pm line 90 thread 6
[2023/12/01 13:01:02][vuh-lb-mgp009.herts.ac.uk][ERROR] [cron] eval {...} called at /usr/share/thruk/lib/Thruk/Pool/Simple.pm line 87 thread 6
[2023/12/01 13:01:02][vuh-lb-mgp009.herts.ac.uk][ERROR] [cron] Thruk::Pool::Simple::_handle_work(Thruk::Pool::Simple=HASH(0x563762d03950)) called at /usr/share/thruk/lib/Thruk/Pool/Simple.pm line 27 thread 6
[2023/12/01 13:01:02][vuh-lb-mgp009.herts.ac.uk][ERROR] [cron] eval {...} called at /usr/share/thruk/lib/Thruk/Pool/Simple.pm line 27 thread 6
[2023/12/01 13:01:02][vuh-lb-mgp009.herts.ac.uk][ERROR] [cron] bp 'Infrastructure Load Balancers' failed: Not a HASH reference at /usr/share/thruk/lib/Thruk/Backend/Manager.pm line 2377.
[2023/12/01 13:01:03][vuh-lb-mgp009.herts.ac.uk][INFO] [cron] OK - 21 business processes updated in 1.07s (19.6/s)
# THIS PART IS WRITTEN BY THRUK, CHANGES WILL BE OVERWRITTEN##############################################################
THRUK_CRON=1
# business process
* * * * * cd /usr/share/thruk && /bin/bash -l -c '/usr/bin/thruk bp all' >/dev/null 2>>/var/lib/thruk/cron.log
# downtimes
0 0 1 * * cd /usr/share/thruk && /bin/bash -l -c '/usr/bin/thruk downtimetask "1"' >/dev/null 2>>/var/lib/thruk/cron.log
# general
20,50 * * * * cd /usr/share/thruk && /bin/bash -l -c '/usr/bin/thruk maintenance' >/dev/null 2>>/var/lib/thruk/cron.log
##############################################################
# END OF THRUK
On Friday, 1 December 2023 at 12:18, Sven Nierlein ***@***.***> wrote:
When I run this bp all job with "-vv" I can see these lines still
[13:05:22,431][E][...b/Thruk/Utils/CLI/Bp.pm:213][thr8] bp '1 - Login / IDM' failed: Can't usestring ("0") as a HASH ref while "strict refs" in use at /usr/share/thruk/lib/Thruk/Backend/Man
ager.pm line 2165.
[13:05:22,431][D][...b/Thruk/Utils/CLI/Bp.pm:222] 14/21 bp update failed in 0.054s | 3.tbp |
'1 - Login / IDM'
[13:05:22,433][E][...b/Thruk/Utils/CLI/Bp.pm:213][thr7] bp 'Infrastructure Load Balancers' fail
ed: Can't use string ("0") as a HASH ref while "strict refs" in use at /usr/share/thruk/lib/Thr
uk/Backend/Manager.pm line 2165.
… You seem to use the packages from the nightly/testing repository. Could you by chance update to the lastet daily pkg and see if it's gone already or if the line number changes.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.[https://mail.proton.me/api/core/v4/images?Url=https%3A%2F%2Fgithub.com%2Fnotifications%2Fbeacon%2FABYKQDVQJKIPUFRVK2PQYZDYHHDJ5A5CNFSM6AAAAABACXSW2CWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTNN6HU2.gif&DryRun=0&UID=kavm3efip772etivhbqdyhz3vzhoompo]
|
thanks for clarification, that's the latest stable release which makes it easier for me to find the corresponding line in the code. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I'm getting a lot of Unknown status in the business processes which aren't true. If I refresh they clear for a while.
In the log I see these lines - these are business process items.
[2023/12/01 11:57:03][vuh-lb-mgp009.herts.ac.uk][ERROR] [cron] bp '1 - Login / IDM' failed: Can't use string ("0") as a HASH ref while "strict refs" in use at /usr/share/thruk/lib/Thruk/Backend/Manager.pm line 2165.
[2023/12/01 11:57:03][vuh-lb-mgp009.herts.ac.uk][ERROR] [cron] bp '1 - Studynet' failed: Can't use string ("0") as a HASH ref while "strict refs" in use at /usr/share/thruk/lib/Thruk/Backend/Manager.pm line 2165.
[2023/12/01 11:57:03][vuh-lb-mgp009.herts.ac.uk][ERROR] [cron] bp 'Infrastructure Load Balancers' failed: Can't use string ("0") as a HASH ref while "strict refs" in use at /usr/share/thruk/lib/Thruk/Backend/Manager.pm line 2165.
Thruk Version
thruk-3.10-36.2
To Reproduce
Well I only have the one service.
Expected behavior
It used to work so Im wondering if its load related. But line 2165? Maybe thats something else?
Screenshots
Just mainly UNKNOWN status which isn't true .. these are not genuine alerts. They refresh immediately OK/green.
Desktop (please complete the following information):
Im on mac, this system is on Rocky Linux 9
Additional context
I have about 211 "nodes" is the bp directory (just saying, its hard to re-create at the moment).
The text was updated successfully, but these errors were encountered: