Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am monitoring one windows client from my linux server ,it is showing an error like this :
What does this mean ?
It means either that you've got a mistake in your Nagios client configuration, or the drive is getting full.
If you tried to Google for this, you'd have found lots in the Nagios forums/archives. Usually related to a misconfiguration, or the attempt by the Windows client to get drive states from a non-local device.
Yes bro F drive exist on that machine and its free 100GB out of 120 GB
Ok...what did you set the alert status to be? And as I asked, is this a local drive??
Code 139 indicates a segfault. So again, you've either got a misconfiguration, a non-local drive, or the device has hit the alert point, and is alerting you.
Check your client configuration file on the Windows machine. This kind of errors happens, just like TB0ne pointed out, when you have an error in your configuration file. See if your Nagios server is allowed to query the Windows machine, restart the service on Windows and check again.
Ok...what did you set the alert status to be? And as I asked, is this a local drive??
Code 139 indicates a segfault. So again, you've either got a misconfiguration, a non-local drive, or the device has hit the alert point, and is alerting you.
I got your point ,this is a local drive but a misconfiguration was leading to that point. I put the wrong drive letter in the configuration.
Thank you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
