Ad Widget

Collapse

Arch Linux agent

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Gokiwi64
    Member
    • Jun 2020
    • 36

    #1

    Arch Linux agent

    Hi,

    I am trying to install the agent on an Arch Linux based machine. The problem I have is that I cannot tell if the agent is started (Im guessing not as I cannot telnet to port 10050 from the server).

    How do I check the status and how do I start the agent on Arch Linux ?

    Regards
  • Gokiwi64
    Member
    • Jun 2020
    • 36

    #2
    I should add that I am using sudo systemctl start zabbix-agent - After prompting for my password it returns to the terminal $ prompt - GUFW is not running in any profile.

    Comment

    • Gokiwi64
      Member
      • Jun 2020
      • 36

      #3
      Still not working ! - Nobody installed the agent on Arch Linux ?

      Comment

      • tim.mooney
        Senior Member
        • Dec 2012
        • 1427

        #4
        I'm not familiar with Arch, but you've indicated that it uses systemd, so that gives us something to try.

        First, though, I would use the netstat command with a particular bundle of options, like this:

        Code:
        $ sudo netstat -tnlp | egrep :10050
        tcp 0 0 0.0.0.0:10050 0.0.0.0:* LISTEN 1068/zabbix_agentd
        tcp6 0 0 :::10050 :::* LISTEN 1068/zabbix_agentd
        That should show at least one line of output (mine shows 2 because the agent is also listening on the IPv6-related addresses).

        If it doesn't show any output, then nothing is listening on port 10050, which is the default agent port.

        If it's not running, then the thing to do is ask systemd why, in the form of

        Code:
        sudo systemctl status -l zabbix-agentd.service
        The '-l' (long) output should show any error messages from the startup. Between that and the contents of the zabbix_agentd.log file (probably in /var/log/zabbix/ ), hopefully there will be a strong clue as to what the problem is.

        Comment

        • Gokiwi64
          Member
          • Jun 2020
          • 36

          #5
          Sorted !! - Thanks for the pointers Tim. It was all installed properly and I had configured the .conf correctly but I hadn't set it to run on reboot, so it just needed enabling. (The joys of using Ubuntu and Arch with little or no (more no) Linux experience).

          Comment

          Working...