12-20-2017
The scanner is not in the server but somewhere on your network, internal I hope, or it may be an attack as mentionned... so in internal it seems there is something looking like a such device at the IP I pointed out - Check!
Years ago I had many HP-UX crashes once a month till I decided to write at the direction saying those "non-intrusive" devices were all but that and crashing HP servers or some mainframe devices, mostly the ones trusted and having/using NFS, the reason is mainly it opens so many connections id doesnt care for itself (MS.. OS?) but on a UNIX server the timeouts are regularly over 5 minutes so a opened port cannot be used till it is cleaned and so in such cases quickly you run out and then no one can connect, not even root and you are doomed... Once I proved where it came from the HP servers were listed out the scanning process... and now they changed system, but I have no more HP either... If you have NFS mounted on that server and the scan manages to make it unreadable then your system depending what is running will try to read desperatly and it s load will go beyond control till the system crashes...
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi I am using unix for last few days. Here is my problem
during boot the machine stop giving video signal and I don't know what's happening.
When I ping (during boot) it from another machine it comes alive then goes out.
The power on the CPU is on all the time.
please help. (9 Replies)
Discussion started by: santosh1981
9 Replies
2. UNIX for Dummies Questions & Answers
Is it common in the Unix/Linux environment to install compute intensive applications on a Server system and have the client machines download the executables into memory at runtime to run locally? This model seems taxing to the network, and as I understand, has been largely abandoned in the... (1 Reply)
Discussion started by: jonwillog
1 Replies
3. UNIX for Advanced & Expert Users
Hi,
When most of the server applications get installed, they create their own user. I believe this is to not use the "root" account. For example, Apache when installed creates a user called "apache". And the directories which it uses are all owned by this user. This seems to be the... (2 Replies)
Discussion started by: srikanths
2 Replies
4. Shell Programming and Scripting
Hi all
I am running a major script of my application in development for implementing code changes for process improvement in time. The script runs in production once in a month . It takes 8 hours 30 mins in Production server . what surprice me is , when I run the same script in development server... (9 Replies)
Discussion started by: sakthifire
9 Replies
5. Programming
hello all,
I have developed a server application in C for ulinux kernel 2.6.It works very fine; creating a socket, binding it to a port, listening for incoming sockets and accepting them ,all finish without any error.
But there is a problem regarding application crash.After an intentionally... (1 Reply)
Discussion started by: Sedighzadeh
1 Replies
6. Programming
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)
Discussion started by: varun.nagpaal
2 Replies
7. Solaris
Hi there,
We have a Solaris 10 machine which has been up and running for more than 400 days. A strange behaviour happened. The system date defaulted to epoch timestamp. Oracle stopped and application failed causing management to parade. We managed to reset the date. All other servers and... (8 Replies)
Discussion started by: sundar63
8 Replies
8. Red Hat
I encounter the following crash on RHEL 7.0 when I run a multithreaded video rendering application using GLFW and OpenGL. OpenGL version is 2.1 and MESA version is 9.3.0
Following is the back trace of the multi-threaded program I am working on:... (0 Replies)
Discussion started by: anuachin
0 Replies
LEARN ABOUT OSX
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: http://developer.apple.com/tech-
notes/tn2004/tn2123.html
SEE ALSO
launchd(8), launchd.plist(8), launchctl(8), spindump(8), SubmitDiagInfo(8)
Mac OS June 1, 2019 Mac OS