icinga is a nagios fork. it is growing fast and as a lot of ex-nagios developers. we need an ebuild to use it with gentoo. thanks. Reproducible: Always
Try write it youself and attach it. the sunrise project will help you if needed.
I've an ebuild to install icinga from git in my personal overlay: layman -a dertobi123 unmask et al and emerge icinga ;)
have started work on this ebuild, give me a day or two to have a go at it. will post progress as i make it. all the best, Tom Lane
hello, have just commited icinga-0.8.0.ebuild to the gentoo sunrise overlay, testing needed, current keywords are ~x86. all the best, Tom Lane
Created attachment 203125 [details] First Ebuild. Testing Required.
Created attachment 203194 [details] new ebuild for latest version. Some what more complete ebuild, which now fetches and compiles. and also is now the latest version, which is 0.8.3 .
(In reply to comment #6) > Created an attachment (id=203194) [edit] > new ebuild for latest version. > > Some what more complete ebuild, which now fetches and compiles. and also is now > the latest version, which is 0.8.3 . > see comment #2 ...
There has been no update to this. Has there been any testing or should I build a new ebuild for 1.0.2?
Oh YES, please build it. I'm your favorite tester...
Created attachment 238647 [details] new ebuild
Created attachment 238651 [details] new metadata
Created attachment 238653 [details] fixed ebuild Forgot the slot param
Created attachment 238655 [details] changed herd
Created attachment 238671 [details] more correct ebuild It's still broken at this point but it's 'better'
Created attachment 238755 [details] more more correct ebuild it installs this time
Created attachment 238765 [details] reviewed ebuild reviewed by some people in sunrise
Created attachment 238779 [details] final (in sunrise)
tested on ~amd64
- Installs CGIs into /usr/sbin - No Apache Config - No Gentoo specific init script - Installs configuration right into /etc instead of /etc/icinga - Installs files into /usr/share - Depends on at least nagios-plugins and php are missing - What are you using EAPI=2 for? Up until today i thought we do have some kind of QA or review session before something is put into the sunrise overlay, but obviously i'm wrong. I'll suggest to take the nagios ebuild to start with, add libdbi depends and probably php use-deps.
As far as I knew we did not have to use libdbi, that's why I have $(use_enable dbi idoutils). I'll be looking at the Makefile to see what needs to be changed, I do not know how to commit the change once needed (I'll see if I can get it upstream though). All that is needed to get something into sunrise is a review of the ebuild, I am responsible for the actual content of it. The reason why I have not added in the web (apache) parts is because I think that the frontend should be split from the backend. In what directory should I put the cgi scripts and the stuff from /usr/share (it looks like that's the web stuff)? I am working on getting the conf files put in their own directory. I have no particular reason to use EAPI=2.
(In reply to comment #19) > I'll suggest to take the nagios ebuild to start with, add libdbi depends and > probably php use-deps. Once again, take the current nagios ebuild to start with. No reason to re-invent the wheel (a quite bad re-invented wheel in that case). You don't need to patch around the Makefile, just add the dbi depend to a renamed nagios ebuild.
Created attachment 242481 [details] icinga-1.0.2.ebuild newly build ebuild with libdbi depencies php useflag and Makefile Patch for correct API Installation all depencies would be added as attachment
Created attachment 242483 [details] icinga-apache.conf
Created attachment 242485 [details] icinga-lighty.conf
Created attachment 242487 [details] icinga-conf.d
Created attachment 242489 [details] icinga-init.d
Created attachment 242491 [details, diff] ebauild with files for icinga and icinga-core a set of files with icinga-core and icinga multi package
Created attachment 242493 [details] ido2db-init.d
Created attachment 242495 [details] ido2db-conf.d
Spent quite a few hours writing and testing the ebuild and then 2 people working parallel the same day. WTF
(In reply to comment #30) > Spent quite a few hours writing and testing the ebuild and then 2 people > working parallel the same day. WTF > Sry about that probably its good to merge the changes to get an better ebuild i will give it a look ;)
Created attachment 242511 [details, diff] updated version. wich includes Mike Becker's changes too updated version. wich includes Mike Becker's changes too
Created attachment 243421 [details, diff] ebuild for icinga 1.0.3 new ebuild for new release
Created attachment 243423 [details, diff] this time with propper checksum ebuild for icinga 1.0.3
Working ebuild for in sunrise. Based on Mike Becker's ebuild (cleaned up and added postgres support). It is also version 1.0.3
Created attachment 248180 [details] update for 1.0.3
Created attachment 248182 [details] 1.0.3 sunrise ebuild (working/tested)
Created attachment 248183 [details] fixed id02db-init.d
Created attachment 248488 [details] cleaned up more with help from tommy and sedzimir
Created attachment 249775 [details] revbump (no big changes)
Who's leg do I need to hump to get this in tree :P
(In reply to comment #41) > Who's leg do I need to hump to get this in tree :P > Should be done within the next two weeks.
Created attachment 249864 [details] add --with-cgiurl=cgi-bin to configure, contributed by RedPepper
fyi: 1.2.0 has been released http://www.icinga.org/2010/10/06/icinga-1-2-unified-stable-released/ Also looking forward to it! :-)
Created attachment 251937 [details] revbump no ebuild changes (that I can remember)
(In reply to comment #45) # ebuild /usr/local/portage/net-analyzer/icinga/icinga-1.2.1.ebuild test [...] * Adding user 'icinga' to your system ... * - Userid: 126 * Do not specify /bin/false yourself, use -1 * ERROR: net-analyzer/icinga-1.2.1 failed: * Pass '-1' as the shell parameter [...]
Created attachment 251963 [details] fixed enewuser
It doesn't seem to work for me... * Adding group 'icinga' to your system ... * - Groupid: next available * Adding user 'icinga' to your system ... * - Userid: 103 * A shell was specified but it does not exist ! * ERROR: net-analyzer/icinga-1.2.1 failed: * /var/spool/icinga does not exist in /
Created attachment 252361 [details] really this time, enewuser is fixed (missed a '-1')
(In reply to comment #49) [...] > really this time, enewuser is fixed [...] Here the next step: make[1]: Leaving directory `/var/tmp/portage/net-analyzer/icinga-1.2.1/work/icinga-1.2.1' !!! newinitd: /usr/local/portage/net-analyzer/icinga/files/icinga-init.d does not exist * ERROR: net-analyzer/icinga-1.2.1 failed: * (no error message)
(In reply to comment #50) > (In reply to comment #49) > [...] > > really this time, enewuser is fixed > [...] > > Here the next step: > > make[1]: Leaving directory > `/var/tmp/portage/net-analyzer/icinga-1.2.1/work/icinga-1.2.1' > !!! newinitd: /usr/local/portage/net-analyzer/icinga/files/icinga-init.d does > not exist > * ERROR: net-analyzer/icinga-1.2.1 failed: > * (no error message) > are you using sunrise (the file is in sunrise) the file is also linked above at https://bugs.gentoo.org/attachment.cgi?id=242489
(In reply to comment #51) > (In reply to comment #50) > > (In reply to comment #49) [...] > are you using sunrise (the file is in sunrise) > the file is also linked above at > https://bugs.gentoo.org/attachment.cgi?id=242489 Thank you, I check it again ;-)
It seems to work over here, but i've found a few things so far... i haven't found that mysterious line 4!? # /etc/init.d/icinga restart : command not found line 4: * Restarting icinga ... * Stopping icinga ... [ ok ] * Starting icinga ... [ ok ] I also needed to add include "lighttpd_icinga.conf" to lighttpd.conf. And then in lighttpd_icinga.conf i added: auth.backend = "htdigest" auth.backend.htdigest.userfile = "/etc/lighttpd/icinga.user" And consequently i created /etc/lighttpd/icinga.user
(In reply to comment #49) > Created an attachment (id=252361) [details] > really this time, enewuser is fixed (missed a '-1') > I'm working within a stable environment (portage-2.1.8.3) without any overlays like sunrise. Added the icinga-1.2.1.ebuild to my local portage overlay directory and tried to merge it. An error appeared in the src_install routine, so I have made the following changes in the ebuild: - find "${D}"/usr/$(get_libdir)/icinga -type d -exec fperms 755 {} + + find "${D}"/usr/$(get_libdir)/icinga -type d -exec chmod 755 {} + - find "${D}"/usr/$(get_libdir)/icinga/cgi-bin -type f -exec fperms 755 {} + + find "${D}"/usr/$(get_libdir)/icinga/cgi-bin -type f -exec chmod 755 {} + The problem was that find is a standard bash program, which needs the whole path (including /var/tmp/portage) as parameter to search, the resulting path/filename is then passed to the exec command. There, the fperms routine was used, which is a special ebuild routine. It always operates in the temporary directory of portage, so the error appears, if the full path is passed as parameter. So I have replaced the fperms routine with chmod which worked fine for me. The I recognized, that the wrong group was applied to /var/icinga/rw. So I've made the following change in the ebuild: - use apache2 && webserver=apache2 || use lighttpd && webserver=lighttpd || webserver=icinga + if use apache2 ; then + webserver=apache + elif use lighttpd ; then + webserver=lighttpd + else + webserver=icinga + fi After that, the right group was applied to the directory.
(In reply to comment #53) > It seems to work over here, but i've found a few things so far... > > i haven't found that mysterious line 4!? > # /etc/init.d/icinga restart > : command not found line 4: > * Restarting icinga ... > * Stopping icinga ... > [ ok ] > * Starting icinga ... > [ ok ] > > I also needed to add > include "lighttpd_icinga.conf" > to lighttpd.conf. > > And then in lighttpd_icinga.conf i added: > auth.backend = "htdigest" > auth.backend.htdigest.userfile = "/etc/lighttpd/icinga.user" > > And consequently i created /etc/lighttpd/icinga.user > I've just found the problem which generates this mysterious "Line 4" error message, it seems that the encoding of some files is wrong. As far as I saw, /etc/conf.d/icinga is in DOS-Format instead uf UNIX. That means that the line delemiters are wrong. Converting the config file and the init scripts to UNIX solves the problem.
chmod instead of fperms indeed does the trick! Also the tip about the dos-newlines in /etc/conf.d/icinga is good! I already converted the initscripts before, but haven't seen the config to them... :-) Thanks! ...but there are still some things wrong with the ebuild: * QA Notice: Unrecognized configure options: * * configure: WARNING: unrecognized options: --enable-embedded-perl, --with-perlcache, --enable-idoutils, --enable-ssl, --disable-DEBUG0, --disable-DEBUG1, --disable-DEBUG2, --disable-DEBUG3, --disable-DEBUG4, --disable-DEBUG5, --disable-statuswrl, --with-cgiurl * configure: WARNING: unrecognized options: --enable-embedded-perl, --with-perlcache, --enable-idoutils, --enable-ssl, --disable-DEBUG0, --disable-DEBUG1, --disable-DEBUG2, --disable-DEBUG3, --disable-DEBUG4, --disable-DEBUG5, --disable-statuswrl, --with-cgiurl * QA Notice: Pre-stripped files found: * /usr/lib64/icinga/cgi-bin/notifications.cgi * /usr/lib64/icinga/cgi-bin/extinfo.cgi * /usr/lib64/icinga/cgi-bin/statuswml.cgi * /usr/lib64/icinga/cgi-bin/cmd.cgi * /usr/lib64/icinga/cgi-bin/history.cgi * /usr/lib64/icinga/cgi-bin/statusmap.cgi * /usr/lib64/icinga/cgi-bin/status.cgi * /usr/lib64/icinga/cgi-bin/tac.cgi * /usr/lib64/icinga/cgi-bin/trends.cgi * /usr/lib64/icinga/cgi-bin/showlog.cgi * /usr/lib64/icinga/cgi-bin/histogram.cgi * /usr/lib64/icinga/cgi-bin/avail.cgi * /usr/lib64/icinga/cgi-bin/config.cgi * /usr/lib64/icinga/cgi-bin/summary.cgi * /usr/lib64/icinga/cgi-bin/outages.cgi * /usr/sbin/icingastats * /usr/sbin/icinga strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment usr/sbin/idomod.o usr/sbin/ido2db
Created attachment 252489 [details] Updated through comment #56 asking about the stripping upstream (debug doesn't seem happy)
Created attachment 252625 [details] Fixed configure (api has less options for configure) Only remaining thing I know of is the prestripped cgi files.
(In reply to comment #58) > Created an attachment (id=252625) [details] > Fixed configure (api has less options for configure) > > Only remaining thing I know of is the prestripped cgi files. > Plus two changes, one minor and one to get apache correctly set up: --- icinga-1.2.1.ebuild 2010-10-31 16:07:15.000000000 +0100 +++ icinga-1.2.1.ebuild 2010-10-31 16:00:07.000000000 +0100 @@ -30,6 +30,7 @@ want_apache2 pkg_setup() { + depend.apache_pkg_setup enewgroup icinga enewuser icinga -1 -1 /var/spool/icinga icinga if use web ; then @@ -95,7 +96,7 @@ $(use_enable debug DEBUG4) $(use_enable debug DEBUG5) --disable-statuswrl - --with-cgiurl=cgi-bin" + --with-cgiurl=/cgi-bin" myconf2="--bindir=/usr/sbin --sbindir=/usr/$(get_libdir)/icinga/cgi-bin
(In reply to comment #59) > (In reply to comment #58) > > Created an attachment (id=252625) [details] [details] > > Fixed configure (api has less options for configure) > > > > Only remaining thing I know of is the prestripped cgi files. > > > > Plus two changes, one minor and one to get apache correctly set up: ... and another one: the dep on nagios-syntax is useless, as nagios-syntax only gets active for files residing in /etc/nagios.
Created attachment 252717 [details] fixed a couple of things (comments 59-60) Fixed with-cgiurl option Fixed depend.apache_pkg_setup (depends go up top not in pkg_setup) Got rid of the depend on nagios-syntax as suggested.
(In reply to comment #61) > Created an attachment (id=252717) [details] > fixed a couple of things (comments 59-60) > > Fixed with-cgiurl option > Fixed depend.apache_pkg_setup (depends go up top not in pkg_setup) > Got rid of the depend on nagios-syntax as suggested. > depend.apache_pkg_setup is not an eclass to inherit, but a function to execute in pkg_setup()
Created attachment 252727 [details] fixed depend.apache_pkg_setup
Now, the cgi-prefix got wrong in icinga-lighty.conf... I don't know if this is intended or not, but here is what i needed to do: -$HTTP["url"] =~ "^/icinga/cgi-bin/" { +$HTTP["url"] =~ "^/cgi-bin/" { dir-listing.activate = "disable" cgi.assign = ( ".pl" => "/usr/bin/perl", ".cgi" => "" ) } alias.url += ( - "/icinga/cgi-bin" => "/usr/lib/icinga/cgi-bin", + "/cgi-bin" => "/usr/lib/icinga/cgi-bin", "/icinga" => "/usr/share/icinga/htdocs" ) But then, the default auth-declaration does not work anymore on the cgi scripts: -auth.require += ( "/icinga" => +auth.require += ( "/" => ( "method" => "digest", "realm" => "icinga", "require" => "valid-user" ) )
(In reply to comment #64) > Now, the cgi-prefix got wrong in icinga-lighty.conf... I don't know if this is > intended or not, but here is what i needed to do: @@ -95,7 +96,7 @@ $(use_enable debug DEBUG4) $(use_enable debug DEBUG5) --disable-statuswrl - --with-cgiurl=cgi-bin" + --with-cgiurl=/cgi-bin" myconf2="--bindir=/usr/sbin --sbindir=/usr/$(get_libdir)/icinga/cgi-bin That's probably caused by this one, would make sense to change --with-cgiurl to --with-cgiurl=/icinga/cgi-bin"
Do we have a list of what needs to be done before this can be added to tree?
(In reply to comment #65) [...] > That's probably caused by this one, would make sense to change --with-cgiurl to > --with-cgiurl=/icinga/cgi-bin" Hello, I prefer this. After 'emerge apache' brings '/etc/apache2/vhosts.d/default_vhost.include' an script alias: ScriptAlias /cgi-bin/ "/var/www/localhost/cgi-bin/" The ScriptAlias via 99_icinga.conf is right for me.
(In reply to comment #67) > (In reply to comment #65) > [...] > > That's probably caused by this one, would make sense to change --with-cgiurl to > > --with-cgiurl=/icinga/cgi-bin" > > Hello, I prefer this. > After 'emerge apache' brings '/etc/apache2/vhosts.d/default_vhost.include' an > script alias: > ScriptAlias /cgi-bin/ "/var/www/localhost/cgi-bin/" > > The ScriptAlias via 99_icinga.conf is right for me. > The reason I have not gone this route is because I think that environments differ too much, also if that is the route that we want to go down, then making it a webapp (through webapp-config) would be best. Is this the only issue holding us up? I'm going to be testing icinga 1.3 soon.
Created attachment 262747 [details] icinga-1.3.0.ebuild only update was to the package version, tested amd64
Again, what is the hold up?
I prefer to have the --with-cgibin=/icinga/cgi-bin in the ebuild as that conflicts with less tooling (other web tools) on a server. At least that is missing atm. This is based on the 1.3.0 version. Are you aware on the problems identified in: http://packetstormsecurity.org/files/99090/Icinga-1.3.0-1.2.1-Cross-Site-Scripting.html
(In reply to comment #71) > I prefer to have the --with-cgibin=/icinga/cgi-bin in the ebuild > as that conflicts with less tooling (other web tools) on a server. > > At least that is missing atm. > > This is based on the 1.3.0 version. > > Are you aware on the problems identified in: > http://packetstormsecurity.org/files/99090/Icinga-1.3.0-1.2.1-Cross-Site-Scripting.html It looks like it is set up that way in the conf provided for both apache and lighttpd, I'll change it. Anything else?
Created attachment 265487 [details] updated --with-cgiurl=icgi-bin to --with-cgiurl=/icinga/cgi-bin
(In reply to comment #72) > (In reply to comment #71) > > I prefer to have the --with-cgibin=/icinga/cgi-bin in the ebuild > > as that conflicts with less tooling (other web tools) on a server. > > > > At least that is missing atm. > > > > This is based on the 1.3.0 version. > > > > Are you aware on the problems identified in: > > http://packetstormsecurity.org/files/99090/Icinga-1.3.0-1.2.1-Cross-Site-Scripting.html > > It looks like it is set up that way in the conf provided for both apache and > lighttpd, I'll change it. Anything else? hi the XSS should now been fixed in git . Please file a bug at the developers site in the future https://dev.icinga.org For details about the fix see https://dev.icinga.org/issues/1275
Created attachment 268137 [details] icinga-1.3.1.ebuild Updated to 1.3.1 (this fixes the xss vuln) any other hold ups to geting this in tree?
Forgot to obsolete https://bugs.gentoo.org/attachment.cgi?id=265487
Some observations: - Default config has logs in /var/icinga, not /var/log - Either a previous install I did screwed it up, or it didn't symlink nagios-plugins from lib/nagios to lib/icinga, resulting in plugins not being found Other than that, good job. Files are generally where I'd expect them now. It could use a message pointing to the apache config.
(In reply to comment #77) > Some observations: > > - Default config has logs in /var/icinga, not /var/log > - Either a previous install I did screwed it up, or it didn't symlink > nagios-plugins from lib/nagios to lib/icinga, resulting in plugins not being > found > > Other than that, good job. Files are generally where I'd expect them now. It > could use a message pointing to the apache config. For the log file, it looks like we will need to patch the make file, I am going to talk to them to see if we can get a --logdir variable added to it. For the symlink, I do not know if I want to symlink it in the ebuild, because the ebuild does not install anything or manage lib/nagios and puts content in lib/icinga .
Created attachment 268799 [details] icinga-1.3.1.ebuild with logdir set changed log directory to /var/log/icinga As for the symlink, nagios creates that directory, so we should not mess with it.
(In reply to comment #79) > Created attachment 268799 [details] > icinga-1.3.1.ebuild with logdir set > > changed log directory to /var/log/icinga > > > As for the symlink, nagios creates that directory, so we should not mess with > it. You're probably right, but having the $USER1$ and $USER2$ macros default to the icinga directory and having a default setup that relies on plugins being there is a little unintuitive. Did you plan for an icinga-plugins ebuild? If not, maybe at least a message, telling the user that the plugins USE installed nagios-plugins in a different directory and that he should copy/symlink them or change his macros?
Created attachment 268865 [details] icinga-1.3.1.ebuild with libexecdir conditional added made libexecdir dependant on the plugins useflag (if plugins are enabled, then the libexecdir will be /usr/$(get_libdir)/nagios/plugins, else replace nagios with icinga)
Created attachment 269497 [details] icinga-1.3.1.ebuild with spacing issue fixed fixed a spacing issue on the src_configure, and removed an OLD ebuild
Anything else preventing inclusion in tree?
After a VM crash the message: * Starting ido2db ... Could not bind socket: Address already in use This patch is inspired by mysql-init.d: --- ido2db.orig 2011-05-05 19:53:06.000000000 +0200 +++ ido2db 2011-05-05 21:07:15.000000000 +0200 @@ -4,6 +4,17 @@ # $Header: $ IDO2DBBIN="/usr/sbin/ido2db" +SOCKET="/var/icinga/ido.sock" + +function check() { + if [[ -S "${SOCKET}" ]] ; then + ewarn "Strange, the socket file already exist in \"${SOCKET}\"" + ewarn "it will be removed now and re-created by ido2db" + ewarn "BUT please make your checks." + + rm -f "${SOCKET}" + fi +} depend() { need net @@ -12,6 +23,8 @@ } start() { + check + ebegin "Starting ido2db" start-stop-daemon --quiet --start --pidfile /var/icinga/ido2db.lock --startas ${IDO2DBBIN} -- -c ${IDO2DBCFG} eend $?
Created attachment 272657 [details] change to ido2db init, thanks to Wolfgang Schricker
Created attachment 272803 [details] made more posix compliant
Created attachment 272861 [details] icinga-1.4.0 version bump, tested amd64
Not that I am not grateful for 1.4.0 ebuild. I installed 1.0.2 on amd64 but for some reason all files in htdocs folder are pointing to /cgi-bin instead of /icinga/cgi-bin ..I did change index.html however there are many like files which need update. Asa curiosity I tried 1.4.0, however emerge fails as below. strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment usr/sbin/ido2db usr/sbin/idomod.o usr/sbin/log2ido 'nfs1/var/tmp/portage/portage/net-analyzer/icinga-1.4.0/image///etc/init.d/icinga: line 8: syntax error near unexpected token `{ 'nfs1/var/tmp/portage/portage/net-analyzer/icinga-1.4.0/image///etc/init.d/icinga: line 8: `depend() { * ERROR: net-analyzer/icinga-1.4.0 failed: * The init.d file has syntax errors: /nfs1/var/tmp/portage/portage/net-analyzer/icinga-1.4.0/image///etc/init.d/icinga * * Call stack: * misc-functions.sh, line 979: Called install_qa_check * misc-functions.sh, line 458: Called die * The specific snippet of code: * bash -n "${i}" || die "The init.d file has syntax errors: ${i}" * * If you need support, post the output of 'emerge --info =net-analyzer/icinga-1.4.0', * the complete build log and the output of 'emerge -pqv =net-analyzer/icinga-1.4.0'. * This ebuild is from an overlay named 'local': '/usr/local/portage/' * The complete build log is located at '/nfs1/var/tmp/portage/portage/net-analyzer/icinga-1.4.0/temp/build.log'. * The ebuild environment file is located at '/nfs1/var/tmp/portage/portage/net-analyzer/icinga-1.4.0/temp/environment'. * S: '/nfs1/var/tmp/portage/portage/net-analyzer/icinga-1.4.0/work/icinga-1.4.0' !!! post install failed; exiting.
I can confirm Comment 88! Emerging fails with the same error! I checked the specified init script and there seems nothing wrong too me! Or are we using the wrong icinga-init.d file?
(In reply to comment #89) > I can confirm Comment 88! > > Emerging fails with the same error! > I checked the specified init script and there seems nothing wrong too me! > > Or are we using the wrong icinga-init.d file? Can I get your use flags? I use the following. Installed versions: 1.4.0(18:32:41 05/23/11)(api idoutils lighttpd perl plugins postgres ssl vim-syntax web -apache2 -debug -mysql) Also, for the init script I updated it to be openrc compliant on the 11th.
(In reply to comment #90) > Can I get your use flags? I use the following. > Installed versions: 1.4.0(18:32:41 05/23/11)(api idoutils lighttpd perl > plugins postgres ssl vim-syntax web -apache2 -debug -mysql) > > Also, for the init script I updated it to be openrc compliant on the 11th. Hey, thanks for responding. My use flags were: net-analyzer/icinga-1.4.0 USE="apache2 idoutils mysql plugins ssl vim-syntax web -api -debug -lighttpd -perl -postgres" On 2011-05-11 you only updated ido2db-init.d, but the emerge error occurs while processing icinga-init.d! (which I here find only from 2010-08-11 and has no difference to the one in sunrise) Or am I missing something?
(In reply to comment #91) > (In reply to comment #90) > > Can I get your use flags? I use the following. > > Installed versions: 1.4.0(18:32:41 05/23/11)(api idoutils lighttpd perl > > plugins postgres ssl vim-syntax web -apache2 -debug -mysql) > > > > Also, for the init script I updated it to be openrc compliant on the 11th. > > Hey, thanks for responding. > > My use flags were: > > net-analyzer/icinga-1.4.0 USE="apache2 idoutils mysql plugins ssl vim-syntax > web -api -debug -lighttpd -perl -postgres" > > On 2011-05-11 you only updated ido2db-init.d, but the emerge error occurs while > processing icinga-init.d! (which I here find only from 2010-08-11 and has no > difference to the one in sunrise) > > Or am I missing something? You are correct, I misunderstood which init.d I updated lol. can you print the output of "bash -n ${initscritp_goes_here}" for me? I get none which means it validates for me.
Narf, I'd like to say! When I simply use the files/* from sunrise and the icinga-1.4.0.ebuild from here, everything emerges fine. (And runs, by the way!) Sorry for the mess ;) Now, let's go for sunrise! Thx, Matthew!
Created attachment 280365 [details] icinga 1.4.2 version bump, tested amd64
Created attachment 284485 [details] icinga-1.5.0.ebuild removed the logdir sed and added --with-log-dir=/var/log/icinga Tested amd64
Should´nt ido2db be started before icinga? --- icinga-init.d 2011-08-30 15:54:51.000000000 +0200 +++ icinga-init.d.orig 2011-08-30 15:45:16.000000000 +0200 @@ -7,7 +7,7 @@ depend() { need net - use dns logger firewall ido2db + use dns logger firewall after mysql postgresql }
It is not necessary to install icinga with idoutils support. That is why the init script is as it is. Order also does not mater I have found, but since I am using the classic interface that could be why (don't think it uses the DB at all). Which interface are you using?
i know that it is not required to install icinga with idoutils, but if you do so ido2db should start before icinga as described in the icinga install manual. And because i added ido2db with "use" instead of "need" it is no problem if you install icinga without idoutils, but it will start it if it is available.
Created attachment 287405 [details] Ebuild for icinga-1.5.1 The ebuild for 1.5.0 works for 1.5.1, too. Tested on amd64.
(In reply to comment #100) > The ebuild for 1.5.0 works for 1.5.1, too. Hello, the directory '/usr/$(get_libdir)/icinga' was not created from both ebuilds with my USE flags: net-analyzer/icinga-1.5.1 USE="plugins ssl vim-syntax -apache2 -api -debug -idoutils -lighttpd -mysql -perl -postgres -web" My HACK in line icinga-1.5.1.ebuild, line 182: [ ! -d /usr/$(get_libdir)/icinga ] && dodir /usr/$(get_libdir)/icinga || die
I'm grateful for this ebuild, but i tried to emerge icinga-1.5.1 and everytime i got this indipendent which use-flags i choose. I used the ebuild from @Comment 100 * ERROR: net-analyzer/icinga-1.5.1 failed (install phase): * (no error message) * * Call stack: * ebuild.sh, line 56: Called src_install * environment, line 2443: Called die * The specific snippet of code: * newinitd "${FILESDIR}"/icinga-init.d icinga || die; emerge --info -> http://pastebin.com/2dV8wnmp build.log -> http://pastebin.com/E72eJwn0 Can someone confirm this error?
I was not able to reproduce the errors from comments number 101 and 102. I have also fixed the pre-stripped binaries with the help of blueness. Version 1.5.1 of icinga is in gentoo proper and has been taken out of sunrise.
