Closed Bug 549722 Opened 15 years ago Closed 15 years ago

New ix linux boxes aren't running sbox

Categories

(Release Engineering :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mozilla, Assigned: bhearsum)

References

Details

The mobile tree is burning from ix boxen dying with "ERROR: Scratchbox is not properly set up!" I imagine /etc/init.d/sbox needs to be set to run on boot on these. Marking as blocking bug 549672, which is the bug we're tracking to pull the ix boxes out of production until some more work is done on them.
Assignee: nobody → bear
Status: NEW → ASSIGNED
well, the ideal fix would be to *not* start scratchbox on boot anywhere, but only at the begining of a build. It looks like we are going to have to go to a dual scratchbox setup. If we don't want to segregate maemo5 capable slaves from maemo4 capable slaves. Can we give cltbld sudo access to that script and add it to the maemo build factories?
They need to be running sbox until we have the run-sbox-on-demand running+tested+reviewed.
full sentence fail :( sorry for the spam well, the ideal fix would be to *not* start scratchbox on boot anywhere, but only at the begining of a build. It looks like we are going to have to go to a dual scratchbox setup. If we don't want to segregate maemo5 capable slaves from maemo4 capable slaves we are going to need to enable/disable scratchboxen as part of the build. Can we give cltbld sudo access to that script and add it to the maemo build factories?
Spoke w/ jhford in person. That work should be part of the setup-scratchbox5 work; unless we want to delay the ix linux rollout until after that (could be weeks), the quick fix is to run sbox normally.
No longer blocks: 549672
Blocks: 545801
Assignee: bear → bhearsum
The following seems to fix scratchbox: chkconfig --level 2345 sbox on service sbox start Still need to run some mobile builds in staging to be sure but I can login to scratchbox from a shell.
I've seen some successful mobile builds in staging, this is fixed.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.