Search found 5 matches
- Thu Oct 31, 2019 9:42 am
- Forum: Nagios XI
- Topic: System call sent warnings to stderr: pst3:
- Replies: 10
- Views: 785
Re: System call sent warnings to stderr: pst3:
Tried all the given solutions, still getting same error.
- Tue Oct 22, 2019 3:04 pm
- Forum: Nagios XI
- Topic: System call sent warnings to stderr: pst3:
- Replies: 10
- Views: 785
Re: System call sent warnings to stderr: pst3:
yes, all other checks like check_disk, load, memory, nfs stale woking fine except check_clearcase.
The nrpe package and plugins are pushed to the server through puppet.
The nrpe package and plugins are pushed to the server through puppet.
- Tue Oct 22, 2019 8:34 am
- Forum: Nagios XI
- Topic: System call sent warnings to stderr: pst3:
- Replies: 10
- Views: 785
Re: System call sent warnings to stderr: pst3:
I can see the same error when executed with root too. Same is the result after changing pst3's permission.
- Mon Oct 21, 2019 2:59 pm
- Forum: Nagios XI
- Topic: System call sent warnings to stderr: pst3:
- Replies: 10
- Views: 785
Re: System call sent warnings to stderr: pst3:
Here is the check command output,
[nagios@usa030043 ~]$ /usr/local/nagios/libexec/check_nrpe -2 -H 13.*.*.* -c check_clearcase -t 60
System call sent warnings to stderr: pst3: This program can only be run by the root user!
And This is happening only with solaris 10 T5-2 zone servers.
[nagios@usa030043 ~]$ /usr/local/nagios/libexec/check_nrpe -2 -H 13.*.*.* -c check_clearcase -t 60
System call sent warnings to stderr: pst3: This program can only be run by the root user!
And This is happening only with solaris 10 T5-2 zone servers.
- Thu Oct 17, 2019 2:04 pm
- Forum: Nagios XI
- Topic: System call sent warnings to stderr: pst3:
- Replies: 10
- Views: 785
System call sent warnings to stderr: pst3:
We are receiving System call sent warnings to stderr: pst3: This program can only be run by the root user! error on Solaris 10 sparc machine while testing the plugin for checking ClearCase process.
We have changed the pst3's ownership to root, still receiving the same error.
We have changed the pst3's ownership to root, still receiving the same error.