Failed to power up


 
Thread Tools Search this Thread
Operating Systems Solaris Failed to power up
Prev   Next
# 1  
Old 01-04-2008
Failed to power up

Dear expert,

I have one server,in /var/adm/messages everyday present these messages:

Jan 3 06:01:30 SERVERGINTING genunix: [ID 353554 kern.warning] WARNING: Device /pci@1d,700000/pci@1/scsi@2,1/sd@5,0 failed to power up.
Jan 3 06:01:31 SERVERGINTING scsi: [ID 107833 kern.warning] WARNING: /pci@1d,700000/pci@1/scsi@2,1/sd@5,0 (sd45):
Jan 3 06:01:39 SERVERGINTING ip: [ID 766727 kern.warning] WARNING: The <if>:ip*_forwarding ndd variables are obsolete and may be removed in a future release of Solaris. Use ifconfig(1M) to manipulate the forwarding status of an interface.


I still confuse,please help me to search how these problem resolved,thank's for your attentions.

Last edited by fredginting; 04-11-2008 at 04:42 AM..
 
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Red Hat

Power Cut

Dear All I am using a redhat server for cdr billing and mediation device on a remote network. I am experiencing problem that I am suspicious it comes from main supply power cut at the remote site. The power supply to the remote site comes from battery charger that will be automatically switched in... (1 Reply)
Discussion started by: hadimotamedi
1 Replies

2. Solaris

Cygwin X Server error: xdmcp fatal error session failed session 23 failed for display

Hi, i got the following error when i tried to access the cygwin x server from a windows XP PC. "xdmcp fatal error session failed session 23 failed for display" Alternatively, when i tried to access the same Cygwin X Server from another windows XP PC which is on a different LAN... (3 Replies)
Discussion started by: HarishKumarM
3 Replies

3. AIX

POWER Hardware

I need book or any useful link about POWER hardware architecture .. Thanks :-) (4 Replies)
Discussion started by: Vit0_Corleone
4 Replies

4. AIX

SFTP Failed---Request for subsystem 'sftp' failed on channel 0

Hi, While I am trying SFTP my machine to another unix machine , it was working fine till 10 min back. But now i am getting the below error "Request for subsystem 'sftp' failed on channel 0" Could you please someone help me to solve or analyise the root cause... Cheers:b:, Mahiban (0 Replies)
Discussion started by: mahiban
0 Replies

5. AIX

How to tell Power 4/5/6

I'm looking for a way - from the command line - to tell whether a given AIX system I have is a Power5, Power4 or Power6 machine - it seems like there would be an option to 'uname' but I couldn't find one. Thanks! (3 Replies)
Discussion started by: thomn8r
3 Replies

6. Shell Programming and Scripting

mdelete power

hi to all! im using hp-ux 10.2 is it posible for the mdelete command to execute on the root directory if it did not find any file on the specified sub-directory? this is my sample script USER=root PASSWD=root cd /u01/app/oralog/arch ftp -n 192.119.10.3 user $USER $PASSWD prompt... (2 Replies)
Discussion started by: gunsbong
2 Replies

7. UNIX for Dummies Questions & Answers

Power Cycling

Hello Friends , I have been reading some of the Sys Admin notes when i came across a term "Power Cycling" Can anybody please explain what this means Thank You (1 Reply)
Discussion started by: DPAI
1 Replies
Login or Register to Ask a Question
SYSLOGD(8)						      System Manager's Manual							SYSLOGD(8)

NAME
syslogd - log systems messages SYNOPSIS
syslogd [ -fconfigfile ] [ -mmarkinterval ] [ -d ] DESCRIPTION
Syslogd reads and logs messages into a set of files described by the configuration file /etc/syslog.conf. Each message is one line. A message can contain a priority code, marked by a number in angle braces at the beginning of the line. Priorities are defined in <sys/sys- log.h>. Syslogd reads from the UNIX domain socket /dev/log, from an Internet domain socket specified in /etc/services, and from the spe- cial device /dev/klog (to read kernel messages). Syslogd configures when it starts up and whenever it receives a hangup signal. Lines in the configuration file have a selector to deter- mine the message priorities to which the line applies and an action. The action field are separated from the selector by one or more tabs. Selectors are semicolon separated lists of priority specifiers. Each priority has a facility describing the part of the system that gener- ated the message, a dot, and a level indicating the severity of the message. Symbolic names may be used. An asterisk selects all facili- ties. All messages of the specified level or higher (greater severity) are selected. More than one facility may be selected using commas to separate them. For example: *.emerg;mail,daemon.crit Selects all facilities at the emerg level and the mail and daemon facilities at the crit level. Known facilities and levels recognized by syslogd are those listed in syslog(3) without the leading ``LOG_''. The additional facility ``mark'' has a message at priority LOG_INFO sent to it every 20 minutes (this may be changed with the -m flag). The ``mark'' facility is not enabled by a facility field containing an asterisk. The level ``none'' may be used to disable a particular facility. For example, *.debug;mail.none Sends all messages except mail messages to the selected file. The second part of each line describes where the message is to be logged if this line is selected. There are four forms: o A filename (beginning with a leading slash). The file will be opened in append mode. o A hostname preceeded by an at sign (``@''). Selected messages are forwarded to the syslogd on the named host. o A comma separated list of users. Selected messages are written to those users if they are logged in. o An asterisk. Selected messages are written to all logged-in users. Blank lines and lines beginning with `#' are ignored. For example, the configuration file: kern,mark.debug /dev/console *.notice;mail.info /usr/spool/adm/syslog *.crit /usr/adm/critical kern.err @ucbarpa *.emerg * *.alert eric,kridle *.alert;auth.warning ralph logs all kernel messages and 20 minute marks onto the system console, all notice (or higher) level messages and all mail system messages except debug messages into the file /usr/spool/adm/syslog, and all critical messages into /usr/adm/critical; kernel messages of error severity or higher are forwarded to ucbarpa. All users will be informed of any emergency messages, the users ``eric'' and ``kridle'' will be informed of any alert messages, and the user ``ralph'' will be informed of any alert message, or any warning message (or higher) from the authorization system. The flags are: -f Specify an alternate configuration file. -m Select the number of minutes between mark messages. -d Turn on debugging. Syslogd creates the file /var/run/syslog.pid, if possible, containing a single line with its process id. This can be used to kill or reconfigure syslogd. To bring syslogd down, it should be sent a terminate signal (e.g. kill `cat /var/run/syslog.pid`). FILES
/etc/syslog.conf the configuration file /var/run/syslog.pid the process id /dev/log Name of the UNIX domain datagram log socket /dev/klog The kernel log device SEE ALSO
logger(1), syslog(3) 4.2 Berkeley Distribution November 16, 1996 SYSLOGD(8)