Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 461640 - dev-perl/Net-Server-2.6.0 uninitialized value in dns resolution cause munin to crash
Summary: dev-perl/Net-Server-2.6.0 uninitialized value in dns resolution cause munin t...
Status: RESOLVED TEST-REQUEST
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Perl team
URL: https://rt.cpan.org/Ticket/Display.ht...
Whiteboard:
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2013-03-13 14:24 UTC by Arnaud Desgranges
Modified: 2016-03-23 08:59 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info "=dev-perl/net-server-2.6.0" (emerge_info.txt,12.59 KB, text/plain)
2013-03-13 14:27 UTC, Arnaud Desgranges
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Arnaud Desgranges 2013-03-13 14:24:10 UTC
i try to run munin but fail with this message in /var/log/munin/munin-node.log :
Use of uninitialized value in pattern match (m//) at /usr/lib64/perl5/vendor_perl/5.12.4/Net/Server.pm line 600.
it is a known bug -> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693320
there is a patch proposed there
upstream bug too here -> https://rt.cpan.org/Ticket/Display.html?id=78828
please apply the patch :)

Reproducible: Always

Steps to Reproduce:
1.emerge munin
2.configure and start munin
3.error in dns resolution (package dev-perl/net-server) cause munin to crash
Actual Results:  
munin fails to work

Expected Results:  
munin working
Comment 1 Arnaud Desgranges 2013-03-13 14:27:04 UTC
Created attachment 341896 [details]
emerge --info "=dev-perl/net-server-2.6.0"
Comment 2 Arnaud Desgranges 2013-03-13 14:51:39 UTC
it doesn't crash munin it's just annoying to see that in the log.
:~
Comment 3 Mikle Kolyada (RETIRED) archtester Gentoo Infrastructure gentoo-dev Security 2013-07-15 19:23:03 UTC
we have v. 2.7.0 stable for now, try reproduce this bug there, and reopen, if bug still alive.