Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NixOS/zabbix-{server,agent}: 1.8 -> 3.4 wip #31123

Closed
wants to merge 9 commits into from
Closed

Conversation

srhb
Copy link
Contributor

@srhb srhb commented Nov 2, 2017

Motivation for this change

Currently, the zabbix modules use a very old version of zabbix. Most of the mechanics appear to have been unaltered, but there are some fixes necessary to bring it to work with a current version. I'm unsure if this module is really used by anyone (because of its age.) If it isn't, I would like to rip it apart entirely and parameterize, among other things, the actual package version used by the module.

I notice that @edolstra is marked as maintainer, so I'm curious if you have strong feelings on keeping this module as-is, or whether I should take a less conservative approach than this on bringing it up-to-date.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

@edolstra
Copy link
Member

edolstra commented Nov 2, 2017

Feel free to take over as maintainer for Zabbix. I'm not using it anymore at the moment.

${pkgs.postgresql}/bin/createuser --no-superuser --no-createdb --no-createrole zabbix || true
${pkgs.postgresql}/bin/createdb --owner zabbix zabbix || true
${pkgs.sudo}/bin/sudo -u postgres ${pkgs.postgresql}/bin/createuser --no-superuser --no-createdb --no-createrole zabbix || true
${pkgs.sudo}/bin/sudo -u postgres ${pkgs.postgresql}/bin/createdb --owner zabbix zabbix || true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe using runuser from utillinux is the better approach here or using su as below.


let

version = "1.8.22";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need both zabbix versions. It also seems the old versions would not be maintained well.

@srhb
Copy link
Contributor Author

srhb commented Nov 2, 2017

Thank you both for the comments. I will take over as maintainer, remove the old versions and revamp the modules in the next week or so. :)

@adamtulinius
Copy link
Member

adamtulinius commented Nov 2, 2017

This might be interesting when figuring out which versions to keep, and which to get rid of: https://www.zabbix.com/life_cycle_and_release_policy

But if nobody has strong opinions on this, it's probably wasted to spend any effort on Zabbix 1.x and 2.x.

@Mic92
Copy link
Member

Mic92 commented Nov 25, 2017

we have merge conflicts here.

@srhb
Copy link
Contributor Author

srhb commented Nov 28, 2017

OK, looks like I'll have to revive 2.0 and 2.2 for now...

@srhb
Copy link
Contributor Author

srhb commented Nov 28, 2017

Wait, no, 2.0 is EOL. I'll revive 2.2 only and try and see if the modules still work.

@PsyanticY PsyanticY mentioned this pull request May 3, 2018
8 tasks
@yesbox
Copy link
Contributor

yesbox commented Sep 16, 2018

The Zabbix web service (nixos/modules/services/web-servers/apache-httpd/zabbix.nix) is currently broken. It seems the old Zabbix server isn't PHP 7 compatible and so it doesn't serve anything. Maybe for the better, I would be very surprised if it isn't full of known vulnerabilities.

[php7:error] PHP Fatal error: 'break' not in the 'loop' or 'switch' context in /nix/store/hzr8p3xifm4912f3h89qppkcp61kdrgw-zabbix-1.8.22/share/zabbix/php/include/maps.inc.php on line 126

@srhb
Copy link
Contributor Author

srhb commented Sep 27, 2018

I also no longer have to use Zabbix, closing.

@srhb srhb closed this Sep 27, 2018
@srhb srhb deleted the zabbix34 branch September 27, 2018 11:58
@Mic92
Copy link
Member

Mic92 commented Sep 27, 2018

In the current state we probably should remove zabbix until someone maintains it properly.

@adamtulinius
Copy link
Member

I've considered fixing it multiple times, but lost the will just by thinking about all the old cruft that had to be supported (v 1.8, 2.0, 2.2). If it was an acceptable solution to only support zabbix 3.4, then the task would be much easier.

@srhb
Copy link
Contributor Author

srhb commented Sep 27, 2018

@adamtulinius Only supporting the newest is, at it stands, way more reasonable than having every version be unsupported, so please don't let that perceived requirement hold you back. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants