11-05-2008
I have never seen anything like that. I still have no idea what it is. But format should complain if a drive is dead, not just seg fault like that.
10 More Discussions You Might Find Interesting
1. Solaris
Hey All
Thanks in Advance.
Iam facing a problem with Netra T1 105 Ram issuse.I have 1 gb ram in the server but when it boots up in ok prompt or in banner it shows 768 mb Ram , if i put 512 mb Ram it show 368 mb Ram but this all ram if i connect in anthore netra server its shows 1 gb and... (1 Reply)
Discussion started by: solaris8in
1 Replies
2. Solaris
Hello,
I wrote a script which monitor the keyswitch state repeatedly each 10 minutes.
I'm extracting the keyswitch status by using prtdiag.
The script works fine for Netra v440 , but I found that prtdiag under Netra 1290 don't give keyswitch status.
unlike Netra 440 server , I found that... (2 Replies)
Discussion started by: Alalush
2 Replies
3. Solaris
Hi,
I have Sun SPARC Enterprise T5140 and I can't access it via serial port using preconfigured administrator account, as described in Sun Integrated Lights Out Manager 2.0 User's Guide: I'm always receive "Login incorrect" message. I'm really confused! Does anyone experience such circumstances?... (12 Replies)
Discussion started by: Sapfeer
12 Replies
4. Debian
Comments/Problems:
Machine boots from CDROM, starts SILO Version 1.4.13,
display welcome message (welcome to Debian GNU/Linux lenny!
built on 20081218-10:06 ).
boot:
Allocated 8 Megs of memory at 0x40000000 for kernel
Loaded kernel version 2.6.26
Loading initial ramdisk... (3 Replies)
Discussion started by: mtk
3 Replies
5. Solaris
Looking for ideas on why I can't dial into our new Avaya CMS server (Sun Netra 210 - Sol 9) - remotely thru our ASA - site admin software.
Running R3-V13 Avaya CMS software - just did a fresh install of the CMS software - install went perfect.
The Sun supplied DB9 connector is installed... (1 Reply)
Discussion started by: drewmich
1 Replies
6. Solaris
Hi,
I have a netra t2000 running solaris 10. It is fully patched with the latest patch cluster and also patch 118833-36 and 126897-02. The SC sys_event level is set to 3.
I am running a test to show hardware log status, e.g simulating a power supply failure.Hence I unplug one of te... (3 Replies)
Discussion started by: ulemsee
3 Replies
7. Ubuntu
hello guys i bought a SPARC neutra system a couple of months ago and after failing to install solaris onto it (and leaving it as a door stop for a couple of months) decided to stick ubuntu onto it
for starters i dont own a sun keyboard i have a cheap pcline usb keyboard (it works... (3 Replies)
Discussion started by: garethmob
3 Replies
8. Solaris
Newbie question.
I've been running OpenSolaris on an Intel box for some time with great success.
I have just bought an old Sun Blade workstation with a corrupted version of Solaris 5 something on it.
The plan was to install OpenSolaris on it.
However beyond my skills, I see, as no Live CD (or... (10 Replies)
Discussion started by: lewtargett
10 Replies
9. Solaris
Hi All,
I had install the solaris 10 into the SUNFIRE V890 server, after installed, it keep rebooting.
I wish to enter the OK mode again, and install back the Solaris 10.
i had try the "break" button and "stop+A" button, but all fail.
kindly advice... (4 Replies)
Discussion started by: SmartAntz
4 Replies
10. Hardware
Hi guys,
when I power on my sun netra 240 server,
it displays these error messages:
1. Notice: cpu 0 has 2048/2048 MB of memory disabled.
2. Error : The following devices are disabled dimm1.
Please can anyone be kind enough to explain this for me?
Thanks (2 Replies)
Discussion started by: cjashu
2 Replies
LEARN ABOUT REDHAT
lamshrink
LAMSHRINK(1) LAM COMMANDS LAMSHRINK(1)
NAME
lamshrink - Shrink a LAM multicomputer.
SYNTAX
lamshrink [-hv] [-w <delay>] [-u <userid>] <node> <hostname>
OPTIONS
-h Print useful information on this command.
-v Be verbose.
<hostname> Remove the LAM node on this host.
<node> Remove the LAM node with this ID.
-w <delay> Notify processes on the doomed node and pause for <delay> seconds before proceeding.
-u <userid> Use this userid to access the host.
DESCRIPTION
An existing LAM session, initiated by lamboot(1), can be shrunk to include less nodes with lamshrink. One node is removed for each invoca-
tion. At a minimum, the node ID and the associated host name is given on the command line. Once lamshrink completes, the node ID is in-
valid across the remaining nodes. If a different userid is required to access the host, it is specified with the -u option.
Existing application processes on the target node can be warned of impending shutdown with the -w option. A LAM signal (SIGFUSE) will be
sent to these processes and lamshrink will then pause for the given number of seconds before proceeding with removing the node. By de-
fault, SIGFUSE is ignored. A different handler can be installed with ksignal(2).
All application processes on all remaining nodes are always informed of the death of a node. This is also done with a signal (SIGSHRINK),
which by default causes a process's runtime route cache to be flushed (to remove any cached information on the dead node). If this signal
is re-vectored for the purpose of fault tolerance, the old handler should be called at the beginning of the new handler. The signal does
not, by itself, give the process information on which node has been removed. One technique for getting this information is to query the
router for information on all relevant nodes using getroute(2). The dead node will cause this routine to return an error.
FAULT TOLERANCE
If enabled with lamboot(1), LAM will watch for nodes that fail. The procedure for removing a node that has failed is the same as lamshrink
after the warning step. In particular, the SIGSHRINK signal is delivered.
EXAMPLES
lamshrink -v newhost n1
Remove LAM on newhost, known within LAM as node 1. Report about important steps as they are done.
lamshrink newhost n30 -w 10
Inform all processes on LAM node 30, which is running on newhost, that the node will be dead in 10 seconds. Wait 10 seconds and remove
the node. Operate silently.
SEE ALSO
lamboot(1), tkill(1), ksignal(2), getroute(2)
LAM 6.5.8 November, 2002 LAMSHRINK(1)