Job definition failing

[jmgascoriego]

Hi Marc,

I am trying to create a daily job to discover the hosts via SNMP. When trying to create this job, I have the below error message in the application:

ERROR
Could not create a cron entry for the job - job was not created
sh: 1: -: not found

In parallel, find below the container logs generated during the error:

[Wed Feb 17 17:03:01.064191 2021] [cgi:error] [pid 363:tid 139700538939136] [client 192.168.126.126:63024] AH01215: Use of uninitialized value $output in pattern match (m//) at ../modules/GestioIP.pm line 28564.: /var/www/html/gestioip/res/ip_insert_scheduled_job.cgi, referer: http://192.168.126.180:3080/res/ip_insert_scheduled_job_form.cgi?client_id=1
[Wed Feb 17 17:03:01.070159 2021] [cgi:error] [pid 363:tid 139700538939136] [client 192.168.126.126:63024] AH01215: sh: 1: -l: not found: /var/www/html/gestioip/res/ip_insert_scheduled_job.cgi, referer: http://192.168.126.180:3080/res/ip_insert_scheduled_job_form.cgi?client_id=1

In case any additional troubleshooting or debugging is required, please let me know.

Thank you.

[muebel]

Hi jmgascoriego
Thanks a lot for reporting this issue. I can reproduce it. A new image will be provided, soon.
Kind regards

[jmgascoriego]

Hi Marc,

Thanks a lot for the update.

[muebel]

Hi jmgascoriego
The gip image was just updated to fix the issue.
Thanks a lot!

[jmgascoriego]

Hi Marc,

I have redeployed the latest version of the container and it seems the job definition works now. Just monitoring the next run of the job to confirm that it works correctly.
I will keep you posted.

Thank you!

[muebel]

Thanks a lot for the feedback.
Please try also if the MS LDAP auth problem still persist. I also tried with user management enabled and it is working correctly.

[jmgascoriego]

Hi Marc,

After monitoring the job, I can see it is correctly defined, but it is not running as per schedule (once a day at 07.00 AM).
Is there any way that I can run the Perl script manually to see whether something is missing or not?
Regarding the AD auth, I will update the other issue, but it is still failing for me with the same error after the login.

Thank you.

[jmgascoriego]

Hi Marc,

I have tried different job configurations. However, none of them seems to work.
I can see the "next run" date is updated once the schedule triggers the job, but actually, the job is not running at all. I can see the discovery job has no history available.
Running the host discovery manually from the network section, it works perfectly fine.

Not sure whether I can run the job from the CLI or not.

Thanks!

[muebel]

Hi
I will try to reproduce this and tell you something.
Thanks a lot!

[muebel]

Hi
It seems that the problem is that the cron daemon is not started automatically. Jobs are not executed because crond is not running.
I just uploaded a new image that fixes this.
Regards

[jmgascoriego]

Hi Marc,

I just tested the latest container version, and it's working fine.

Appreciated your time fixing this issue ;)

Thanks a lot