Bug #255

PING time configuration

Added by Madars over 6 years ago. Updated over 6 years ago.

Status:ClosedStart date:11/29/2017
Priority:Normal (Code 4)Due date:
Assignee:-% Done:

100%

Category:-
Target version:-

Description

Following config causes all processes to fail the ping:

        <appconfig>
                <sanity>5</sanity>
...
        <defaults>
                <pingtime>5</pingtime>
                <ping_max>2</ping_max>

I would understand that this is:
- Every 25 seconds, perform ping, pin max response time 10 sec.

But for some reason Enduro/X thinks that pings have failed for all processes.

History

#1 Updated by Madars over 6 years ago 

N:NDRX:5:19462:7f543fd187c0:000:20171129:220132000:sanity.c:0150:Time for sanity checking...
N:NDRX:5:19462:7f543fd187c0:000:20171129:220132000:iutils.c:0492:gencall command: 52, reply_only=0, need_reply=0 call flags=0x0, getcall flags=1
N:NDRX:4:19462:7f543fd187c0:000:20171129:220132000:iutils.c:0528:Sending data to [/n00b,srv,admin,tmsrv,310,19467] call flags=0x0
N:NDRX:5:19462:7f543fd187c0:000:20171129:220132000:iutils.c:0300:Enabling NONBLOCK send
N:NDRX:5:19462:7f543fd187c0:000:20171129:220132001:iutils.c:0550:Reply not needed!
N:NDRX:4:19462:7f543fd187c0:000:20171129:220132001:d_ping.c:0101:srv_send_ping returns with status 0
N:NDRX:5:19462:7f543fd187c0:000:20171129:220132001:sanity.c:0554:Ping response not in time - requesting kill (ping_time=5 delta=6 ping_max=5)
N:NDRX:3:19462:7f543fd187c0:000:20171129:220132001:sanity.c:0490:Killing PID: 19467/tmsrv/310 with signal -2
N:NDRX:4:19462:7f543fd187c0:000:20171129:220132001:cessor.c:0342:>>>>>>>>>>>>>>>>>>got message, len : 184
N:NDRX:5:19462:7f543fd187c0:000:20171129:220132001:cessor.c:0406:Command ID: 53
N:NDRX:5:19462:7f543fd187c0:000:20171129:220132001:cessor.c:0426:Source: [/n00b,srv,reply,tmsrv,310,19467] Command: 53 Executing command: srvping
N:NDRX:4:19462:7f543fd187c0:000:20171129:220132001:d_ping.c:0129:Server id=310 ok, binary: [tmsrv] ping reply seq: 1, rsptime: 1ms

#3 Updated by Madars over 6 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

#4 Updated by Madars over 6 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF