search for: retrying

The retry filter defaults to 5 retries, but when run with verbose details produces some confusing output: $ rm -f /tmp/inject; (sleep 5s; touch /tmp/inject)& ./nbdkit -f -v -U - \ null 1G --filter=retry --filter=noextents --filter=error error-rate=100% \ error-file=/tmp/inject --filter=delay rdelay=1 \ --run 'qemu-img convert $nbd out.img' ... nbdkit: null[1]: debug: noextents:

Hi! We have an Asterisk Bussines Edition ABE-A.1-6 on a PowerEdge 2850 with 4Gb RAM. It was working 24/7 without any for a month, but for not related causes I rebooted it a week ago. Yesterday the machine suddenly stop working, with a kernel panic. We was watching logs, and found in /var/log/asterisk just before the machine hung the messages posted avobe(is the first time we see it). Anyone

On 4/1/20 5:12 AM, Richard W.M. Jones wrote: > On Tue, Mar 31, 2020 at 04:00:22PM -0500, Eric Blake wrote: >> The retry filter defaults to 5 retries, but when run with verbose >> details produces some confusing output: >> >> $ rm -f /tmp/inject; (sleep 5s; touch /tmp/inject)& ./nbdkit -f -v -U - \ >> null 1G --filter=retry --filter=noextents --filter=error

I'm having some trouble with placing some iax calls over an openvpn: Setup A is a 1.8GHz Celeron, T100P attached to a Zhone Zplex. Setup B is a 266MHz P2, T100P attached to a Zhone Zplex. Setup C is a 700MHz P3, T100P attached to an Adtran TA 750. Setup D is a 233MHz Pentium, with an X100P. Setups A and B are on the same physical network. IAX calls routed between them work fine. Setup D is

v2 was here: https://www.redhat.com/archives/libguestfs/2019-September/msg00221.html I think this is more like "the one". It handles reopen failing correctly, and there is a second test for that. I also ran my sshd tests locally and it worked in all scenarios I could think up (except of course sshd not being available at the start, but we want that to fail). Rich.

...error-rate=100% error-file=/tmp/inject --filter=delay rdelay=1 retries=3 --run 'qemu-img convert $nbd /var/tmp/out.img' nbdkit: null[1]: error: injecting EIO error into pread nbdkit: null[1]: debug: pread failed: original errno = 5 nbdkit: null[1]: debug: retry 1: waiting 2 seconds before retrying nbdkit: null[1]: error: injecting EIO error into pread nbdkit: null[1]: debug: pread failed: original errno = 5 nbdkit: null[1]: debug: retry 2: waiting 4 seconds before retrying nbdkit: null[1]: error: injecting EIO error into pread nbdkit: null[1]: debug: pread failed: original errno = 5 nbdkit...

...assObject class {0968e258-16c7-4dba-aa86-462dd61e31a3} not registered err:ole:CoGetClassObject no class object {0968e258-16c7-4dba-aa86-462dd61e31a3} could be created for context 0x1 err:ntdll:RtlpWaitForCriticalSection section 0x151b25c "?" wait timed out in thread 0009, blocked by 0024, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x151b25c "?" wait timed out in thread 0009, blocked by 0024, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x151b25c "?" wait timed out in thread 0009, blocked by 0024, retrying (60 sec) err:ntdll:RtlpWaitFo...

...-136,6 +136,12 @@ nbdkit-rate-filter: * split large requests to avoid long, lumpy sleeps when request size is much larger than rate limit +nbdkit-retry-filter: + +* allow user to specify which errors cause a retry and which ones are + passed through; for example there's probably no point retrying on + ENOMEM + Filters for security -------------------- diff --git a/configure.ac b/configure.ac index 8261a7f..7ce3dbb 100644 --- a/configure.ac +++ b/configure.ac @@ -872,6 +872,7 @@ filters="\ partition \ rate \ readahead \ + retry \ stats \...

On Tue, Mar 31, 2020 at 04:00:22PM -0500, Eric Blake wrote: > The retry filter defaults to 5 retries, but when run with verbose > details produces some confusing output: > > $ rm -f /tmp/inject; (sleep 5s; touch /tmp/inject)& ./nbdkit -f -v -U - \ > null 1G --filter=retry --filter=noextents --filter=error error-rate=100% \ > error-file=/tmp/inject --filter=delay rdelay=1

hallo, i am really confused how nativ briging is working with asterisk, i use a asterisk server as central server and register another asterisk and an iaxcomm client to the server, all three have public ips on the internet. somtimes, when i call from iaxcomm to my asterisk, the calls go peer to peer (i can see it with tcpdump) but sometimes the get routed through the central asterisk server

...-136,6 +136,12 @@ nbdkit-rate-filter: * split large requests to avoid long, lumpy sleeps when request size is much larger than rate limit +nbdkit-retry-filter: + +* allow user to specify which errors cause a retry and which ones are + passed through; for example there's probably no point retrying on + ENOMEM + Filters for security -------------------- diff --git a/configure.ac b/configure.ac index 8261a7f..7ce3dbb 100644 --- a/configure.ac +++ b/configure.ac @@ -872,6 +872,7 @@ filters="\ partition \ rate \ readahead \ + retry \ stats \...

...+ +requires qemu-img --version +requires stat --version + +files="retry-reopen-fail.img retry-reopen-fail-start + retry-reopen-fail-count retry-reopen-fail-open-count" +rm -f $files +cleanup_fn rm -f $files + +touch retry-reopen-fail-start + +# Create a custom plugin which will test retrying. +nbdkit -v -U - --filter=retry \ + sh - \ + --run 'qemu-img convert $nbd retry-reopen-fail.img' <<'EOF' +case "$1" in + open) + # Count how many times the connection is (re-)opened. + i=`cat retry-reopen-fail-open-count` + ((i++))...

In https://bugzilla.redhat.com/show_bug.cgi?id=1841820, it was pointed out that the retry filter not retrying .open means that an ssh connection (such as in a vmx+ssh v2v conversion) fails when the ssh connection itself cannot be retried. A year ago, this was an inherent limitation of our retry implementation; but in the meantime, my work to allow filters to open independent backends has made it feasible...

This happened on s390 in Koji, once. The key lines from the log are: + start_t=0 nbdkit: sh[1]: debug: retry 1: waiting 1 seconds before retrying nbdkit: sh[1]: debug: retry 1: waiting 1 seconds before retrying + end_t=1 Somehow nbdkit did wait 2 seconds (or at least, nbdkit_nanosleep (1, 0) was called twice by the retry filter). But in the bash script, time (as measured by $SECONDS) advanced from 0 to 1. I'm not sure I can explain th...

According to the mongrel_cluster.yml file you provided, you''re starting only 14 mongrels, but in your proxy balancer config you have 30 mongrels listed on ports 21000 - 21029. In this scenario, if apache tries to proxy to any ports higher than 21014 then you''ll get a proxy error as a mongrel doesn''t exist on that port. Or am I missing something? -----Original

I''ve posted this to rails-deployment as well. I have to administer a medium size rails app (1''5 million requests each day), recently I''ve switched from lighttpd + fcgi to apache + mongrel. In the following lines I am going to describe the platform: All machines are running Debian Etch, with 4 gb ram and dual core intel32 processors. Web server runs debian''s

I have an issue where * tries to route a call over IAX to another server even if the server is down. I have included the relevant entries from my iax.conf, extensions.conf, and some debug output. If someone could tell me what I have configured incorrectly, I would appreciate it. Thanks, Stephen -----------iax.conf on voip2---------- [voip1] type=friend username=voip1 host=x.x.x.x (ip

v1 was here: https://www.redhat.com/archives/libguestfs/2019-September/msg00199.html v2: - Adds a fairly simple yet comprehensive test using sh plugin. - Rebase and retest. Patch 1 is a misc patch not really related to the series. Rich.

Includes a rework of the previously posted patch for --run improvements (mostly with improved comments and commit message; I decided that waiting for the captive nbdkit to exit was overkill), and four new patches. The tests are intentionally separate, to allow rearranging the order of the series to see the failures being fixed. Eric Blake (6): server: Propagate unexpected nbdkit failure with

Hi I've 3 iax connections to my provider , each of them have own DID , PH1<----| | \/ PH2<-->|-----| <---------------------------> |----|<-- DID1 | A1 | <---------------------------> |ISP |<-- DID2 PH3<-->|-----| <---------------------------> |----|<-- DID3 I had iax phone on each of this connection , but now I want to terminate all