Displaying 3 results from an estimated 3 matches for "254b".
Did you mean:
254
2013 Oct 04
2
failing connections w/ virt-manager
...nabled)
Active: active (running) since Do 2013-10-03 17:39:37 CEST; 13h ago
Main PID: 1242 (libvirtd)
CGroup: name=systemd:/system/libvirtd.service
└─1242 /usr/sbin/libvirtd --listen
Okt 03 17:39:38 jupiter libvirtd[1242]: [251B blob data]
Okt 03 17:39:38 jupiter libvirtd[1242]: [254B blob data]
Okt 03 17:39:38 jupiter libvirtd[1242]: [301B blob data]
Okt 03 17:39:38 jupiter libvirtd[1242]: firewall tools were not found or
cannot be used
Okt 03 17:39:41 jupiter libvirtd[1242]: [338B blob data]
Okt 03 17:39:41 jupiter libvirtd[1242]: failed to add iptables rule to
allow DHCP requ...
2009 Sep 01
3
dovecot 1.2 and logging start failures
Hi,
I've got report about issue when dovecot fails to start and there is no error
logged (error goes only to stderr)
situation:
1) dovecot is running
2) dovecot is automatically updated to new version (by yum update daemon),
after update, dovecot is restarted (it's part of update script)
3) new dovecot fails to start (for whatever reason)
result:
dovecot not running and no error
2013 Oct 09
3
Re: failing connections w/ virt-manager
Am 08.10.2013 14:46, schrieb Stefan G. Weichinger:
>> Try enabling the flag, re-emerging the package, setting the logs and
>> then reproduce it again. Check the logs and you should see why it's
>> disconnecting.
The docs say that libvirtd has to listen on the TCP port ... checked that:
# netstat -alnp | grep libv
tcp 0 0 0.0.0.0:16509 0.0.0.0:*