search for: 5000ms

...tus = -107 Mar 8 07:20:50 groupwise-1-mht last message repeated 255 times Mar 8 07:20:53 groupwise-1-mht kernel: (4377,0):dlm_send_remote_convert_request:398 ERROR: status = -107 Mar 8 07:20:53 groupwise-1-mht kernel: (4377,0):dlm_wait_for_node_death:371 2062CE05ABA246988E9CCCDAE253F458: waiting 5000ms for notification of death of node 2 Mar 8 07:20:58 groupwise-1-mht kernel: (4377,0):dlm_send_remote_convert_request:398 ERROR: status = -107 Mar 8 07:20:58 groupwise-1-mht kernel: (4377,0):dlm_wait_for_node_death:371 2062CE05ABA246988E9CCCDAE253F458: waiting 5000ms for notification of death of no...

...e tried constant pings and the line is up constantly. I'm getting the following: [2010-11-13 17:56:27] NOTICE[26082] chan_sip.c: Peer 'client_201' is now UNREACHABLE! Last qualify: 29 [2010-11-13 17:56:37] NOTICE[26082] chan_sip.c: Peer 'client _201' is now Reachable. (26ms / 5000ms) [2010-11-13 17:58:12] NOTICE[26082] chan_sip.c: Peer 'client _201' is now UNREACHABLE! Last qualify: 28 [2010-11-13 17:58:22] NOTICE[26082] chan_sip.c: Peer 'client _201' is now Reachable. (27ms / 5000ms) [2010-11-13 17:59:58] NOTICE[26082] chan_sip.c: Peer 'client _201' i...

...:1] Answer("SIP/twilio-0000006e", "") in > new stack > -- Executing [100 at makeCall:2] > WaitForSilence("SIP/twilio-0000006e", "5000,2,60") in new stack > -- Waiting 2 time(s) for 5000 ms silence with 60 timeout > -- Exiting with 5000ms silence >= 5000ms required > -- Exiting with 5000ms silence >= 5000ms required > -- Executing [100 at makeCall:3] AGI("SIP/twilio-0000006e", > "agi://127.0.0.1/playmessage,45") in new stack > -- Playing '/var/nam/data/outgoing/60' (escape_d...

...:1] Answer("SIP/twilio-0000006e", "") in > new stack > -- Executing [100 at makeCall:2] > WaitForSilence("SIP/twilio-0000006e", "5000,2,60") in new stack > -- Waiting 2 time(s) for 5000 ms silence with 60 timeout > -- Exiting with 5000ms silence >= 5000ms required > -- Exiting with 5000ms silence >= 5000ms required > -- Executing [100 at makeCall:3] AGI("SIP/twilio-0000006e", > "agi://127.0.0.1/playmessage,45") in new stack > -- Playing '/var/nam/data/outgoing/60' (escape_d...

...2.0-1 ocfs2-2.6.9-22.ELsmp-1.2.0-1 rpm -qa | grep -i device device-mapper-1.01.04-1.0.RHEL4 device-mapper-multipath-0.4.5-6.0.RHEL4 Console messages: (5104,1):dlm_send_remote_convert_request:393 ERROR: status = -107 (5104,1):dlm_wait_for_node_death:285 4E4133205E3C4AD980D6BBBE4AE4014B: waiting 5000ms for notification of death of node 0 (6360,0):dlm_send_remote_convert_request:393 ERROR: status = -107 (6360,0):dlm_wait_for_node_death:285 EDB955CBD81B44C78CD9258B99F91E4C: waiting 5000ms for notification of death of node 0 (5104,1):dlm_send_remote_convert_request:393 ERROR: status = -107 (5104,1)...

...7754.698002 adv 1215977754.698025:1215977754.698028 func (88eefa53:505) 1215977362.803220:1215977362.803229) Jul 14 05:36:54 node3 (9283,2):dlm_send_remote_convert_request:398 ERROR: status = -107 Jul 14 05:36:54 node3 (9283,2):dlm_wait_for_node_death:365 0E8DC7044BA147F68D1407509F9AF3F3: waiting 5000ms for notification of death of node 0 Jul 14 05:36:54 node2 (11618,2):dlm_send_remote_convert_request:398 ERROR: status = -107 Jul 14 05:36:54 node2 (11618,2):dlm_wait_for_node_death:365 0E8DC7044BA147F68D1407509F9AF3F3: waiting 5000ms for notification of death of node 0 Jul 14 05:36:59 node3 (928...

Hi I have a question regarding CTDB RecLockLatencyMs tunable parameter. Is there any relationship between the RecLockLatencyMs property and the RecoverInterval property? Does one need to be larger than the other? Or if RecLockLatencyMs were increased to 5000ms, should some other setting be changed in proportion? We're using a geo-distributed etcd cluster for the CTDB recovery lock and I noticed a "*High RECLOCK latency"* (of 4s) message in syslog, and just wanted to see if we could safely squelch the warning, and if so, how? Thank you, -...

...s the interface so slow to hardly usable. For reasons best known to its authors, libc-client first initiates GSSAPI authentication, then checks if there is a Kerberos ticket it can use (there is none), then realizes its mistake and aborts SASL, and tries PLAIN. At this point dovecot delays for 5000ms. While not defending libs-client's odd behaviour of not checking for tickets first, it has probably done so for a long time, and dovecot from Debian lenny does not delay at this point. I am lost as how to get around this without changing the code. The "nodelay" parameter can not...

...t, DIALSTATUS doesn't return any status. How to now if a call in queue has been answered or if caller just hangup? Second, how to deal with timeout, I have strange behaviors. If I put timeout=60 in queue.conf and I call the queue passing also 60 as timeout value, asterisk is returning after 5000ms the 4000 then 2000 then 2000 aso. I can replace the 60sec value on both place, or 60 in queue conf and 10 when calling queue, I never have a stable behavior and more, not what I want. Exemple: let say asterisk should try all 20 seconds to call the member for 8 seconds: how to configure this? W...

...s*, connectivity to *some* destinations does not work for the first few seconds. To demonstrate: $ mongo mongo.example.com:27017 MongoDB shell version: 3.2.12 connecting to: mongo.example.com:27017/test 2017-02-21T03:29:30.243+0000 W NETWORK [thread1] Failed to connect to 10.1.2.3:27017 after 5000ms milliseconds, giving up. 2017-02-21T03:29:30.243+0000 E QUERY [thread1] Error: couldn't connect to server mongo.example.com:27017, connection attempt failed : connect at src/mongo/shell/mongo.js:231:14 @(connect):1:6 exception: connect failed Then connect again immediately after - connec...

...t,22622,7):dlm_send_remote_convert_request:395 ERROR: status = -112 Dec 4 09:15:06 heraclito kernel: (snmpd,16452,10):dlm_send_remote_convert_request:395 ERROR: status = -112 Dec 4 09:15:06 heraclito kernel: (snmpd,16452,10):dlm_wait_for_node_death:370 0D3E49EB1F614A3EAEC0E2A74A34AFFF: waiting 5000ms for notification of de ath of node 1 Dec 4 09:15:06 heraclito kernel: (httpd,4615,10):dlm_do_master_request:1334 ERROR: link to 1 went down! Dec 4 09:15:06 heraclito kernel: (httpd,4615,10):dlm_get_lock_resource:917 ERROR: status = -112 Dec 4 09:15:06 heraclito kernel: (python,20750,10):dlm_d...

...00:38 mgr01 kernel: o2net: no longer connected to node rack105 (num 7) at 10.244.1.105:7777 Nov 6 01:00:38 mgr01 kernel: (3270,0):dlm_send_remote_convert_request:395 ERROR: status = -112 Nov 6 01:00:38 mgr01 kernel: (3270,0):dlm_wait_for_node_death:370 4FF4E858AF6E4AEEB2650A543A320C2F: waiting 5000ms for notification of death of node 7 Nov 6 01:00:38 mgr01 kernel: o2net: accepted connection from node rack105 (num 7) at 10.244.1.105:7777 Nov 6 01:00:46 mgr01 kernel: connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4325798155, last ping 4325803155, now 4325808155 Nov...

...(timeout: 6000ms) EID 18 > NSOCK INFO [6.1610s] nsock_trace_handler_callback(): Callback: READ TIMEOUT for EID 18 [78.46.56.141:993] > Service scan sending probe GetRequest to 78.46.56.141:993 (tcp) > NSOCK INFO [6.1610s] nsock_read(): Read request from IOD #1 [78.46.56.141:993] (timeout: 5000ms) EID 34 > NSOCK INFO [6.1610s] nsock_trace_handler_callback(): Callback: WRITE SUCCESS for EID 27 [78.46.56.141:993] > NSOCK INFO [6.1840s] nsock_trace_handler_callback(): Callback: READ ERROR [Connection reset by peer (104)] for EID 34 [78.46.56.141:993] > NSOCK INFO [6.1840s] nsi_delete(...

...ct RTP learning complete - Locking on source address xx.xx.114.237:16498 I'm a bit confused because the second "Strict RTP learning after remote address set" should reset the rtp_source_learn.start timestamp, and yet the "Strict RTP learning complete" messages are less than 5000ms after that. What could be happening? Thanks again. On Tue, 18 Apr 2023 at 10:40, Joshua C. Colp <jcolp at sangoma.com> wrote: > It's probably best if you read the logic[1]. There's an entire comment > that talks about how it works. > > [1] > https://github.com/aster...

...lists.samba.org> wrote: > I have a question regarding CTDB RecLockLatencyMs tunable parameter. Is > there any relationship between the RecLockLatencyMs property and > the RecoverInterval property? Does one need to be larger than the other? Or > if RecLockLatencyMs were increased to 5000ms, should some other setting be > changed in proportion? > > We're using a geo-distributed etcd cluster for the CTDB recovery lock and I > noticed a "*High RECLOCK latency"* (of 4s) message in syslog, and just > wanted to see if we could safely squelch the warning, and i...

...- Locking on source address > xx.xx.114.237:16498 > > I'm a bit confused because the second "Strict RTP learning after remote > address set" should reset the rtp_source_learn.start timestamp, and yet the > "Strict RTP learning complete" messages are less than 5000ms after that. > What could be happening? > > Thanks again. > > > On Tue, 18 Apr 2023 at 10:40, Joshua C. Colp <jcolp at sangoma.com> wrote: > >> It's probably best if you read the logic[1]. There's an entire comment >> that talks about how it works. >...

...ts transmitted, 3 received, 0% packet loss, time 2001ms rtt min/avg/max/mdev = 91.023/93.193/96.263/2.245 ms [frankcox at mutt ~]$ ping 24.89.92.180 PING 24.89.92.180 (24.89.92.180) 56(84) bytes of data. --- 24.89.92.180 ping statistics --- 6 packets transmitted, 0 received, 100% packet loss, time 5000ms Incidentally, it is my current understanding that anything that I do with an "ip route" command will go away on a reboot, therefore if I somehow screw up the routing on this box completely all I have to do is reboot it and I'll be back to what I had before. Which is not a bad thing...

...gt; > > I have a question regarding CTDB RecLockLatencyMs tunable parameter. Is > > there any relationship between the RecLockLatencyMs property and > > the RecoverInterval property? Does one need to be larger than the other? > Or > > if RecLockLatencyMs were increased to 5000ms, should some other setting > be > > changed in proportion? > > > > We're using a geo-distributed etcd cluster for the CTDB recovery lock > and I > > noticed a "*High RECLOCK latency"* (of 4s) message in syslog, and just > > wanted to see if we could...

It's probably best if you read the logic[1]. There's an entire comment that talks about how it works. [1] https://github.com/asterisk/asterisk/blob/20/res/res_rtp_asterisk.c#L8158 On Mon, Apr 17, 2023 at 7:10 PM David Cunningham <dcunningham at voisonics.com> wrote: > Hi Joshua, > > Could you confirm if the 5 second period for learning a new audio stream > is a minimum

I didn't get any response at all to my last "request for status" on IAXTEL. So, when this happens, I attribute it to one of a number of things: 1. No-one knows. 2. No-one cares. 3. Everyone knows, but are too busy to reply. At any rate, my investigative side kicks in and I began searching thru the digest's I've gotten, looking for references to IAXTEL. Mostly it is