[zeromq-dev] Meaning of: "Pgm-WARNING: peer expired"?
Steven McCoy
steven.mccoy at miru.hk
Wed Oct 20 16:15:21 CEST 2010
On 20 October 2010 20:53, Bob Beaty <bobbeaty at comcast.net> wrote:
> All,
> I'm using the "epgm://" transport for ZeroMQ (2.0.10) and every now and
> then I'm seeing
> the following log message in my receiver:
>
> (process:26126): Pgm-WARNING **: peer expired, tsi
> 248.89.62.188.110.153.920
>
> and I'm not sure what happened, or what I should do from the ZeroMQ point
> of view.
> If it's a timeout, then maybe it's nothing major and I can ignore it, but
> it *looks* ominous,
> and I didn't want to ignore it at my own peril.
> I googled for this and got a few hits on the github issues page for
> ZeroMQ, but couldn't
> dig into the issues, sadly.
> Is this something I need to worry about?
>
>
>
It means a peer has timed out instead of cleanly shut down with a FIN
marker.
You can capture and redirect OpenPGM log messages elsewhere if you wish,
ZeroMQ doesn't do anything with them currently.
http://code.google.com/p/openpgm/wiki/OpenPgm5CReferenceErrorHandling
You can also enable the SNMP & HTTP interfaces for extra statistics,
although the additional libraries are not built within ZeroMQ. Getting SNMP
working on Windows is arduous, I've only tried cross-compiles to date
though.
http://code.google.com/p/openpgm/wiki/OpenPgm5CReferenceMonitoringAndAdministration
Somebody might get around to a ZeroMQ equivalent to JMX and make all that
information available via ZeroMQ messages, but I doubt any time soon.
--
Steve-o
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20101020/fc538596/attachment.htm>
More information about the zeromq-dev
mailing list