1.9.7 compiles but crashes without giving any message

[frater]

I am running 1.9.6 for a while. On an Ubuntu LTS 32-bits system it was quite stable but on Ubuntu LTS 64-bits system I need to keep it running with a watchdog.

I hoped 1.9.7 would be better, but although it compiles fine it crashes immediately after startup.

Does an strace tell you something?

[richlv]

define "crashes". quick guess - did you note that the default config file location has changed ?

[frater]

It started and stopped....
I used 'strings /usr/local/sbin/zabbix_server | grep conf' to find out the location.
It's running if I copy my config from /etc/zabbix/zabbix_server.conf to /usr/local/etc/zabbix_server.conf

Why was it changed?

I have external scripts that extract the TimeOut from the zabbix_server.conf and these need rewriting now

ZABBIX_TIMEOUT=`grep -i '^Timeout' /etc/zabbix/zabbix_server.conf 2>/dev/null | awk -F= '{print $2}' | tr -cd '0-9'`

I did a new ./configure --enable-agent --enable-server --with-mysql --with-net-snmp --with-libcurl --sysconfdir=/etc/zabbix and things will probably be the same now.

Why isn't the default behaviour the same as its behaviour all those years before?

[richlv]

i suspect you didn't start the server directly, but by an initscript - which, unfortunately, discarded any messages about config file missing.

this was a result of actually implementing support for sysconfdir - it never worked before. and a logical place for sysconfdir is prefix/etc

[frater]

After I noticed it wasn't working I started the daemon from the prompt and didn't get a message either....

Do you have an idea how an external script can obtain the place of zabbix_server.conf....?

[richlv]

After I noticed it wasn't working I started the daemon from the prompt and didn't get a message either....

can't confirm this. just tried 1.9.7 and got :

zabbix_server [17360]: cannot open config file [/path_to/zabbix_server.conf]: [2] No such file or directory

Do you have an idea how an external script can obtain the place of zabbix_server.conf....?

how do you mean that ? for a specific zabbix_server binary (as there might be multiple on the system) ? i'd probably use a standard location, but it might be useful to see that in --help output - if you'd like to see that, please, open a new feature request