creation of scheduled cron job assigns wrong user:group

Please check It seems that on the creation of a scheduled cron job, the wrong user and group are assigned.

Operating system Debian Linux 9 Webmin version 1.872 Usermin version 1.734 Virtualmin version 6.02 Theme version Authentic Theme 19.07 Kernel and CPU Linux 4.9.0-5-amd64 on x86_64 Processor information Intel(R) Atom(TM) x5-Z8350 CPU @ 1.44GHz, 4 cores



Was this a cron job created by Virtualmin as part of the installation of Nextcloud?

Also, did the domain perhaps have it's name or login changed at some point?

No, I created these scheduled cron jobs aftercreating a vhost and installing the application. nextcloud) There was already an instance running in another vhost (also nextcloud) no problems there. Also a tool that updates my dynamic IP runs fine. These were installed somewhere in November '17.

Of course some updates to webmin/virtualmin/theme did happen in the mean time (november till now)

Ok, so how did you create this cron job exactly?

Sorry for a late reaction... flu is on the loose in the Netherlands...

at first I cloned a job as it was a similar one to an existing (working) one. made the appropriate changes to the command (path) and owner (execute cron job as) fiddled with the time schedule to not overlap the other ones.. that did not trigger any. then deleted that one and created one from scratch... that did not work either..

then as I wrote in it appeared the user:group and permissions where set incorrect...

If you SSH in as root and create a cron job with the command crontab -e -u XXX where XXX is a domain owner, does the file still get created with the wrong permissions?