CerebralXor
commented
8 years ago I think this might have been caused by the remote computer configuration. The host that I had set up was something like plex.myfqdn.com, but when the job ran the FQDN for the host was reported back to minicron server as simply plex.
In minicron server, I changed the FQDN of the host from plex.myfqdn.com to plex and it has resolved the issue. I can leave the Hostfield as the entire FQDN though. I'm not sure what the difference between the FQDN and Host fields are in minicron server.
(Obviously I'm not actually using myfqdn.com as my domain, I'd just prefer not to post my private domain here.)
jamesrwhite
Using Minicron 0.9.6, fresh new installation on Ubuntu 16.04.
I create a job in the Web Gui, and it is created in the crontab on the remote computer no problems. When that job executes (either at the scheduled time or by manually running it from the Minicron web interface), Minicron server doesn't detect the execution as the existing job, so it creates a new one using the command itself as the name. As you can see in the screen shot below, there's a job 'Upgrade Plex' but when that job runs, the 'executions' table at the bottom stays blank and a new job is created with the command as the title.