I have several similar cron jobs, getting regular reports from another host, with similar URL, with only different last segment (please look at picture, host name is hidden for security purposes).
When I click "No" near last cron job to run it - webmin shows two cron jobs are running.
Expected behavior: webmin should show only last one (URL ends with /11) cron job is running
Hi,
Have this issue been happening with previous Webmin version?
Anyway, what makes you think that job is not really running? Perhaps it's infact still running? Try searching for it in Running Processes module.
Hello, Ilia,
I have other server with Webmin 1.960 and just replicated the problem. So this is not new version bug. I just had no commands, that are almost same (with just one digit added).
I'm pretty sure /checkPrices/1 job is/was not running, as every run is logged and trey run only at evening/night.
I suppose this is related to almost same commands, as incorrectly marked "running" cron is with similar command, as actually running cron, just without last one symbol.
So I believe it should be "regexp - related" problem.
What is the full command line of the cron job for which you're seeing this issue?
/usr/bin/wget -q --timeout=0 https://api.xxxxx-server.com/checkPrices/11
I have changed server name for privacy - it is not public server anyway.
This script takes long time to run on server side (one hour or more).
Last edit: CaptAm 2021-03-05
So for the two commands that are both shown as running, what exactly is the difference in the command line?
Ok, please follow the "recipe" for simulating the problem:
1. Create a file /tmp/test1 with following content (file attached also) - :
#!/bin/bash
echo "Hi, I'm sleeping for 60 seconds..."
for i in {1..12}
do
echo "sleeping..."
sleep 5s
done
echo "all Done."
2. Give file permissions 755.
3. Copy file to /tmp/test11, /tmp/test2, /tmp/test22 (without the extension!).
4. Create four webmin scheduled cron jobs, for every of those four files with schedule at midnight only.
5. Click on "No" to run /tmp/test11, then return to "Scheduled cron jobs" list.
Expected behavior: /tmp/test11 should be shown as only one running process.
Actual behavior: /tmp/test1 and /tmp/test11 are shown as both running (picture attached).
This can be tested with /tmp/test22 also (/tmp/test2 will be incorrectly shown as running).
If you run /temp/test1 - /temp/test11 will be not shown as running. as /temp/test11 is not a substring of /temp/test1.
Hope this helps to understand and replicate the problem.
Last edit: CaptAm 2021-03-06
Hi,
Thanks for the heads up and for exemplary bug report with steps to reproduce an issue.
Here is the fix.