search for: retrie

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 co...

...ame 65, but we only have others! May 15 20:27:49 WARNING[4033]: PRI: !! Got reject for frame 106, but we only have others! May 15 20:30:13 WARNING[4033]: PRI: !! Got reject for frame 114, but we only have others! May 15 20:36:10 WARNING[4033]: Avoided initial deadlock for 'Zap/63-1', 10 retries! May 15 20:37:48 WARNING[4033]: Avoided initial deadlock for 'Zap/64-1', 10 retries! May 15 20:38:37 WARNING[4033]: Failed to write frame May 15 20:39:08 WARNING[4033]: Avoided initial deadlock for 'Zap/64-1', 10 retries! May 15 20:39:14 WARNING[4033]: Avoided initial deadlock fo...

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 error-rate=100% \ >> error-file=/tmp/inject --fi...

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.

On Wed, Apr 01, 2020 at 08:46:53AM -0500, Eric Blake wrote: > 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 error-rate=100% \ > >> error-...

I use eMule 0.50a with wine 1.1.43, and crashes every day. I am attaching the log. Code: Xlib: extension "Generic Event Extension" missing on display ":1.0". Xlib: extension "Generic Event Extension" missing on display ":1.0". fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.VC90.CRT" (9.0.21022.8) Xlib:

...--filter=retry host=remote /var/tmp/test.iso \ --run 'qemu-img convert -p -f raw $nbd -O qcow2 test.qcow2' this operation can recover from temporary failures in at least some circumstances. The NBD connection (a local Unix domain socket in the example above) is not interrupted during retries, so NBD clients don't need to be taught how to retry - everything is handled internally by nbdkit. --- TODO | 6 + configure.ac | 2 + docs/nbdkit-captive.pod | 3 + filters/retry/Makefile.am | 67 +++++...

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

...--filter=retry host=remote /var/tmp/test.iso \ --run 'qemu-img convert -p -f raw $nbd -O qcow2 test.qcow2' this operation can recover from temporary failures in at least some circumstances. The NBD connection (a local Unix domain socket in the example above) is not interrupted during retries, so NBD clients don't need to be taught how to retry - everything is handled internally by nbdkit. --- TODO | 6 + configure.ac | 2 + docs/nbdkit-captive.pod | 3 + filters/retry/Makefile.am | 67 +++++...

We use a custom sh plugin to test retries are working. --- tests/Makefile.am | 8 +++ tests/test-retry-reopen-fail.sh | 108 ++++++++++++++++++++++++++++++++ tests/test-retry.sh | 97 ++++++++++++++++++++++++++++ 3 files changed, 213 insertions(+) diff --git a/tests/Makefile.am b/tests/Makefile.am index 1b1e...

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 to implement. Eric Blake (2): retry: Add in retry support during .open retry: Test previous patch tests/Makefile.am...

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

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.

...o allow rearranging the order of the series to see the failures being fixed. Eric Blake (6): server: Propagate unexpected nbdkit failure with --run tests: Enhance captive test retry: Check next_ops->can_FOO on retry tests: Test for retry-readonly behavior retry: Avoid assertion during retried extents tests: Test retry after partial extents server/captive.c | 47 +++++++++++---- filters/retry/retry.c | 80 ++++++++++++++++++++++-- tests/Makefile.am | 4 ++ tests/test-captive.sh | 46 ++++++++++++-- tests/test-retry-extents.sh | 114 ++++++++...

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