Topic: Frequency of Server Updates

[srushik]

The updates issued with "yum" come out way to frequently.

It seems that there is a new update to be installed 3-5 times per week.   It feels as though nearly everyday I receive an email to install more updates.

Now, I understand the concept of the contribs network of programmers, working together around the globe to make the server better.  I also appreciate that the server is constantly being updated with better security & other enhancements. 

I just want to express my frustration in having to install yum updates nearly every day.  Why can't these updates be issued weekly or bi-weekly.

Please take this in the spirit is was meant.  I love the SME server and all the work that goes into making it what it is.  I just don't want to have to apply updates so often.

Shane

[CharlieBrady]

Why can't these updates be issued weekly or bi-weekly?

If you want the updates to be weekly or bi-weekly, you can just do updates weekly or bi-weekly.

We have no control over when RedHat and/or CentOS release updates.

[shriddx]

... or fortnightly....monthly... annually.... every bi-year... every decade...etc...etc...

You are NOT forced to check/apply updates daily....

[girkers]

I think the message that srushik is trying to get across is that when a new update is released, you get an email everyday until the update is installed. Perhaps srushik could put in a New Feature Request (NFR) to ask that the update frequency can be set to a time frame instead of only being able to turn it on or off for daily checks. Also it does not appear that you can do a check manually so that does not appear to be an option.

[shriddx]

OK.... except I never get any e-mails and never have done??? 

But I don't use SME as a mail server - use my ISPs mail server via Outlook - so maybe that's the reason?

I think the message that srushik is trying to get across is that when a new update is released, you get an email everyday until the update is installed. Perhaps srushik could put in a New Feature Request (NFR) to ask that the update frequency can be set to a time frame instead of only being able to turn it on or off for daily checks. Also it does not appear that you can do a check manually so that does not appear to be an option.

[girkers]

That is right shriddx, if you don't have your server as a mail server and have not forwarded your admin account you will never receive any server email messages.

[shriddx]

AaaaaaHHH!

That's solved then... and reminded me ... I'll check whether there's any updates for me now...

[shell]

hi srushik

i have had a few comments from onsite management at remote sme sites (admin notifications are forwarded to onsite staff) about the increase in the volume and frequency of updates. 

I explain to them that this is a great indication of the work that is being put into both SME and upstream distribs.  imho if an update is released there is generally a good reason, so advice is to update asap!

having said that i can see there are some circumstances when finer control of the timing would be useful, as long as you are aware this is outside of the standard setup...

OPTION ONE:

turn off the server-manager controlled check for updates and periodically run

Code: [Select]

yum update
from the console (via ssh if remote).

this will check for updates and offer for you to run through the install process, which will need to be done all from the console, ie the web install and reconfigure options

alternatively you could turn off daily check for updates from server-manager and create a new cron job - stored in (for example) cron.weekly for weekly checks, or cron.d structured for more fine tuned timing that calls the update check. 

looking at the job that is created when update checking is turned on in server manager - /etc/cron.daily/0check4updates
this cron job first calls sleep for a random length of time  (presumably to not inundate update servers at the same time each day) and then

Code: [Select]

check4updates -m
(the -m switch sends the output to admin via email)

which does all the work.

you would get email notification of the updates needed.

I believe (but haven't confirmed) that both the above will remove the ability to run the updates from the server-manager (triggered by the turning off of the check?) so a third option could be to edit the cron job to remove the -m switch (not receive the emails).  the check would still be made, the server-manager update panel still available and no emails. 

perhaps a combination of the last two options...  weekly email, daily check with no email...

again all non standard suggestions are at your own risk and maybe broken on update.  which brings us full circle i guess!

cheers, shell

[raem]

shell & srushik

On two sme7.2 servers (upgraded from sme7.0) I looked at, there is also the same cron job in
/etc/cron.weekly
This may not be the case on all servers, as reported later in this thread by Paul Floor.

Depending on how frequently you want to receive notifications do the following, and keep in mind some updates you would probably want to apply asap (security issues), while others perhaps can wait a while.
Weekly would seem tolerable, whereas monthly might be waiting too long for notification of a security update.

To receive update notifications weekly:

mv /etc/cron.daily/0check4updates /etc/cron.weekly/
/etc/init.d/crond restart

To receive update notifications monthly:

mv /etc/cron.daily/0check4updates /etc/cron.monthly/
/etc/init.d/crond restart

As far as I know the server manager software updates panel will still function, it's just that any updates won't appear as being available until the cron job runs weekly or monthly or however often you set it to run in say /etc/cron.d/...

I'm not aware if cron jobs get replaced during minor upgrades (I don't think so), but they may get replaced during major point or version upgrades, but it's easy to change them back to what you prefer if required.

[girkers]

If this is so easy to modify by hand from daily to weekly, why is this option not then available in the server manager. I agree a month is way to long, but a week seems a reasonable time frame.

[raem]

girkers

I think it would be hard to justify coding time to create the server manager panel for a mostly one off change.

You are welcome to submit code, examples are shown in the developer manual re how to create basic server manager pages, and there is plenty of existing code to copy & modify.

[pfloor]

There is also the same cron job in
/etc/cron.weekly

Ray, I don't think that is correct.  None of my servers have 0check4updates in /etc/cron/weekly.  You may want to update your instructions.

I think it would be hard to justify coding time to create the server manager panel for a mostly

I agree.  This would probably be best as an added DB entry to yum eg: Check4Updates=daily (or weekly or monthly) and change it from /etc/cron.daily/ to /etc/crontab.

I will open a bug and submit some code.

[pfloor]

Related bug already exists concerning check4updates not disabling when disabled in Server-Manager.  http://bugs.contribs.org/show_bug.cgi?id=3250

I have revised my initial code to add a frequency DB value to allow you to set check4updates to daily, weekly or monthly.

[raem]

Paul

None of my servers have 0check4updates in /etc/cron/weekly.

I looked at 2 servers originally installed from 7.0 CD and upgraded to 7.2 + latest with yum, they both have 0check4updates in /etc/cron.weekly

I will check another clean 7.2 install, but it's offline at present.
Instructions modified to suit either situation.

Your bugzilla code changes to use a db setting look good and will replace the need to move cron files anyway.