Bug 192832 - net-mgmt/nfsen: perl uid 80 exited on signal 11
Summary: net-mgmt/nfsen: perl uid 80 exited on signal 11
Status: Closed Not Enough Information
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Mark Felder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-19 12:33 UTC by Marko Cupać
Modified: 2016-03-17 13:47 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marko Cupać 2014-08-19 12:33:59 UTC
pacija@rsbgyucnix09:~ % uname -a
FreeBSD rsbgyucnix09.kappastar.com 9.2-RELEASE-p10 FreeBSD 9.2-RELEASE-p10 #0: Tue Jul  8 10:48:24 UTC 2014     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

pacija@rsbgyucnix09:~ % pkg info -d -x fsen
nfsen-1.3.6p1_3:
	php5-session-5.4.31
	php5-sockets-5.4.31
	p5-Socket6-0.25_1
	nfdump-1.6.12_1
	p5-Mail-Tools-2.13
	php5-5.4.31
	perl5-5.16.3_11
	rrdtool-1.4.8_2
	libiconv-1.14_3

While clicking in web interface, I get the following error quit frequently:
ERROR: nfsend socket_read() communication error: Connection reset by peer!

Also, the following is logged in messages:
Aug 19 13:32:43 rsbgyucnix09 kernel: pid 5018 (perl), uid 80: exited on signal 11
Aug 19 13:49:30 rsbgyucnix09 kernel: pid 5282 (perl), uid 80: exited on signal 11
Aug 19 13:54:31 rsbgyucnix09 kernel: pid 5302 (perl), uid 80: exited on signal 11
Aug 19 14:05:23 rsbgyucnix09 kernel: pid 5448 (perl), uid 80: exited on signal 11
Comment 1 John Marino freebsd_committer freebsd_triage 2014-08-19 12:41:43 UTC
over to maintainer
Comment 2 Mark Felder freebsd_committer freebsd_triage 2014-08-20 12:11:52 UTC
I've been seeing this error since possibly Perl 5.14. Do you find any functionality is actually broken? All of my graphs and filter requests work correctly; the error message is just annoying.
Comment 3 Mark Felder freebsd_committer freebsd_triage 2016-03-17 13:47:50 UTC
Closing as I have never seen this cause functionality issues and I haven't seen upstream address it.