similar to: "virsh list" ahngs

On 02/20/2017 09:10 PM, Michal Privoznik wrote: > On 17.02.2017 17:18, Yunchih Chen wrote: >> `virsh list` hangs on my server that hosts a bunch of VMs. >> This might be due to the Debian upgrade I did on Feb 15, which upgrades >> `libvirt` from 2.4.0-1 to 3.0.0-2. >> I have tried restarting libvirtd for a few times, without luck. >> >> Attached below are

`virsh list` hangs on my server that hosts a bunch of VMs. This might be due to the Debian upgrade I did on Feb 15, which upgrades `libvirt` from 2.4.0-1 to 3.0.0-2. I have tried restarting libvirtd for a few times, without luck. Attached below are some relevant logs; let me know if you need some more for debugging. Thanks for your help!! root@vm-host:~# uname -a Linux vm-host 4.6.0-1-amd64 #1

On Sat, Feb 18, 2017 at 12:21:31AM +0800, Yunchih Chen wrote: > >`virsh list` hangs on my server that hosts a bunch of VMs. >This might be due to the Debian upgrade I did on Feb 15, which upgrades >`libvirt` from 2.4.0-1 to 3.0.0-2. >I have tried restarting libvirtd for a few times, without luck. > >Attached below are some relevant logs; let me know if you need some more

I have identical two hypervisors same operating system: Ubuntu 22.04.2 LTS Recently both virsh stopped talking to the libvirtd. Both stopped within a few days of each other. Currently if I run: virsh uri virsh version virsh list # virsh list ..nothing just hangs When I ran strace on these broken machines it get stuck at same spot: strace virsh list ...

On 02/21/2017 12:07 PM, Yunchih Chen wrote: > On 02/20/2017 09:10 PM, Michal Privoznik wrote: >> On 17.02.2017 17:18, Yunchih Chen wrote: >>> `virsh list` hangs on my server that hosts a bunch of VMs. >>> This might be due to the Debian upgrade I did on Feb 15, which upgrades >>> `libvirt` from 2.4.0-1 to 3.0.0-2. >>> I have tried restarting libvirtd

On Fri, Feb 24, 2017 at 11:52:43PM +0800, Yunchih Chen wrote: > > > On 02/24/2017 11:30 PM, Daniel P. Berrange wrote: > > On Tue, Feb 21, 2017 at 12:07:41PM +0800, Yunchih Chen wrote: > > > On 02/20/2017 09:10 PM, Michal Privoznik wrote: > > > > On 17.02.2017 17:18, Yunchih Chen wrote: > > > > > `virsh list` hangs on my server that hosts a bunch

On Tue, Feb 21, 2017 at 12:07:41PM +0800, Yunchih Chen wrote: > On 02/20/2017 09:10 PM, Michal Privoznik wrote: > > On 17.02.2017 17:18, Yunchih Chen wrote: > > > `virsh list` hangs on my server that hosts a bunch of VMs. > > > This might be due to the Debian upgrade I did on Feb 15, which upgrades > > > `libvirt` from 2.4.0-1 to 3.0.0-2. > > > I have

On 17.02.2017 17:18, Yunchih Chen wrote: > > `virsh list` hangs on my server that hosts a bunch of VMs. > This might be due to the Debian upgrade I did on Feb 15, which upgrades > `libvirt` from 2.4.0-1 to 3.0.0-2. > I have tried restarting libvirtd for a few times, without luck. > > Attached below are some relevant logs; let me know if you need some more > for debugging.

Hi, i am really depressed at this moment. I set up an domain controller using samba4 and an raspberry pi. I can join the domain and everything works BUT kerberos has some strange problems resolving my raspberry hostname. First of all some information: Raspberry pi is DHCP Server and DNS-Server (BIND9). First of all the configurations: Code: /usr/local/samba/etc/smb.conf # Global

Hi, /etc/resolv.conf looks exactly like this: domain family.rapsberry.local search family.rapsberry.local nameserver 192.168.178.222 So to answer your question: yes the only Nameserver the raspberry has is itself. Greetings Am 2015-01-03 um 7:40 PM schrieb Rowland Penny: > On 03/01/15 16:31, Robert Hartmann wrote: >> Hi, >> >> i am really depressed at this moment. I set

Hi, thank you so! much. Turning off avahi daemon was the solution! rapsberry instead of raspberry is a typo during porivision actually. Thank you again :) I will write an entry on my blog to make sure that does not happen again. One last time for google bots. IF you receive kinit: Cannot contact any KDC for realm while getting initial credentials make sure you don't run avahi However

Hi list, i removed my second DC from the domain, and now the re-join as DC hangs. the join hangs now for ca. 2 hours at the step "Committing SAM database" version: samba 4.5.0 on ubuntu 14.04 with a "strace -p " i see this: strace -p 1793 Process 1793 attached brk(0x35e18000) = 0x35e18000 brk(0x35e39000) = 0x35e39000

Hi Heinz, > now the join finished > > but ... i have a high CPU load caused by a samba-process. Samba is consuming 100% of one CPU and the replication fails. you have quite a few objects (>12000) in you main partition. Do you have a large group with all those objects inside? The commit of large group used to result in very very long commit time. There should have been some

Hi Heinz, > > yes, the problem initiated after changing the primary group of all my 11034 users. > > I changed the primary group to different groups. This caused that now every user is member of the LDAP object "Domain users" > > ldapsearch -LLL -x -h dc1 -x -b "cn=domain users,cn=users,dc=example,dc=net" member | grep ^member: | wc -l > 11034 > >

Hi, I installed Dovecot on FreeBSD 4-STABLE machine and have a problem. MTA is postfix delivering to ~/Maildir, runs perfectly. Dovecot is configured to use plaintext auth, config file is at the end of this mail. When trying to get mail via IMAP, I'm getting the following errors: /var/log/dovecot.log > Aug 24 12:00:35 Info: Dovecot starting up > Aug 24 12:00:51 Info: Login: goshik

nmbd has been dying on me occasionally. I'm running mandrake 9.2 with samba3-server-3.0.0-2mdk. We've got our users in ldap but I'd seen this symptom previously when I was using an earlier version of samba that didn't support ldap. There is nothing useful in the logs and a PS shows a nmb process still running. This last time around, I had a ptrace running on both nmbd

Hi all, can somebody explain this ? Thanks, Thomas. ******************************************* beroNet technologies GmbH Dipl.- Ing. Thomas H?ger Potsdamer Str. 18 A 14513 Teltow FON: +49 (0) 3328 3077731 FAX: +49 (0) 3328 334779 Email: thomas.haeger@beronet.com *******************************************

http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz.sig Documentation is probably the only important thing left before v1.0. * deliver doesn't ever exit with Dovecot's internal exit codes anymore. All its internal exit codes are changed to EX_TEMPFAIL. * mbox: X-Delivery-ID header is now dropped when saving mails. * mbox: If

http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz.sig Documentation is probably the only important thing left before v1.0. * deliver doesn't ever exit with Dovecot's internal exit codes anymore. All its internal exit codes are changed to EX_TEMPFAIL. * mbox: X-Delivery-ID header is now dropped when saving mails. * mbox: If