Closed
Bug 468121
Opened 16 years ago
Closed 16 years ago
qm-pmac-fast01, qm-pmac02, and qm-pmac03 burning for no reason
Categories
(Release Engineering :: General, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: samuel.sidler+old, Assigned: catlee)
References
Details
The following machines are failing with "FAIL: Busted: tp FAIL: browser frozen": MacOSX Darwin 8.8.1 talos trunk fast qm-pmac-fast01 MacOSX Darwin 8.8.1 talos trunk qm-pmac02 MacOSX Darwin 8.8.1 talos trunk qm-pmac03 Second time Mac Talos has had an issue this week. Note that I didn't notice them because we haven't been taking checkins on this branch while 1.9.0.5 is being worked on.
Reporter | ||
Updated•16 years ago
|
Severity: normal → major
Comment 1•16 years ago
|
||
Fall out from scheduled auto-reboots. Currently being worked on.
Blocks: 463020
Updated•16 years ago
|
Component: Release Engineering: Maintenance → Release Engineering: Talos
Priority: -- → P2
Comment 2•16 years ago
|
||
qm-pmac-fast01 is stuck again.
Comment 3•16 years ago
|
||
Apache still having trouble starting post-reboot. I've added specific entries to the firewall to allow opening of port 80. It's a long shot, but that may be why we are having trouble starting the server.
Assignee | ||
Comment 4•16 years ago
|
||
crontab was adjusted to have full path to SystemStarter instead of unqualified path. Initial test on qm-pmac-fast01 is promising. FTR, the crontab looks like this: @reboot ps -axc | grep httpd || /sbin/SystemStarter start "Web Server" */5 * * * * ps -axc | grep httpd || /sbin/SystemStarter start "Web Server"
Comment 5•16 years ago
|
||
Correct path in crontab appears to have fixed this up. This change will have to be a part of the general roll out of auto-rebooting.
Assignee: nobody → catlee
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•