Ad Widget

Collapse

Zabbix-java-gateway won't start after update

Collapse
This topic has been answered.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Mitchell-Zabbix
    Junior Member
    • Feb 2023
    • 10

    #1

    Zabbix-java-gateway won't start after update

    Hello all

    My zabbix-java-gateway.service does not seem to start after the latest update.
    I can't seem to get a lot of information out of the logging, where else should I be looking?

    Zabbix Java Gateway version: 6.0.21 (revision 9624968c6b8)

    Systemctl

    Code:
     zabbix-java-gateway.service - Zabbix Java Gateway
         Loaded: loaded (/lib/systemd/system/zabbix-java-gateway.service; enabled; vendor preset: enabled)
         Active: failed (Result: timeout) since Fri 2023-09-08 13:03:37 CEST; 49min ago
        Process: 8185 ExecStart=/usr/sbin/zabbix_java_gateway_startup (code=exited, status=143)
            CPU: 7.951s
    
    Sep 08 13:02:06 hostname systemd[1]: Starting Zabbix Java Gateway...
    Sep 08 13:03:36 hostname systemd[1]: zabbix-java-gateway.service: start operation timed out. Terminating.
    Sep 08 13:03:37 hostname systemd[1]: zabbix-java-gateway.service: Failed with result 'timeout'.
    Sep 08 13:03:37 hostname systemd[1]: Failed to start Zabbix Java Gateway.
    Sep 08 13:03:37 hostname systemd[1]: zabbix-java-gateway.service: Consumed 7.951s CPU time.​[B][/B]
    Journalctl

    Code:
    Sep 08 12:50:01 hostname sudo[6192]: usr : TTY=pts/0 ; PWD=/etc/zabbix ; USER=root ; COMMAND=/usr/bin/systemctl status zabbix-java-gateway.service
    Sep 08 12:54:43 hostname sudo[7067]: usr : TTY=pts/0 ; PWD=/etc/zabbix ; USER=root ; COMMAND=/usr/bin/systemctl restart zabbix-java-gateway.service
    ░░ Subject: A start job for unit zabbix-java-gateway.service has begun execution
    ░░ A start job for unit zabbix-java-gateway.service has begun execution.
    Sep 08 12:56:13 hostname systemd[1]: zabbix-java-gateway.service: start operation timed out. Terminating.
    Sep 08 12:56:14 hostname systemd[1]: zabbix-java-gateway.service: Failed with result 'timeout'.
    ░░ The unit zabbix-java-gateway.service has entered the 'failed' state with result 'timeout'.
    ░░ Subject: A start job for unit zabbix-java-gateway.service has failed
    ░░ A start job for unit zabbix-java-gateway.service has finished with a failure.
    Sep 08 12:56:14 hostname systemd[1]: zabbix-java-gateway.service: Consumed 8.104s CPU time.
    ░░ The unit zabbix-java-gateway.service completed and consumed the indicated resources.​
  • Answer selected by Mitchell-Zabbix at 05-12-2023, 10:42.
    Mitchell-Zabbix
    Junior Member
    • Feb 2023
    • 10

    The issue is resolved.

    Resolved by

    In my /etc/zabbix/* folder I had 2 config files after the update: 'zabbix_java_gateway.conf' & 'zabbix_java_gateway.conf.dpkg-dist'.
    I've created a back-up of 'zabbix_java_gateway.conf', removed it and renamed the dpkg file to 'zabbix_java_gateway.conf'.

    I had to readjust the port & active pollers configuration, but after this my gateway seemed to start.
    The data is also coming in from my hosts that are monitored by jmx.

    Config files compared

    Code:
    < # It is sourced by startup.sh and shutdown.sh scripts.
    ---
    > # It is sourced by "/etc/init.d/zabbix-java-gateway".
    21d20
    < #     If omitted, Zabbix Java Gateway is started as a console application.
    26,27c25
    <
    < PID_FILE="/var/run/zabbix/zabbix_java_gateway.pid"
    ---
    > # PID_FILE="/run/zabbix/zabbix_java_gateway.pid"
    50a49,54
    >
    > ### JVM options (passed to /usr/bin/java).
    > #
    > # Mandatory: no
    > #
    > # JAVA_OPTIONS="-Xmx256m"​[B][/B]

    Only the PID_FILE seems different here.

    Comment

    • Mitchell-Zabbix
      Junior Member
      • Feb 2023
      • 10

      #2
      The issue is resolved.

      Resolved by

      In my /etc/zabbix/* folder I had 2 config files after the update: 'zabbix_java_gateway.conf' & 'zabbix_java_gateway.conf.dpkg-dist'.
      I've created a back-up of 'zabbix_java_gateway.conf', removed it and renamed the dpkg file to 'zabbix_java_gateway.conf'.

      I had to readjust the port & active pollers configuration, but after this my gateway seemed to start.
      The data is also coming in from my hosts that are monitored by jmx.

      Config files compared

      Code:
      < # It is sourced by startup.sh and shutdown.sh scripts.
      ---
      > # It is sourced by "/etc/init.d/zabbix-java-gateway".
      21d20
      < #     If omitted, Zabbix Java Gateway is started as a console application.
      26,27c25
      <
      < PID_FILE="/var/run/zabbix/zabbix_java_gateway.pid"
      ---
      > # PID_FILE="/run/zabbix/zabbix_java_gateway.pid"
      50a49,54
      >
      > ### JVM options (passed to /usr/bin/java).
      > #
      > # Mandatory: no
      > #
      > # JAVA_OPTIONS="-Xmx256m"​[B][/B]

      Only the PID_FILE seems different here.

      Comment

      Working...