Sponsored Content
Operating Systems Solaris Sun Server T2000 occasionally reboot Post 302323750 by honmin on Monday 8th of June 2009 11:01:00 PM
Old 06-09-2009
I have tried re-attaching the chassis but its weird still. Appreciate if you can shed some lights.

That's the patch that i installed to fix the bug.
Quote:
139434-02 to fix bug ID 6815610 (RFE T2000 systems may experience a shutdown with SC alert "Chassis cover removed")
 

10 More Discussions You Might Find Interesting

1. Solaris

How to create Logical domain in Sun Fire T2000 server

Hi I am fresher in Virtualisation in solaris 10.I need to know how to install and configure guest OS, I have a server Sun T2000 with solaris 10 OS BASE. How to install logical domain, what are the prerequest for installing l domain can some one guide me what are the basic requirement to... (2 Replies)
Discussion started by: solaris8in
2 Replies

2. Solaris

Sun Fire V490 occasionally downs

I can't find why but I suppose it is because of some hardware failures... I have a Sun Fire V490 with Solaris 10 5/08 which runs Sun Cluster 3.2 and it downs occasionally with a circumstances I can't define... Also I note some strange behavior after server failures: when I ran any diagnostics from... (6 Replies)
Discussion started by: Sapfeer
6 Replies

3. Solaris

Auto boot problem on Sun T2000

Hi All I have a problem on T2000 server. bash-3.00# uname -a SunOS 5.10 aaa Generic_120011-14 sun4v sparc SUNW,Netra-T2000After the initial solaris installation server failed to boot: Rebooting with command: boot Boot device: disk:b File and args: The file just loaded does not appear... (1 Reply)
Discussion started by: ouzist
1 Replies

4. Solaris

locator led SUN T2000

Hi Guys, I am unable to turn on the locator led light on a SUN T2000 machine # uname -a SunOS node1 5.10 Generic_137137-09 sun4v sparc SUNW,Sun-Fire-T200 when i try to turn it on I have following error. # locator -n 'system' locator not found Although the hardware specfication... (5 Replies)
Discussion started by: Asteroid
5 Replies

5. Solaris

Sun T2000 question

This may be a stupid question, but I don't want to take any chances. I have a Sun T2000 in production. I want to run the "resetsc" command on the ALOM controller to active an IP address change. Will resetting ALOM affect the running OS? Thanks (2 Replies)
Discussion started by: soliberus
2 Replies

6. Hardware

Hardware RAID on Sun T2000 Server

Hi All I have a Sun T2000 server. Couple of years ago I had configured and mirrored the boot drive with an other drive using hardware RAID 1 using raidctl command. Following is the hardware RAID output. root@oracledatabaseserver / $ raidctl RAID Volume RAID RAID Disk... (0 Replies)
Discussion started by: Tirmazi
0 Replies

7. Solaris

Sun T2000 error codes

I got a Power supply failure. I replaced the power supply and still got the error. Any ideas on what I should try next? (1 Reply)
Discussion started by: 642fiddi
1 Replies

8. Solaris

Any specific time to reboot the sun server to avoid unplanned outage ??

Hi, Would like to know the uptime or specific time limit to reboot the sun microsystem to avoid unplanned outage. Regards,Tarun (9 Replies)
Discussion started by: taruntan
9 Replies

9. Solaris

Patching failed on Sun T2000

Hi folks, I was patching Sun server (SunOS suns121 5.10 Generic_144488-17 sun4v sparc SUNW,Sun-Fire-T200) with the lateset bundle. It was completed with no errors. Server was restarted with shutdown command (/usr/sbin/shutdown -y -i6 -g0) after patching was complete. However, after that,... (3 Replies)
Discussion started by: zulu1
3 Replies

10. Solaris

Need Help, I want to reset password for Sun Fire T2000 Server

============================== ALOM BOOTMON v1.3.1 ALOM Build Release: 001 Reset register: f0000000 EHRS ESRS LLRS SWRS ALOM POST 1.0 Dual Port Memory Test, PASSED. TTY External - Internal Loopback Test TTY External - Internal Loopback Test, PASSED. TTYC - Internal Loopback Test TTYC -... (4 Replies)
Discussion started by: Sameer Naik
4 Replies
apport-bug(1)						      General Commands Manual						     apport-bug(1)

NAME
apport-bug, apport-collect - file a bug report using Apport, or update an existing report SYNOPSIS
apport-bug apport-bug symptom | pid | package | program path | .apport/.crash file apport-collect report-number DESCRIPTION
apport-bug reports problems to your distribution's bug tracking system, using Apport to collect a lot of local information about your sys- tem to help the developers to fix the problem and avoid unnecessary question/answer turnarounds. You should always start with running apport-bug without arguments, which will present a list of known symptoms. This will generate the most useful bug reports. If there is no matching symptom, you need to determine the affected program or package yourself. You can provide a package name or program name to apport-bug, e. g.: apport-bug firefox apport-bug /usr/bin/unzip In order to add more information to the bug report that could help the developers to fix the problem, you can also specify a process ID instead: $ pidof gnome-terminal 5139 $ apport-bug 5139 As a special case, to report a bug against the Linux kernel, you do not need to use the full package name (such as linux- image-2.6.28-4-generic); you can just use apport-bug linux to report a bug against the currently running kernel. Finally, you can use this program to report a previously stored crash or bug report: apport-bug /var/crash/_bin_bash.1000.crash apport-bug /tmp/apport.firefox.332G9t.apport Bug reports can be written to a file by using the --save option or by using apport-cli. apport-bug detects whether KDE or Gnome is running and calls apport-gtk or apport-kde accordingly. If neither is available, or the session does not run under X11, it calls apport-cli for a command-line client. UPDATING EXISTING REPORTS
apport-collect collects the same information as apport-bug, but adds it to an already reported problem you have submitted. This is useful if the report was not originally filed through Apport, and the developers ask you to attach information from your system. OPTIONS
Please see the apport-cli(1) manpage for possible options. ENVIRONMENT
APPORT_IGNORE_OBSOLETE_PACKAGES Apport refuses to create bug reports if the package or any dependency is not current. If this environment variable is set, this check is waived. Experts who will thoroughly check the situation before filing a bug report can define this in their ~/.bashrc or temporarily on the command line when calling apport-bug. SEE ALSO
apport-cli(1) AUTHOR
apport and the accompanying tools are developed by Martin Pitt <martin.pitt@ubuntu.com>. Martin Pitt September 08, 2009 apport-bug(1)
All times are GMT -4. The time now is 08:07 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy