Bug#715141: apt_all update cronjob creates error mails when testing and unstable are not in the apt sources

2019-02-21 Thread Jan Wagner
Hi Lars,

Am 20.02.19 um 21:13 schrieb Lars Kruse:
> Am Wed, 20 Feb 2019 13:33:34 +
> schrieb Holger Levsen :
>> strangely this commit is in Buster:
>> ~/Projects/munin/munin$ git tag --contains 44604624b1c27f6
>> 2.0.44
>> 2.0.45
>> debian/2.0.44-1
>> debian/2.0.44-1_bpo9+1
>> debian/2.0.44-2
>> debian/2.0.45-1
>> debian/2.0.45-1_bpo9+1
>>
>> Lars, any idea?
[...]> @Jan: could you please verify that the issue is fixed for you?
> At least the error output of David's initial bug report should be impossible,
> unless your plugin is somehow older or you have another plugin configuration
> file hiding somewhere below /etc/munin.

I was using the version from stretch, with 2.0.45-1~bpo9+1 this issue
seems fixed, anyway ... I'm not able to filter the releases as described
in
https://github.com/munin-monitoring/munin/commit/44604624b1c27f60b78270dd577836d15f0d3c5c.

On the node:

# cat /etc/munin/plugin-conf.d/apt_all
[apt_all]
env.releases stretch
# apt-get update --print-uris|grep stretch| grep InRelease
'http://ftp.cyconet.org/debian/dists/stretch-backports/InRelease'
ftp.cyconet.org_debian_dists_stretch-backports_InRelease 0
'http://ftp.cyconet.org/debian/dists/stretch-updates/InRelease'
ftp.cyconet.org_debian_dists_stretch-updates_InRelease 0
'http://security.debian.org/dists/stretch/updates/InRelease'
security.debian.org_dists_stretch_updates_InRelease 0
'http://ftp.de.debian.org/debian/dists/stretch/InRelease'
ftp.de.debian.org_debian_dists_stretch_InRelease 0
'http://ftp.de.debian.org/debian/dists/stretch-updates/InRelease'
ftp.de.debian.org_debian_dists_stretch-updates_InRelease 0
'http://ftp.de.debian.org/debian/dists/stretch-backports/InRelease'
ftp.de.debian.org_debian_dists_stretch-backports_InRelease 0


On the Log on the munin system:

2019/02/21 14:15:13 [WARNING] Service apt_all on 192.168.66.59:4949
returned no data for label hold_1
2019/02/21 14:15:13 [ERROR] Unable to update apt_all on
192.168.66.59:4949 -> pending_stretch_backports: Missing data source
configuration attribute: label
2019/02/21 14:15:13 [WARNING] Service apt_all on 192.168.66.59:4949
returned no data for label pending_1

This results also into broken graphs. When having 4 releases filtered I
get 'pending_4' and 'hold_4' in my grpahs for example.

Cheers, Jan.
-- 
Never write mail to , you have been warned!
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GIT d-- s+: a C+++ UL P+ L+++ E--- W+++ N+++ o++ K++ w--- O M+ V- PS
PE Y++
PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h r+++ y
--END GEEK CODE BLOCK--


signature.asc
Description: OpenPGP digital signature


Bug#715141: apt_all update cronjob creates error mails when testing and unstable are not in the apt sources

2019-02-20 Thread Lars Kruse
Hello,


Am Wed, 20 Feb 2019 13:33:34 +
schrieb Holger Levsen :

> strangely this commit is in Buster:
> 
> ~/Projects/munin/munin$ git tag --contains 44604624b1c27f6
> 2.0.44
> 2.0.45
> debian/2.0.44-1
> debian/2.0.44-1_bpo9+1
> debian/2.0.44-2
> debian/2.0.45-1
> debian/2.0.45-1_bpo9+1
> 
> Lars, any idea?

indeed I am quite confident that the issue should be fixed.
I just forgot to close this bug report. Thanks for the reminder, Jan!

@Jan: could you please verify that the issue is fixed for you?
At least the error output of David's initial bug report should be impossible,
unless your plugin is somehow older or you have another plugin configuration
file hiding somewhere below /etc/munin.

Cheers,
Lars



Bug#715141: apt_all update cronjob creates error mails when testing and unstable are not in the apt sources

2019-02-20 Thread Holger Levsen
Hi Jan,

thanks for coming back to this!

On Wed, Feb 20, 2019 at 02:21:10PM +0100, Jan Wagner wrote:
> Am 06.07.13 um 09:23 schrieb David Schmitt:
> > root@testagent:~# /usr/share/munin/plugins/apt_all update 7200 1
> > E: The value 'testing' is invalid for APT::Default-Release as such a
> > release is not available in the sources
> > E: The value 'unstable' is invalid for APT::Default-Release as such a
> > release is not available in the sources
> > E: The value 'testing' is invalid for APT::Default-Release as such a
> > release is not available in the sources
> > E: The value 'unstable' is invalid for APT::Default-Release as such a
> > release is not available in the sources
> > Hit http://security.debian.org wheezy/updates Release.gpg
> > Hit http://security.debian.org wheezy/updates Release
> > Hit http://security.debian.org wheezy/updates/main amd64 Packages
> > Hit http://security.debian.org wheezy/updates/main Translation-en
> 
> As this has been fixed upstream by
> https://github.com/munin-monitoring/munin/commit/44604624b1c27f60b78270dd577836d15f0d3c5c
> can we please ship this fix with Debian buster?

strangely this commit is in Buster:

~/Projects/munin/munin$ git tag --contains 44604624b1c27f6
2.0.44
2.0.45
debian/2.0.44-1
debian/2.0.44-1_bpo9+1
debian/2.0.44-2
debian/2.0.45-1
debian/2.0.45-1_bpo9+1

Lars, any idea?


-- 
tschau,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature


Bug#715141: apt_all update cronjob creates error mails when testing and unstable are not in the apt sources

2019-02-20 Thread Jan Wagner
Am 06.07.13 um 09:23 schrieb David Schmitt:
> root@testagent:~# /usr/share/munin/plugins/apt_all update 7200 1
> E: The value 'testing' is invalid for APT::Default-Release as such a
> release is not available in the sources
> E: The value 'unstable' is invalid for APT::Default-Release as such a
> release is not available in the sources
> E: The value 'testing' is invalid for APT::Default-Release as such a
> release is not available in the sources
> E: The value 'unstable' is invalid for APT::Default-Release as such a
> release is not available in the sources
> Hit http://security.debian.org wheezy/updates Release.gpg
> Hit http://security.debian.org wheezy/updates Release
> Hit http://security.debian.org wheezy/updates/main amd64 Packages
> Hit http://security.debian.org wheezy/updates/main Translation-en

As this has been fixed upstream by
https://github.com/munin-monitoring/munin/commit/44604624b1c27f60b78270dd577836d15f0d3c5c
can we please ship this fix with Debian buster?

Many thanks, Jan.



signature.asc
Description: OpenPGP digital signature


Bug#715141: apt_all update cronjob creates error mails when testing and unstable are not in the apt sources

2017-03-03 Thread Marc Gallet
Package: munin-plugins-core
Version: 2.0.25-1+deb8u2
Followup-For: Bug #715141

Hi,

This issue just appeared on my Jessie stable in one of the recent update
of the package through unattended-upgrades.

For now I've worked around by manually editing the apt_all script to
change

> my @releases = ("stable", "testing","unstable");

to

> my @releases = ("stable")

and using dpkg-divert to avoid subsequent updates to nuke the change...

That's not really a good solution.

What fix can be expected for jessie concerning this issue?

Regards
Marc


-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages munin-plugins-core depends on:
ii  munin-common  2.0.25-1+deb8u2
ii  perl  5.20.2-3+deb8u6

Versions of packages munin-plugins-core recommends:
ii  libnet-snmp-perl  6.0.1-2

Versions of packages munin-plugins-core suggests:
ii  conntrack   1:1.4.2-2+deb8u1
ii  libcache-cache-perl 1.07-2
ii  libdbd-mysql-perl   4.028-2+deb8u2
ii  libnet-dns-perl 0.81-2+deb8u1
pn  libnet-netmask-perl 
pn  libnet-telnet-perl  
ii  libxml-parser-perl  2.41-3
ii  python  2.7.9-1
ii  ruby1:2.1.5+deb8u2
ii  ruby2.1 [ruby-interpreter]  2.1.5-2+deb8u3

-- no debconf information



Bug#715141: apt_all update cronjob creates error mails when testing and unstable are not in the apt sources

2014-09-12 Thread I. Schrey

Hi,

I too am interested in getting this fixed.
(see also: #761190)

Regards
Ingmar


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#715141: apt_all update cronjob creates error mails when testing and unstable are not in the apt sources

2014-09-08 Thread Andre Klärner
Hi Steve,

On Tue 03.09.2013 08:17:36, Steve Schnepp wrote:
> Looking closely, that was done specifically like that. But it sounds wrong
> to me, and qualifies as a bug. Will be fixed in the next upstream stable
> release.
>
> The extra $ARGV will be transparently given to the plugin, as the "config"
> or "update" is already.
>
> Well, as it's an upstream issue, it will be solved upstream :)

Has already been anything done to fix it? I also got a bunch of servers,
that update only if I work around it manually, as #720275 broke the cronjob
by introducing munin-run to run them.

If you'd like I can try to prepare a pull request for merging upstream.

Kind regards,
Andre

-- 
Andre Klärner


smime.p7s
Description: S/MIME cryptographic signature


Bug#715141: apt_all update cronjob creates error mails when testing and unstable are not in the apt sources

2013-09-02 Thread Steve Schnepp
Le 3 sept. 2013 03:15, "DUVERGIER Claude"  a
écrit :

> But sadly munin-run don't push the extra "7200" and "12" parameters to
the apt_all

Looking closely, that was done specifically like that. But it sounds wrong
to me, and qualifies as a bug. Will be fixed in the next upstream stable
release.

The extra $ARGV will be transparently given to the plugin, as the "config"
or "update" is already.

which in turns only has "update" in it's $ARGV and sees it as an error and
display the helping usage text:

> I'm not sure how this could be easily solved.

Well, as it's an upstream issue, it will be solved upstream :)


Bug#715141: apt_all update cronjob creates error mails when testing and unstable are not in the apt sources

2013-09-02 Thread DUVERGIER Claude

Hi,

I've applied the proposed solution (using $ENV{MUNIN_APT_RELEASES}) but 
ran into an unsuspected issue:


munin-node package creates a cron jobs file ("/etc/cron.d/munin-node") 
where it directly runs the apt_all plugin, as an executable script, not 
through Munin's system (like `munin-run` would), thus not taking 
munin-node configuration into account.



# If the APT plugin is enabled, update packages databases approx. once
# an hour (12 invokations an hour, 1 in 12 chance that the update will
# happen), but ensure that there will never be more than two hour (7200
# seconds) interval between updates..
*/5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then 
/etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x 
/etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi


My naive attempt to fix this was to replace direct
`/etc/munin/plugins/apt_all update 7200 12`
calls with a
`munin-run apt_all update 7200 12`
But sadly munin-run don't push the extra "7200" and "12" parameters to 
the apt_all, which in turns only has "update" in it's $ARGV and sees it 
as an error and display the helping usage text:



# munin-run apt_all update 7200 12
apt update   -- update apt databases randomly

 maxinterval:
  Enforce the updating of the apt database if it has
  been more than (maxinterval many seconds since the last update.

 probability:
  There's a 1 in (probability) chance that the database
  will be updated.


I'm not sure how this could be easily solved.

--
Duvergier Claude


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#715141: apt_all update cronjob creates error mails when testing and unstable are not in the apt sources

2013-07-06 Thread David Schmitt

Package: munin-plugins-core
Version: 2.0.6-4+deb7u1
Severity: minor

Hi,

when using the apt_all plugin the cronjob creates the following error 
messages, when only stable is configured:



root@testagent:~# /usr/share/munin/plugins/apt_all update 7200 1
E: The value 'testing' is invalid for APT::Default-Release as such a release is 
not available in the sources
E: The value 'unstable' is invalid for APT::Default-Release as such a release 
is not available in the sources
E: The value 'testing' is invalid for APT::Default-Release as such a release is 
not available in the sources
E: The value 'unstable' is invalid for APT::Default-Release as such a release 
is not available in the sources
Hit http://security.debian.org wheezy/updates Release.gpg
Hit http://security.debian.org wheezy/updates Release
Hit http://security.debian.org wheezy/updates/main amd64 Packages
Hit http://security.debian.org wheezy/updates/main Translation-en


This is because the plugin unconditionally tries to dist-upgrade to all 
values of @releases = ("stable", "testing","unstable"), which cannot be 
configured from the outside.


This also applies to 2.0.14-1~bpo70+1 and 2.0.16 seems to contain this too.

It would be nice to replace this with something like this:


my @releases = split(",", ($ENV{MUNIN_APT_RELEASES} || 
"stable,testing,unstable"))


which would allow easy configuration from the environment and plugin-conf.d.


Regards, David


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org