Visit Our UNIX and Linux User Community

Top Forums UNIX for Advanced & Expert Users Solaris 8 crash on Enterprise 3500 Post 20383 by alex blanco on Thursday 25th of April 2002 11:17:03 AM
Old 04-25-2002
Solaris8

Hi, as I see your problem could be a damage library (lib.so.1) or perhaps there is a missing link to that library, did you try to install any kind of "workshop" where all those libraries are included?
Let me tell you something I've installed Solaris8 in several Enterprises and only in a E3500 I had troubles in my case "man pages" seems not to be installed there was no entry for man, could it be a bug for E3500?

cheers
 
Test Your Knowledge in Computers #551
Difficulty: Medium
If variable i has the value 10, after x = 5 + (i++); the value of x after this code is 15.
True or False?

10 More Discussions You Might Find Interesting

1. 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

2. Solaris

Solaris 10 on Enterprise 250

Hi experts, I have bought a used SUN Enterprise 250 server that currently runs solaris 8. Ive downloaded solaris 10 (sparc edition) from sun.com, and have burned the iso files to cd roms. So far so good. I can log into the system via the serial interface (port A). I want to sweep the discs,... (21 Replies)
Discussion started by: congo
21 Replies

3. Solaris

Solaris 10 on Enterprise 3500

Hellocan someone tell me if there are any special tricks at hand t set up Solaris 10 on a Enterprise 3500? I`ve tried with different cd`s, burnt on different speeds, and also with bought one`s. All give the same result after boot cdrom, it starts but freezes right after the license message.And... (16 Replies)
Discussion started by: vatch23
16 Replies

4. IP Networking

More then 3500 sockets in FIN_WAIT1

Hello, My config: SLES 10 sp1 Apache / drupal / mysql I have a saturation of TCP ports on this hosts. Hosting about 60 websites. The event tonight was ~200 hits minutes. With "netstat-n" I see ~5500 connections. Including approximately 3800 in FIN_WAIT1. As a first step I would... (3 Replies)
Discussion started by: lilech
3 Replies

5. 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

6. 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

7. 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

8. Solaris

Need help -- netra 5 Solaris enterprise 2

I need help to resurrect very old netra machines. two of them are netra enterprise 2 and they do not boot with the message Cant open boot device The IDPROM contents are invalid Boot device: net File and args the host is not connected to any LAN I brought up another Netra 5 connected to... (3 Replies)
Discussion started by: rk2153
3 Replies

9. Solaris

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... (3 Replies)
Discussion started by: Aswex
3 Replies

10. 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
savecore(1M)                                              System Administration Commands                                              savecore(1M)

NAME
savecore - save a crash dump of the operating system SYNOPSIS
/usr/bin/savecore [-Lvd] [-f dumpfile] [directory] DESCRIPTION
The savecore utility saves a crash dump of the kernel (assuming that one was made) and writes a reboot message in the shutdown log. It is invoked by the dumpadm service each time the system boots. savecore saves the crash dump data in the file directory/vmcore.n and the kernel's namelist in directory/unix.n. The trailing .n in the pathnames is replaced by a number which grows every time savecore is run in that directory. Before writing out a crash dump, savecore reads a number from the file directory/minfree. This is the minimum number of kilobytes that must remain free on the file system containing directory. If after saving the crash dump the file system containing directory would have less free space the number of kilobytes specified in minfree, the crash dump is not saved. if the minfree file does not exist, savecore assumes a minfree value of 1 megabyte. The savecore utility also logs a reboot message using facility LOG_AUTH (see syslog(3C)). If the system crashed as a result of a panic, savecore logs the panic string too. OPTIONS
The following options are supported: -d Disregard dump header valid flag. Force savecore to attempt to save a crash dump even if the header information stored on the dump device indicates the dump has already been saved. -f dumpfile Attempt to save a crash dump from the specified file instead of from the system's current dump device. This option may be useful if the information stored on the dump device has been copied to an on-disk file by means of the dd(1M) command. -L Save a crash dump of the live running Solaris system, without actually rebooting or altering the system in any way. This option forces savecore to save a live snapshot of the system to the dump device, and then immediately to retrieve the data and to write it out to a new set of crash dump files in the specified directory. Live system crash dumps can only be per- formed if you have configured your system to have a dedicated dump device using dumpadm(1M). savecore -L does not suspend the system, so the contents of memory continue to change while the dump is saved. This means that live crash dumps are not fully self-consistent. -v Verbose. Enables verbose error messages from savecore. OPERANDS
The following operands are supported: directory Save the crash dump files to the specified directory. If directory is not specified, savecore saves the crash dump files to the default savecore directory, configured by dumpadm(1M). FILES
directory/vmcore.n directory/unix.n directory/bounds directory/minfree /var/crash/'uname -n' default crash dump directory ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
adb(1), mdb(1), svcs(1), dd(1M), dumpadm(1M), svcadm(1M), syslog(3C), attributes(5), smf(5) NOTES
The system crash dump service is managed by the service management facility, smf(5), under the service identifier: svc:/system/dumpadm:default Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. If the dump device is also being used as a swap device, you must run savecore very soon after booting, before the swap space containing the crash dump is overwritten by programs currently running. SunOS 5.10 25 Sep 2004 savecore(1M)

Featured Tech Videos

All times are GMT -4. The time now is 09:13 PM.
Unix & Linux Forums Content Copyright 1993-2020. All Rights Reserved.
Privacy Policy