Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CHECK_NRPE: Invalid packet type received from server. #115

Closed
cvanaxel opened this issue Feb 25, 2015 · 3 comments
Closed

CHECK_NRPE: Invalid packet type received from server. #115

cvanaxel opened this issue Feb 25, 2015 · 3 comments
Labels
Milestone

Comments

@cvanaxel
Copy link

I saw in one of your post that you fixed this bug.

Im running the latest version and I get this issue.

Nagios:
./check_nrpe -n -H 1XX.X.X.X -c check_citrix_sessies

script(check_sessies.ps1):
$SPAdmin = "DOMAIN\USER"
$Password = Get-Content C:\Temp\securestring.txt | convertto-securestring
$Credential = new-object -typename System.Management.Automation.PSCredential -argumentlist $SPAdmin, $Password

Add-PSSnapin Citrix.*
$Active = (Get-BrokerSession -MaxRecordCount 1100 -SessionState Active).count
$Disconnected = (Get-BrokerSession -MaxRecordCount 1100 -SessionState Disconnected).count
echo "Total active sessions: $Active & disconnected sessions: $Disconnected"
exit 0

nsclient.ini:
[/settings/external scripts/scripts]
check_citrix_sessies = cmd /c echo scripts\check_sessies.ps1; exit ($lastexitcode) | powershell.exe -command -

[/settings/external scripts]
allow arguments = true
allow nasty characters = true

@mickem
Copy link
Owner

mickem commented Feb 25, 2015

Define latest version (please use version numbers)...

Please provide output of check_nrpe as well as debug log from NSClient++

@cvanaxel
Copy link
Author

Version: NSCP-0.4.3.88-x64

There is no debug log from nsclient++

The only bug i get is: CHECK_NRPE: Invalid packet type received from server.

@mickem mickem added the invalid label Feb 25, 2015
@mickem mickem added this to the 0.4.3 milestone Feb 25, 2015
@mickem
Copy link
Owner

mickem commented Feb 25, 2015

There we have it, the comment about me fixing it in #83 read: "0.4.3.102 should fix this issue, please reopen if issue still persists..." so if you are on 0.4.3.88 you are not using the latest (and fixed) version...

Pleas reopen if you still have this issue with a more recent version.

@mickem mickem closed this as completed Feb 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants