Sponsored Content
Full Discussion: Solaris U10 - Crash OS
Operating Systems Solaris Solaris U10 - Crash OS Post 302841103 by Aswex on Wednesday 7th of August 2013 02:51:29 AM
Old 08-07-2013
Solaris U10 - Crash OS

Hello,

I an triyng to write an emergency procedure, and I need your help, or point of view.

I trying to find a way to get connected to an U10 Sun Solaris by the serial port to be able to get access to the system to debug systeme crash before restarting the server.

The SUN U10 does not have MGT or NET admin port. So mouse and keyboard are linked to the avocent, but this useless in case of a system crash.

I did try 10 times to get connected to the system by the serial port using Putty or Hyper terminal, but all failed.... Only once, when I rebooted the serveur with the serial port connected.

If anyone may share his experience or help.

It may be impossible to make it work, but if anyone knows how to do, I will be pleased to read it ... ; )


Thanks
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Solaris 8 crash on Enterprise 3500

Hi Should anyone be able to help, one of my colleagues was doing a truss this morning and I am not sure if it has offset the system crash, but we have had these type of errors coming up???? # ls ls: Cannot read /usr/lib/ld.so.1 Killed # ps -ef ps: Cannot read /usr/lib/ld.so.1 Killed #... (1 Reply)
Discussion started by: NAV4869
1 Replies

2. UNIX for Advanced & Expert Users

Solaris Server Crash

We have had a server (Solaris 2.6) hardisk crash. When booting the server we get: ok> boot -S Boot Device: /sbus/espdmc@e, 8400000/esp@e,8800000/sd@0,0 short read 0x2000 chars read disk read error The only way we can get into the console is to ok> boot cdrom whereby everything (e.g.... (3 Replies)
Discussion started by: Breen
3 Replies

3. Solaris

problem with tar command in solaris9 on sun U10

I try to install globus toolkit 4 and have major problem that's error in tar command while it install by make command tar -C /usr/local/globus/ -xzf binary-trees/globus_libtool-*/*.tar.gz tar: C: unknown function modifierand it notice me to use tar {c|r|t|u|x} I think it can't use -z... (3 Replies)
Discussion started by: Harmut
3 Replies

4. Solaris

Sparc Solaris 8 crash dump

My sparc solaris 8 server crashed/rebooted yesterday and I have the vmcore files. I have some initial output from SCAT and ACT. I have not included all but any info would be helpful. I can supply more output if necessary. Thanks you. Can I have any information about this ACT and SCAT... (2 Replies)
Discussion started by: csgonan
2 Replies

5. Solaris

Solaris 10 zone crash dump file?

Hi, I'm running Solaris 10 with a zone called "testzone" If I do a "reboot -d" on the host, as expected the kernet panics, reboots and creates a crash dump file in /var/crash However no crash file is created in testzone. My question is how can I tell if a zone crashs or shuts down... (4 Replies)
Discussion started by: fastexit
4 Replies

6. Solaris

Question with Solaris Crash Analysis Tool with Solaris 9

Hello all. I am new hear and would like to ask a question regarding to the Solaris Crash Analysis Tool. We are analyzing the results of "thread summary" but not quite sure what the asterisk represents. Following are the items that asterisk were attached. 50* threads sleeping on a semaphore (49... (1 Reply)
Discussion started by: YuW
1 Replies

7. Solaris

Can't Log into Solaris 10 u10 due to Pam and DH errors

Dears,, i hope everything is going fine with you,, Yesterday i was trying to log into My Solaris 10 u10 x86 Via SSH , But it showing me many error message and refusing to login even with with the root account and below you can find the error message: # ssh -v root@192.168.10.1... (6 Replies)
Discussion started by: ieee99
6 Replies

8. Solaris

Check for existence of crash on Solaris 10

Hey all what is the command to check "Check for existence of crash/coredump files in /var/crash/"hostname" directory" thanks for help (4 Replies)
Discussion started by: gema.utama
4 Replies

9. Solaris

How to recover x86 Solaris 10 u10 boot record/grub menu overwritten by Debian 9?

I installed x86 Solaris 10 update 10 after Windows XP, later I removed xp and installed Debian 9 stretch on the same partition but, Debian couldn't find any other os so it deleted Solaris 10 grub or did something like that I couldn't got. I thought I would be able to recover the lost record by... (0 Replies)
Discussion started by: vectrum
0 Replies
ace(7)							 Miscellaneous Information Manual						    ace(7)

NAME
ace - Serial communications interface SYNOPSIS
controller ace0 at * slot ? vector aceintr DESCRIPTION
The ace serial line controller provides a serial communications interface on DEC 2000, AlphaStation, and AlphaServer platforms. The serial communications ports that are controlled by ace adhere to the RS-232 standard and can operate at rates from 50 to 115200 baud (see tty(7)). These communications ports support serial-line printers, modems, and terminals. In alternate console configurations (that is, no graphics head), the terminal to be the system console must be connected to the port that is mapped to /dev/tty00. (See ports(7) for information about mapping AlphaStation and AlphaServer port labels to device pathnames.) Cur- rently, some processors that use the ace driver limit the serial console port to 9600 baud, 8-bit, no parity and no modem support. However, some processor consoles do support baud rates other than 9600 baud and allow the use of modems as console devices. Consult your hardware documentation to determine the type of console support your system provides. The driver for the ace interface supports hardware flow control using the Request to Send (RTS) and Clear to Send (CTS) signals. When hardware flow control is enabled, the flow of input data is controlled by the RTS signal and the flow of output data is controlled by the CTS signal. If the CTS signal is off, the driver suspends output to that line until the CTS lead is reasserted. Likewise the driver turns off the RTS lead to tell the device connected to the line to stop sending data as a result of congestion on the host side. When the condi- tion clears, the driver turns on the RTS lead to tell the device to resume sending data. The DCD (carrier detect) timer value defaults to 2 seconds. This value may be changed if your modem hardware requires a different value. the change can be made in the /etc/sysconfigtab file as follows: ace: dcd_timer=n where n is the time interval in seconds, and can be set to 0 (no timeout), 1, or 2 seconds. Alternatively, you can use the sysconfig com- mand to set the same time interval option as follows: # sysconfig -r ace dcd_timer=[n] If you use the sysconfig command, the value will not be preserved when the system is rebooted. To preserve the setting, put the entry in the /etc/sysconfigtab file NOTES
If you are using the alternate system console to perform kernel debugging, you must change the kdebug entry in the /etc/remote file to use /dev/tty01; when the kernel is running in debugging mode, no other application can use the port. See Kernel Debugging for information on setting up your system for kernel debugging. RESTRICTIONS
Unless alternative specifications are stated in your system hardware documentation, data communications equipment attached to the console serial port in alternate console configurations must be set to 9600 baud, 8-bits, no parity. If a serial console is being used, /dev/tty00 cannot be opened by another process. The ace driver enforces this restriction. Baud rates greater than 38400 are not supported on the two primary serial ports on the DEC 2000 system. However, if you use an ISA serial or modem card that is capable of communicating at the higher rates, the higher rates are supported. FILES
console terminal local terminal local terminal RELATED INFORMATION
MAKEDEV(8), console(7), devio(7), modem(7), ports(7), tty(7) Kernel Debugging System Administration delim off ace(7)
All times are GMT -4. The time now is 09:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy