On Mon, Mar 18, 2013 at 02:33:28PM +0100, Arturo Moral wrote:
Well, after upgrading, unattended-upgrades was launched daily as it should
be. The only problem then was that it didn't perform any package upgrade
even when there were things to upgrade.
After checking the
On Tue, Mar 19, 2013 at 7:48 AM, Michael Vogt m...@debian.org wrote:
On Mon, Mar 18, 2013 at 02:33:28PM +0100, Arturo Moral wrote:
Well, after upgrading, unattended-upgrades was launched daily as it
should
be. The only problem then was that it didn't perform any package upgrade
even when
Well, after upgrading, unattended-upgrades was launched daily as it should
be. The only problem then was that it didn't perform any package upgrade
even when there were things to upgrade.
After checking the /var/log/unattended-upgrades/unattended-upgrades.log, I
spotted the problem:
Initial
I just upgraded to version 0.79.5 (current in wheezy).
I replaced my old /etc/apt/apt.conf.d/50unattended-upgrades config file
by the new one and modified some lines:
// Automatically upgrade packages from these origin patterns
Unattended-Upgrade::Origins-Pattern {
// Archive or Suite
On Sat, Mar 9, 2013 at 12:21 AM, Steven Chamberlain ste...@pyro.eu.orgwrote:
On 08/03/13 17:37, Arturo Moral wrote:
[...] I should see a log
file inside /var/log/unattended-upgrades/ with details on every day's
check [...]
I agree. On a wheezy/sid system using regular cron (not anacron)
Hi,
Today could you please re-check:
# cat /var/spool/anacron/cron.daily
# grep anacron /var/log/syslog.1
or:
# zgrep anacron /var/log/syslog.1.gz
# tail /var/log/unattended-upgrades/unattended-upgrades.log
Thanks!
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email
On Sat, Mar 9, 2013 at 1:42 PM, Steven Chamberlain ste...@pyro.eu.orgwrote:
Hi,
Hello, Steven,
Today could you please re-check:
# cat /var/spool/anacron/cron.daily
20130308
# grep anacron /var/log/syslog.1
Mar 7 12:54:22 raspi anacron[1939]: Job `cron.daily' terminated
Mar 7
On Fri, Mar 8, 2013 at 6:50 AM, Michael Vogt m...@debian.org wrote:
On Thu, Mar 07, 2013 at 04:43:03PM +0100, g0to wrote:
Package: unattended-upgrades
Version: 0.79.4
Severity: grave
Tags: security
Justification: renders package unusable
Thanks for your bugreport.
after trying to
Hi, Teodor,
On Fri, Mar 8, 2013 at 7:50 AM, Teodor MICU mteo...@gmail.com wrote:
2013/3/7 g0to amo...@gmail.com:
-- Configuration Files:
/etc/apt/apt.conf.d/50unattended-upgrades changed:
// Automatically upgrade packages from these origin patterns
Unattended-Upgrade::Origins-Pattern {
Hi g0to,
This looks to be an anacron issue, and /etc/cron.daily/apt not running
automatically. Please could you take a look at:
# cat /var/spool/anacron/cron.daily
# grep daily /var/log/cron.log.1
# ps aux | grep cron | grep -v grep
Thanks!
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
On Fri, Mar 8, 2013 at 3:20 PM, Steven Chamberlain ste...@pyro.eu.orgwrote:
Hi g0to,
Hello, Steven!
This looks to be an anacron issue, and /etc/cron.daily/apt not running
automatically. Please could you take a look at:
# cat /var/spool/anacron/cron.daily
20130308
# grep daily
On 08/03/13 15:08, Arturo Moral wrote:
# cat /var/spool/anacron/cron.daily
20130308
This means 'cron' was working properly, and it updated the timestamp in
that file.
What about the file /etc/cron.d/anacron ? Is it there, what are its
contents? Also:
$ ls -al /usr/sbin/anacron
On Fri, Mar 8, 2013 at 4:15 PM, Steven Chamberlain ste...@pyro.eu.orgwrote:
On 08/03/13 15:08, Arturo Moral wrote:
# cat /var/spool/anacron/cron.daily
20130308
This means 'cron' was working properly, and it updated the timestamp in
that file.
What about the file /etc/cron.d/anacron
On 16:27, Arturo Moral wrote:
# grep -i daily /var/log/syslog
Mar 8 11:27:51 raspi anacron[1920]: Job `cron.daily' terminated
The log was probably rotated at that point. Is there anythikng more of
interest in the preceding log, e.g. syslog.1 or syslog.1.gz?
Thanks,
Regards,
--
Steven
On Fri, Mar 8, 2013 at 4:49 PM, Steven Chamberlain ste...@pyro.eu.orgwrote:
On 16:27, Arturo Moral wrote:
# grep -i daily /var/log/syslog
Mar 8 11:27:51 raspi anacron[1920]: Job `cron.daily' terminated
The log was probably rotated at that point. Is there anythikng more of
interest in
control: -1 severity normal
2013/3/8 Arturo Moral amo...@gmail.com:
This config was removed in version 0.79.5 and might not work at all:
I'm currently using 0.79.4, therefore the config change does not affect me,
right?
You should not use it, 0.79.5 will migrate to testing on the following
Hey, Teodor,
On Fri, Mar 8, 2013 at 6:09 PM, Teodor MICU mteo...@gmail.com wrote:
control: -1 severity normal
2013/3/8 Arturo Moral amo...@gmail.com:
This config was removed in version 0.79.5 and might not work at all:
I'm currently using 0.79.4, therefore the config change does not
On 08/03/13 17:37, Arturo Moral wrote:
[...] I should see a log
file inside /var/log/unattended-upgrades/ with details on every day's
check [...]
I agree. On a wheezy/sid system using regular cron (not anacron) I get
exactly this each day from unattended-upgrades 0.79.4 when there are no
Package: unattended-upgrades
Version: 0.79.4
Severity: grave
Tags: security
Justification: renders package unusable
Dear Maintainer,
after trying to make it run by myself and googling and make a few questions
here[1] and there[2], I've decided to contact you to report what seems to be a
lack
On Thu, Mar 07, 2013 at 04:43:03PM +0100, g0to wrote:
Package: unattended-upgrades
Version: 0.79.4
Severity: grave
Tags: security
Justification: renders package unusable
Thanks for your bugreport.
after trying to make it run by myself and googling and make a few questions
here[1] and
2013/3/7 g0to amo...@gmail.com:
-- Configuration Files:
/etc/apt/apt.conf.d/50unattended-upgrades changed:
// Automatically upgrade packages from these origin patterns
Unattended-Upgrade::Origins-Pattern {
// Codename based matching:
// This will follow the migration of a
21 matches
Mail list logo
