Can't login to N4000

[Cara Tock]

I am trying to get into an N4000 running HP-UX 11.0 and I am unable. I have tried telnet, ftp, rexec, and I have tried loging in on the console. The console gives me a login prompt, but then just hangs after I enter a username. I don't get a login prompt when I telnet in. Is there anything else I can try?
Thanks,
Damon

[G. Vrijhoeven]

Hi Damon,

Did you try different users? If you are able to login as non root user you could try a su to root to start your diagnostics.

HTH,

Gideon

[John Poff]

Hi Damon,

This doesn't sound good. I've seen systems behave like this in the past, and usually it was a hardware problem, such as a bad root disk or a SCSI controller. Disks are mirrored? Backups are current?

JP

[Prashant Zanwar_4]

No really very sure. But do you have all latest security inclusing the password patches installed..just a thought..

But for now seems what you have tried is not working. Try on console with some different user and then su..

All the best
Thanks
Prashant

[Rick Garland]

Have seen this - replaced SCSI controller.

Test - are you able to bounce the system and then you can log in?

Still able to get in GSP? You can reset the system from there.

[Prashant Zanwar_4]

yes...Your best bet will be to reboot the system once to see if any error messages are there and then try logging in...
If nay users are using the system already, just try working from one of the users desk if you get to see any error messages..or if system is functioning correctly or no..

All the best
Thanks
Prashant

[Cara Tock]

I can not bounce the system. I have tried different users with no success. I do remember having a problem with a scsi controller. I think that I may try to disconnect a controller and try to login.

[doug mielke]

I believe I've seen this condition when a root disk gets full, and there is no room to update things like utmp and history. Full / will result in other greif as well, but a reboot might fix if this is the case inthat some temp files will be re-written.

[Pedro Cosmen]

Hello Damon,

Can you reboot the system?, if so boot in Single-user mode and then look the space available in your root lvol, if it's near the 100% maybe Doug is right and you have to free space in your lvol1.

Regards.

[Cara Tock]

This is our disaster recovery system and there are no users logged in. I can't get any kind of access to the system. I have no way of booting the system (other than the power switch).

[John Poff]

Can you do a TOC? As Rick mentioned, if you can get to the GSP you can issue a TOC. Also, I think the N4000 has a small TOC button somewhere in back.

JP

[Rick Garland]

If you are unable to log in to the system I do not know what other options are available besides a reboot.

[Lee Hundley]

Was it set up for NIS/LDAP authentication? It could be timing out looking for an auth server. I've seen IRIX machines do similar things because of missing auth server, or, on rare occasions, even a missing DNS server.

[Gerhard Roets]

Hi Damon

Please check that your DNS servers is up and that there ip's is still the same.

When you telnet to a machine it tries a reverse nslookup before letting you log in. Whe you log in on the console it also looks for some DNS.

They might be picking up DNS from DHCP.

Regards
Gerhard

[rmueller58]

can you get to the GSP>
I believe from the GSP you can reboot or ignite if you have a fairly current ignite tape.

It sounds as if you may have a run-away process, you may have to power cycle the box and face the consequences.. I had a user that built a faulty SQL statement in Powerbuilder accessing an informix DB, it put my N4000 into a tailspin, no one could log in, no response on the console. (same type of responses), the only way we could get back was power cycle, correct the SQL statement before it was ran.

[Gerhard Roets]

Hi Damon

Just to add. You will eventually get the password prompt. If you just sit and waite if this is the DNS issue i am talking about.

But be warned the moment you dare go to the loo or go get coffee it will come up ;) According to Uncle Murphy and hiw laws

Regards
Gerhard

[Cara Tock]

I had to cycle the power. I couldn't get in. It turns out that I had a slew of scsi errors when the dba was removing old log files.

[Rick Garland]

Removing files would not normally cause scsi errors. Sounds as if something else is happening. Are you able to create files and then remove them along this same SCSI path? Do you get the errors as well?

This needs more looking into.