Hi Jamie,
make an extra thread for this:
The Webmin shedule functions are completely broken.
None of the jobs are proceeded.
The other System Sheduled Cron Jobs with crontabs are all working fine.
In my case the webmin jobs, time, temp files and system info are not working.
Nothing is logged as proceeded in syslog.
cheers mike
hi again,
i tried to verify this issue.
i could do this with let's encrypt,
cause there is a proof if there was the demand for the file on my internet site.
in this case the shedule worked ok.
in the other cases there is no verify possible, since all webmin shedule functions are nomore logged into syslog. this was the case before. it seems since the upgrade to debian 9.4 the webmin shedules are no more logged into syslog.
it would be helpful, if you could have a look for this, if possible.
thanks in advance
hope this helps.
cheer mike
sorry,
if i come back to these points.
i have been verifying when clening of temp files i proceeded.
i find this in syslog at a time which has nothing to do of the shedule time setup in webmin shedule functions.
additionally i find no entries for updating system info, whic is also setup in webmin shedule functions. is this proceeded or not, i do not know.
thanks for your assistance
cheers mike
Last edit: M.T.R 2018-06-29
That's a good suggestion - I will look into logging these.
This will be included in the next Webmin release - they will show up in the Webmin Actions Log module.
Please log the proceeded shedules also into syslog, like crontab does.
webmin actions log is not the same utilisation.
for me this more a log for changing settings etc.
the shedules are system related like the system shedules.
thanks for your assistance.
cheers mike
Last edit: M.T.R 2018-07-01
Logging to syslog isn't always possible, as it requires an extra Perl module that we can't count on being installed.
well,
you have an option in webmin/webmin configuration/loggin
where there is the option to log ALSO to syslog.
if you include the shedule procceeding loggin into this,
wouldn't it be possible then to filter JUST these shedule proceeds
and log them into syslog?
thanks for clarification.
cheers mike
You can actually turn on logging of all events to syslog, at Webmin -> Webmin Configuration -> Logging -> Also log Webmin actions to syslog?
thanks for the info.
i tried this and enabled the filter for shedule, enabled also log to syslog.
but nothing was logged at the time when the sheduled jobs were proceeded.
i still prefer a separate option to log just the webmin shedule jobs to syslog.
if there is another perl module to be installed, why not, just inform the user.
there are also other dependies in webmin moduls.
this log option should be placed directly in the webmin shedule page.
cheers mike
Hi,
Is some extra perl module still required for the 'Also log to syslog' functionality?
I am using Ubuntu 22.04 LTS and have enabled the feature but don't see anything in my syslog server.
Yes, you will need the Sys::Syslog module
Ok. I have Perl 5.34.0 installed.
And now the Syslog module is also installed.
cpan[2]> install Sys::Syslog
Sys::Syslog is up to date (0.36).
Still I don't really see anything in my syslog server.
I see these things:
webmin[851]: Webmin starting
webmin[996]: Webmin reloaded configuration
But I saw that before installing that Perl module.
I would like to see things like what is seen in logfiles like:
/var/webmin/webmin.log
/var/webmin/miniserv.log
Last edit: Fredrik Jansson 2023-01-09
What is the output of
systemctl status syslogcommand?But you really don't need syslog service on
systemdsystems. You should usejournalctland a new Webmin System Logs Viewer module.Hi,
We use syslog to gather logfiles from all devices in the network on central syslog servers.
It works fine from the server running webmin as well and I could use imfile option in rsyslog to send those logfiles I mention above to the central syslog server.
But the built-in option sounded smoother, just tick a box.