Question

VEEAM - job-status - CHECK_NRPE: Receive header underflow - only 0 bytes received (4 expected).

  • 4 September 2023
  • 9 replies
  • 577 views
S
Userlevel 1
Badge +8

Hello everyone,

Does anyone have an idea how to resolve this error:

CHECK_NRPE: Receive header underflow - only 0 bytes received (4 expected).

 

Command:

/usr/lib64/nagios/plugins/check_centreon_nrpe3 -H 10.192.30.9 -p 8084 -t 60 -u -2 -P 8192 -c check_centreon_plugins -a 'apps::backup::veeam::local::plugin' 'job-status'  ' --filter-name="" --filter-start-time="" --filter-end-time="86400" --filter-counters="" --ok-status="" --warning-status="" --critical-status="%{is_running} == 0 and not %{status} =~ /Success/i" --warning-long="" --critical-long="" --verbose'

 

Other commands are ok.

 

 

NSClient++ version number

/usr/lib64/nagios/plugins/check_centreon_nrpe3 -H 10.192.30.9 -p 8084 -t 60 -u -2 -P 8192

I (0.5.2.41 2018-04-26) seem to be doing fine...

If there's no solution to your problem, create your own.

9 replies

F
Badge +1

Hello, i had this trouble to.

to resolve this, i had to change the centreon_plugins.exe.

i took an old version then without almost changing the ini file, it worked

try the version 20210427 from this build github.com/centreon/centreon-nsclient-build/releases/tag/20210518194507

S
Userlevel 1
Badge +8

Bonjour,

Après des tests croisés, je m'aperçois que depuis la version Centreon Plugins release 2022050400000. Les tests avec le plugin Veeam NSClient++ NRPE renvoi très souvent des erreurs "CHECK_NRPE: Receive header underflow - only 0 bytes received (4 expected).". Le problème c'est que les version en deça ne contiennent pas le mode Repositories. C’est un problème.

If there's no solution to your problem, create your own.
F
Badge +1

Est-ce obsolète pour les développeurs ? ou un oublie ?

F
Badge

UP. j’ai le même souci 

C
Badge +4

UP same trouble here

C
Userlevel 1
Badge +4

same trouble for me.

 

ldubrunfaut
Rank
Userlevel 2
Badge +2

Hello,

Thank you all for your patience, we have taken note of the problem and we will implement the strategy to address the issue in the best delay. Do not hesitate if you have any additional information or element to bring them to our attention.

omercier
Rank
Userlevel 4
Badge +12

Hi all,

If the issue comes from the plugin, then maybe we can get more information by runnin it directly on the Windows server.

Can you run this command?

"C:\Program Files\Centreon NSClient++\scripts\centreon\centreon_plugins.exe" --plugin=apps::backup::veeam::local::plugin --mode=job-status  --filter-name="" --filter-start-time="" --filter-end-time="86400" --filter-counters="" --ok-status="" --warning-status="" --critical-status="%{is_running} == 0 and not %{status} =~ /Success/i" --warning-long="" --critical-long="" --verbose --debug

Feel free to run it several times and send the output here. It may help us a lot in the troubleshooting process.

I love it when a plan comes together!
S
Userlevel 1
Badge +8

Bonjour,

voici ce que me renvoi la commande en local.

PS C:\Program Files\Centreon NSClient++\scripts\centreon> .\centreon_plugins.exe --plugin apps::backup::veeam::local::plugin --mode=job-status --filter-end-time="86400" --critical-status="%{is_running} == 0 and not %{status} =~ /Success/i" --verbose --debug
UNKNOWN: Cannot decode json response: malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "#< CLIXML\n<Objs Ver...") at C:\Windows\temp\par-41646d696e697374726174657572\cache-041a39e2bf0cf2311fc6f64e8ebbbc6239255a0e\inc\lib/apps/backup/veeam/local/mode/jobstatus.pm line 182.

 

If there's no solution to your problem, create your own.

Reply


Terms & ConditionsCookie settings