ndo2db Error: queue recv error. in Ubuntu 18.04

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
pepe_carlos
Posts: 43
Joined: Wed Aug 17, 2011 9:09 am
Location: Madrid, Spain

ndo2db Error: queue recv error. in Ubuntu 18.04

Post by pepe_carlos »

Hi

This post is related to https://support.nagios.com/forum/viewto ... =7&t=55496

I found that after upgrade of the operative system to Ubuntu 18.04, the ndo process dump this error to syslog:

Code: Select all

ndo2db: Error: queue recv error.
ndo2db: message repeated 278 times: [ Error: queue recv error.]
The only solution that I found to resolve this is performing login at the console, but if I perform logoff from this console the error happens again.

Left the console with the user logged is a problem for me because means a security fault

My configuration:

ndo2db.cfg

Code: Select all

ndo2db_user=nagios
ndo2db_group=nagios
socket_type=tcp
socket_name=/usr/local/nagios/var/ndo.sock
tcp_port=5668
db_servertype=mysql
db_host=localhost
db_name=ndodb
db_port=3306
db_prefix=nagios_
db_user=user
db_pass=Password
max_timedevents_age=1440
max_systemcommands_age=1440
max_servicechecks_age=1440
max_hostchecks_age=1440
max_eventhandlers_age=1440
ndomod.cfg

Code: Select all

instance_name=Central
output_type=tcpsocket
output=127.0.0.1
tcp_port=5668
output_buffer_items=5000
file_rotation_interval=14400
file_rotation_timeout=60
reconnect_interval=15
reconnect_warning_interval=900
data_processing_options=-1
config_output_options=3
sysctl.conf

Code: Select all

kernel.msgmnb = 131072000
kernel.msgmax = 131072000
kernel.shmmax = 4294967295
kernel.shmall = 268435456

Do you know why this happens?

Thanks!
benjaminsmith
Posts: 5324
Joined: Wed Aug 22, 2018 4:39 pm
Location: saint paul

Re: ndo2db Error: queue recv error. in Ubuntu 18.04

Post by benjaminsmith »

Hello,

1. Please enable debug mode and the restart ndo and then post the log file. Make the following changes in ndo2db.cfg.

Code: Select all

#change
debug_level=0
# to
debug_level=-1
Save and the run the following to re-start ndo, and the post usr/local/nagios/var/ndo2db.debug to the thread. Please log on and off to capture any relevant errors.

Code: Select all

systemctl restart ndo2db.service
2. What is the output of:

Code: Select all

ipcs -q
3. Post the database log as well. Thanks
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.

Be sure to check out our Knowledgebase for helpful articles and solutions!
pepe_carlos
Posts: 43
Joined: Wed Aug 17, 2011 9:09 am
Location: Madrid, Spain

Re: ndo2db Error: queue recv error. in Ubuntu 18.04

Post by pepe_carlos »

Hi,

When the problem happens the ndo2db log (debug mode) stop writing:

Code: Select all

...
[1570519716.166977] [002.0] [pid=19112] DELETE FROM nagios_timedevents WHERE instance_id='2' AND scheduled_time<FROM_UNIXTIME(1570433316)
[1570519716.167454] [002.0] [pid=19112] DELETE FROM nagios_systemcommands WHERE instance_id='2' AND start_time<FROM_UNIXTIME(1570433316)
[1570519716.168021] [002.0] [pid=19112] DELETE FROM nagios_servicechecks WHERE instance_id='2' AND start_time<FROM_UNIXTIME(1570433316)
[1570519716.389004] [002.0] [pid=19112] DELETE FROM nagios_hostchecks WHERE instance_id='2' AND start_time<FROM_UNIXTIME(1570433316)
[1570519716.499540] [002.0] [pid=19112] DELETE FROM nagios_eventhandlers WHERE instance_id='2' AND start_time<FROM_UNIXTIME(1570433316)
[1570519716.500077] [002.0] [pid=19112] INSERT INTO nagios_logentries SET instance_id='2', logentry_time=FROM_UNIXTIME(1570519716), entry_time=FROM_UNIXTIME(1570519716),entry_time_usec='124834', logentry_type='262144', logentry_data='ndomod registered for system command data\'', realtime_data='1',inferred_data_extracted='1'
[1570519716.500375] [002.0] [pid=19112] INSERT INTO nagios_logentries SET instance_id='2', logentry_time=FROM_UNIXTIME(1570519716), entry_time=FROM_UNIXTIME(1570519716), entry_time_usec='124863', logentry_type='262144', logentry_data='ndomod registered for event handler data\'', realtime_data='1', inferred_data_extracted='1'
[1570519880.581827] [002.0] [pid=19111] UPDATE nagios_conninfo SET disconnect_time=NOW(), last_checkin_time=NOW(), data_end_time=FROM_UNIXTIME(0), bytes_processed='0', lines_processed='0', entries_processed='0' WHERE conninfo_id='0'

The ipcs before:

Code: Select all

------ Colas de mensajes -----
key        msqid      propietario perms      bytes utilizados mensajes
0x33010002 201752576  nagios     600        0            0
0x8b010002 201785345  nagios     600        0            0
after:
-

Code: Select all

----- Colas de mensajes -----
key        msqid      propietario perms      bytes utilizados mensajes
0x8b010002 201818112  nagios     600        5783552      5648

The mysql.log (error.log):

Code: Select all

2019-10-08T07:23:03.328758Z 39692 [Note] Aborted connection 39692 to db: 'ndodb' user: 'user' host: 'localhost' (Got an error reading communication packets)
2019-10-08T07:27:42.398819Z 49702 [Note] Aborted connection 49702 to db: 'ndodb' user: 'user' host: 'localhost' (Got an error reading communication packets)
2019-10-08T07:31:20.582970Z 49741 [Note] Aborted connection 49741 to db: 'ndodb' user: 'user' host: 'localhost' (Got an error reading communication packets)
benjaminsmith
Posts: 5324
Joined: Wed Aug 22, 2018 4:39 pm
Location: saint paul

Re: ndo2db Error: queue recv error. in Ubuntu 18.04

Post by benjaminsmith »

Hello @pepe_carlos,

I discussed your issue with another team member, and it's likely there's a libary issue ( when upgrading) and you should try to re-install Nagios Core and then re-compile Ndo.

Also, you have ndo configured to write to a tcp socket, and since the database is local, I would recommend changing this back to the unix socket option.

Finally, make sure the nagios account is not expired.

Code: Select all

chage -l nagios
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.

Be sure to check out our Knowledgebase for helpful articles and solutions!
pepe_carlos
Posts: 43
Joined: Wed Aug 17, 2011 9:09 am
Location: Madrid, Spain

Re: ndo2db Error: queue recv error. in Ubuntu 18.04

Post by pepe_carlos »

Hi,

I recompile and reinstalled nagios and ndoutils, and change tcp to unix socket in ndoutils configuration but the result is the same.

The sugested command chage -l nagios return the next:

Code: Select all

Last password change                                    : mar 20, 2013
Password expires                                        : never
Password inactive                                       : never
Account expires                                         : never
Minimum number of days between password change          : 0
Maximum number of days between password change          : 99999
Number of days of warning before password expires       : 7
Thx

Regards
User avatar
tgriep
Madmin
Posts: 9177
Joined: Thu Oct 30, 2014 9:02 am

Re: ndo2db Error: queue recv error. in Ubuntu 18.04

Post by tgriep »

Maybe it is a kernel limit setting that is getting reset at logout.
Can you post the following files here so we can view them?

Code: Select all

/etc/security/limits.conf
/etc/sysctl.conf
Also, run the following commands as root and post the output here so we can view it.

Code: Select all

ps -ef --cols=300
grep nag /etc/group
When the issue happens, is the ndo2db daemon running on the server?
Be sure to check out our Knowledgebase for helpful articles and solutions!
pepe_carlos
Posts: 43
Joined: Wed Aug 17, 2011 9:09 am
Location: Madrid, Spain

Re: ndo2db Error: queue recv error. in Ubuntu 18.04

Post by pepe_carlos »

Hi,

/etc/security/limits.conf file, has all entries with comment,that is to say, all by default.

/etc/sysctl.conf

Code: Select all

kernel.msgmnb = 131072000
kernel.msgmax = 131072000
kernel.shmmax = 4294967295
kernel.shmall = 268435456
ps -ef --cols=300

Code: Select all

UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  0 oct03 ?        00:06:30 /sbin/init
root         2     0  0 oct03 ?        00:00:00 [kthreadd]
root         4     2  0 oct03 ?        00:00:00 [kworker/0:0H]
root         6     2  0 oct03 ?        00:00:00 [mm_percpu_wq]
root         7     2  0 oct03 ?        00:04:55 [ksoftirqd/0]
root         8     2  0 oct03 ?        00:26:44 [rcu_sched]
root         9     2  0 oct03 ?        00:00:00 [rcu_bh]
root        10     2  0 oct03 ?        00:01:21 [migration/0]
root        11     2  0 oct03 ?        00:00:02 [watchdog/0]
root        12     2  0 oct03 ?        00:00:00 [cpuhp/0]
root        13     2  0 oct03 ?        00:00:00 [cpuhp/1]
root        14     2  0 oct03 ?        00:00:02 [watchdog/1]
root        15     2  0 oct03 ?        00:01:21 [migration/1]
root        16     2  0 oct03 ?        00:04:46 [ksoftirqd/1]
root        18     2  0 oct03 ?        00:00:00 [kworker/1:0H]
root        19     2  0 oct03 ?        00:00:00 [cpuhp/2]
root        20     2  0 oct03 ?        00:00:02 [watchdog/2]
root        21     2  0 oct03 ?        00:01:21 [migration/2]
root        22     2  0 oct03 ?        00:04:59 [ksoftirqd/2]
root        24     2  0 oct03 ?        00:00:00 [kworker/2:0H]
root        25     2  0 oct03 ?        00:00:00 [cpuhp/3]
root        26     2  0 oct03 ?        00:00:02 [watchdog/3]
root        27     2  0 oct03 ?        00:01:20 [migration/3]
root        28     2  0 oct03 ?        00:04:55 [ksoftirqd/3]
root        30     2  0 oct03 ?        00:00:00 [kworker/3:0H]
root        31     2  0 oct03 ?        00:00:00 [cpuhp/4]
root        32     2  0 oct03 ?        00:00:02 [watchdog/4]
root        33     2  0 oct03 ?        00:01:23 [migration/4]
root        34     2  0 oct03 ?        00:04:38 [ksoftirqd/4]
root        36     2  0 oct03 ?        00:00:00 [kworker/4:0H]
root        37     2  0 oct03 ?        00:00:00 [cpuhp/5]
root        38     2  0 oct03 ?        00:00:02 [watchdog/5]
root        39     2  0 oct03 ?        00:01:20 [migration/5]
root        40     2  0 oct03 ?        00:04:50 [ksoftirqd/5]
root        42     2  0 oct03 ?        00:00:00 [kworker/5:0H]
root        43     2  0 oct03 ?        00:00:00 [cpuhp/6]
root        44     2  0 oct03 ?        00:00:02 [watchdog/6]
root        45     2  0 oct03 ?        00:01:22 [migration/6]
root        46     2  0 oct03 ?        00:04:48 [ksoftirqd/6]
root        48     2  0 oct03 ?        00:00:00 [kworker/6:0H]
root        49     2  0 oct03 ?        00:00:00 [cpuhp/7]
root        50     2  0 oct03 ?        00:00:02 [watchdog/7]
root        51     2  0 oct03 ?        00:01:22 [migration/7]
root        52     2  0 oct03 ?        00:04:51 [ksoftirqd/7]
root        54     2  0 oct03 ?        00:00:00 [kworker/7:0H]
root        55     2  0 oct03 ?        00:00:00 [kdevtmpfs]
root        56     2  0 oct03 ?        00:00:00 [netns]
root        57     2  0 oct03 ?        00:00:00 [rcu_tasks_kthre]
root        58     2  0 oct03 ?        00:00:00 [kauditd]
root        62     2  0 oct03 ?        00:00:00 [khungtaskd]
root        63     2  0 oct03 ?        00:00:00 [oom_reaper]
root        64     2  0 oct03 ?        00:00:00 [writeback]
root        65     2  0 oct03 ?        00:00:00 [kcompactd0]
root        66     2  0 oct03 ?        00:00:00 [ksmd]
root        67     2  0 oct03 ?        00:00:00 [khugepaged]
root        68     2  0 oct03 ?        00:00:00 [crypto]
root        69     2  0 oct03 ?        00:00:00 [kintegrityd]
root        70     2  0 oct03 ?        00:00:00 [kblockd]
root        75     2  0 oct03 ?        00:00:00 [ata_sff]
root        76     2  0 oct03 ?        00:00:00 [md]
root        77     2  0 oct03 ?        00:00:00 [edac-poller]
root        78     2  0 oct03 ?        00:00:00 [devfreq_wq]
root        79     2  0 oct03 ?        00:00:00 [watchdogd]
root        83     2  0 oct03 ?        00:00:49 [kswapd0]
root        84     2  0 oct03 ?        00:00:00 [kworker/u17:0]
root        85     2  0 oct03 ?        00:00:00 [ecryptfs-kthrea]
root       127     2  0 oct03 ?        00:00:00 [kthrotld]
root       128     2  0 oct03 ?        00:00:00 [acpi_thermal_pm]
root       130     2  0 oct03 ?        00:00:00 [scsi_eh_0]
root       131     2  0 oct03 ?        00:00:00 [scsi_tmf_0]
root       132     2  0 oct03 ?        00:00:00 [scsi_eh_1]
root       133     2  0 oct03 ?        00:00:00 [scsi_tmf_1]
root       139     2  0 oct03 ?        00:00:00 [ipv6_addrconf]
root       148     2  0 oct03 ?        00:00:00 [kstrp]
root       165     2  0 oct03 ?        00:00:00 [charger_manager]
root       227     2  0 oct03 ?        00:00:00 [mpt_poll_0]
root       228     2  0 oct03 ?        00:00:00 [mpt/0]
root       230     2  0 oct03 ?        00:00:14 [kworker/3:1H]
root       231     2  0 oct03 ?        00:00:00 [scsi_eh_2]
root       232     2  0 oct03 ?        00:00:00 [scsi_tmf_2]
root       239     2  0 oct03 ?        00:00:07 [kworker/0:1H]
root       280     2  0 oct03 ?        00:03:54 [jbd2/sda1-8]
root       281     2  0 oct03 ?        00:00:00 [ext4-rsv-conver]
root       318     1 48 oct03 ?        3-07:17:08 /lib/systemd/systemd-journald
root       332     2  0 oct03 ?        00:00:09 [kworker/6:1H]
root       341     1  0 oct03 ?        00:00:03 /lib/systemd/systemd-udevd
root       361     2  0 oct03 ?        00:00:05 [kworker/1:1H]
root       380     2  0 oct03 ?        00:00:17 [kworker/7:1H]
root       386     2  0 oct03 ?        00:00:00 [ttm_swap]
root       387     2  0 oct03 ?        00:00:00 [irq/16-vmwgfx]
root       446     2  0 oct03 ?        00:00:10 [kworker/2:1H]
root       461     2  0 oct03 ?        00:00:18 [kworker/5:1H]
systemd+   540     1  0 oct03 ?        00:00:04 /lib/systemd/systemd-timesyncd
systemd+   542     1  0 oct03 ?        00:00:09 /lib/systemd/systemd-resolved
root       561     1  0 oct03 ?        00:07:43 /usr/sbin/haveged --Foreground --verbose=1 -w 1024
syslog     573     1 31 oct03 ?        2-03:45:17 /usr/sbin/rsyslogd -n
message+   576     1  0 oct03 ?        00:03:26 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
root       577     2  0 oct03 ?        00:00:16 [kworker/4:1H]
root       590     1  0 oct03 ?        00:00:04 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
root       591     1  0 oct03 ?        00:00:00 /usr/bin/python3 /usr/bin/networkd-dispatcher --run-startup-triggers
root       594     1  0 oct03 ?        00:01:46 /usr/lib/accountsservice/accounts-daemon
daemon     599     1  0 oct03 ?        00:00:00 /usr/sbin/atd -f
root       610     1  0 oct03 ?        00:02:04 /lib/systemd/systemd-logind
root       614     1  0 oct03 ?        00:02:13 /usr/sbin/irqbalance --foreground
root       653     1  0 oct03 ?        00:00:13 /usr/sbin/cron -f
root       741     1  0 oct03 ?        00:01:13 /usr/lib/policykit-1/polkitd --no-debug
root       766     1  0 oct03 ?        00:00:00 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal
root       829     1  0 oct03 ?        00:00:15 /usr/sbin/sshd -D
mysql      835     1  5 oct03 ?        08:40:27 /usr/sbin/mysqld --daemonize --pid-file=/run/mysqld/mysqld.pid
root       885     1  0 oct03 ?        00:01:02 /usr/sbin/apache2 -k start
www-data   889     1  0 oct03 ?        00:00:23 /usr/bin/htcacheclean -d 120 -p /var/cache/apache2/mod_cache_disk -l 300M -n
root      1261     1  0 oct03 ?        00:12:17 /usr/sbin/vmtoolsd
root      1322     1  0 oct03 ?        00:00:00 /usr/lib/vmware-vgauth/VGAuthService -s
whoopsie  1332     1  0 oct03 ?        00:00:00 /usr/bin/whoopsie -f
root      1422     1  0 oct03 ?        00:00:00 /usr/sbin/xinetd -pidfile /run/xinetd.pid -stayalive -inetd_compat -inetd_ipv6
root      1910     1  0 oct08 ?        00:00:00 sudo linuxvnc 1
root      1911  1910  4 oct08 ?        02:07:21 linuxvnc 1
pepecarlos    2079     1  0 oct07 ?        00:00:03 /lib/systemd/systemd --user
pepecarlos    2086  2079  0 oct07 ?        00:00:00 (sd-pam)
root      3753     2  0 10:41 ?        00:00:00 [kworker/1:0]
root      4055     2  0 oct04 ?        00:00:00 [xfsalloc]
root      4056     2  0 oct04 ?        00:00:00 [xfs_mru_cache]
root      4096     2  0 oct04 ?        00:00:00 [jfsIO]
root      4097     2  0 oct04 ?        00:00:00 [jfsCommit]
root      4098     2  0 oct04 ?        00:00:00 [jfsCommit]
root      4099     2  0 oct04 ?        00:00:00 [jfsCommit]
root      4100     2  0 oct04 ?        00:00:00 [jfsCommit]
root      4101     2  0 oct04 ?        00:00:00 [jfsCommit]
root      4102     2  0 oct04 ?        00:00:00 [jfsCommit]
root      4103     2  0 oct04 ?        00:00:00 [jfsCommit]
root      4104     2  0 oct04 ?        00:00:00 [jfsCommit]
root      4105     2  0 oct04 ?        00:00:00 [jfsSync]
root      4366     2  0 10:56 ?        00:00:00 [kworker/6:1]
www-data  4712   885  0 10:54 ?        00:00:00 /usr/sbin/apache2 -k start
root      5029     2  0 10:47 ?        00:00:00 [kworker/7:1]
root      6074     2  0 10:54 ?        00:00:00 [kworker/7:2]
www-data  7473   885  0 10:48 ?        00:00:00 /usr/sbin/apache2 -k start
root      8607     2  0 10:48 ?        00:00:00 [kworker/u16:1]
pepecarlos   10232 14827  0 10:56 pts/2    00:00:00 ps -ef --cols=400
root     10753     2  0 09:57 ?        00:00:01 [kworker/1:2]
root     10854     2  0 10:09 ?        00:00:02 [kworker/u16:0]
nagios   11253     1  0 oct09 ?        00:00:00 /lib/systemd/systemd --user
nagios   11254 11253  0 oct09 ?        00:00:00 (sd-pam)
nagios   11267 29972  0 oct09 tty1     00:00:00 -bash
root     11694     2  0 10:27 ?        00:00:00 [kworker/0:2]
root     12581     2  0 08:40 ?        00:00:03 [kworker/7:0]
root     12757     2  0 08:40 ?        00:00:04 [kworker/6:2]
www-data 12888   885  0 10:51 ?        00:00:00 /usr/sbin/apache2 -k start
www-data 12889   885  0 10:51 ?        00:00:00 /usr/sbin/apache2 -k start
root     13094     1  0 oct07 tty2     00:00:00 /sbin/agetty -o -p -- \u --noclear tty2 linux
root     14477   829  0 10:42 ?        00:00:00 sshd: pepecarlos [priv]
pepecarlos   14800 14477  0 10:42 ?        00:00:00 sshd: pepecarlos@pts/2
pepecarlos   14827 14800  0 10:42 pts/2    00:00:00 -bash
nagios   14961     1  0 oct09 ?        00:00:00 /usr/local/nagios/bin/ndo2db -c /usr/local/nagios/etc/ndo2db.cfg
nagios   14999     1  1 oct09 ?        00:18:57 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
nagios   15001 14999  0 oct09 ?        00:01:49 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios   15002 14999  0 oct09 ?        00:01:49 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios   15003 14999  0 oct09 ?        00:01:47 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios   15004 14999  0 oct09 ?        00:01:49 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios   15005 14999  0 oct09 ?        00:01:49 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios   15006 14999  0 oct09 ?        00:01:49 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios   15007 14999  0 oct09 ?        00:01:50 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios   15008 14999  0 oct09 ?        00:01:49 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios   15009 14999  0 oct09 ?        00:01:47 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios   15010 14999  0 oct09 ?        00:01:47 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios   15011 14999  0 oct09 ?        00:01:49 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios   15012 14999  0 oct09 ?        00:01:48 /usr/local/nagios/bin/nagios --worker /usr/local/nagios/var/rw/nagios.qh
nagios   15013 14961  0 oct09 ?        00:04:51 /usr/local/nagios/bin/ndo2db -c /usr/local/nagios/etc/ndo2db.cfg
nagios   15014 15013  3 oct09 ?        00:35:59 /usr/local/nagios/bin/ndo2db -c /usr/local/nagios/etc/ndo2db.cfg
nagios   15015 14999  0 oct09 ?        00:00:06 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
root     16095     2  0 10:42 ?        00:00:00 [kworker/6:0]
root     17692     2  0 09:04 ?        00:00:03 [kworker/3:0]
root     19122     2  0 10:55 ?        00:00:00 [kworker/2:1]
www-data 20008   885  0 10:49 ?        00:00:00 /usr/sbin/apache2 -k start
root     20326     1  0 oct03 ?        00:00:35 sendmail: MTA: accepting connections
www-data 20966   885  0 10:37 ?        00:00:00 /usr/sbin/apache2 -k start
root     21134     2  0 10:40 ?        00:00:00 [kworker/0:1]
root     21721     2  0 09:14 ?        00:00:02 [kworker/2:2]
www-data 22367   885  0 10:55 ?        00:00:00 /usr/sbin/apache2 -k start
root     25216     2  0 07:33 ?        00:00:05 [kworker/4:2]
root     25466     2  0 10:46 ?        00:00:00 [kworker/2:0]
root     26005     2  0 10:46 ?        00:00:00 [kworker/5:2]
www-data 26662   885  0 10:55 ?        00:00:00 /usr/sbin/apache2 -k start
www-data 26680   885  0 10:52 ?        00:00:00 /usr/sbin/apache2 -k start
root     26970     2  0 10:52 ?        00:00:00 [kworker/5:1]
root     27607     2  0 10:35 ?        00:00:00 [kworker/3:2]
nagios   27831 27829  0 10:55 ?        00:00:00 tail -1
root     29801     2  0 10:50 ?        00:00:00 [kworker/4:1]
root     29972     1  0 oct09 tty1     00:00:00 /bin/login -p --
root     30441     2  0 09:59 ?        00:00:02 [kworker/5:0]
root     30875     2  0 09:44 ?        00:00:02 [kworker/u16:3]
root     30902     2  0 10:53 ?        00:00:00 [kworker/3:1]
www-data 31108   885  0 10:53 ?        00:00:00 /usr/sbin/apache2 -k start
grep nag /etc/group

Code: Select all

adm:x:4:nagios,syslog
sudo:x:27:nagios
nagios:x:1001:nagios,www-data,oracle,adm
nagcmd:x:1002:nagios,www-data
User avatar
tgriep
Madmin
Posts: 9177
Joined: Thu Oct 30, 2014 9:02 am

Re: ndo2db Error: queue recv error. in Ubuntu 18.04

Post by tgriep »

Add this line

Code: Select all

kernel.msgmni = 512000
to the /etc/sysctl.conf file

Add these entries

Code: Select all

* hard nofile 10000
* soft nofile 10000
root hard nofile 10000
root soft nofile 10000
* hard stack 102400
* hard stack 102400
to the /etc/security/limits.conf file.

Reboot the server for the changes to take effect and see if the Kernel Message queue is processed while not logged in.
If not, look in the /var/log/syslog for any errors that could hold a clue on why the ndo2db processes is not running which I feel is the issue.
Be sure to check out our Knowledgebase for helpful articles and solutions!
pepe_carlos
Posts: 43
Joined: Wed Aug 17, 2011 9:09 am
Location: Madrid, Spain

Re: ndo2db Error: queue recv error. in Ubuntu 18.04

Post by pepe_carlos »

Hi,

The error persists with the suggested changes, The curious thing is that it only works without problems when the nagios user is logged into the system console.
User avatar
tgriep
Madmin
Posts: 9177
Joined: Thu Oct 30, 2014 9:02 am

Re: ndo2db Error: queue recv error. in Ubuntu 18.04

Post by tgriep »

I would suspect it is a user account limitation or a entry in the /etc/sudoers file that is requiring a tty to be present for the nagios user.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked