Description of problem: Fedora 35 ships version 8.0 of PHP and version 5.0 of Zabbix, but as stated in the "Requirements" [1], this combination is not supported. The PHP softare for the Zabbix frontend needs to have version 7.2 or later, BUT not 8. Version-Release number of selected component (if applicable): zabbix-web-5.0.16-1.fc35.noarch php-common-8.0.12-2.fc35.x86_64 The symptomps were discussed in the Zabbix forum already: - white pages instead of maps [2] - error messages on the screen [3] with the conclusion that downgrading PHP from 8 to 7 fixed the problems. The more recent Zabbix 5.4 also doesn't support PHP 8 as of now, the only solution to have a working frontend is to install PHP 7.4 from another source. Additional info: [1] https://www.zabbix.com/documentation/5.0/manual/installation/requirements [2] https://www.zabbix.com/forum/zabbix-help/421102-help-maps-and-screen-pages-are-blank [3] https://www.zabbix.com/forum/zabbix-troubleshooting-and-problems/421048-zabbix-error-on-top-of-the-screen
I can confirm this. After upgrade from fedora 34 to 35 zabbix server is mostly broken, the "screens" page is completely blank. Looking at the http error log it shows: AH01071: Got error 'PHP message: PHP Fatal error: Uncaught ArgumentCountError: array_merge() does not accept unknown named parameters in /usr/share/zabbix/include/classes/macros/CMacrosResolver.php:2018\nStack trace:\n#0 /usr/share/zabbix/include/classes/macros/CMacrosResolver.php(2018): array_merge()\n#1 [internal function]: CMacrosResolver->{closure}()\n#2 /usr/share/zabbix/include/classes/macros/CMacrosResolver.php(2019): array_map()\n#3 /usr/share/zabbix/include/classes/macros/CMacrosResolverHelper.php(565): CMacrosResolver->resolveMacrosInMapElements()\n#4 /usr/share/zabbix/include/classes/helpers/CMapHelper.php(103):CMacrosResolverHelper::resolveMacrosInMapElements()\n#5 /usr/share/zabbix/include/classes/screens/CScreenMap.php(36): CMapHelper::get()\n#6 /usr/share/zabbix/include/classes/screens/CScreenBuilder.php(487): CScreenMap->get()\n#7 /usr/share/zabbix/include/views/monitoring.screen.php(145): CScreenBuilder->show()\n#8 /usr/share/zabbix/include/classes/mvc/CView.php(122): include('/usr/share/zabb...')\n#9 /usr/sh...'
Same problem. Additional info: - https://support.zabbix.com/browse/ZBXNEXT-7080 - https://support.zabbix.com/browse/ZBX-19323
FYI i ended up moving my zabbix server and web frontend to docker containers instead as a workaround. Works just fine. I did run in to the expected problem of macvlan based network in docker not able to communicate with the host itself, but found a workaround (basically add an extra interface on the host itself using macvlan on the same net)
This was added to https://fedoraproject.org/wiki/Common_F35_bugs but the bug isn't linked by the CommonBugs keyword. Adding it for triage.
(In reply to Torbjorn Jansson from comment #3) > FYI i ended up moving my zabbix server and web frontend to docker containers > instead as a workaround. I'm curious -- what packages/source did you use for Zabbix and PHP within that container? Are you aware of / have you used the "remi" PHP repositories at https://blog.remirepo.net/pages/Config-en? Fedora 35 provides PHP version 8.0 in its official repository Command to install the Remi repository configuration package: dnf install https://rpms.remirepo.net/fedora/remi-release-35.rpm You want multiple versions which means using a Software Collection The php74 collection is available in the remi repository Command to install: dnf --enablerepo=remi install php74 Command to install additional packages: dnf --enablerepo=remi install php74-php-xxx Command to install testing packages: dnf --enablerepo=remi-test install php74-php-xxx Command to check the installed version and available extensions: php74 --version php74 --modules When a single version is installed, command in default path (/usr/bin/php) can be installed: dnf install php74-syspaths Remi is the maintainer of the PHP packages in Fedora Linux, and I trust his repositories. :)
(In reply to Matthew Miller from comment #5) > (In reply to Torbjorn Jansson from comment #3) > > FYI i ended up moving my zabbix server and web frontend to docker containers > > instead as a workaround. > > I'm curious -- what packages/source did you use for Zabbix and PHP within > that container? > I used the official docker containers as published on the download page of zabbix. I don't know where they get the php from but the containers created by zabbix should have whatever is needed to get their own product working. I used the exact same version of the zabbix docker container as i used to have from the fedora packages so i more easily could switch over and still keep the same db and configuration. > Are you aware of / have you used the "remi" PHP repositories at > https://blog.remirepo.net/pages/Config-en? > No, i had never heard of it until now.
FYI, my repository now also have 7.4 as module (for those who want a single version and want to avoid Software Collections) https://rpms.remirepo.net/wizard/ in short: dnf module install php:remi-7.4
Zabbix 6.0.0 LTS has been released. https://www.zabbix.com/de/rn/rn6.0.0
*** Bug 2086282 has been marked as a duplicate of this bug. ***
Do we have any idea about the integration of Zabbix 6.x in F36 to remove this incompatibility that exists with PHP 8 since F35?
I think we probably should update F36 to 6.0. Any other comments?
To fix the incompatibility we need at least 6.2, I think: https://www.zabbix.com/release_notes. Now that it's released, maybe we should target 6.2 instead of 6.0?
6.0.6 also mentions PHP 8.1 fixes, so I think we can stick with that.
You're correct - 6.0.6 has the PHP 8.1 fixes too. Sorry, I missed that.
Why not provide the latest stable version 6.2? Are there any restrictions?
We've generally stuck with the LTS version to avoid more mid-release version bumps. But if the Fedora maintainer would like to change to using the latest, I don't think it would be too much of an issue. Version updates have been fairly smooth lately.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
The incompatibility is still present in F36. Please upgrade Zabbix to a LTS version that supports PHP 8.1 for F36 at least.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
Why comment 18 was ignored? The incompatibility is still present in F36. Please upgrade Zabbix to a LTS version that supports PHP 8.1 for F36 at least. Please re-open this bug report for F36.
Reopening per comment 20.
FEDORA-2023-0bdab8767d has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-0bdab8767d
So I honestly have no idea if 5.0.30 will resolve this, but it's the latest 5.0.X available so worth a shot.
FEDORA-2023-0bdab8767d has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-0bdab8767d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-0bdab8767d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-0bdab8767d has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
Unfortunately, zabbix 5.0.30 still has the problem in Fedora 36
I have decided to upgrade to Fedora 37 which currently provides Zabbix 6.0.8 solving the issue with PHP 8.1 This works perfectly for me now.
I had made the same decision when F37 was released and it works well too.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.