Unable to connect to system

[Carles Viaplana Cruells]

Hello,

We're trying to connect to system but we're not able.

From local console we are able to connect but when we try to access to OS console we have no answer.

in addition, it could be /stand filesystem is full.

Can it cause this kind of problems?
Is there any way to connect to system and solve this issue?

Thanks in advance for your help.

Regards,

Carles Viaplana

[SKR_1]

Reduce the /stand utilization from login throgh local console.

Thanks

SKR

[Torsten.]

Do you have network access?

Sooo many possible reasons for this, some are

- console is "somewhere" else (e.g. on VGA instead of serial)

- another process (waiting for something) is blocking the console

- system is hung or even down already

Check the virtual front panel - what does it show?

How should /stand getting full? ...

[SKR_1]

If you are not able to reduce it, then you need to boot the machine from its ignite backup tape or net recovery and then extend the same.

Thanks

SKR

[Carles Viaplana Cruells]

Hello,

We can ping system, but not to connect it.

We have tried to connect to system through console but we can't (we inserted CO command and after few seconds screen shows menu again).

Thanks for your help.

Regards,

Carles Viaplana

[Patrick Wallek]

What is the model of the system? What menu is showing? Is it the MP Menu?

[Carles Viaplana Cruells]

Server is a HP RX4640 and output is redirected to console.

Console shows system crashes when HP-UX should be loaded, probably because an OS filesystem is full.

We have tried to start system in Single User Mode but we can't (maybe system doesn't allows, maybe we don't do it right).

Thanks for your help!

[Patrick Wallek]

OK. The system crashes.

What messages do you get. There could be many reasons for the system to crash. Assuming it is because a filesystem is full may not be a valid assumption.

What happens when you try to go to single-user mode? How did you do it? What messages do you get?

Again, what menu are you at? Is it the MP menu? Or is it the boot menu?

We really need some real information to go much further.

[Carles Viaplana Cruells]

Hello,

How can I get messages from a terminal conected to local console?

When I tried to connect to Single User Mode we just saw no system processes are started.

About Menu I told, this is MP.

On the other hand, If I'm right, if /stand filesystem is full system doesn't allow to open new connections.

As we're not able to connect to system even in local we assumed mail cause is /stand filesystem is full. Unfortunatelly I'm not a HP-UX expert so I'm not sure about. What do you think?

Thanks a lot for your help.

Regards,

[Dennis Handly]

Why would /stand be full, did you mean /?

>we try to access to OS console we have no answer.

The system is likely down, you need to reboot.
Unless you have some evidence of disk activity.

>We can ping system, but not to connect it.

Unfortunately this doesn't mean the system is up, it could be hung, for all but ping.

>mail cause is /stand filesystem is full.

No, mail can cause /var/mail/ and /var/spool/mqueue/ to be full.

[Gokul Chandola]

Hi,
You have to try with MP console.
So that you can use options and see the system status in which stage its making problem.

So you can try for solution.

Regards,
Gokul Chandola

[ramendra]

I face the same issue earlier and founf that my /var file system has become 100% full and the system was not allowing us to login to the server.Maybe a manual hard reboot can solve the issue.

[Carles Viaplana Cruells]

Hello,

We detected a local disk crashed, so we're waiting the new one for changing.

Anyway, in RAID-1 disk configuration a disk failure shouldn't cause system connections down.

About my previous comment, I mean /stand filesystem is used for reading kernel and it's 1st filesystem mounted.

If this filesystem is full kernel can't be read and system can't be started up. Is that true?

If this is the case, is there any way to resolve issue?

Thanks in advance for your help.

Regards,

Carles Viaplana

[Dennis Handly]

>If this filesystem is full kernel can't be read and system can't be started up. Is that true?

I wouldn't think so. Full doesn't stop reading.

>If this is the case, is there any way to resolve issue?

Try to prove this by booting in single user mode.

[Torsten.]

>>" Console shows system crashes when HP-UX should be loaded, probably because an OS filesystem is full."

Boot into single user mode and record console output, if it is still crashing, post this output.

No matter what file system could be full, booting into single user mode should work anyway.


Why do you thing

/stand

is full ???

What have you done ???

[Carles Viaplana Cruells]

Hi all,

When we tried to startup system in Single-User mode it crashes too.

On the other hand, we detected a message regarding LOG files are full.

When we listed /stand contents through IPF (when we interrupted autoboot process) and we found a directory called "oldput".

I think this directory is not a HP-UX directory, but could it be root cause of issue? Is there any way to remove it from? Maybe booting system from tape, DVD, etc.

Thanks to all for your answers.

Regards,

Carles Viaplana

[Torsten.]

Can you record the screen output (with putty or something) during boot to single user mode and post?

[sreekanthtm]

When we listed /stand contents through IPF (when we interrupted autoboot process) and we found a directory called "oldput".

>> This will not stop you from booting in Single user mode.

Whats the command you have given @ ISL> prompt?.

[Carles Viaplana Cruells]

Hello,

I can't arrive to see ISL prompt. from vt100 term.

We can see MP Console promtp and HPUX> prompt, but we can't see ISL prompt or the point where boot process has to be stopped.

In addition, we have problems to see EFI options menu correctly.

Can anybody post a detailed procedure for accessing to ISL? Or how can we change console view in order to watch EFI menu fine and gain access to EFI?

Thanks to all for your help.

Regards,

Carles Viaplana

[Carles Viaplana Cruells]

Into the following doc I've read ISL is available only for HP9000 servers:

http://docs.hp.com/en/5991-1247B/5991-1247B.pdf

[...]
The Initial System Loader (ISL) interface is available only from HP-UX boot devices on
HP 9000 servers (PA-RISC systems).
[...]

As my system is IA64 server, how can I access to server in maintenance mode?

Thanks to all for your help.

Regards,

Carles Viaplana

[sreekanthtm]

Use the command boot vmunix -is
HPUX> boot vmunix -is
To boot the server in Single user mode

[Carles Viaplana Cruells]

Hi all,

I tried to execute boot vmunix -Im as you suggested but always system dumps.

I've found following threads but it haven't worked with our system.

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=733627

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=472211

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=986047

I think I already told we're not able to watch EFI menu fine. Could this issue with our console do our commands are not well executed?

Thanks to all for your help.

Regards,

Carles Viaplana

[OldSchool]

ok, so did you ever interrupt the boot process as noted above?

Did you get the "HPUX>" prompt as described above?

Did you do:
boot vmunix -is
at the HPUX prompt?

What, if anything, happened when you did that?

You keep saying the "system dumps". You also say you get nothing back at the console. If so, how do you know it "dumps"? If not, what are you getting on the console that indicates this?

A correctly configured console should show the EFI prompts and menus w/o issue.

[sreekanthtm]

Try to connect the server to a windows system trough serial cable (there is 9pin serial cable available). And get the console through hyperterm.

[Carles Viaplana Cruells]

Hi all,

I attached a photo of dump, even when we executed "boot vmunix -Is" from HPUX prompt.

Regards,

Carles Viaplana