Navigation Menu

Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #2221] reload problem #831

Closed
icinga-migration opened this issue Dec 23, 2011 · 8 comments
Closed

[dev.icinga.com #2221] reload problem #831

icinga-migration opened this issue Dec 23, 2011 · 8 comments
Labels

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/2221

Created by rudolfasd on 2011-12-23 03:01:05 +00:00

Assignee: (none)
Status: Closed (closed on 2012-05-05 12:05:17 +00:00)
Target Version: (none)
Last Update: 2012-05-05 12:05:17 +00:00 (in Redmine)


Sorry for my bad English.
icinga don't understand kill -HUP signal, so init script reload command will not work properly.

[root@sl03800008006 init.d]# service icinga status
icinga (pid 5395) is running...
[root@sl03800008006 init.d]# service icinga reload
Running configuration check...OK
Reloading icinga configuration...done
[root@sl03800008006 init.d]# service icinga status
icinga is not running
[root@sl03800008006 init.d]# cat /var/icinga/icinga.pid
5395
[root@sl03800008006 init.d]#

Attachments

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2012-01-27 20:43:21 +00:00

  • Status changed from New to Feedback

i don't understand the issue - what happens on the reload? tried a manual kill -HUP then?

what does the log tell? any debug logs which might point to a possible segfault then?

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2012-01-27 20:43:36 +00:00

and which versions are used, which addons are installed, etc

@icinga-migration
Copy link
Author

Updated by rudolfasd on 2012-02-01 05:49:40 +00:00

Icinga version 1.6.1. Installed icinga-web 1.6.0 and icinga-reports 1.6.0.

In icinga.cfg debug_level=-1

I tried a manual kill -HUP :

[root@sl03800008006 icinga]# service icinga status
icinga (pid 19456) is running...
[root@sl03800008006 icinga]# kill -HUP 19456
[root@sl03800008006 icinga]# service icinga status
icinga is not running
[root@sl03800008006 icinga]# tail /var/log/icinga/icinga.log
[1328074135] Warning: Host '00-com.C6' has no services associated with it!
[1328074135] Warning: Host '00-com.C6' has no default contacts or contactgroups defined!
[1328074135] Warning: Host '00.-Teledayn' has no services associated with it!
[1328074135] Warning: Host '00.-Teledayn' has no default contacts or contactgroups defined!
[1328074135] Finished daemonizing... (New PID=19456)
[1328074138] Event loop started...
[1328074154] Caught SIGHUP, restarting...
[1328074154] idomod: Shutdown complete.
[1328074154] Event broker module '/usr/bin/idomod.o' deinitialized successfully.
[1328074154] Caught SIGSEGV, shutting down...
[root@sl03800008006 icinga]# service icinga start
Running configuration check...OK
Icinga PID 19456 not running. Removing lockfile.
Starting icinga: Starting icinga done.
[root@sl03800008006 icinga]#

P.S This problem makes impossible icinga reload through nagiosql.

@icinga-migration
Copy link
Author

Updated by rudolfasd on 2012-02-01 06:07:56 +00:00

  • File added icinga.debug

debug file

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2012-02-01 09:51:11 +00:00

os?
system?
selinux?
how is icinga installed - git / tarball / packages?

[1328074154.128137] [064.0] [pid=19456] Attempting to unload module '/usr/bin/idomod.o': flags=1, reason=2
[1328074154.128533] [064.0] [pid=19456] Module '/usr/bin/idomod.o' unloaded successfully.
[1328074154.128671] [064.0] [pid=19456] Attempting to unload module '/usr/bin/idomod.o': flags=1, reason=2

and naturally, attach your configs without whitespaces and #.

especially, explain to me, why you have 2 idomod neb modules loaded (icinga.cfg:broker_module versus etc/modules/idoutils.cfg)

@icinga-migration
Copy link
Author

Updated by rudolfasd on 2012-02-02 03:31:30 +00:00

I'm sorry to have kept you spend time.
I realized my mistake and removed the line from icinga.cfg:
broker_module=/usr/bin/idomod.o config_file=/etc/icinga/idomod.cfg
Now everything is working correctly.

Thank you for your help.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2012-02-02 10:10:20 +00:00

well it would be interesting, what exactly was causing the segfault. i.e. running the core startup not via initscript but terminate within an gdb shell and backtrace the sigsegv.
see https://wiki.icinga.org/display/Dev/Debug for some insights using gdb.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2012-05-05 12:05:17 +00:00

  • Status changed from Feedback to Closed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant