Page 1 of 2
error after upgrade
Posted: Wed Nov 16, 2016 2:35 pm
by benhank
I have been getting the following error after upgrading to versio 532
Code: Select all
wproc: GLOBAL SERVICE EVENTHANDLER job 479 from worker Core Worker 17948 is a non-check helper but exited with return code 255
from the google searches I have done it seems that this was a bug that was patched 2 years ago. Wieeeerrrddd..
Re: error after upgrade
Posted: Wed Nov 16, 2016 2:48 pm
by dwhitfield
Could you post your nagios.cfg? It's possible you need to enable macros.
Also, you might as well go ahead and PM me your profile from Admin > System Config > System Profile and click the Download Profile button in the top right corner.
Please update this thread once you have PMed the file. Thanks!
UPDATE: profile received and shared with techs
Re: error after upgrade
Posted: Wed Nov 16, 2016 2:57 pm
by benhank
sent
Re: error after upgrade
Posted: Wed Nov 16, 2016 3:07 pm
by dwhitfield
What issue are you actually seeing? I ask because of a couple of things I see in your nagios.cfg, which I provide below for others (there's nothing in this file that needs to be scrubbed, unlike the profile):
Code: Select all
# MODIFIED
admin_email=root@localhost
admin_pager=root@localhost
translate_passive_host_checks=1
log_event_handlers=0
use_large_installation_tweaks=1
enable_environment_macros=0
# NDOUtils module
broker_module=/usr/local/nagios/bin/ndomod.o config_file=/usr/local/nagios/etc/ndomod.cfg
# PNP settings - bulk mode with NCPD
process_performance_data=1
# service performance data
service_perfdata_file=/usr/local/pnp4nagios/var/service-perfdata
service_perfdata_file_template=DATATYPE::SERVICEPERFDATA\tTIMET::$TIMET$\tHOSTNAME::$HOSTNAME$\tSERVICEDESC::$SERVICEDESC$\tSERVICEPERFDATA::$SERVICEPERFDATA$\tSERVICECHECKCOMMAND::$SERVICECHECKCOMMAND$\tHOSTSTATE::$HOSTSTATE$\tHOSTSTATETYPE::$HOSTSTATETYPE$\tSERVICESTATE::$SERVICESTATE$\tSERVICESTATETYPE::$SERVICESTATETYPE$\tSERVICEOUTPUT::$SERVICEOUTPUT$
service_perfdata_file_mode=a
service_perfdata_file_processing_interval=15
service_perfdata_file_processing_command=process-service-perfdata-file
# host performance data
host_perfdata_file=/usr/local/pnp4nagios/var/host-perfdata
host_perfdata_file_template=DATATYPE::HOSTPERFDATA\tTIMET::$TIMET$\tHOSTNAME::$HOSTNAME$\tHOSTPERFDATA::$HOSTPERFDATA$\tHOSTCHECKCOMMAND::$HOSTCHECKCOMMAND$\tHOSTSTATE::$HOSTSTATE$\tHOSTSTATETYPE::$HOSTSTATETYPE$\tHOSTOUTPUT::$HOSTOUTPUT$
host_perfdata_file_mode=a
host_perfdata_file_processing_interval=15
host_perfdata_file_processing_command=process-host-perfdata-file
# OBJECTS - UNMODIFIED
#cfg_file=/usr/local/nagios/etc/objects/commands.cfg
#cfg_file=/usr/local/nagios/etc/objects/contacts.cfg
#cfg_file=/usr/local/nagios/etc/objects/localhost.cfg
#cfg_file=/usr/local/nagios/etc/objects/templates.cfg
#cfg_file=/usr/local/nagios/etc/objects/timeperiods.cfg
# STATIC OBJECT DEFINITIONS (THESE DON'T GET EXPORTED/IMPORTED BY NAGIOSQL)
cfg_dir=/usr/local/nagios/etc/static
# OBJECTS EXPORTED FROM NAGIOSQL
cfg_file=/usr/local/nagios/etc/contacttemplates.cfg
cfg_file=/usr/local/nagios/etc/contactgroups.cfg
cfg_file=/usr/local/nagios/etc/contacts.cfg
cfg_file=/usr/local/nagios/etc/timeperiods.cfg
cfg_file=/usr/local/nagios/etc/commands.cfg
cfg_file=/usr/local/nagios/etc/hostgroups.cfg
cfg_file=/usr/local/nagios/etc/servicegroups.cfg
cfg_file=/usr/local/nagios/etc/hosttemplates.cfg
cfg_file=/usr/local/nagios/etc/servicetemplates.cfg
cfg_file=/usr/local/nagios/etc/servicedependencies.cfg
cfg_file=/usr/local/nagios/etc/serviceescalations.cfg
cfg_file=/usr/local/nagios/etc/hostdependencies.cfg
cfg_file=/usr/local/nagios/etc/hostescalations.cfg
cfg_file=/usr/local/nagios/etc/hostextinfo.cfg
cfg_file=/usr/local/nagios/etc/serviceextinfo.cfg
cfg_dir=/usr/local/nagios/etc/hosts
cfg_dir=/usr/local/nagios/etc/services
# GLOBAL EVENT HANDLERS
global_host_event_handler=xi_host_event_handler
global_service_event_handler=xi_service_event_handler
# UNMODIFIED
accept_passive_host_checks=1
accept_passive_service_checks=1
additional_freshness_latency=15
auto_reschedule_checks=1
auto_rescheduling_interval=30
auto_rescheduling_window=45
bare_update_check=0
cached_host_check_horizon=15
cached_service_check_horizon=15
check_external_commands=1
check_for_orphaned_hosts=1
check_for_orphaned_services=1
check_for_updates=1
check_host_freshness=0
check_result_path=/usr/local/nagios/var/spool/checkresults
check_result_reaper_frequency=10
check_service_freshness=1
command_file=/usr/local/nagios/var/rw/nagios.cmd
daemon_dumps_core=0
date_format=us
debug_file=/usr/local/nagios/var/nagios.debug
debug_level=0
debug_verbosity=1
enable_event_handlers=1
enable_flap_detection=1
enable_notifications=1
enable_predictive_host_dependency_checks=1
enable_predictive_service_dependency_checks=1
event_broker_options=-1
event_handler_timeout=30
execute_host_checks=1
execute_service_checks=1
high_host_flap_threshold=20.0
high_service_flap_threshold=20.0
host_check_timeout=30
host_freshness_check_interval=60
host_inter_check_delay_method=s
illegal_macro_output_chars=`~$&|'"<>
illegal_object_name_chars=`~!$%^&*|'"<>?,()=
interval_length=60
lock_file=/usr/local/nagios/var/nagios.lock
log_archive_path=/usr/local/nagios/var/archives
log_external_commands=0
log_file=/usr/local/nagios/var/nagios.log
log_host_retries=1
log_initial_states=0
log_notifications=1
log_passive_checks=0
log_rotation_method=d
log_service_retries=1
low_host_flap_threshold=5.0
low_service_flap_threshold=5.0
max_check_result_file_age=3600
max_check_result_reaper_time=30
max_concurrent_checks=0
max_debug_file_size=1000000
max_host_check_spread=30
max_service_check_spread=30
nagios_group=nagios
nagios_user=nagios
notification_timeout=30
object_cache_file=/usr/local/nagios/var/objects.cache
obsess_over_hosts=0
obsess_over_services=0
ocsp_timeout=5
passive_host_checks_are_soft=0
perfdata_timeout=5
precached_object_file=/usr/local/nagios/var/objects.precache
resource_file=/usr/local/nagios/etc/resource.cfg
retained_contact_host_attribute_mask=0
retained_contact_service_attribute_mask=0
retained_host_attribute_mask=0
retained_process_host_attribute_mask=0
retained_process_service_attribute_mask=0
retained_service_attribute_mask=0
retain_state_information=1
retention_update_interval=60
service_check_timeout=60
service_freshness_check_interval=60
service_inter_check_delay_method=s
service_interleave_factor=s
soft_state_dependencies=0
state_retention_file=/usr/local/nagios/var/retention.dat
status_file=/usr/local/nagios/var/status.dat
status_update_interval=10
temp_file=/usr/local/nagios/var/nagios.tmp
temp_path=/tmp
use_aggressive_host_checking=0
# enable regular expression matching 18-may-2015 -pjk
use_regexp_matching=1
use_retained_program_state=1
use_retained_scheduling_info=0
use_syslog=1
use_true_regexp_matching=0
# disable embedded perl 3-15-2016 -pjk
#enable_embedded_perl=0
#use_embedded_perl_implicitly=0
Re: error after upgrade
Posted: Wed Nov 16, 2016 3:25 pm
by benhank
after the upgrade, we noticed that we could not enable checks via admin/Monitoring Engine Status/
When I clicked 'active checks' or anything else, nothing happened. I resolved the issue by doing a restore from a backup, enabling all checks and then redid the upgrade.
Errors like the one in the OP were pointed out to me, which werent happening prior to the upgrade.
According to my log server, I have 1050 and counting entries for the error in the OP.
We are in the process of migrating from our "old" nagios environment to the "new".
The Server with the issue is in the "New" environment, and I am making sure that everything is running smooth before we migrate our users.
Re: error after upgrade
Posted: Wed Nov 16, 2016 3:31 pm
by dwhitfield
benhank wrote:I resolved the issue by doing a restore from a backup, enabling all checks and then redid the upgrade.
So, as of the moment, you aren't seeing any actual issues, just the error, correct?
Are you using anything in
use_large_installation_tweak? This turns off some env variables, so if you aren't specifically using that, you might try setting that to 0.
Again, unless you have a specific reason for doing so, you should set
enable_environment_macros=1. Please make those changes if you can, or report back why you can't. If you can make those changes, please wait and see if they resolve the error.
Thanks!
Re: error after upgrade
Posted: Wed Nov 16, 2016 3:37 pm
by benhank
agreed no other issues aside from the error, "I will do what you suggested and let you know . thanks man!
Re: error after upgrade
Posted: Wed Nov 16, 2016 3:40 pm
by dwhitfield
Fantastic. There's no rush on our end, but we do have 5.3.3 scheduled to come out pretty soon, so if this ends up being a bug, it'd be great to squash it in 5.3.3. If not, we can always squash it in 5.3.4, especially since it sounds like it might be a false positive.
Re: error after upgrade
Posted: Wed Nov 16, 2016 4:57 pm
by benhank
i cant disable large environment tweaks, because we have a large environment lol, but i enabled macros and the problem persists:
Capture.PNG
Re: error after upgrade
Posted: Wed Nov 16, 2016 5:44 pm
by avandemore
Usually such an error is due to the plugin failing due to an incorrect command or service definition. Your logs detail a variety of plugin issues and xi_service_event_handler in particular seems to be broken. It also is non-standard compared to a default XI install.