SYSTEM INFORMATION | |
---|---|
OS type and version | Ubuntu Linux 20.04.6 |
Webmin version | 2.202 |
Virtualmin version | 7.30.4 |
hello, i have a Scheduled Cron Jobs that shares some images between websites and i did an update for virtualmin/webmin which lead to stoping the Scheduled Cron Jobs and i started them again but they againt working… | |
can anyone help, maybe i should downgrade them so it start working? or anyother option (and i dont have a backup)… | |
for example: i had Virtualmin version [7.20.2] and rn i have 7.30.4 | |
for packages New version 3.20191218.1ubuntu1.3 | |
Installed version 3.20191218.1ubuntu1.2 |
learning to be a system admin?
day 1 - install OS - make a backup.
@Stegan thought i had it before, but when i check yesterday i ddint have it ig there is nothing i can do
Find out what is going wrong rather than taking actions that may compound your problems, why not try running your cron jobs from the command line and noting errors (if any) if they work check that the cron daemon is running, but to be fair you have not supplied enough information for anybody to help, we can only guess as to what is going wrong
hi @jimr1 i did run the command and theres error
thats the cron job ([ -x /usr/share/awstats/tools/update.sh ] && /usr/share/awstats/tools/update.sh)
Error while processing /etc/awstats/awstats.conf
Error: SiteDomain parameter not defined in your config/domain file. You must edit it for using this version of AWStats.
Setup (‘/etc/awstats/awstats.conf’ file, web server or permissions) may be wrong.
Check config file, permissions and AWStats documentation (in ‘docs’ directory).
and thats the second cron job ([ -x /usr/share/awstats/tools/buildstatic.sh ] && /usr/share/awstats/tools/buildstatic.sh)
when i run it it shows nothing
that looks like an issue in AWStats reporting
have you checked configuration recently? System Settings -> ReCheck Configuration
or maybe disabling and re-enabling AWStats Reporting
in VS Edit VS?
but we are still just guessing without knowing all the steps between last working system and it breaking.
downgrade is never a good move
didnt work, looks like i have to wait for the developer who made it to check it since i think the awstats.conf was messed up (the confguration are gone like domainnames…)
More likely you did something else at the time of update which caused the config files not to be written maybe disable awstats completely and try again
wait i didnt disable and reenable AWStats Reporting
in VS Edit VS can u tell me how to do it @Stegan
maybe also idk how to do it can u tell me how to disable awstats completely @jimr1
You can edit each virtual server and disable awstats or you maybe able to alter it in the server template and apply it to existing domains, to be fair it is a long time since I needed to disable something across a bunch of virtual servers … I find it easier to edit each server as you may have tweaked the odd server and your changes are lost
Sorry been away from desk try: Virtualmin -> Edit Virtual Server (for the selected server) then uncheck this box.
Save - then then repeat and check the box it should rebuild the AWStats conf files.
To disable completely Virtualmin -> System Settings -> Features and Plugins
uncheck AWStats Reporting. but you may want to check the configure
button to check that you have the Setup Cron Job = yes and the other options make sense.
you can also get to that same page via Virtualmin -> Manage Virtual Server -> AWStats Configuration
as always start with a good backup - even if you never need to use it.
Never make system changes without one - and make written notes of ever step - and keep them for future reference
thanks @Stegan but its not even selected for the 3 website that the cron job incloud…
Definitely not this.
You need to look at the log to see what’s going wrong with your cron jobs (you always need to look at the log, no matter what problem you have…guessing and randomly installing different software is not a way to solve problems).
That’s probably in the journal for the cron
unit. (i.e. journalctl -fu cron
to tail the log, and you can then trigger your failing cron jobs to see what’s going wrong). Or, if it’s not going to the journal you might find the cron logs in /var/log/syslog
(to tail that do tail -f /var/log/syslog |grep -i cron
). You can also view logs and the journal in Webmin in the System Logs or System Logs RS module (depending on whether you have the journal or text logs).
Edit: Oops, nevermind, I see you’ve already figured out the problem. Still, always reach for logs when you have a problem, never panic and start randomly installing/downgrading/whatever packages. Random behavior can only ever break more stuff.
true @Joe and thanks for the help everyone.