06-26-2008
Solaris box V440 got stucked
Hi Friends,
My solaris box V440 got stucked. I couldn't accessit from the remote console. Finally i restarted the box.
Can you tell me what are the ways we can find out the issues
and what are the logs we can check other than /var/log/messages.
Thanks
Jinu
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I need a clarification.
Is there any difference between AIX box and Sun Solaris box?
The bzip command with -c option works in AIX box and the same does not work in Sun Solaris box.
Can anyone please explain if there is an implementation difference in both these boxes for the shell... (1 Reply)
Discussion started by: nisha4680
1 Replies
2. Solaris
Hello,
I've a very weird problem with one of the machines. When I try to boot off a working DVD that I used to install another system with it spits out the following message:
Sun Fire V440, No Keyboard
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.22.33, 8192 MB... (14 Replies)
Discussion started by: stoci
14 Replies
3. Solaris
hi,
can someone please guide me if there is any special hardware to use when we need to terminate an E1/T1 link on a Solaris10 box. I have a number of boxes and these all are located at longer distances. the only connectivity is the E1 links between these far location locations.
Would it be... (0 Replies)
Discussion started by: busyboy
0 Replies
4. Solaris
Hi:
I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Discussion started by: mguazzardo
1 Replies
5. Shell Programming and Scripting
Hi,
I am using sed in way desribed below:
sed "
s/study_seq_no/$STUDY_SEQ_NO/g
s/table_nm/$TBL_NM/g
s/dmp_file_nm/$DMP_FILE_NM/g
s/dmp_file_lst/'`ls \/opt\/abcd\/efgh\/export_dump\/$DMP_FILE_NM*.dmp`'/g
s/log_file_nm/$LOG_FILE_NM/g
s/dt_of_init/$DT/g
... (15 Replies)
Discussion started by: manubatham20
15 Replies
6. IP Networking
Hello my friends , i am totally stuck in ssh port forwarding topic
i had learn iptables and other networking topic without any problem but ssh port forwarding is headache
1. local port = what is this ? is this incoming traffic or outgoing traffic
2. remote port = same as above
3. dynamic... (2 Replies)
Discussion started by: rink
2 Replies
7. Solaris
Got a T2000 which has got the 2.5" SAS drives. Want to be able, if I can, to connect to USB caddy and connect to a V440.
Anyone ever tried this? To be honest, having problems even finding a SAS-USB caddy. (0 Replies)
Discussion started by: psychocandy
0 Replies
8. Solaris
Hi,
I have Sun Solaris V440, every two days or so, the system crashes and it's at OK prompt. After that I do the FSCK and clear all the bad sectors. Then system stays up for close to 48 hours. Then it crashes again. I checked the logs and I don't see anything under /var/adm/messages file.
... (1 Reply)
Discussion started by: samnyc
1 Replies
9. Solaris
Hi,
I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either.
Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an... (5 Replies)
Discussion started by: Echo68
5 Replies
10. Solaris
Hi there,
I have a V440 Server based on Sun Microsystem with Solaris OS.
Is there any way to auto power on the system only with cabling the V440 with 220 v?
Thanks! (10 Replies)
Discussion started by: proof_enrique
10 Replies
LEARN ABOUT DEBIAN
ipsec_barf
IPSEC_BARF(8) [FIXME: manual] IPSEC_BARF(8)
NAME
ipsec_barf - spew out collected IPsec debugging information
SYNOPSIS
ipsec barf [--short --maxlines <100>]
DESCRIPTION
Barf outputs (on standard output) a collection of debugging information (contents of files, selections from logs, etc.) related to the
IPsec encryption/authentication system. It is primarily a convenience for remote debugging, a single command which packages up (and labels)
all information that might be relevant to diagnosing a problem in IPsec.
The --short option limits the length of the log portion of barf's output, which can otherwise be extremely voluminous if debug logging is
turned on.
--maxlines <100> option sets the length of some bits of information, currently netstat -rn. Useful on boxes where the routing table is
thousands of lines long. Default is 100.
Barf censors its output, replacing keys and secrets with brief checksums to avoid revealing sensitive information.
Beware that the output of both commands is aimed at humans, not programs, and the output format is subject to change without warning.
Barf has to figure out which files in /var/log contain the IPsec log messages. It looks for KLIPS and general log messages first in
messages and syslog, and for Pluto messages first in secure, auth.log, and debug. In both cases, if it does not find what it is looking for
in one of those "likely" places, it will resort to a brute-force search of most (non-compressed) files in /var/log.
FILES
/proc/net/*
/var/log/*
/etc/ipsec.conf
/etc/ipsec.secrets
HISTORY
Written for the Linux FreeS/WAN project <http://www.freeswan.org> by Henry Spencer.
BUGS
Barf uses heuristics to try to pick relevant material out of the logs, and relevant messages which are not labelled with any of the tags
that barf looks for will be lost. We think we've eliminated the last such case, but one never knows...
Finding updown scripts (so they can be included in output) is, in general, difficult. Barf uses a very simple heuristic that is easily
fooled.
The brute-force search for the right log files can get expensive on systems with a lot of clutter in /var/log.
[FIXME: source] 17 March 2002 IPSEC_BARF(8)