NethServer Version: 7.7.1908 Module: software center
Since I’ve updated my system to 7.7.1908 the software center update notifications have stopped. This happened before i upgraded to Cockpit so i think the bug is somewhere in the 7.7.1908 update and not cockpit.
System > software center > config is configured to send admin emails
System > settings > Smarthost is configured
System > settings > email notifications is configured to send messages to me
I’ve tested email notifications using the old server manager, and messages get through. However the software center is not sending notifications.
Everything worked fine prior to upgrading to 7.7.1908
Seeing as you are now on the latest version, exactly what e-mails do you think you should be receiving. You should only get them if there are installed components that have a pending update.
That’s a good point!!!
Before I updated to 7.7.1908 I used to get email notifications if there were ANY updates available, I can’t remember the exact wording of the emails (I’m at work), but it was something like
Yum: Updates available
The notification emails were sent to root@nethbox and the root user was redirected to actualuser@nethbox, the messages would arrive in my inbox everyday if there were updates to install.
So far, 7.7.1908 has not sent any update emails, even though there are updates available (some for webtop and some for cockpit)
How are the update notifications supposed to behave with version 7.7.1908?
@fasttech my system is a standard nethserver install with subscription. I’m not sure what’s happened, but the behavior is different now the system has updated to 7.7.1908
Thank you for the thread reference, that doesn’t explain what’s happened.
I used to get software center update messages, now i don’t. The only difference is the update to 7.7.1908.
Here is an example of the emails i used to get:
The following updates will be downloaded on nethserver.xxx.org.uk:
================================================================================
Package Arch Version Repository Size
================================================================================
Updating:
nethserver-webtop5 noarch 1.4.0-1.ns7 sb-nethserver-updates 177 k
tomcat8 noarch 8.5.35-2.ns7 sb-nethserver-updates 8.5 M
webtop5 noarch 1.4.0-1.ns7 sb-nethserver-updates 116 M
webtop5-webdav noarch 0.2.0-1.ns7 sb-nethserver-updates 1.1 M
webtop5-zpush noarch 1.2.0-1.ns7 sb-nethserver-updates 1.0 M
Installing for dependencies:
nethserver-rh-php72-php-fpm noarch 1.0.0-1.ns7 sb-nethserver-updates 5.6 k
rh-php72 x86_64 1-2.el7 sb-centos-sclo-rh 4.3 k
Transaction Summary
================================================================================
Install ( 14 Dependent packages)
Upgrade 5 Packages
Updates downloaded successfully.
Software center currently shows 21 updates are available, but i’ve not recieved any email. 4 updates are “nethserver” items, 17 updates are “base system” items.
AFAIK it’s down to 2 things, because you have a subscription.
Firstly, if you query the updates via the UI it will always show what’s available to update, regardless of when it was added to the repository.
The e-mail will only show what’s been available for a certain length of time (can’t remember the exact time) so that, as a subscriber, you only see them after they’ve been validated as not causing issues.
Cheers.
I’ve been investigating this problem.
I’ve been following the guide here:
If I change the random_sleep time to 0 and run yum-cron /etc/yum/yum-cron.conf
I get an email notification
This is the contents of /etc/cron.daily/0yum-cron on my system
#!/bin/bash
# Only run if this flag is set. The flag is created by the yum-cron init
# script when the service is started -- this allows one to use chkconfig and
# the standard "service stop|start" commands to enable or disable yum-cron.
if [[ ! -f /var/lock/subsys/yum-cron ]]; then
exit 0
fi
# Action!
exec /usr/sbin/yum-cron
Should the last line be
exec /usr/sbin/yum-cron /etc/yum/yum-cron.conf
For reference, this is the contents of /etc/cron.hourly/0yum-hourly.cron
#!/bin/bash
# Only run if this flag is set. The flag is created by the yum-cron init
# script when the service is started -- this allows one to use chkconfig and
# the standard "service stop|start" commands to enable or disable yum-cron.
if [[ ! -f /var/lock/subsys/yum-cron ]]; then
exit 0
fi
# Action!
exec /usr/sbin/yum-cron /etc/yum/yum-cron-hourly.conf