You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All is working well (setup, scans, integration with Director), except that jobs run is doing nothing.
"icingacli x509 jobs run" command is launched, either manually, either via /etc/systemd/system/icinga-x509.service
When launching it manually, the command never ends and is getting stuck.
Yet I see that the schedules have been ran (the web gui is showing the dates of the recent retries I made)
this behaviour is preventing us to keep this command in a systemd service that keeps failing silently.
Expected behavior
This command should succeed or fail, but at least tell us something.
I also would love to know in which additional log files I could check things. I tried to enable icinga2 debug mode and look at the log files, which I usually do for other icinga debug matters, but here, to no avail.
Screenshots
Here is a sample :
root@xxxxx:~# icingacli x509 jobs run --verbose --debug
Scheduling sched_10.32.0.0 of job 10.32.0.0 to run at 2024-10-08 11:21:09
Scheduling sched_10.32.11.0 of job 10.32.11.0 to run at 2024-10-08 11:22:58
Scheduling sched_10.100.1.0 of job 10.100.1.0 to run at 2024-10-08 11:23:58
Scheduling sched_10.32.255.0 of job 10.32.255.0 to run at 2024-10-08 11:24:35
[... never ending nor writing anything more]
Here, I have to ctrl-C it to interrupt it.
Your Environment
Icinga Web 2 Version 2.12.1
director 1.11.1
icingadb 1.1.3
x509 1.3.2
Icinga Web 2 version and modules (System - About): 2.12.1
Web browser used: Firefox 130.0.1
Icinga 2 version used (icinga2 --version): r2.14.2-1
PHP version used (php --version): 7.4.33
Server operating system and version: Debian 11
The text was updated successfully, but these errors were encountered:
All is working well (setup, scans, integration with Director), except that jobs run is doing nothing.
Expected behavior
This command should succeed or fail, but at least tell us something.
I also would love to know in which additional log files I could check things. I tried to enable icinga2 debug mode and look at the log files, which I usually do for other icinga debug matters, but here, to no avail.
Screenshots
Here is a sample :
[... never ending nor writing anything more]
Here, I have to ctrl-C it to interrupt it.
Your Environment
Icinga Web 2 Version 2.12.1
director 1.11.1
icingadb 1.1.3
x509 1.3.2
icinga2 --version
): r2.14.2-1php --version
): 7.4.33The text was updated successfully, but these errors were encountered: