(Not reopening as we have a workaround for Ubuntu (rm of the .pid file)
and this is an upstream bug; please reopen if you want to track this in
Ubuntu)
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
https://bugs.launchpad.net/bugs/510658
You
(Not reopening as we have a workaround for Ubuntu (rm of the .pid file)
and this is an upstream bug; please reopen if you want to track this in
Ubuntu)
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
https://bugs.launchpad.net/bugs/510658
You
On a): what I meant here is not that libvirt should catch all cases of
itself disappearing, but rather that the other daemons don't have a rm
on the .pid file; I didn't check what the other daemons to, I guess they
are checking for a running process with that pid and whether it's the
same program
Thanks for the research, Loic.
The logic is perfectly sound, to me.
I wholeheartedly agree that the upstream daemon (or whatever creates
the bloody pid file) should clean up the damn thing. But as you said,
for Lucid, we probably shouldn't go mucking about in the daemon's
internals.
What we
For lucid, I'm happy enough with the rm before starting the process --
upstart should already track life and death, so we don't need to do the
ps tricks IMO.
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
https://bugs.launchpad.net/bugs/510658
This bug was fixed in the package libvirt - 0.7.5-5ubuntu20
---
libvirt (0.7.5-5ubuntu20) lucid; urgency=low
* debian/libvirt-bin.upstart:
- remove unnecessary pid file existence test, LP: #510658
- revert virbr0 up/down hack added in 0.7.5-5ubuntu17, LP: #345485
-- Dustin
This bug was fixed in the package libvirt - 0.7.5-5ubuntu20
---
libvirt (0.7.5-5ubuntu20) lucid; urgency=low
* debian/libvirt-bin.upstart:
- remove unnecessary pid file existence test, LP: #510658
- revert virbr0 up/down hack added in 0.7.5-5ubuntu17, LP: #345485
-- Dustin
On a): what I meant here is not that libvirt should catch all cases of
itself disappearing, but rather that the other daemons don't have a rm
on the .pid file; I didn't check what the other daemons to, I guess they
are checking for a running process with that pid and whether it's the
same program
So I checked what two other popular daemons were doing.
If started manually, bind9 just ignores the contents of the .pid file
and starts again: if the .pid file is present and mentions a pid which
was kill-9-ed, it starts and writes its pid in it instead; if the .pid
file is present and mentions
Thanks for the research, Loic.
The logic is perfectly sound, to me.
I wholeheartedly agree that the upstream daemon (or whatever creates
the bloody pid file) should clean up the damn thing. But as you said,
for Lucid, we probably shouldn't go mucking about in the daemon's
internals.
What we
For lucid, I'm happy enough with the rm before starting the process --
upstart should already track life and death, so we don't need to do the
ps tricks IMO.
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
https://bugs.launchpad.net/bugs/510658
a) shouldn't libvirtd handle this by itself as the other daemons do? I
realize upstart is in the proper position to know that the service
crashed, but upstart doesn't care about the pid file
b) perhaps this:
[ -f /var/run/libvirtd.pid ] rm -f /var/run/libvirtd.pid
could simply be:
rm -f
Hi Loic-
a) If it was kill -9'd, I don't think the daemon can trap and handle
that.
b) Agreed. I'll change this in the next upload.
c) I'm up for other ideas, here, but I think pidof() is about the best
we can do at this point. I don't think this is about working around
upstart bugs as
Dustin's right on 'a'. Can't catch -9 and if libvirtd dies for some
reason, its pid file is left around.
However, Loic is right about 'c' because of qemu:///session (I forgot
about this when we discussed this initially). Since the upstart job is
only for qemu:///system, and only the libvirtd for
Cool, thanks, Jamie. I'm uploading that now ...
** Changed in: libvirt (Ubuntu Lucid)
Status: In Progress = Fix Committed
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
https://bugs.launchpad.net/bugs/510658
You received this bug
Uploaded libvirt_0.7.5-5ubuntu21_source.changes to the queue.
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
https://bugs.launchpad.net/bugs/510658
You received this bug notification because you are a member of Ubuntu
Server Team, which is
a) shouldn't libvirtd handle this by itself as the other daemons do? I
realize upstart is in the proper position to know that the service
crashed, but upstart doesn't care about the pid file
b) perhaps this:
[ -f /var/run/libvirtd.pid ] rm -f /var/run/libvirtd.pid
could simply be:
rm -f
Hi Loic-
a) If it was kill -9'd, I don't think the daemon can trap and handle
that.
b) Agreed. I'll change this in the next upload.
c) I'm up for other ideas, here, but I think pidof() is about the best
we can do at this point. I don't think this is about working around
upstart bugs as
Dustin's right on 'a'. Can't catch -9 and if libvirtd dies for some
reason, its pid file is left around.
However, Loic is right about 'c' because of qemu:///session (I forgot
about this when we discussed this initially). Since the upstart job is
only for qemu:///system, and only the libvirtd for
Cool, thanks, Jamie. I'm uploading that now ...
** Changed in: libvirt (Ubuntu Lucid)
Status: In Progress = Fix Committed
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
https://bugs.launchpad.net/bugs/510658
You received this bug
Uploaded libvirt_0.7.5-5ubuntu21_source.changes to the queue.
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
https://bugs.launchpad.net/bugs/510658
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This bug was fixed in the package libvirt - 0.7.5-5ubuntu16
---
libvirt (0.7.5-5ubuntu16) lucid; urgency=low
* debian/libvirt-bin.upstart: libvirt has a nasty habit of leaving
it's pidfile lying around when/if it crashes; add a pre-start
check that removes the pidfile if it
This bug was fixed in the package libvirt - 0.7.5-5ubuntu16
---
libvirt (0.7.5-5ubuntu16) lucid; urgency=low
* debian/libvirt-bin.upstart: libvirt has a nasty habit of leaving
it's pidfile lying around when/if it crashes; add a pre-start
check that removes the pidfile if it
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Also affects: libvirt (Ubuntu Lucid)
Importance: Medium
Assignee: Dustin Kirkland (kirkland)
Status: Triaged
** Changed in: libvirt (Ubuntu Lucid)
Status: Triaged = In Progress
**
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Also affects: libvirt (Ubuntu Lucid)
Importance: Medium
Assignee: Dustin Kirkland (kirkland)
Status: Triaged
** Changed in: libvirt (Ubuntu Lucid)
Status: Triaged = In Progress
**
Would like to add, realise I'm a regular user, not technical advocate
like Arnd and Dustin Kirkland.
On my system,
ide...@karmic:~$ sudo /etc/init.d/libvirt-bin restart
* Restarting libvirt management daemon /usr/sbin/libvirtd
[fail]
ide...@karmic:~$ sudo libvirtd
Just wanted to drop a line that the problem is still present in libvirt-
bin 0.7.5-5ubuntu4.
Howto reproduce:
Simulate a crash of libvirtd:
sudokillall -9 libvirtd
Start libvirtd manually
10:08:04.344: error : qemudWritePidFile:494 : Failed to open pid file
'/var/run/libvirtd.pid' : File
After thinking some time about this, I'm not convinced anymore that
libvirtd itself should handle this.
If libvirtd is started and finds the stale pid file there. It could
check if the process with the pid contained in that file is running
anymore. But even if libvirtd crashed, in the meantime
Just wanted to drop a line that the problem is still present in libvirt-
bin 0.7.5-5ubuntu4.
Howto reproduce:
Simulate a crash of libvirtd:
sudokillall -9 libvirtd
Start libvirtd manually
10:08:04.344: error : qemudWritePidFile:494 : Failed to open pid file
'/var/run/libvirtd.pid' : File
After thinking some time about this, I'm not convinced anymore that
libvirtd itself should handle this.
If libvirtd is started and finds the stale pid file there. It could
check if the process with the pid contained in that file is running
anymore. But even if libvirtd crashed, in the meantime
This is likely a problem with Libvirt's new upstart script.
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
https://bugs.launchpad.net/bugs/510658
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This can happen if libvirtd is stopped unexpectedly (crash, kill -9). I
doubt it is the upstart job (though I haven't looked at it).
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
https://bugs.launchpad.net/bugs/510658
You received this bug
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Triaged
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
https://bugs.launchpad.net/bugs/510658
Ah, well, I'll unassign myself this bug, then. If it turns out to be a
problem with the upstart script, let me know and I'll try to fix it
there.
** Changed in: libvirt (Ubuntu)
Assignee: Dustin Kirkland (kirkland) = (unassigned)
--
error : qemudWritePidFile:498 : Failed to open pid file
This is likely a problem with Libvirt's new upstart script.
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
https://bugs.launchpad.net/bugs/510658
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This can happen if libvirtd is stopped unexpectedly (crash, kill -9). I
doubt it is the upstart job (though I haven't looked at it).
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
https://bugs.launchpad.net/bugs/510658
You received this bug
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Triaged
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
https://bugs.launchpad.net/bugs/510658
Ah, well, I'll unassign myself this bug, then. If it turns out to be a
problem with the upstart script, let me know and I'll try to fix it
there.
** Changed in: libvirt (Ubuntu)
Assignee: Dustin Kirkland (kirkland) = (unassigned)
--
error : qemudWritePidFile:498 : Failed to open pid file
Looks like pid file is not being removed after it crashes in the upstart
script. Can you try remove the /var/run/libvirt.pid file?
chuck
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Medium
** Changed in: libvirt (Ubuntu)
Status: New = Confirmed
--
error :
@chuck
Well, that was obviously the point I tried to explain.
libvirt should have removed the pid file, by itself.
Off course it works if I remove the file manually.
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
Looks like pid file is not being removed after it crashes in the upstart
script. Can you try remove the /var/run/libvirt.pid file?
chuck
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Medium
** Changed in: libvirt (Ubuntu)
Status: New = Confirmed
--
error :
@chuck
Well, that was obviously the point I tried to explain.
libvirt should have removed the pid file, by itself.
Off course it works if I remove the file manually.
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38187826/Dependencies.txt
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
https://bugs.launchpad.net/bugs/510658
You received this bug notification because you are a member
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38187826/Dependencies.txt
--
error : qemudWritePidFile:498 : Failed to open pid file '/var/run/libvirtd.pid'
: File exists
https://bugs.launchpad.net/bugs/510658
You received this bug notification because you are a member
44 matches
Mail list logo
