Hello Possible reasons this may have happen might be due to two factors; this week the internet connection from Spectrum(TWC) has been unstable (cutting out) effecting some updates OR the Ubuntu backup (duplicity) lost it freaking mind and restored many folders/files to the wrong place, and then there after is now corrupt and unusable. Spent the last weak using (gnome-ubuntu) grsync to get things back where they belong, but still not correct as my drive has exploded to >60% from 47% anyway how do I fix the cron jobs? I have Ubuntu timeshift to restore but it does the whole drive and introduces other errors. I can do rsync from the timeshift folders with an external Application, but I am mot sure what to look for? Is there a way to fix it in Webmin/Virtualmin? I have never had to deal with this so I am not sure where to start? So far all I got done was the missing log folder in nilandtrading home directory. I am still sometimes getting 504 connection errors when trying to connect to the web pages in the sub-servers? I can only access the top domain nilandtrading.com. I am considering recreating all the sub-servers as only one out of four were done. When creating a sub-server do DNS records get created automatically, seems I only got one of them that I had to create to get chat.nilandtrading.com to work?
Beginning validation of selected virtual servers. Any problems found will be shown in red ..
nilandtrading.com
All features OK
directory.nilandtrading.com
AWstats reporting : AWstats Cron job was not found
chat.nilandtrading.com
Webalizer reporting : No Webalizer Cron job found
ProFTPD virtual FTP : No ProFTPD virtual server found for 192.168.0.4
AWstats reporting : AWstats Cron job was not found
forum.nilandtrading.com
AWstats reporting : AWstats Cron job was not found
article.nilandtrading.com
Webalizer reporting : No Webalizer Cron job found
AWstats reporting : AWstats Cron job was not found
Comments
Submitted by andreychek on Tue, 10/17/2017 - 13:04 Comment #1
Howdy -- it sounds like you're seeing a few different issues there... perhaps we can tackle those one at a time to help us from getting confused, as we get confused pretty easily :-)
First, regarding your cron jobs -- the simplest way to re-create those would be to disable the "Awstats" and "Webalizer" features within the Virtual Server (or Sub-Server), and then re-enable it.
That will re-create those cron jobs.
Note that all those cron jobs are stored in root's crontab, which is in /var/spool/cron/crontabs/root. If you happen to have a backup of that, you could restore it, though I'm not sure I'd recommend that, as any newly created/modified jobs would be removed, which would cause another sort of problem :-)