Closed Bug 545801 Opened 16 years ago Closed 15 years ago

Fix up linux ix machines

Categories

(Release Engineering :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: catlee, Assigned: bhearsum)

References

Details

Attachments

(1 file)

The /builds drive is on /dev/hda4, not /dev/sda4 (which is in the fstab)
Attachment #426629 - Flags: review? → review?(nrthomas)
Attachment #426629 - Flags: review?(nrthomas) → review+
If you change the SATA Configuration from IDE to AHCI in the BIOS, then you get /dev/sda4 as expected. And much better performance too, according to hdparm.
slave01, slave02 done. I'll do the rest now.
Assignee: nobody → catlee
Status: NEW → ASSIGNED
Summary: Fix fstab on new ix machines → Update BIOS on ix linux machines
slaves 01-13,25 done.
Checklist for remaining machines: * Update BIOS to set SATA Configuration to AHCI * Set puppet to run with 'chkconfig --levels 2345 puppet on'
Summary: Update BIOS on ix linux machines → Fix up linux ix machines
* Update root password
Also need to run: 'chkconfig --level 2345 sbox on' to make Scratchbox work properly.
Need to add the Config::General.pm for release updates.
Depends on: 546424
Depends on: 549722
(In reply to comment #7) > Also need to run: > 'chkconfig --level 2345 sbox on' to make Scratchbox work properly. (In reply to comment #8) > Need to add the Config::General.pm for release updates. I just did both of these things on 01 - 25.
Assignee: catlee → bhearsum
Apparently ccache is failing on some of them: (view as text) ccache -z in dir /builds/slave/tryserver-linux-debug/build (timeout 1200 secs) watching logfiles {} argv: ['ccache', '-z'] environment: CC=/tools/gcc/bin/gcc CCACHE_DIR=/builds/ccache CCACHE_UMASK=002 CVS_RSH=ssh CXX=/tools/gcc/bin/g++ DISPLAY=:2 G_BROKEN_FILENAMES=1 HISTSIZE=1000 HOME=/home/cltbld HOSTNAME=mv-moz2-linux-ix-slave22.build.mozilla.org INPUTRC=/etc/inputrc JAVA_HOME=/builds/jdk LANG=en_US.UTF-8 LD_LIBRARY_PATH=obj-firefox/dist/bin LESSOPEN=|/usr/bin/lesspipe.sh %s LOGNAME=cltbld LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=01;32:*.cmd=01;32:*.exe=01;32:*.com=01;32:*.btm=01;32:*.bat=01;32:*.sh=01;32:*.csh=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*.tif=01;35: MAIL=/var/spool/mail/cltbld MOZ_CRASHREPORTER_NO_REPORT=1 MOZ_OBJDIR=obj-firefox PATH=/opt/local/bin:/tools/buildbot/bin:/tools/twisted/bin:/tools/twisted-core/bin:/tools/python/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/cltbld/bin PWD=/builds/slave/tryserver-linux-debug/build PYTHONHOME=/tools/python PYTHONPATH=/tools/buildbotcustom:/tools/buildbot/lib/python2.5/site-packages:/tools/twisted/lib/python2.5/site-packages:/tools/twisted-core/lib/python2.5/site-packages:/tools/zope-interface/lib/python2.5/site-packages/ SHELL=/bin/bash SHLVL=1 SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass TBOX_CLIENT_CVS_DIR=/builds/tinderbox/mozilla/tools TERM=linux USER=cltbld XPCOM_DEBUG_BREAK=stack-and-abort _=/tools/buildbot/bin/buildbot closing stdin using PTY: True Upon execvpe ccache ['ccache', '-z'] in environment id 167566844: Traceback (most recent call last): File "/tools/twisted-2.4.0/lib/python2.5/site-packages/twisted/internet/process.py", line 777, in __init__ os.execvpe(command, args, environment) File "/tools/python-2.5.1/lib/python2.5/os.py", line 363, in execvpe _execvpe(file, args, env) File "/tools/python-2.5.1/lib/python2.5/os.py", line 392, in _execvpe func(fullname, *argrest) OSError: [Errno 2] No such file or directory program finished with exit code 1 elapsedTime=0.004548
Looks like Puppet isn't running on many of them. 14 - 24 have never talked with the Puppet server.
(In reply to comment #11) > Looks like Puppet isn't running on many of them. 14 - 24 have never talked with > the Puppet server. I fixed this awhile ago. All the machines are all fixed up and up to date AFAIK.
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.

Attachment

General

Created:
Updated:
Size: