similar to: Re: [ovirt-users] Bug in Snapshot Removing

Displaying 20 results from an estimated 900 matches similar to: "Re: [ovirt-users] Bug in Snapshot Removing"

2015 Jun 02
2
Re: [ovirt-users] Bug in Snapshot Removing
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
2015 May 31
0
Re: [ovirt-users] Bug in Snapshot Removing
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>>,
2015 Jun 03
0
Re: [ovirt-users] Bug in Snapshot Removing
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
2015 Jun 04
2
Re: [ovirt-users] Bug in Snapshot Removing
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
2015 Jun 04
2
Re: [ovirt-users] Bug in Snapshot Removing
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
2015 May 31
1
Bug in Snapshot Removing
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
2011 Jul 25
1
dahdi channels busy/congested
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
2011 Aug 07
1
fail to correctly build 1.8.5 ??
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
2020 Oct 05
2
certbot stopped working on CentOS 7: pyOpenSSL module missing required functionality
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.
2020 Oct 05
0
certbot stopped working on CentOS 7: pyOpenSSL module missing required functionality
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:
2015 Jun 03
2
Re: [ovirt-users] Bug in Snapshot Removing
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
2009 Dec 22
2
traffic not going through tunnel
Dear all, we have a very strange problem, - we have 3 VPN endpoints - all are in one NETWORK - all daemons come up and connect without any problem and normally we have no problem working through the VPN but in some cases the connection does not work because the traffic leaves the TAP interface on one VPN endpoint but never arrives on the other end, the similarities between the packages seem to
2005 Jan 22
1
te405P and german PMX
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
2015 Jun 11
0
Re: [ovirt-users] Bug in Snapshot Removing
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
2015 Jun 04
0
Re: [ovirt-users] Bug in Snapshot Removing
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
2007 Jun 27
1
SEM model fit
I wonder if someone could explain why, when I perform confirmatory factor-analysis model using polychoric correlations why I do not get an estimated confidence interval for the RMSEA. My experience with these type models is that I would obtain a confidence interval estimate. I did not get any warning messages with the output. RESULTS: Model Chisquare = 1374 Df = 185 Pr(>Chisq) = 0
2008 May 13
2
(PR#11281) Bug in R 2.7 for over long lines (crasher+proposed fix!)
>>>>> "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
2008 Apr 25
2
Bug in R 2.7 for over long lines (crasher+proposed fix!) (PR#11281)
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 >
2019 Sep 04
1
Winbind group mapping
Hey there, currently I'm trying to map my users and groups using winbind on a samba fileserver member server which is connected to a samba DC. Both are running version 4.10.0 from the 19.04 ubuntu repository. Here's my samba member servers smb.conf: [global] security = ADS workgroup = SAMDOM realm = SAMDOM.DOMAIN:TLD log file = /var/log/samba/%m.log log level = 1 server min protocol =
2008 May 10
1
(PR#11281) Bug in R 2.7 for over long lines (crasher+proposed
You will see the current code is different, and your 'fix' is not needed nor applies in R-devel. You failed to provide an example to reproduce the alleged bug, but the issue does seem to be using lines beyond the documented line length. So it would have only affected people who did that .... And generating a new report (PR#11438) was distinctly unfriendly. If after studing the R FAQ