Nagios Support Forum

Blank host and service entry is showing as pending state on "Service Status" Page. Could you please guide how to delete Blank entry on our Service Status Page.

Some how null service object got created, and I don't find any option to delete this entry. Is there any way I can delete this from backend.

Nagios XI version : 5.7.2
curl -XGET "http://XXXXXXXX.jc.jefco.com/nagiosxi/a ... X&pretty=1"
{
"host_name": null,
"service_description": null,
"display_name": null,
"host_object_id": null,
"host_address": null,
"host_alias": null,
"icon_image": null,
"icon_image_alt": null,
"notes": null,
"notes_url": null,
"action_url": null,
"servicestatus_id": "131787",
"instance_id": "1",
"service_object_id": "0",
"status_update_time": "1969-12-31 19:00:00",
"output": "0",
"long_output": "0",
"perfdata": "0",
"current_state": "0",
"has_been_checked": "0",
"should_be_scheduled": "0",
"current_check_attempt": "0",
"max_check_attempts": "0",
"last_check": "1969-12-31 19:00:00",
"next_check": "1969-12-31 19:00:00",
"check_type": "0",
"check_options": "0",
"last_state_change": "1969-12-31 19:00:00",
"last_hard_state_change": "1969-12-31 19:00:00",
"last_hard_state": "0",
"last_time_ok": "1969-12-31 19:00:00",
"last_time_warning": "1969-12-31 19:00:00",
"last_time_unknown": "1969-12-31 19:00:00",
"last_time_critical": "1969-12-31 19:00:00",
"state_type": "0",
"last_notification": "1969-12-31 19:00:00",
"next_notification": "1969-12-31 19:00:00",
"no_more_notifications": "0",
"notifications_enabled": "0",
"problem_has_been_acknowledged": "0",
"acknowledgement_type": "0",
"current_notification_number": "0",
"passive_checks_enabled": "0",
"active_checks_enabled": "0",
"event_handler_enabled": "0",
"flap_detection_enabled": "0",
"is_flapping": "0",
"percent_state_change": "0",
"latency": "0",
"execution_time": "0",
"scheduled_downtime_depth": "0",
"failure_prediction_enabled": "0",
"process_performance_data": "0",
"obsess_over_service": "0",
"modified_service_attributes": "0",
"event_handler": "0",
"check_command": "0",
"normal_check_interval": "0",
"retry_check_interval": "0",
"check_timeperiod_object_id": "0"
}

I believe this could be a possible bug related to the NDO upgrade in 5.7.2, this has since been resolved, I would highly recommend upgrading to 5.8.1