Ad Widget

Collapse

zabbix 6 PROXY cannot start

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • yusewy
    Junior Member
    • Feb 2022
    • 5

    #1

    zabbix 6 PROXY cannot start

    hi guys,

    I have setup zabbix 6 proxy on centos8, when I start the proxy service, the log shows that "cannot connect to RTC service: Cannot connect to service "rtc": [13] Permission denied.", I have searched on google, but no any information about this, can someone help me on this issue? Thanks in advance!
  • mattalvis
    Junior Member
    • Dec 2020
    • 3

    #2
    I am experiencing the same issues. The zabbix 6 documentation does not explaing Proxy configuration(s) very well, at all, imo

    Comment

    • dstrickler
      Junior Member
      • Mar 2022
      • 10

      #3
      Sorry to cross-post, but in my post (https://www.zabbix.com/forum/zabbix-...rsion-of-proxy) I am looking for the 6.0 proxy software, and can't find it in the downloads section on Zabbix's website. Is there a better place to find it?

      TIA,

      Dave

      Comment


      • yusewy
        yusewy commented
        Editing a comment
        why you don't run "yum install zabbix-proxy-mysql" to install proxy?
    • mattalvis
      Junior Member
      • Dec 2020
      • 3

      #4
      Originally posted by yusewy
      hi guys,

      I have setup zabbix 6 proxy on centos8, when I start the proxy service, the log shows that "cannot connect to RTC service: Cannot connect to service "rtc": [13] Permission denied.", I have searched on google, but no any information about this, can someone help me on this issue? Thanks in advance!
      I have created https://support.zabbix.com/browse/ZBX-20708 to hopefully help escalate this issue. rtc is not a package/service that is include within RHEL8 that I am aware of. The time daemon is "chronyd", and possibly ntpdate depending on customer preference. It appears "rtc" is an old dependency that was need in older versions of zabbix from my digging, but not sure here. This instance of RHEL8 I am testing with is pretty vanilla - clean install, nothing special, although is running in AWS (EC2) - so not sure if that is creating any issues.

      Comment

      Working...