You are right! It's running as root. But shouldn't the init script start it as icinga?
And one other weird thing --> sometimes there are two or more ido2db processes?!? root 17524 0.0 0.1 130576 2880 ? Sl 11:54 0:01 /usr/local/icinga/bin/ido2db -c /usr/local/icinga/etc/ido2db.cfg root 25508 0.0 0.0 51784 884 ? Ss 09:35 0:00 /usr/local/icinga/bin/ido2db -c /usr/local/icinga/etc/ido2db.cfg Andreas -----Ursprüngliche Nachricht----- Von: Armin Maier [mailto:[email protected]] Gesendet: Donnerstag, 01. Dezember 2011 11:48 An: [email protected] Betreff: Re: [icinga-users] event broker problem (ido2db socket) Did you check unter which user ido2db is running, it has to run with the same credentials like the icinga daemon, in your case "icinga" i think. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ icinga-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/icinga-users ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ icinga-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/icinga-users
