Ad Widget

Collapse

Unable to get Agent running on Server

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • GrumpyZAF
    Junior Member
    • Nov 2020
    • 1

    #1

    Unable to get Agent running on Server

    I am very new to zabbix and I am trying to get it running on an Azure VM running Ubuntu 18.04.

    Managed to get everything setup and installed, on the front end I am unable to connect to the server.

    Here is the snippets from the log files.

    Server

    Code:
    11110:20201119:144604.149 Starting Zabbix Server. Zabbix 5.0.5 (revision eaa427cf19).
    11110:20201119:144604.149 ****** Enabled features ******
    11110:20201119:144604.149 SNMP monitoring: YES
    11110:20201119:144604.149 IPMI monitoring: YES
    11110:20201119:144604.149 Web monitoring: YES
    11110:20201119:144604.149 VMware monitoring: YES
    11110:20201119:144604.149 SMTP authentication: YES
    11110:20201119:144604.149 ODBC: YES
    11110:20201119:144604.149 SSH support: YES
    11110:20201119:144604.149 IPv6 support: YES
    11110:20201119:144604.149 TLS support: YES
    11110:20201119:144604.149 ******************************
    11110:20201119:144604.149 using configuration file: /etc/zabbix/zabbix_server.conf
    11110:20201119:144604.159 [Z3001] connection to database 'zabbix' failed: [1045] Access denied for user 'zabbix'@'localhost' (using password: NO)
    11110:20201119:144604.159 database is down: reconnecting in 10 seconds
    Agent

    Code:
    43600:20201119:103742.378 Starting Zabbix Agent [Zabbix server]. Zabbix 5.0.5 (revision eaa427cf19).
    43600:20201119:103742.378 **** Enabled features ****
    43600:20201119:103742.378 IPv6 support: YES
    43600:20201119:103742.378 TLS support: YES
    43600:20201119:103742.378 **************************
    43600:20201119:103742.378 using configuration file: /etc/zabbix/zabbix_agentd.conf
    43600:20201119:103742.379 agent #0 started [main process]
    43605:20201119:103742.380 agent #5 started [active checks #1]
    43604:20201119:103742.381 agent #4 started[listener #3]
    43603:20201119:103742.382 agent #3 started[listener #2]
    43602:20201119:103742.389 agent #2 started[listener #1]
    43605:20201119:103742.394 active check configuration update from [127.0.0.1:10051] started to fail (cannot connect to [[127.0.0.1]:10051]: [111] Connection refused)
    43601:20201119:103742.395 agent #1 started [collector]
    43600:20201119:111539.625 Got signal [signal:15(SIGTERM),sender_pid:62415,sender_uid:111 ,reason:0]. Exiting ...
    43600:20201119:111539.629 Zabbix Agent stopped. Zabbix 5.0.5 (revision eaa427cf19).
    Any assistance would be highly appreciated

    much <3
  • tim.mooney
    Senior Member
    • Dec 2012
    • 1427

    #2
    You have two separate (unrelated) problems:

    Originally posted by GrumpyZAF
    Code:
    11110:20201119:144604.159 [Z3001] connection to database 'zabbix' failed: [1045] Access denied for user 'zabbix'@'localhost' (using password: NO)
    11110:20201119:144604.159 database is down: reconnecting in 10 seconds
    Your zabbix_serverd process cannot access the database. You need to review the database setup, make certain you've followed all the steps for setting up and that the /etc/zabbix/zabbix_server.conf has the right configuration for connecting to your database. If the zabbix_serverd processes can't connect to the database, not much is going to work.

    Originally posted by GrumpyZAF
    Agent

    Code:
    43605:20201119:103742.394 active check configuration update from [127.0.0.1:10051] started to fail (cannot connect to [[127.0.0.1]:10051]: [111] Connection refused)
    43601:20201119:103742.395 agent #1 started [collector]
    43600:20201119:111539.625 Got signal [signal:15(SIGTERM),sender_pid:62415,sender_uid:111 ,reason:0]. Exiting ...
    43600:20201119:111539.629 Zabbix Agent stopped. Zabbix 5.0.5 (revision eaa427cf19).
    That says that your agent can't get a list of what active checks it should be running because the zabbix_serverd has the first problem (described above). Then, the agent exits with SIGTERM, which is probably intentional, but I would have to look at the code to be certain.

    Get your zabbix_serverd fixed up so that it's running and working, then restart your agent to see if the problem goes away once the server is functional

    Comment

    Working...