similar to: traffic not going through tunnel

Small addition again: This error shows up in the log while removing snapshots WITHOUT rendering the Vms unresponsive — Jun 01 01:33:45 mc-dc3ham-compute-02-live.mc.mcon.net libvirtd[1657]: Timed out during operation: cannot acquire state change lock Jun 01 01:33:45 mc-dc3ham-compute-02-live.mc.mcon.net vdsm[6839]: vdsm vm.Vm ERROR vmId=`56848f4a-cd73-4eda-bf79-7eb80ae569a9`::Error getting block

Hello Soeren. I've started to look at this issue and I'd agree that at first glance it looks like a libvirt issue. The 'cannot acquire state change lock' messages suggest a locking bug or severe contention at least. To help me better understand the problem I have a few questions about your setup. >From your earlier report it appears that you have 15 VMs running on the

Hi, I would send those, but unfortunately we did not think about the journals getting deleted after a reboot. I just made the journals persistent on the servers, we are trying to trigger the error again last time we only got half way through the VM’s when removing the snapshots so we have a good chance that it comes up again. Also the libvirt logs to the journal not to libvirtd.log, i would

Hi Adam, Hi Eric, We had this issue again a few minutes ago. One machine went down exactly the same way as described, the machine had only one snapshot and it was the only snapshot that was removed, before that in the same scriptrun we deleted the snapshots of 15 other Vms, some without, some with 1 and some with several snapshots. Can i provide anything from the logs that helps ? Regards

On 03/06/15 07:36 +0000, Soeren Malchow wrote: >Dear Adam > >First we were using a python script that was working on 4 threads and >therefore removing 4 snapshots at the time throughout the cluster, that >still caused problems. > >Now i took the snapshot removing out of the threaded part an i am just >looping through each snapshot on each VM one after another, even with

Hello everybody, I've been using asterisk 1.2 for quite a long time now, but I thought it's time to try a newer version of asterisk. So I downloaded 1.8.5, extracted the tar, ran configure, make, make install ... Everything looks fine (no obvious compile/link errors). But as soon as I start asterisk, it dies with a segfault. I executed asterisk within strace and last action before the

Yes, I had a typo in the mail, but not in the cronjob Still wondering how to get certbot-1.7.0-1.el7.noarch working on CentOS 7 again.

Dear all, i have a problem with a system running - Ubuntu 10.04 ( all updates done ) - ii asterisk 1:1.8.5.0-1digium1~lucid Open Source Private Branch Exchange (PBX) - ii asterisk-dahdi 1:1.8.5.0-1digium1~lucid DAHDI devices support for the Asterisk PBX I also use freepbx 2.9 for the configuration. Hardware is a Dell R410 and a Digium

Not directly an answer to your question, but we had so many problems with the certbot in different constellations, that we moved to https://github.com/acmesh-official/acme.sh which works just fine basically everywhere cheers Soeren ?On 05.10.20, 15:18, "CentOS on behalf of Alexander Farber" <centos-bounces at centos.org on behalf of alexander.farber at gmail.com> wrote:

Hi all, i am stuck with the configuration of asterisk - modules are loaded ( zaptel and wct4xxp ) - i have zaptel.conf configure, output of ztcfg -vv --- snip -- rapid:~# ztcfg -vv Zaptel Configuration ====================== SPAN 1: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1) SPAN 2: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet (DSX-1) SPAN 3: ESF/B8ZS Build-out: 0 db (CSU)/0-133 feet

Dear all I am not sure if the mail just did not get any attention between all the mails and this time it is also going to the libvirt mailing list. I am experiencing a problem with VM becoming unresponsive when removing Snapshots (Live Merge) and i think there is a serious problem. Here are the previous mails, http://lists.ovirt.org/pipermail/users/2015-May/033083.html The problem is on a

And sorry, another update, it does kill the VM partly, it was still pingable when i wrote the last mail, but no ssh and no spice console possible From: Soeren Malchow <soeren.malchow@mcon.net<mailto:soeren.malchow@mcon.net>> Date: Monday 1 June 2015 01:35 To: Soeren Malchow <soeren.malchow@mcon.net<mailto:soeren.malchow@mcon.net>>,

Dear Adam First we were using a python script that was working on 4 threads and therefore removing 4 snapshots at the time throughout the cluster, that still caused problems. Now i took the snapshot removing out of the threaded part an i am just looping through each snapshot on each VM one after another, even with ³sleeps² inbetween, but the problem remains. But i am getting the impression that

Currently, i have nodes with PMTUDiscovery =yes and ClampMSS = yes. When the server does not receive a PMTU request back from one of the clients even when the packet size is very small (say 164), then it reverts to TCP. Should i turn off PMTUDiscovery or should it be ok to leave on? It takes a very long time to do simple pings (1 second or so), so i wonder what else i can do?

We are still having this problem and we can not figure out what to do, i sent the logs already as download, can i do anything else to help ? On 04/06/15 17:08, "Soeren Malchow" <soeren.malchow@mcon.net> wrote: >Hi, > >I would send those, but unfortunately we did not think about the journals >getting deleted after a reboot. > >I just made the journals

On 04/06/15 13:08 +0000, Soeren Malchow wrote: >Hi Adam, Hi Eric, > >We had this issue again a few minutes ago. > >One machine went down exactly the same way as described, the machine had >only one snapshot and it was the only snapshot that was removed, before >that in the same scriptrun we deleted the snapshots of 15 other Vms, some >without, some with 1 and some with

>>>>> "BDR" == Prof Brian Ripley <ripley at stats.ox.ac.uk> >>>>> on Tue, 13 May 2008 07:32:43 +0100 (BST) writes: BDR> This example does not crash in R 2.7.0, R-patched nor BDR> R-devel (r45677) for me (x86_64 F8 Linux.) It also BDR> does not crash with the CRAN build of R 2.7.0 on BDR> Windows XP. Neither does it

> Currently, i have nodes with PMTUDiscovery =yes and ClampMSS = yes. Hello, these features were introduced in 1.0.13 correct ?? I also understand that the two settings are by default "yes" if not explictly set to "no" in the config file. what may happen if I have a network with mixed versions from 1.0.11 and 1.0.13, where the older daemons do not implement that feature

Well this has had me stumped for days now. For months I've been using tinc in TCPOnly because I always received the unknown host error when using UDP. On Monday, i set the flag IndirectData = yes in my host files, and removed the TCPOnly line. Initially, everything worked great. My throughput increased from 600KB/sec to 2MB/sec between the sites. However, I also did some testing with

OK, I am just sending it here too as it looks like r-devel at r-project.org is not the right place: =EF=BB=BFOn Fri, 2008-04-25 at 08:48 +0200, Soeren Sonnenburg wrote: > While trying to fix swig & R2.7 I actually discovered that there is a > bug in R 2.7 causing a crash (so R & swig might actually work): >=20 > the bug is in ./src/main/gram.c line 3038: >=20 >