Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] perfsonar_ma failed for segmentation fault on perfSONAR v3.3.2

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] perfsonar_ma failed for segmentation fault on perfSONAR v3.3.2


Chronological Thread 
  • From: Andrew Lake <>
  • To: Jarvis Zhang <>
  • Cc: "" <>
  • Subject: Re: [perfsonar-user] perfsonar_ma failed for segmentation fault on perfSONAR v3.3.2
  • Date: Mon, 3 Nov 2014 09:30:55 -0500

Hi,

You might want to run memtest or a similar tool to make sure your system memory is ok. It might also be worth trying a reboot. The fact it hit multiple services and that the segfault is happening on a pretty harmless looking echo in the start-up script (not even in the MA code) makes me wonder if something else is happening.

Thanks,
Andy



On Nov 3, 2014, at 1:38 AM, Jarvis Zhang <> wrote:

Hi,
I’m working on perfSONAR v3.3.2 for several months, and all modules works well when suddenly all Measurement Archive(perfSONAR-BUOY, PingER, SNMP) breakdown this morning. The status on Web Interface says ’Not Running’.

I’ve tried to start it manually but I get segmentation fault: 
service /etc/init.d/perfsonarbuoy_ma restart
/opt/perfsonar_ps/perfsonarbuoy_ma/bin/daemon.pl --config=/opt/perfsonar_ps/perfsonarbuoy_ma/etc/daemon.conf --pidfile=perfsonarbuoy_ma.pid --piddir=/var/run 
logger=/opt/perfsonar_ps/perfsonarbuoy_ma/etc/daemon_logger.conf --user=perfsonar --group=perfsonar
/etc/init.d/perfsonarbuoy_ma: line 48:  2826 Segmentation fault      $PERFSONAR
/etc/init.d/perfsonarbuoy_ma start: perfSONAR perfSONAR-BUOY MA Service could not be started

The output of ‘ulimit -a’:
core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 127176
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) unlimited
cpu time               (seconds, -t) unlimited
max user processes              (-u) 127176
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

And the content of /var/log/perfsonar/perfsonarbuoy_ma.log is below:
2014/11/03 14:28:32 (2859) WARN> daemon.pl:262 main:: - Setting listener queue size to 100 
2014/11/03 14:28:32 (2859) WARN> daemon.pl:267 main:: - Setting LS registration interval at 60 minutes
2014/11/03 14:28:32 (2859) WARN> daemon.pl:272 main:: - Enabling echo service for each endpoint unless specified otherwise
2014/11/03 14:28:32 (2859) INFO> perfSONARBUOY.pm:241 perfSONAR_PS::Services::MA::perfSONARBUOY::init - Setting service access point to http://$my_global_ipv4_add:8085/perfSONAR_PS/services/pSB
2014/11/03 14:28:32 (2859) WARN> perfSONARBUOY.pm:256 perfSONAR_PS::Services::MA::perfSONARBUOY::init - Setting 'service_description' to 'perfSONAR_PS perfSONAR-BUOY MA at Sino-German Joint Software Institute'.
2014/11/03 14:28:32 (2859) WARN> perfSONARBUOY.pm:263 perfSONAR_PS::Services::MA::perfSONARBUOY::init - Setting 'service_name' to 'perfSONAR-BUOY MA'.
2014/11/03 14:28:32 (2859) WARN> perfSONARBUOY.pm:270 perfSONAR_PS::Services::MA::perfSONARBUOY::init - Setting 'service_type' to 'MA'.

Any insights appreciated.

Thanks,
Jarvis Zhang




Archive powered by MHonArc 2.6.16.

Top of Page