Portage 2.2.0_alpha142 (hardened/linux/amd64/no-multilib, gcc-4.5.4-asneeded-asneeded, glibc-2.15-r3, 3.4.7-hardened x86_64) ================================================================= System uname: Linux-3.4.7-hardened-x86_64-AMD_Opteron-TM-_Processor_6272-with-gentoo-2.1 Timestamp of tree: Fri, 02 Nov 2012 20:00:01 +0000 ld GNU ld (GNU Binutils) 2.22 distcc 3.1 x86_64-pc-linux-gnu [disabled] ccache version 3.1.7 [disabled] app-shells/bash: 4.2_p37 dev-java/java-config: 2.1.11-r3 dev-lang/python: 2.6.8, 2.7.3-r2, 3.2.3 dev-util/ccache: 3.1.7 dev-util/cmake: 2.8.9 sys-apps/baselayout: 2.1-r1 sys-apps/openrc: 0.9.8.4 sys-apps/sandbox: 2.5 sys-devel/autoconf: 2.13, 2.68 sys-devel/automake: 1.4_p6-r1, 1.9.6-r3, 1.10.3, 1.11.6 sys-devel/binutils: 2.22-r1 sys-devel/gcc: 4.5.4 sys-devel/gcc-config: 1.7.3 sys-devel/libtool: 2.4-r1 sys-devel/make: 3.82-r3 sys-kernel/linux-headers: 3.4-r2 (virtual/os-headers) sys-libs/glibc: 2.15-r3 Repositories: gentoo ACCEPT_KEYWORDS="amd64" ACCEPT_LICENSE="*" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -pipe -ggdb -march=native -ftracer -frecord-gcc-switches" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /opt/openfire/resources/security/ /usr/share/config /usr/share/gnupg/qualified.txt /usr/share/maven-bin-2.2/conf /usr/share/openvpn/easy-rsa /usr/share/themes/oxygen-gtk/gtk-2.0 /var/bind /var/lib/hsqldb /var/qmail/alias /var/qmail/control /var/spool/torque /var/vpopmail/etc /var/yp/Makefile" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/games/angband/edit/ /etc/gconf /etc/gentoo-release /etc/php/apache2-php5.3/ext-active/ /etc/php/apache2-php5.4/ext-active/ /etc/php/cgi-php5.3/ext-active/ /etc/php/cgi-php5.4/ext-active/ /etc/php/cli-php5.3/ext-active/ /etc/php/cli-php5.4/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c" CXXFLAGS="-O2 -pipe -ggdb -march=native -ftracer -frecord-gcc-switches" DISTDIR="/var/cache/portage/distfiles" FCFLAGS="-O2 -pipe -ggdb -march=native -frecord-gcc-switches" FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fail-clean fixlafiles merge-sync news parallel-fetch protect-owned sandbox sfperms strict test test-fail-continue unknown-features-warn unmerge-orphans userfetch userpriv usersandbox" FFLAGS="-O2 -pipe -ggdb -march=native -frecord-gcc-switches" GENTOO_MIRRORS="http://ftp.ucsb.edu/pub/mirrors/linux/gentoo/ http://gentoo.mirrors.hoobly.com/ http://gentoo.llarian.net/" LDFLAGS="-Wl,-O1 -Wl,--as-needed" MAKEOPTS="-j24" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/tmp" PORTDIR="/var/cache/tinderbox/tree" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow 3dnowex acl amd64 berkdb bzip2 cli cracklib crypt cups curl cxx dri ffmpeg gdbm gpm hardened iconv introspection ipv6 justify mmx modules mudflap ncurses nls nptl openmp pam pax_kernel pcre plasma pppd qt3support readline semantic-desktop session sse sse2 sse3 sse4 ssl ssse3 tcpd unicode urandom vhosts zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" PHP_TARGETS="php5-3" PYTHON_TARGETS="python3_2 python2_7" RUBY_TARGETS="ruby18 ruby19" USERLAND="GNU" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON
This is a real problem now and the fix in 2.0 isn't really pretty. The proper code should be something like this: start_pre() { checkpath -d -m 0750 -o zabbix:zabbix /var/run/zabbix }
I'll look at this bug tonight, note that 2.0.4 will likely become highest stable soon...1.8.* will be left for those who can not upgrade to 2.0.x for some reason.
Can we please get this change in the tree? If you don't have time: I can do it, just tell me: do you want a -r1 for the initd-file or should I bump the directory with all config files at once to 1.8.16 (and drop 1.4.6, 1.6.5 while being add it)?
Zabbix 2.0.x has been fixed for ages. There shouldn't be any reason why someone should need to still run zabbix 1.8.x....upgrades to zabbix 2.0.x are relatively painless even on the server end and 2.0.x has been stable for a good bit. The only changes I'd like to make for 1.8.x going forward is to remove its ebuilds from portage but I've been holding off on that....if there is a qa issue, I'll go ahead and remove it though. Done.
Maybe a 200+ installation isn't that easy to upgrade... but what would you know about it? Since this is kindergarten where you first promise to do something and then become stubborn if someone reminds you of it. But ok, will put it in an overlay then...
This was fixed....in 2.0.x....months ago. I've made clear on numerous bugs, including all stabilization requests, that the 1.8.x ebuilds were eventually going to go away...at least for the last six months. As far as managing 200+ nodes, I likely have more experience than you....but whatever, this isn't a contest. Unlike the 1.6.x to 1.8.x transition, the 1.8.x -> 2.0.x transition is much easier. 2.0.x feels like a minor upgrade from 1.8.x than the major changes from 1.6. 2.0.x has been out for a year now...more than enough time to put it on a staging/test box and adjust for minor template changes. DB upgrade is also mostly seamless.
Also, in the process of creating the 2.0.x ebuilds, I found numerous bugs in the 1.8.x ebuilds...and ended up rewriting much of the logic...I know that internally zabbix is focused on supporting 2.0.x, and developing 2.1.x....I'm not sure how many resources are going to support 1.8.x. I personally did not use 1.8.x ebuilds for very long as I kept production servers on 1.6.x until just before 2.0.x was released. I'll offer that if you want to maintain 1.8.x ebuilds, than feel free to re-add 1.8.16 back into the tree. I plan to only maintain 2.0.x+ going forward.
(In reply to comment #7) > Also, in the process of creating the 2.0.x ebuilds, I found numerous bugs in > the 1.8.x ebuilds...and ended up rewriting much of the logic...I know that > internally zabbix is focused on supporting 2.0.x, and developing > 2.1.x....I'm not sure how many resources are going to support 1.8.x. I > personally did not use 1.8.x ebuilds for very long as I kept production > servers on 1.6.x until just before 2.0.x was released. > > I'll offer that if you want to maintain 1.8.x ebuilds, than feel free to > re-add 1.8.16 back into the tree. I plan to only maintain 2.0.x+ going > forward. Thanks, I appreciate your analysis and the offer. And sorry for the harsh words before. Since we have to migrate to zabbix-2 soon anyway I guess we are happy with the ebuild in our overlay until then, despite the bugs in it.
