https://bugzilla.novell.com/show_bug.cgi?id=803845 https://bugzilla.novell.com/show_bug.cgi?id=803845#c Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |lrupp@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803845 https://bugzilla.novell.com/show_bug.cgi?id=803845#c2 Robert Munteanu changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|robert.munteanu@gmail.com | --- Comment #2 from Robert Munteanu 2013-02-18 18:59:18 UTC --- (In reply to comment #1)

Did you follow the descriptions here? https://en.opensuse.org/index.php?title=Nagios-plugins-zypper&stable=1#Refreshing_or_ignoring_outdated_repositories

I have ns3:~ # grep -e PERMISSION_SECURITY /etc/sysconfig/security PERMISSION_SECURITY="easy local So I haven't touched any permissions. Since I use check_zypper -r I expect the repositories to be refreshed.

If this still does not resolve your problem, please enable debug output like described here: https://en.opensuse.org/index.php?title=Nagios-plugins-zypper&oldid=58321

I have set the debug flag to 1 ns3:~ # grep -e DEBUG /usr/lib/nagios/plugins/check_zypper | head -n 2 use vars qw($PROGNAME $VERSION $DEBUG); $DEBUG = 1; But there is no extra debug information included in the email. Am I doing something wrong? And there is no /tmp/check_zypper_output.txt file in my system. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803845 https://bugzilla.novell.com/show_bug.cgi?id=803845#c4 Robert Munteanu changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|robert.munteanu@gmail.com | --- Comment #4 from Robert Munteanu 2013-02-27 19:11:00 UTC --- $ /usr/lib/nagios/plugins/check_zypper -r -w '' -d INFO: check_zypper version: 1.40 INFO: userid : root INFO: groupid: nagios INFO: groupid: nagios INFO: groupid: nagcmd INFO: openSUSE,12.1,0 INFO: $VAR1 = { 'openSUSE' => [ '11.2', '11.3', '11.4', '12.1' ], 'SLE' => [ '10.4', '11.1', '11.2' ] }; Trying: /usr/sbin/zypp-refresh-wrapper 2>/dev/null 1>&2 LINE: refreshing 'Apache:Modules' ... Done. LINE: refreshing 'devel_tools_scm' ... Done. LINE: refreshing 'home_robert_munteanu' ... Done. LINE: refreshing 'repo-non-oss' ... Done. LINE: refreshing 'repo-oss' ... Done. LINE: refreshing 'repo-update' ... Done. LINE: refreshing 'server_php_applications' ... Done. LINE: refreshing 'server_php_extensions' ... Done. LINE: refreshing 'sonar' ... Done. INFO: Trying unset LANG; /usr/bin/zypper sl 2>/dev/null 1>&2 INFO: Trying unset LANG; /usr/bin/zypper --xmlout --non-interactive list-updates -t package -t patch LINE: <?xml version='1.0'?> LINE: <stream> LINE: <message type="info">Loading repository data...</message> LINE: <message type="info">Reading installed packages...</message> LINE: <update-status version="0.6"> LINE: <update-list> LINE: </update-list> LINE: </update-status> LINE: </stream> INFO: Packages (paccount): 0 INFO: Optional (optcount): 0 INFO: Recommended (reccount): 0 INFO: Security (seccount): 0 INFO: Unsupported (uspcount): 0 $VAR1 = { 'security' => {}, 'optional' => {}, 'unsupported' => {}, 'recommended' => {}, 'package' => {} }; INFO: found openSUSE - checking supportstatus INFO: found 12.1 for openSUSE in %supported_release - OK Updates OK : no updates available | security=0;;;; recommended=0;;;; optional=0;;;; packages=0;;;; INFO: Exit-Code: 0 $ rpm -q nagios-plugins-zypper nagios-plugins-zypper-1.40-1.1.1.noarch Would it help if I passed '-d' to check_zypper in my nagios config? I don't mind the extra noise as long as I can catch one valuable debug output in my email in a couple of days. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803845 https://bugzilla.novell.com/show_bug.cgi?id=803845#c6 --- Comment #6 from Lars Vogdt 2013-03-14 16:54:28 CET --- Any news here? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803845 https://bugzilla.novell.com/show_bug.cgi?id=803845#c8 --- Comment #8 from Lars Vogdt 2013-03-15 10:01:14 CET --- Thanks for the reply - awaiting input ;-) (In reply to comment #7)

By the way, would upgrading to 1.45 make any difference?

No. The biggest change from 1.40 to 1.45 affected only the apparmor profile, which is unrelated in your case. The rest was just distribution specific. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803845 https://bugzilla.novell.com/show_bug.cgi?id=803845#c10 Lars Vogdt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME Severity|Normal |Major --- Comment #10 from Lars Vogdt 2013-04-04 23:56:44 CEST ---

From the logfile:

LINE: refreshing 'sonar' .. Error: LINE: refusing unsigned file repomd.xml LINE: Error: LINE: Could not refresh repository 'sonar': So there is an error in one of your repositories, that the plugin could not resolve automatically. As result, especially this repo is not refreshed. I do not see this as a problem of the plugin, as the behavior is expected: repo could not be refreshed -> critical state If you disable this repo (or fix it? - just to mention 2 possible solutions), the plugin should be able to work as expected. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803845 https://bugzilla.novell.com/show_bug.cgi?id=803845#c12 --- Comment #12 from Robert Munteanu 2013-04-30 19:48:26 UTC --- Created an attachment (id=537498) --> (http://bugzilla.novell.com/attachment.cgi?id=537498) Debug log -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803845 https://bugzilla.novell.com/show_bug.cgi?id=803845#c14 Lars Vogdt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |robert.munteanu@gmail.com --- Comment #14 from Lars Vogdt 2013-07-09 17:59:43 CEST --- Robert: did you meanwhile find the time to test if the package in http://download.opensuse.org/repositories/server:/monitoring/openSUSE_12.1/n... fixes your problem ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803845 https://bugzilla.novell.com/show_bug.cgi?id=803845#c16 Lars Vogdt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |maintenance@opensuse.org --- Comment #16 from Lars Vogdt 2013-07-31 18:05:33 CEST --- (In reply to comment #15)

However, it would be good to add another check, for ' (Service Check Timed Out)' , which now causes a CRITICAL event.

Well, the check can of course try to rerun if there is a timeout. But neither Nagios, NRPE nor SSH will wait forever that the check finished. So the logic here is: if there is a problem and the check can not be executed, raise an error. Depending on the paranoia of the administrator, this can be from "Security problem, as I can not check if there is a security update" to "well, relax, I will try it tomorrow again"... As (open)SUSE should be secure in a default installation, CRICITAL is following the paranoid administrator here. It's right that the check might be able to handle this problem in another way, but I guess I need some time to think about a solution that is useful for both admins here and allows them to define what they think the result should look like. I hope that's understandable for you? If yes, please open a feature request for this on https://features.opensuse.org/ For the reported problem, I like to schedule a maintenance update with the current package in server:monitoring. Maintenance: can you please provide a SWAMP-ID for a nagios-plugins-zypper update on all current openSUSE distributions ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803845 https://bugzilla.novell.com/show_bug.cgi?id=803845#c18 Lars Vogdt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |FIXED --- Comment #18 from Lars Vogdt 2013-07-31 18:44:56 CEST --- (In reply to comment #17)

Hi Lars, a swampid for openSUSE is not necessary. Just open a maintenancerequest with the updated packages for 12.2 and 12.3. Thanks.

Thanks. Maintenancerequest 185289 submitted for 12.2 and 12.3. Closing here as fixed, rest up to maintenance. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.