@giacomo
You are right, the “xxx-yyy.de” is not our real domain name…
Next days I will give it a try with a template, many thanks!
Kudos to this community here, I am a fan of nethserver and linux in general
@giacomo
You are right, the “xxx-yyy.de” is not our real domain name…
Next days I will give it a try with a template, many thanks!
Kudos to this community here, I am a fan of nethserver and linux in general
I have edited /etc/yum/yum-cron.conf
manually (changed email_from =… and email_to =… , you know). But this will always get lost every night. The reason is:
Mar 29 03:49:02 mail esmith::event[54933]: Event: software-repos-save
Mar 29 03:49:02 mail esmith::event[54933]: expanding /etc/nethserver/eorepo.conf
Mar 29 03:49:02 mail esmith::event[54933]: expanding /etc/nethserver/pkginfo.conf
Mar 29 03:49:02 mail esmith::event[54933]: expanding /etc/yum/yum-cron.conf
Mar 29 03:49:02 mail esmith::event[54933]: expanding /etc/yum/vars/nsrelease
Mar 29 03:49:02 mail esmith::event[54933]: expanding /etc/yum.repos.d/NethServer.repo
Mar 29 03:49:02 mail esmith::event[54933]: expanding /etc/yum.repos.d/subscription.repo
Mar 29 03:49:02 mail esmith::event[54933]: Action: /etc/e-smith/events/actions/generic_template_expand SUCCESS [0.421979]
Mar 29 03:49:02 mail esmith::event[54933]: [NOTICE] eorepo sb-base sb-updates sb-epel sb-extras sb-centos-sclo-rh sb-centos-sclo-sclo sb-nethserver-base sb-nethserver-updates
Mar 29 03:49:03 mail esmith::event[54933]: Loaded plugins: changelog, fastestmirror, nethserver_events
Mar 29 03:49:03 mail esmith::event[54933]: Cleaning repos: sb-base sb-centos-sclo-rh sb-centos-sclo-sclo sb-epel sb-extras
Mar 29 03:49:03 mail esmith::event[54933]: : sb-nethserver-base sb-nethserver-updates sb-updates
Mar 29 03:49:03 mail esmith::event[54933]: Action: /etc/e-smith/events/software-repos-save/S20nethserver-base-software-repos SUCCESS [1.307214]
Mar 29 03:49:03 mail esmith::event[54933]: Action: /etc/e-smith/events/software-repos-save/S21nethserver-base-import-repokeys SUCCESS [0.0185]
Mar 29 03:49:03 mail esmith::event[54933]: Event: software-repos-save SUCCESS
I could verify this behaviour after editing yum-cron.conf
again and then calling
signal-event software-repos-save
So I think the only way to save my changes permanently is to create the right template…
I copied
/etc/e-smith/templates/etc/yum/yum-cron.conf/30email
to
/etc/e-smith/templates-custom/etc/yum/yum-cron.conf/30email
.
Now I can edit this file:
This line is important:
email_from = root@{$SystemName}.{$DomainName}
Now everything works the way I want it to. I will wait one more day to see that the mail arrives, then I will install the updates.
Maybe, but this solution is not perfect. Hints and advice are always welcome…
Hmmm, some time has passed - new updates arrived but I still don’t get automatic mail from yum-cron
that new updates are available???
What is wrong? I thought everything was working, but it doesn’t seem to be.
… file /etc/yum/yum-cron.conf
has right settings. If I change "random_sleep = 360"
into "random_sleep = 0"
for test purposes and then calling yum-cron
manually I get mails for updates available…
After a few days’ holiday at Easter, I tried the following:
I made a second (additional) template file… copying
/etc/e-smith/templates/etc/yum/yum-cron.conf/10commands
to
/etc/e-smith/templates-custom/etc/yum/yum-cron.conf/10commands
.
Inside the file I changed parameter
random_sleep = 0
and the miracle happened: next day I received automatic mail from yum-cron
that new updates are available!
I’m afraid I don’t know what makes the difference between 360 and 0 from the random_sleep
parameter…
I hope this is now the final solution. Maybe someone can explain the behaviour, but for now I’m glad it’s working…
If I recall correcrly, more or less, it is the time (in minutes) so multiple servers do not run yum-cron at the same time (consuming bandwidth) or hit remote servers at once.
After all adjustments I described so far, the problem occurs again. It has worked for a few weeks, but now I don’t get mails from yum-cron
if it was called by the cron task.
If I run yum-cron
from console (manually), I get mails with information for updates available!!
What can I do, how do I find the cause?