Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.98 minutes in June 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

Failed to register iobroker in Nagios – How to fix this

by | Apr 7, 2021

Wondering how to fix ‘Failed to register iobroker’ in Nagios. We can help you.

Often Nagios users come across this error. Recently one of our customers reported that there was some issue with the Nagios check, as it didn’t exit properly. Also, found ‘Failed to register iobroker for stdout’ in the logs.

Here at Bobcares, we get requests from our customers to fix similar issues as a part of our Server Management Services.

Today let’s see how our Support Engineers fix this issue for our clients.

What causes ‘Failed to register iobroker’

Before going into the solution, we will see what causes this issue.

Following is the configuration for that particular check is

define service {
service_description fan
check_command check_cisco!snmpcommunitystring!bob@12
host_name SW-SRA-03
check_period 24x7 1/min 1/w
notification_period 24x7 1/min 1/w
contact_groups +admins,EuroFiber WAN
action_url /bob4nagios/graph?host=$HOSTNAME$&srv=$SERVICEDESC$
max_check_attempts 10
check_interval 10
retry_interval 1
first_notification_delay 10
notification_interval 9999
notification_options w,u,c,r,f,s
active_checks_enabled 1
passive_checks_enabled 1
notifications_enabled 1
check_freshness 1
freshness_threshold 3600
event_handler_enabled 0

Following is the result when the above configuration check exits properly:

Current Status: OK (for 1d 12h 9m 7s)
Status Information: Fans: OK - 2 Fans are running all good
Performance Data: total=2 err=0
Current Attempt: 1/10 (HARD state)
Last Check Time: 01-04-2021 09:28:18
Check Type: ACTIVE
Check Latency / Duration: 0,000 / 0,000 seconds
Next Scheduled Check: 01-04-2021 09:38:18

However, sometimes the check may end abruptly, showing some strange Core Worker errors in the Nagios.log.

We can see the following in the log.

Failed to register iobroker for stdout
Failed to register iobroker for stderr

this can happen when the core worker is trying to get hold of stdout and stderr, but that fails. However is still launches the check, even though it will not be able to catch the output. At times, many different checks can fail at that time.

The following errors can be seen in the nagios.log file:

[1504231962] wproc: Core Worker 68003: Failed to register iobroker for stdout
[1504231962] wproc: Core Worker 68003: Failed to register iobroker for stderr
[1504231962] Warning: Check of host 'SOME_HOST' did not exit properly!
[1504231962] HOST ALERT: SOME_HOST;UNREACHABLE;SOFT;1;(Host check did not exit properly)

 This problem occurs when custom operating system limits restrict the max number of processes that it can execute.

Generally, custom limits are defined in the /etc/security/limits.conf file.

Following is an example of limits in an openSUSE Leap 42.x:

# harden against fork-bombs
* hard nproc 1700
* soft nproc 1200
root hard nproc 3000
root soft nproc 1850

How to fix this issue

We can fix this by increasing the hard and soft values as given n the following example:

># harden against fork-bombs
* hard nproc 10000
* soft nproc 10000
root hard nproc 10000
root soft nproc 10000

Once the changes are made, we need to reboot the system to ensure the limits are applied.

[Need assistance? We are happy to help you!]


In short, we saw how our Support Engineers fix this ‘Failed to register iobroker’ issue in Nagios for our customers.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.