Hi
I faced a problem while booting linux which is as follows;-
*************************************************
Inode 146180 has illegal block(s)
xauth:error in locking authority file /home/root/.Xauthority
Fatal Server Error:
Could not create lock file in /tmp/tXo-lock
... (1 Reply)
Our SUn Solaris Server has crashed second time in 2 days, reason is not known , we are trying to determine what could have gone wrong, any ideas, the power supply seems to be fine, there is no response from keyboard,monitor etc and we had to do a hot boot yesterday..
Any suggestions what could be... (9 Replies)
We have had a server (Solaris 2.6) hardisk crash. When booting the server we get:
ok> boot -S
Boot Device: /sbus/espdmc@e, 8400000/esp@e,8800000/sd@0,0
short read 0x2000 chars read
disk read error
The only way we can get into the console is to
ok> boot cdrom
whereby everything (e.g.... (3 Replies)
Is it possible for a group of servers to monitor each other and then send an alert if one of them is no longer 'alive'?
Or if its easier have one server that monitors the other five and then sends an alert.
If so how would this be done?
Thanks (3 Replies)
Is it true that you can't have the crash dump server/client on the same server?
I know I've installed Nagios open source before, I though it's only for that kind of thing. I never though that Red hat ent 4 would be like client/server on the crash dump.
if someone is having problem with high... (0 Replies)
Problem
- Linux Client/Server Socket Application: Preventing Client from quitting on server crash
Hi,
I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64.
I am having problem trying to implement a scenario where the client should keep running even when the... (2 Replies)
Hi there.
Well i have a really bad problem with my server:
UnixWare Version 5 Release 7
The system crash :wall: and show the error:
Panic: Kernel-mode address fault on user address 0x00000004 :eek:
If anyone knows about the reason of this error please give me a help
Sorry by my english.... (3 Replies)
The steps to test the problem
1. Open TCP Server
2. Open TCP Client
3. TCP Client sends data to Server.
4. Close TCP Server and the client also crash without any notification
Second wonderful test:
1. Comment the following statement in Client.c (at line 168) and compile it
Writen(... (1 Reply)
hi,
i would like to configure netdump, but saving the var/crash in the server itself, not in another server.
could anybody tell me if this is possible?
thanks (4 Replies)
Hi there
I've bought a used System p 9115-505. When I attach the LAN cable to my router the HMC receives an IP address from my router, but the HMC is unreachable. There are no open ports.
Does anybody know that problem?
Any help greatly appreciated. Greetings from Italy! (2 Replies)
Discussion started by: mediaset23
2 Replies
LEARN ABOUT MOJAVE
reportcrash
ReportCrash(8) BSD System Manager's Manual ReportCrash(8)NAME
ReportCrash -- Generates crash reports
SYNOPSIS
ReportCrash
DESCRIPTION
ReportCrash analyzes crashing processes and saves a crash report to disk. A crash report contains information that can help a developer
diagnose the cause of a crash. ReportCrash also records the identity of the crashing process and the location of the saved crash report in
the system.log and the ASL log database.
ReportCrash is invoked automatically by launchd when a crash is detected. For applications and other processes running in the per-user
launchd context, ReportCrash runs as a LaunchAgent and saves crash reports in the user's ~/Library/Logs/DiagnosticReports/ directory. For
daemons, other processes running in the system launchd context and other privileged processes, ReportCrash runs as a LaunchDaemon and saves
crash reports in the system's /Library/Logs/DiagnosticReports directory where they are only readable by admin users. If there are too many
crash reports saved for a particular process, older reports will automatically be removed in order to conserve disk space.
launchtl can be used to disable and re-enable crash reporting. To disable crash reporting:
launchctl unload -w /System/Library/LaunchAgents/com.apple.ReportCrash.plist
sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist
To re-enable crash reporting:
launchctl load -w /System/Library/LaunchAgents/com.apple.ReportCrash.plist
sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.ReportCrash.Root.plist
For application crashes (but not background process crashes) ReportCrash will display a dialog notifying the user that the application unex-
pectedly quit and offering to reopen the application or send the report to Apple. For developers, the behavior of this dialog can be
adjusted using /Developer/Applications/Utilities/CrashReporterPrefs.app which is installed as part of the developer tools.
Crash reports which are sent to Apple are submitted anonymously by the SubmitDiagInfo process. The reports are used by Apple to improve its
products. Users who need support should use http://www.apple.com/support or other authorized support channels. Developers who are ADC mem-
bers should report bugs using http://bugreporter.apple.com in order to allow for two way communication between Apple and the bug reporter.
More information about interpreting the contents of crash reports can be found in Technote 2123: https://developer.apple.com/library/con-
tent/technotes/tn2004/tn2123.html
SEE ALSO launchd(8), launchd.plist(8), launchctl(8), spindump(8), SubmitDiagInfo(8)Mac OS June 1, 2019 Mac OS