11-04-2009
Did the server actually panic I cant see any panic string.
The problems I see could have made the server sluggish or hang it.
The first messages has to do with veritas volumemanager/filesystem
and you are having problems with the fibre connection to the SUN3510 raid.
I would update HBA card driver (sun would probably tell you to ugrade tha SAN "package" its varios patches) ,firmware in the 3510 array and check
fibre cables and "GBICS"
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I still haven't got an answer to this question...
Excerpt from My SysAd Blog
A colleague of mine is having a problem with a Sun Fire v1280 server crashing. He tried Googling for the error message in red but hasn't found anything yet. Your insights would be greatly appreciated.
"cannot... (2 Replies)
Discussion started by: esofthub
2 Replies
2. UNIX for Dummies Questions & Answers
Hello all,
I'm lost and can't figure this problem out.
I have a Sun fire 280R running Solaris 8. Everything was working great. I have one drive in bay 1(not 0). But when I reboot the system it trys to open files in /dev/rdsk/c1t1d0s0. Should it have been opeing /dev/rdsk/c1t0d0s0, the... (4 Replies)
Discussion started by: larryase
4 Replies
3. Solaris
Hello, I'm trying to fix this server System Board (CPU/Memory Unit). The error indicates that its missing 3.3VDC. So far all the fuses and caps have been checked. I new at this type of machine, need help for idea on this system. Thank you in advance.
Vu (0 Replies)
Discussion started by: vhtran
0 Replies
4. Solaris
During system startup the following warnings are appear.
Warning: /pci@8, 700000/scsi@6, 1 (g1m1)
Connected command timeout for target 9.0
Warning: /pci@8, 700000/scsi@6, 1 (g1m1)
Target 9 reducing sync, transfer rate
Warning: /pci@8, 700000/scsi@6, 1... (5 Replies)
Discussion started by: tabreaz
5 Replies
5. Solaris
I am new to Sun.
I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor?
Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies
6. Solaris
Hi men,
Have you ever meet this error ?
I install full Sun MC 4.0 packages (+ Add ons) exception of Sun Midrange Platform Administration because i don't know how to configure it
Then all other servers are ok, only E2900 servers have Config reader module error: Data Acquisition error
I... (12 Replies)
Discussion started by: tien86
12 Replies
7. Solaris
I am running Sun Explorer to collect data, but /proc is very big in size so it is takin time to get completed. (Running from past 3 hours). I ran -->
/opt/SUNWexplo/bin/explorer -w all,zones
root@tsrim03:/# ps -ef | grep -i explo
root 27623 6539 0 06:28:59 pts/1 0:03 ksh -p... (1 Reply)
Discussion started by: solaris_1977
1 Replies
8. Solaris
several newbie questions:
> how-to find serialnumber for Sun E2900
prtdiag -v does not show chassis serial number
> LOM is not connectable .
Are there any tools to get automatically Serial numbers for HW.
Thanks ! (7 Replies)
Discussion started by: magedfawzy
7 Replies
9. Solaris
Hello,
I have purchaced an old SUn fire x2270 server .
I wanted to make ILOM upgrade to the latest version of software :
ILOM 3.0.9.18.a r126592
BIOS vers. 2.09
Server 2.2.3
(10-Aug-2018)
Because my version is very outdated.
But i can't download the updatebecause it's require... (4 Replies)
Discussion started by: LouisLakoute
4 Replies
LEARN ABOUT REDHAT
netdump-server
NETDUMP-SERVER(8) System Programs NETDUMP-SERVER(8)
NAME
netdump-server - handle crash dumps over the network
SYNOPSIS
netdump-server [--port portnumber]
[--concurrent number]
[--pidfile path]
[--daemon]
[--help] [--usage]
DESCRIPTION
Listens to the network for clients that crashes and uses the netdump protocol to recieve a memory dump and a stack trace. The memory dump
and oops message are stored in a timestamped directory in /var/crash. The server can also run scripts when some events happen.
OPTIONS
--port portnumber
Specifies the IP port number for the netdump server to listen to. The default is 6666.
--concurrent number
You can limit the amount of concurrent dumps being done at any one time. If more clients than the specified maximum connects at one
time the last ones will just be logged and then rebooted.
--pidfile path
Store a pidfile. The default service uses /var/run/ttywatch.pid. The default is not to write a pidfile.
--daemon
ttywatch should background itself and run as a daemon.
EXAMPLES
netdump-server --daemon
This launches the netdump-server and puts it in the background, listening for crashed clients.
EXIT STATUS
Exit status is 0 for a clean exit and non-0 for a non-clean exit.
FILES
/etc/netdump.conf
A configuration file read by netdump-server on startup. It is a "key=value" style file. Currently it supports the options: port,
max_concurrent_dumps, daemon and pidfile.
/etc/init.d/netdump-server
An init script to start a default system installation of netdump-server. This is normally turned off by default; use the command
/sbin/chkconfig netdump-server on
to enable the netdump-server service.
/var/crash
The main directory where the crash dump files are stored. Each dump is put in a subdirectory named with the ip of the crashed
machine and the date and time of the crash.
/var/crash/scripts
This directory can contain scripts that are run at various times. They all get passed the ip of the crashing machine as the first
argument, and each one except netdump-start gets the directory that the dump is written into as the second argument.
netdump-start - This is called when a client connects to the server to tell it that it has just started the netdump client. This
normally means that the machine just booted up.
netdump-crash - This is run when a client reports that it has crashed. If it returns a non-zero value the dump request will be
ignored and the client will be told to reboot immediately
netdump-nospace - This is run when there is not enough diskspace for the dump of the crashed machine. If this script exits with a
non-zero return value netdump-server will try once again (but only once) before giving up the dump. If this script exits with a zero
return value, netdump-server will reboot the client without performing a dump.
netdump-reboot - This is run when netdump-server is finished with a client and is about to tell the client to reboot itself.
SEE ALSO
netdump(8)
BUGS
Report any bugs you find to http://bugzilla.redhat.com/bugzilla
AUTHOR
Alexander Larsson <alexl@redhat.com>
Linux 14 Feb 2002 NETDUMP-SERVER(8)