[asterisk-bugs] [AsteriskNOW 0014651]: GUI crash

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=14651 
====================================================================== 
Reported By:                epesce
Assigned To:                bkruse
====================================================================== 
Project:                    AsteriskNOW
Issue ID:                   14651
Category:                   Asterisk GUI Issues
Reproducibility:            unable to reproduce
Severity:                   crash
Priority:                   normal
Status:                     resolved
Resolution:                 unable to reproduce
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-03-12 04:10 CDT
Last Modified:              2009-03-13 16:48 CDT
====================================================================== 
Summary:                    GUI crash
Description: 
this night lighttpd crashed

[admin at sip gui]$ cat lighttpd.error.log 
2009-03-09 11:53:11: (log.c.75) server started 
2009-03-09 12:11:46: (server.c.1470) server stopped by UID = 0 PID = 3172

2009-03-09 12:12:58: (log.c.75) server started 
2009-03-12 04:02:01: (server.c.1344) unlink failed for:
/var/run/gui-lighttpd.pid 2 No such file or directory 
2009-03-12 04:02:01: (server.c.1356) [note] graceful shutdown started 
2009-03-12 04:02:01: (server.c.1470) server stopped by UID = 0 PID = 8905

2009-03-12 09:54:47: (log.c.75) server started 

resolved with simply reboot at 09:54:47
====================================================================== 

---------------------------------------------------------------------- 
 (0101766) qwell (administrator) - 2009-03-13 16:48
 http://bugs.digium.com/view.php?id=14651#c101766 
---------------------------------------------------------------------- 
Since we don't do anything special with lighttpd, and since this has only
happened once, I'm going to go ahead and close this as unable to
reproduce.

If it keeps occurring, we can try to figure something out. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-13 16:48 qwell          Note Added: 0101766                          
2009-03-13 16:48 qwell          Status                   assigned => resolved
2009-03-13 16:48 qwell          Resolution               open => unable to
reproduce
======================================================================