On 10/1/2012 10:21 πμ, Nikolaos Milas wrote:
> I am using nfsen 1.3.5 on CentOS 5.7 x86_64.
>
> Occasionally nfsen will crash for unknown reason. For example:
>
> # /data/nfsen/bin/nfsen status
> NfSen version: 1.3.5
> NfSen status:
> Collector for (pen thi) port 9995 is running [2688].
> nfsen daemon: pid: [2690] died for unknown reason.
>
> Nothing was logged regarding this crash. The time of the crash
> (indicated by stopped data graph update) does not indicate any
> association with other events that may have an influence.
>
> We are running nfsen by including in /etc/rc.local:
>
> /data/nfsen/bin/nfsen start
>
> So, why could this be happening?
Hi,
I've reported this some months earlier. In the meantime I have upgraded
to Centos 5.8 x86_64 (it's a virtual server running under a KVM host).
Nfsen remains same version (1.3.5)
I continue to see this almost daily crash ("nfsen ... died for unknown
reason)". Can anyone suggest a cause and a solution?
Note that nfdump is running flawlessly, never crashing. When restarting:
# /data/nfsen/bin/nfsen start
Starting nfcapd:(pen thi)
Error( Port: 9995 ): a collector with pid[2768] is already running
Starting nfsend.
I could set a cron job to restart nfsen every e.g. half an hour (just to
make sure) but it's not an elegant solution. Is it possible to
investigate/identify the source of these crashes?
Thanks,
Nick
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Nfsen-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
