Closed Bug 425052 Opened 18 years ago Closed 17 years ago

backup and then reimage xserve04

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Assigned: phong)

References

Details

We've recently mothballed xserve04. 1) Can we take a full image of this machine, just in case we need to un-mothball and revive it for some (unforeseen) reason? 2) After backing up, can you reimage xserve04 to be identical to bm-xserve03 or bm-xserve05? We'd like to have bm-xserve04 be available as a ready-to-use spare.
fyi: bm-xserve03 (in bug#391742) and bm-xserve05 (in bug#391498) were both imaged from bm-xserve02... in case that helps.
You have two master images - one that's called bm-xserve05 and one from 10 (this one is the most recent).
Flags: colo-trip+
Assignee: server-ops → phong.tran
XSERV04 imaged. Currently restoring from bm-server10 image. I'm going to let it run through the night.
whats the status on this?
The first couple of attempts to image didn't work. The server would not detect the drives after the restore. I had to blow away the RAID and install from CD. I left the restore from PPC 10.4 running over night.
This box doesn't seem to like any of the images I've put on there. I'm getting the big red cross when I reboot after the PPC image.
Status: NEW → ASSIGNED
Can you image from bm-xserve03 / bm-xserve05 directly onto bm-xserve04?
bm-serve03 was image with the same image that I have been trying to put on xserve04. I can try to take an image of bm-xserve05, but I will need to take it down for about 2 hours to take the image.
Can I take down bm-xserve03 or bm-xserve05 tonight to take any image?
I rebuilt this server from the install 10.4.7 disc. IP: 10.2.71.35 It is also attached to console port 4
Think this is done. reopen if there is anymroe work.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Please turn VNC on and set the password to the standard value for cltbld. Then we can try to figure out if there is some hardware difference that prevents the image of xserve03 from being applied.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Should be something you guys can do - http://www.macosxhints.com/article.php?story=20071024123234595 http://www.macgeekery.com/tips/cli/setting_remote_desktops_vnc_password_in_terminal The quick version of those two sites is to run: cd /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resource ./kickstart -configure -clientopts -setvncpw -vncpw PASSWORD
Punting back over the fence. You should have all you need in this.
Assignee: phong.tran → nobody
Status: REOPENED → NEW
Component: Server Operations → Release Engineering
Flags: colo-trip+
QA Contact: justin → release
Status: NEW → RESOLVED
Closed: 18 years ago18 years ago
Resolution: --- → FIXED
(In reply to comment #13) > Should be something you guys can do - > > http://www.macosxhints.com/article.php?story=20071024123234595 > http://www.macgeekery.com/tips/cli/setting_remote_desktops_vnc_password_in_terminal > > The quick version of those two sites is to run: > > cd /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resource > ./kickstart -configure -clientopts -setvncpw -vncpw PASSWORD Thanks but the usual build accounts don't seem to be setup.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
> Thanks but the usual build accounts don't seem to be setup. cltbld works. Keep in mind that the ref images don't have your new passwords so you'll need to use the old one (or eventually update the reference images).
Sorry, typos defeated me.
(In reply to comment #17) > > Thanks but the usual build accounts don't seem to be setup. > > cltbld works. > > Keep in mind that the ref images don't have your new passwords so you'll need > to use the old one (or eventually update the reference images). > (confused) Comment#10 says this machine was built from fresh OS install, not built from a refimage. If a refimage was used, which refimage?
That is very true and I have no idea who created the accounts but unless Phong created cltbld, I'm assuming Build did since no one else knows your passwords.
Phong, can you clarify how this was setup?
Assignee: nobody → server-ops
Status: REOPENED → NEW
Component: Release Engineering → Server Operations
QA Contact: release → justin
Assignee: server-ops → phong.tran
Some other woes from offline emails with Nick. I'd guess that bm-xserve04 needs a little TLC. [snip] I tried to get onto this machine with VNC but something is not right with the config - "Connection terminated - Please configure Apple Remote Desktop to allow VNC Viewers to control the screen. Unknown authType 30" from Chicken of the VNC. I've run cd /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources sudo ./kickstart -configure -clientopts -setvncpw -vncpw <the-current-VNC-password-in-plain> (NB the p/w should not be in plain but encoded, so it's incorrectly set at the moment. I believe this is independent of the error above). Also tried sudo /System/Library/CoreServices/RemoteManagement/\ ARDAgent.app/Contents/Resources/kickstart -activate \ -configure -access -on -restart -agent -privs -all and got Starting... Created preference to start ARD after reboot. Stopped ARD Helper. Stopped ARD Agent. Stopped VNC Server. cltbld: Set user remote control privileges. cltbld: Set user remote access. Started ARD Agent. Done. And tried sudo /System/Library/CoreServices/RemoteManagement/\ ARDAgent.app/Contents/Resources/kickstart -configure \ -allowAccessFor -allUsers -privs -all and got Unknown option: allowaccessfor Unknown option: allusers Starting... cltbld: Set user remote control privileges. Done. Still no joy from the Chicken after that, possibly it needs a reboot. [snip]
Your client sucks :) Using OSX 10.5's VNC client, I was able to connect as cltbld (using the old cltbld password). Reset VNC password to the new. VNC was also checked as disabled so I enabled it. Tested with Vine Viewer. I thought 10.5's VNC client only worked with 10.5 machines, guess not. Good to know though! Tossing back to you - don't think there's anything else for us to do.
Assignee: phong.tran → nobody
Component: Server Operations → Release Engineering
QA Contact: justin → release
In reply to comment #23) > Your client sucks :) err.. Nick's client sucks?! :-) Not sure if some of the install working Nick did fixed VNC or not, but at least now Armen and Nick can VNC to the machine. > > Tossing back to you - don't think there's anything else for us to do. > We're still uncomfortable using this machine in production, because its imaged from a CD install, and would require significant manual setup, whereas cloned from an already-configured-and-online build machine is much safer. From comments above, it seems that cloning from bm-xserve03 to bm-xserve04 didnt work, which is still a mystery. Imaging from intel-based bm-xserve10 is not expected to work on PPC-based bm-xserve04. fyi: I also just verified that bm-xserve01, 02, 03, 04, 05 all have the same bios (517f2). The only differences I could spot across the 5 machines was that bm-xserve05 has a slightly different CPU (PowerPC G5 3.1) compared to the others (PowerPC G5 3.0), and bm-xserve05 has different ram (2GB) compared to the others (4GB). Can you try cloning from bm-xserve02 or bm-xserve05 onto bm-xserve04?
(In reply to comment #24) > In reply to comment #23) > > Your client sucks :) > err.. Nick's client sucks?! :-) Not sure if some of the install working Nick > did fixed VNC or not, but at least now Armen and Nick can VNC to the machine. Probably largely a result of me turning VNC on! However with it turned off, like I mentioned, I was able to use OSX 10.5's built in VNC client and log into (desktop sharing).
Assignee: nobody → phong.tran
(In reply to comment #24) > In reply to comment #23) > We're still uncomfortable using this machine in production, because its imaged > from a CD install, and would require significant manual setup, whereas cloned > from an already-configured-and-online build machine is much safer. > > Can you try cloning from bm-xserve02 or bm-xserve05 onto bm-xserve04? > Phong, can you try this and let us know what happens?
Component: Release Engineering → Server Operations
can I take this server down right now?
Status: NEW → ASSIGNED
You can take down bm-xserve03 and bm-xserve04 whenever when you are ready.
I will take care of it this weekend. I will be on vacation next week so I will try to get this done before I leave.
bm-xserve04 has been imaged from bm-xserve03. I don't have the new cltbld password to logon and change the name and IP. I've attached it to console port 4.
That's great news! mrz, anything need finishing off before handing us the keys ?
Nope, all yours.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago17 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.