[ZBX-16132] jabber support in 4.2 Created: 2019 May 15 Updated: 2019 May 20 Resolved: 2019 May 16 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S) |
Affects Version/s: | 4.2.1 |
Fix Version/s: | None |
Type: | Problem report | Priority: | Trivial |
Reporter: | adnet | Assignee: | dimir |
Resolution: | Workaround proposed | Votes: | 0 |
Labels: | regression | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
debain jessie |
Description |
Steps to reproduce: use a jabber media on zabbix server 4.2
Result: Details Media type test failed.
Expected: jabber message sent.
// espace réservé du code dpkg -l 'zabb*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-====================================================================================-===============================================-===============================================-============================================================================================================================================================================== ii zabbix-agent 1:4.2.1-1+jessie amd64 Zabbix network monitoring solution - agent ii zabbix-frontend-php 1:4.2.1-1+jessie all Zabbix network monitoring solution - PHP front-end ii zabbix-get 1:4.2.1-1+jessie amd64 Zabbix network monitoring solution - get ii zabbix-release 4.2-1+jessie all Zabbix official repository configuration ii zabbix-sender 1:4.2.1-1+jessie amd64 Zabbix network monitoring solution - sender ii zabbix-server-mysql 1:4.2.1-1+jessie amd64 Zabbix network monitoring solution - server (MySQL) un zabbix-server-pgsql <none> <none> (no description available)
|
Comments |
Comment by Aleksandrs Petrovs-Gavrilovs [ 2019 May 16 ] |
Hello, Could you please also attach config.log from sources directory after failed configure? Best Regards, |
Comment by richlv [ 2019 May 16 ] |
These might be official Zabbix packages. |
Comment by adnet [ 2019 May 16 ] |
this is the zabbix official debian packages. I do not compiled it. Since my upgrade to 4.2 the jabber system failed to work. It seems the 4.2 is not compiled with jabber support
sorry for not being clear.
best regards, Ghislain. |
Comment by Aleksandrs Petrovs-Gavrilovs [ 2019 May 16 ] |
Thanks you mentioning this richlv In that case, i need to mention that, we dropped support of Jabber in 4.2 on library level in packaging. To enable Jabber functionality you need to manually install libiksimel and then compile Zabbix from sources with appropriate flag. Best Regards, |
Comment by Glebs Ivanovskis [ 2019 May 16 ] |
See |
Comment by dimir [ 2019 May 16 ] |
cyclone, the upgrade notes page you mention never had any relation to the packages. It is meant for changes we make in software itself, which is absolutely not the case. I agree that it is good idea to mention packaging changes somewhere but we currently just don't have any place for that. Besides, I'm not sure we need to, because a responsible administrator would check changelog before installing the package, e. g.: # apt install --download-only zabbix-server-mysql Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: zabbix-frontend-php The following packages will be upgraded: zabbix-server-mysql 1 upgraded, 0 newly installed, 0 to remove and 12 not upgraded. Need to get 0 B/2317 kB of archives. After this operation, 603 kB of additional disk space will be used. Download complete and in download only mode # mkdir /tmp/zabbix-server-mysql # dpkg -x /var/cache/apt/archives/zabbix-server-mysql_1%3a4.2.1-1+stretch_amd64.deb /tmp/zabbix-server-mysql # zless /tmp/zabbix-server-mysql/usr/share/doc/zabbix-server-mysql/changelog.Debian.gz ---------------------------------------------------------------------------------------------------- zabbix (1:4.2.0-1) stable; urgency=low * update to 4.2.0 * removed jabber notifications support and dependency on iksemel library ---------------------------------------------------------------------------------------------------- |
Comment by Glebs Ivanovskis [ 2019 May 16 ] |
dimir, you are right. Since the change only affects packages you can mention it here and here. Or, in general, these pages need to mention that there are additionally upgrade notes for packages. |
Comment by Ingus Vilnis [ 2019 May 17 ] |
Hi guys, My 2 cents from user perspective. Why don't you put package changes in general upgrade notes? Imagine user willing to upgrade. One already has to read Upgrade notes and What's new pages. Most advanced would read the changelog too, yes. These places should give enough information to do a successful upgrade. So you read through all this heap of info and go for the upgrade because you have done the package upgrades numerous times before, know it by heart, have documented it in your own specific internal upgrade notes page and don't need to read that additional Zabbix docs page once again. And then - surprise surprise - some stuff got broken because no one warned about it happening in the pages where you really expected this information. Put at least a link to the package upgrade pages in the Upgrade notes. |
Comment by adnet [ 2019 May 17 ] |
i agree, thanks for the additions to the doc pages I am sorry to being a non responsible admin
For lazy peoples that prefer to kkeep the official packages : one simple, way that perhaps do not scale as much as builtin jabber, is to use alert script like this: apt install sendxmpp use a custom script with 3 parameters exactly like the exemple on #!/bin/dash echo -n "$3" | sendxmpp -tls -u user -p pass -d -j jabber.yourserver.com -s "$2" "$1"; not as clean as the built in , but it works with the officials packages. |
Comment by dimir [ 2019 May 17 ] |
Thank you, ingus.vilnis. I think you're right, we should start documenting package changes in the well known upgrade notes page. Proposed this internally. Thank you, aqueos. This looks like a candidate in our documentation, as an alternative to rebuilding packages. |