Ad Widget

Collapse

1.8.3 - Problem with key log[]

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Vincent60
    Junior Member
    • Dec 2007
    • 4

    #1

    1.8.3 - Problem with key log[]

    Hi everybody,

    I encountered a problem with a item using the key log[].
    Agent and server are both 1.8.3.

    My item is configured like this:
    Type: ZABBIX agent (active)
    Key: log["path_log_file",,"UTF-8",100]
    Type of Information: Log
    Interval: 10 sec

    The log can be accessed by all. (777)
    In zabbix_agentd.conf, the hostname is the same as in the frontend.

    Active checks are enabled:
    zabbix_agentd.conf:
    #DisableActive=1

    But I don't see any data in Latest data.
    Does somebody knows how to solve this problem?

    Thank you for help.
  • EnigmA-X
    Senior Member
    Zabbix Certified Specialist
    • Oct 2010
    • 116

    #2
    Are you receiving other values from this host properly?

    Check your zabbix_agentd.log file to locate any issues. Also, you can try to become the zabbix user (do 'su - zabbix' as root) and check if you can read the targeted logfile.

    Please share the outcome with us

    Comment

    • Vincent60
      Junior Member
      • Dec 2007
      • 4

      #3
      Hello,
      Thanks a lot for your reply.
      Yes, I am receiving other values from this host.

      I don't see any issues in the zabbix_agentd.log:
      Code:
      24637:20101105:140728.422 Zabbix Agent started. Zabbix 1.8.3 (revision 13936).
       24638:20101105:140728.435 zabbix_agentd collector started
       24639:20101105:140728.435 zabbix_agentd listener started
       24640:20101105:140728.436 zabbix_agentd listener started
       24641:20101105:140728.436 zabbix_agentd listener started
       24642:20101105:140728.436 zabbix_agentd active check started [x64lmwbiejw.hp.erp.sncf.fr:10051]
      I tried to set the DebugLevel to 4, but I don't see any info of this item.
      My zabbix user (His name is not zabbix, perhaps my problem comes from this) has read access to the targeted log file.

      Comment

      Working...