Re: Small issue with net/zabbix web

Index: pkg/PLIST-web
===================================================================
RCS file: /cvs/ports/net/zabbix/pkg/PLIST-web,v
diff -u -p -r1.61 PLIST-web
--- pkg/PLIST-web 3 May 2024 11:16:54 -0000 1.61
+++ pkg/PLIST-web 12 Sep 2024 14:28:43 -0000
@@ -637,7 +637,6 @@ zabbix/conf/maintenance.inc.php
zabbix/conf/zabbix.conf.php.example
@mode 0640
@group www
-@sample zabbix/conf/zabbix.conf.php
@mode
@group
zabbix/data/
On 9/12/24 16:14, Robert Nagy wrote:
> Hi
>
> I think the default config should be ammended to reflect the default
> openbsd behaviour. Do you want to come up with a patch?
>
Hi Robert,

I am not sure you could amend the default configuration to cope with a
password. And it is recommended to configure it with setup.php, which
also tells you if you have something wrong in your php config regarding
limits. This is not some kind of package you install just for fun and
which needs to run asap.

So removing the config line from PLIST-web seems more appropriate as it
will be created by setup.php anyway. And there is always
zabbix/conf/zabbix.conf.php.example to get inspiration from if you
really need it.

> On 11/09/24 16:11 GMT, Renaud Allard wrote:
>> Hello,
>>
>> When I install the package zabbix-web, it installs the file
>> /var/www/zabbix/conf/zabbix.conf.php with some default variables. So, by
>> default, it tries to connect to MySQL DB on default unix socket without any
>> password. This means that if you try to run https://server/zabbix/setup.php
>> (without having MySQL listening on a unix socket without password), it will
>> throw a custom error "no such file or directory". This is extremely hard to
>> debug why because it doesn't log any useful error message and doesn't relate
>> to database. Also, there is no mention of that in the package README file.
>>
>> Since the preferred way of configuring zabbix seems to be through setup.php,
>> it might be a good idea to remove that default config to prevent clueless
>> errors. Or maybe at least mention it in the package README.
>>
>> What do you think?
>>
>> Best Regards
>
>
>