[GH-ISSUE #230] Crashes with segfault when storage is clicked (not always) #179

Closed
opened 2026-02-27 16:38:17 +03:00 by kerem · 5 comments
Owner

Originally created by @afk4life on GitHub (Feb 10, 2014).
Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/230

On two separate systems, I've had the manager crash when I clicked storage. There doesn't seem to be any debug for this, or if there is I don't know where it would be.

Originally created by @afk4life on GitHub (Feb 10, 2014). Original GitHub issue: https://github.com/retspen/webvirtmgr/issues/230 On two separate systems, I've had the manager crash when I clicked storage. There doesn't seem to be any debug for this, or if there is I don't know where it would be.
kerem closed this issue 2026-02-27 16:38:17 +03:00
Author
Owner

@retspen commented on GitHub (Feb 10, 2014):

What crashed - nginx or supervisor?

<!-- gh-comment-id:34642807 --> @retspen commented on GitHub (Feb 10, 2014): What crashed - nginx or supervisor?
Author
Owner

@afk4life commented on GitHub (Feb 10, 2014):

No, not nginx (is that even possible? :D) In debug mode even ./manager runserver it will die with segfault. Not terribly informative.

These are the ones where I was testing in debug:
[ 2118.092037] python[11844]: segfault at 87a900 ip 000000000087a900 sp 00007fc8fbffc428 error 15 in python2.7[871000+69000]
[ 5750.285321] python[12906]: segfault at 8808e0 ip 00000000008808e0 sp 00007f1b0348f528 error 15 in python2.7[871000+69000]
[ 5870.321293] python[13123]: segfault at 7f323000ae10 ip 00007f323000ae10 sp 00007f324339d428 error 15
[16638.282499] python[13937]: segfault at 2 ip 0000000000000002 sp 00007fc602ffa428 error 14 in python2.7[400000+270000]

In both case it only seems to happen when I do anything to the storage but not necessarily every time, especially when I do anything with an ISO involved.

<!-- gh-comment-id:34659720 --> @afk4life commented on GitHub (Feb 10, 2014): No, not nginx (is that even possible? :D) In debug mode even ./manager runserver it will die with segfault. Not terribly informative. These are the ones where I was testing in debug: [ 2118.092037] python[11844]: segfault at 87a900 ip 000000000087a900 sp 00007fc8fbffc428 error 15 in python2.7[871000+69000] [ 5750.285321] python[12906]: segfault at 8808e0 ip 00000000008808e0 sp 00007f1b0348f528 error 15 in python2.7[871000+69000] [ 5870.321293] python[13123]: segfault at 7f323000ae10 ip 00007f323000ae10 sp 00007f324339d428 error 15 [16638.282499] python[13937]: segfault at 2 ip 0000000000000002 sp 00007fc602ffa428 error 14 in python2.7[400000+270000] In both case it only seems to happen when I do anything to the storage but not necessarily every time, especially when I do anything with an ISO involved.
Author
Owner

@retspen commented on GitHub (Feb 10, 2014):

You use develop mode - this is normal if django crash. https://github.com/retspen/webvirtmgr/wiki/Install-WebVirtMgr

<!-- gh-comment-id:34662772 --> @retspen commented on GitHub (Feb 10, 2014): You use develop mode - this is normal if django crash. https://github.com/retspen/webvirtmgr/wiki/Install-WebVirtMgr
Author
Owner

@afk4life commented on GitHub (Feb 10, 2014):

Only one of the servers was started using ./manager runserver. The other is by supervise.

Python - 2.7.3 (#1) 2.7.6 (#2)
Django - 1.5.5

<!-- gh-comment-id:34667547 --> @afk4life commented on GitHub (Feb 10, 2014): Only one of the servers was started using ./manager runserver. The other is by supervise. Python - 2.7.3 (#1) 2.7.6 (#2) Django - 1.5.5
Author
Owner

@retspen commented on GitHub (Apr 29, 2014):

Update WebVirtMgr

<!-- gh-comment-id:41649328 --> @retspen commented on GitHub (Apr 29, 2014): Update WebVirtMgr
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/webvirtmgr#179
No description provided.