Ignite-UX has hijacked my server

[Gary Cooper_1]

I have never used Ignite before and so I thought I would run the tutorial (latest version). The welcome page said that it wouldn't actually do any thing and that it was safe, so I followed the instructions and the next thing I know is one of my other servers is rebooting from the server running ignite. I managed to shut both down then restart my hijacked machine, but is is now saying:

======= 11/25/05 09:46:45 EST HP-UX Installation Initialization. (Fri Nov 25
09:46:45 EST 2005)
@(#) Ignite-UX Revision C.6.2.241
@(#) install/init (opt) $Revision: 10.319 $
* Scanning system for IO devices...
* Querying disk device: 0/0/1/1.15.0 ...
* Querying disk device: 0/0/2/1.15.0 ...
NOTE: Default (boot) source does not appear to be a valid (or complete)
install source, switching source to Network
* Bringing up Network (lan0)
* Reading configuration information from server...


ERROR: Could not read /var/opt/ignite/INDEX from install tftp server.
ERROR: Failed to read "INDEX" file from install server. Check that the
install server's IP address is correct and the server has the
"Ignite-UX" product loaded and is available via the tftp(1) service.
Failed to startup networking, user interaction required
Press Return to continue:

This is due to impact my main production server at amy minute.

Urgent help would be most appreciated.

(Am waiting for a callback fro HP support).

Thanks,

Gary

[Denver Osborn · Accepted solution]

If you managed to performed a "bootsys" that caused the remote node to reboot... that would mean the IUX server would've changed the AUTO file to have that box boot the Ignite-UX install kernel.

Try booting your "rebooted box" up and interact with ISL... from the ISL load /stand/vmunix.

boot pir <-- yes to interact with ISL
hpux /stand/vmunix

After the box is up, check the AUTO file... you may see it is set to "hpux /stand/WINSTALL". You'll want to set it back to "hpux /stand/vmunix" or what ever you had it set to before.

hope this helps,
-denver

[Gary Cooper_1]

I said Yes to interract with ISL, now, it just sits at the ISL prompt.

What next?

Thanks,

Gary

[Gavin Clarke]

hpux /stand/vmunix

which Denver said

[V. Nyga]

Hi,

I've done this with one of my clients once - you will have no chance because ignite is destroying everything at the boot disk (this is announced shortly before ignite is doing that).

You can test like Denver said, but my experience is that it doesn't work.
Also you can search for system.prev or vmunix.prev in /stand, but I believe you will not find any.

Hopefully I'm wrong.
Volkmar

[Denver Osborn]

Thanks Gavin...


Yes, once at ISL prompt you need tell the system how to boot... :)

hpux /stand/vmunix


I suspect the problem you had with it booting into the Ignite-UX interface was because the AUTO file was update to have the box boot from the Ignite-UX install kernel... which would be the same as you running "hpux /stand/WINSTALL" from the ISL prompt. We're interacting with the ISL so that the AUTO file isn't run... so we can get the box back up.

After it boots up use this command and you'll see the AUTO file was changed my IUX to boot the Ignite-UX install kernel -vs- vmunix.

lifcp /dev/rdsk/cXtXdX:AUTO -

where cXtXdX is your primary boot disk


To fix the AUTO file use mkboot...

mkboot -a "hpux /stand/vmunix" /dev/rdsk/cXtXdX

-denver

[Gary Cooper_1]

Hi Guys,

Thanks for the help. The machine's back up again now.

I'm going to pick this up again on Monday. Will let you know what happens then.

Cheers,

Gary

[Gavin Clarke]

Sorry to jump in there Denver.

If I were in a situation like this I'd want all the responses I could get.

Good Luck Gary, I hope it works out well for you. I'm sorry I don't have any answers of my own right now.

[Denver Osborn]

good deal... with the system up it up sounds like you shutdown the box before it booted the install kernel and did anything destructive!

To be safe next time you're playing with Ignite-UX but don't want to boot a client... be sure to touch a /.bootsys_block on the client's root dir. This file will prevent bootsys from being able to reboot a client.

-denver

[Sยภเl Kย๓คг]

Hi,

1. At ISL prompt type 'lsa', this will display the content of the Auto-execute file. It should be 'hpux', not the one which is pointing to the igniteUX install kernel.

2. At ISL prompt type 'hpux ll' this will display the content of boot filesystem, ie /stand. Check wether vmunix or vmunix.prev is available.
3. At ISL prompt type 'hpux set autofile
4. ISL > hpux

I think this will help u to resolve the problem

Regards,
Sunil

[Gary Cooper_1]

Thanks for the help guys, especially Denver. You really came through in my moment of need!

I rebooted the machine this morning and it came up normally without any intervention.

I checked the AUTO file and it was set to hpux.

BTW, Gavin, your post was very much appreciated on Friday. I was struggling with the hpux command because I had missed the space between hpux and /stand/vmunix (it's a real sign that you 're getting old when the eyesight starts to play those tricks).

I must say this whole experience has made me quite nervous of trying to do anything with Ignite-UX.

Thanks again - it's a shame I can't buy the beers!

Cheers,

Gary