Ad Widget

**jluvs2ride** · 08-04-2018, 15:43

I have several Zabbix Proxies set up at remote locations. They are all running on Raspberry PIs with Raspbian. If the devices restart I have to manually restart the Proxy and Agent Services using;

sudo /usr/sbin/zabbix_agentd
sudo /usr/sbin/zabbix_proxy

I haven't been able to figure out how to get these to start automatically when the device restarts.

Is this possibly related to your issue?

**bitmeup** · 11-04-2018, 22:19

Originally posted by jluvs2ride

I have several Zabbix Proxies set up at remote locations. They are all running on Raspberry PIs with Raspbian. If the devices restart I have to manually restart the Proxy and Agent Services using;

sudo /usr/sbin/zabbix_agentd
sudo /usr/sbin/zabbix_proxy

I haven't been able to figure out how to get these to start automatically when the device restarts.

Is this possibly related to your issue?

If you are on version Jessie and you installed a packaged version of zabbix, it should be possible to manage the service by using systemctl:

Code:

systemctl list-unit-files # to see the list of services
systemctl enable zabbix-proxy

**bitmeup** · 11-04-2018, 22:24

Originally posted by systemsmb

Hi there,

I'm unable to get Zabbix-Proxy (sqlite3) to start. I'm running version 3.4.4-4 on Raspbian (latest stable version).

When trying to start the service using the command 'sudo service zabbix-proxy start' I receive the following error.

Job for zabbix-proxy.service failed because a fatal signal was delivered to the control process.
See "systemctl status zabbix-proxy.service" and "journalctl -xe" for details.

If I run "systemctl status zabbix-proxy.service" I get the following.

● zabbix-proxy.service - Zabbix Proxy
Loaded: loaded (/lib/systemd/system/zabbix-proxy.service; disabled; vendor pr
Active: activating (auto-restart) (Result: signal) since Fri 2018-04-06 09:56
Process: 2026 ExecStart=/usr/sbin/zabbix_proxy -c $CONFFILE (code=killed, sign

Apr 06 09:56:57 raspberrypi systemd[1]: zabbix-proxy.service: Unit entered faile
Apr 06 09:56:57 raspberrypi systemd[1]: zabbix-proxy.service: Failed with result
lines 1-7/7 (END)
● zabbix-proxy.service - Zabbix Proxy
Loaded: loaded (/lib/systemd/system/zabbix-proxy.service; disabled; vendor preset: enabled)
Active: activating (auto-restart) (Result: signal) since Fri 2018-04-06 09:56:57 UTC; 5s ago
Process: 2026 ExecStart=/usr/sbin/zabbix_proxy -c $CONFFILE (code=killed, signal=SEGV)

Apr 06 09:56:57 raspberrypi systemd[1]: zabbix-proxy.service: Unit entered failed state.
Apr 06 09:56:57 raspberrypi systemd[1]: zabbix-proxy.service: Failed with result 'signal'.

If I run "journalctl -xe" I get the following.

Apr 06 09:57:38 raspberrypi systemd[1]: Stopped Zabbix Proxy.
-- Subject: Unit zabbix-proxy.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit zabbix-proxy.service has finished shutting down.
Apr 06 09:57:38 raspberrypi systemd[1]: Starting Zabbix Proxy...
-- Subject: Unit zabbix-proxy.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit zabbix-proxy.service has begun starting up.
Apr 06 09:57:39 raspberrypi systemd[1]: zabbix-proxy.service: Control process exited, code=killed status=11
Apr 06 09:57:39 raspberrypi systemd[1]: Failed to start Zabbix Proxy.
-- Subject: Unit zabbix-proxy.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit zabbix-proxy.service has failed.
--
-- The result is failed.
Apr 06 09:57:39 raspberrypi systemd[1]: zabbix-proxy.service: Unit entered failed state.
Apr 06 09:57:39 raspberrypi systemd[1]: zabbix-proxy.service: Failed with result 'signal'.

I appreciate this may be down to configuration issues but having looked through the config files at both ends (proxy and server) as well as looking through the official documentation I cannot find an issue.

It may be worth mentioning that I'm running the sqlite database file in RAM (tmpfs). This is re-creating upon each boot as obviously it gets deleted when shutdown or rebooted.

Thanks in advance.

Systemsmb

I have the same symptoms. The only thing I have to add is that when I run the executable of zabbix-proxy I immediately get a segmentation fault before any logs are written. This was on a fresh install of the same version you listed.
Seems to be related to this months-old thread https://www.zabbix.com/forum/zabbix-...entation-fault

Edit: missed a letter

**aigars.kadikis** · 13-04-2018, 15:08

Originally posted by jluvs2ride

I have several Zabbix Proxies set up at remote locations. They are all running on Raspberry PIs with Raspbian. If the devices restart I have to manually restart the Proxy and Agent Services using;

sudo /usr/sbin/zabbix_agentd
sudo /usr/sbin/zabbix_proxy

I haven't been able to figure out how to get these to start automatically when the device restarts.

Is this possibly related to your issue?

You can manually install zabbix-proxy startup service:

Code:

#move to root
sudo su

#go to home dir
cd

#download source
wget http://downloads.sourceforge.net/project/zabbix/ZABBIX%20Latest%20Stable/3.4.8/zabbix-3.4.8.tar.gz

#extract source
tar -vzxf zabbix-3.4.8.tar.gz -C ~

#install zabbix-proxy startup script by taking zabbix-server base and substituting "server" with "proxy"
sed "s/server/proxy/g" ~/zabbix-3.4.8/misc/init.d/debian/zabbix-server > /etc/init.d/zabbix-proxy

You need to manually open file

Code:

vi /etc/init.d/zabbix-proxy

please include in file header also:

Code:

### BEGIN INIT INFO
# Provides:          zabbix-proxy
# Required-Start:    $remote_fs $network
# Required-Stop:     $remote_fs
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Should-Start:      mysql
# Should-Stop:       mysql
# Short-Description: Start zabbix-proxy daemon
### END INIT INFO

I believe in your case you need to replace the line:

Code:

DAEMON=/usr/local/sbin/${NAME}

with

Code:

DAEMON=/usr/sbin/${NAME}

Set file executable:

Code:

chmod +x /etc/init.d/zabbix-proxy

Reload systemd manager configuration

Code:

systemctl daemon-reload

Enable service:

Code:

systemctl enable zabbix-proxy

**bitmeup** · 17-04-2018, 01:24

Just to add that I compiled zabbix proxy (version 3.4.8) from sources on the same device that had the segmentation fault (when using the version mentioned above from the zabbix repository) and it seems to work as expected. The server on this topology is a Centos 7 VM. I was unable to use version 3.0 proxy (from the raspbian repository) on the raspberry pi, because the pi would not talk to the hosts being monitored by it.

I compiled it much like it is done in the link. I used mariadb instead.

**kloczek** · 17-04-2018, 02:09

Did you ever look on the zabbix logs which are usually in /var/log/zabbix?
Please stop compiling anything if you are not able to diagnose issues with generated binaries (SIGSEGV).

What ever you've already published it says that something is wrong with your system consistency or your zabbix setup (I'm betting that this is more likely cause) and has nothing to do with zabbix per se.

**bitmeup** · 17-04-2018, 10:33

Originally posted by kloczek

Did you ever look on the zabbix logs which are usually in /var/log/zabbix?
Please stop compiling anything if you are not able to diagnose issues with generated binaries (SIGSEGV).

What ever you've already published it says that something is wrong with your system consistency or your zabbix setup (I'm betting that this is more likely cause) and has nothing to do with zabbix per se.

I am not really sure who you are asking for logs since you did not quote anyone, but in my case and in the case of the post I linked in my first post on this thread the proxy logs at /var/log do not have a single line in them and at least I made sure to increase the logging level (to debug) and made sure the path of the log files was correct in the proxy configuration.

Perhaps you want to be more clear about the troubleshooting process for segmentation faults in a way that it helps in this context.

Ad Widget

Unable to start zabbix-proxy service on Raspbian

Unable to start zabbix-proxy service on Raspbian

Comment

Comment

Comment

Comment

Comment

Comment

Comment