Sponsored Content
Operating Systems Solaris Sun Fire X4540 in a reboot cycle Post 302554108 by DukeNuke2 on Saturday 10th of September 2011 04:25:57 AM
Old 09-10-2011
looks like a hardware error to me... sadly such errors are hard to troubleshoot.
 

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Sun Fire v1280 is crashing

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

Sun Fire 280R

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

Sun Fire 280R Sun Solaris CRT/Monitor requirements

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

4. Solaris

Sun X4540 Ilom - Solaris 10

Hello Admins, I am trying to access the solaris 10 host using the ilo. When I do start /SP/console, it just hangs, it doesn't give me any login prompt... I tried reset /SYS and also did reset /SP...but no luck... We have Sun X4540.... Any help appreciated..Thanks (9 Replies)
Discussion started by: snchaudhari2
9 Replies

5. Hardware

Sun fire 4270 reset BIOS settings after reboot

Hello, I am trying to perform Suse 10 SP3 installation via network in 6 Sun Fire 4270 M2 servers. The problem is that even if i set first prio boot device the hard disk the system always try to boot from network.And after the first restart the BIOS setting has been lost(and PXE come first... (2 Replies)
Discussion started by: @dagio
2 Replies

6. Solaris

Sun fire x2270

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
filterlog(8)						      System Manager's Manual						      filterlog(8)

NAME
filterlog - Logs and reports system Correctable Read Data (CRD) memory errors on specific systems. SYNOPSIS
/usr/sbin/filterlog [-l] [-d crdlog] [-d crdlifetime] [-s crdlength #] [-s crdcount #] [-h] OPTIONS
Logs or filters an entry from stdin. This option is used by the binary event-log daemon, binlogd. Dumps the contents of the CRD log file in text format. Errors shown in the file are those recorded by the system since the last boot. Dumps the CRD lifetime log information in text format. Used to set the CRD interval time in minutes. The default is 24 hours. Used to set the CRD interval count. The default is 50. Prints a list of the command option options defined in this reference page. DESCRIPTION
This utility ensures that only genuine memory errors are reported to system log files on certain system types. The command filterlog is called directly by the binary event-log daemon, binlogd to filter system CRD (memory hardware) errors. CRD errors are logged according to user-definable parameters. If it is determined that a genuine memory problem exists, an entry is passed to binlogd. The error will then be written to the system's error log file and can be notified to the user through DECevent. The filterlog utility uses two variables to determine if a CRD error signifies a genuine memory hardware problem -- crdlength and crdcount. If crdcount number of errors occur during crdlength minutes, an entry is passed to binlogd. The default settings are 50 errors in 24 hours (1440 minutes). The filterlog utility reads the /etc/binlog.conf file to determine what log file should be used to record any events. The default log file is /usr/adm/binary.crdlog. SEE ALSO
Commands: binlogd(8), dia(8) (DECevent) filterlog(8)
All times are GMT -4. The time now is 10:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy