[ZBXNEXT-816] Support of demand reload of a configuration cache data Created: 2011 Jun 15  Updated: 2011 Jul 12  Resolved: 2011 Jul 11

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Proxy (P), Server (S)
Affects Version/s: 1.8.6
Fix Version/s: 1.8.6

Type: New Feature Request Priority: Major
Reporter: Alexander Vladishev Assignee: Aleksandrs Saveljevs
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Support of forced reload of a configuration cache for Zabbix server and proxy will be introduced.

 Comments   
Comment by Aleksandrs Saveljevs [ 2011 Jun 15 ]

Duplicates feature #2 of ZBXNEXT-416.

Comment by Alexander Vladishev [ 2011 Jun 20 ]

Available in the development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-816

Comment by richlv [ 2011 Jun 22 ]

<Rich> how will this be exposed to users ? what would be a one-sentence overview of how the runtime signal is passed ?

<asaveljevs> When you do "zabbix_server --runtime-control config_cache_reload", this process parses zabbix_server PID file to find out the parent Zabbix process. Signal SIGUSR1 along with some information is sent to the parent process. Parent process analyses the information and determines to which child process the same signal should be sent. Then the parent process sends SIGUSR1 to the configuration syncer process.

Comment by Aleksandrs Saveljevs [ 2011 Jul 07 ]

Available in pre-1.8.6 in r20454.

Comment by Aleksandrs Saveljevs [ 2011 Jul 07 ]

Reopening: if configuration cache reload is requested for passive proxy, the signal will not be sent to configuration syncer process (because it is not started), but to datasender process. Nothing will actually happen, but a user will get a false message indicating success.

Comment by Aleksandrs Saveljevs [ 2011 Jul 11 ]

If a passive proxy receives a signal for reloading the configuration cache, it will now write a warning message into the log file. A user will still get the message "command sent successfully".

Comment by Oleksii Zagorskyi [ 2011 Jul 12 ]

It seems need to reopen.

  1. cat /etc/redhat-release
    CentOS release 5.5 (Final)
  1. zabbix_server -V
    Zabbix Server v1.9.5 (revision 20509) (18 May 2011)
    Compilation time: Jul 12 2011 01:26:28
  1. ps ax | grep zabbix
    2043 ? SN 0:00 /usr/local/sbin/zabbix_agentd
    2045 ? SN 1:22 /usr/local/sbin/zabbix_agentd
    2046 ? SN 2:20 /usr/local/sbin/zabbix_agentd
    2047 ? SN 2:17 /usr/local/sbin/zabbix_agentd
    2048 ? SN 2:21 /usr/local/sbin/zabbix_agentd
    2049 ? SN 0:01 /usr/local/sbin/zabbix_agentd
    10599 ? SN 0:00 /usr/local/sbin/zabbix_server
    10604 ? RN 0:00 /usr/local/sbin/zabbix_server
    10606 ? SN 0:00 /usr/local/sbin/zabbix_server
    10607 ? SN 0:00 /usr/local/sbin/zabbix_server
    10608 ? SN 0:00 /usr/local/sbin/zabbix_server
    10609 ? SN 0:00 /usr/local/sbin/zabbix_server
    10610 ? SN 0:00 /usr/local/sbin/zabbix_server
    10611 ? SN 0:00 /usr/local/sbin/zabbix_server
    10612 ? SN 0:00 /usr/local/sbin/zabbix_server
    10614 ? SN 0:00 /usr/local/sbin/zabbix_server
    10616 ? SN 0:00 /usr/local/sbin/zabbix_server
    10617 ? SN 0:00 /usr/local/sbin/zabbix_server
    10619 ? SN 0:00 /usr/local/sbin/zabbix_server
    10621 ? SN 0:00 /usr/local/sbin/zabbix_server
    10623 ? SN 0:00 /usr/local/sbin/zabbix_server
    10625 ? RN 0:02 /usr/local/sbin/zabbix_server
    10627 ? SN 0:00 /usr/local/sbin/zabbix_server
    10628 ? SN 0:00 /usr/local/sbin/zabbix_server
    10631 ? SN 0:00 /usr/local/sbin/zabbix_server
    10632 ? SN 0:00 /usr/local/sbin/zabbix_server
    10634 ? SN 0:00 /usr/local/sbin/zabbix_server
    10636 ? SN 0:00 /usr/local/sbin/zabbix_server
    10638 ? SN 0:00 /usr/local/sbin/zabbix_server
    10639 ? SN 0:00 /usr/local/sbin/zabbix_server
    10642 ? SN 0:00 /usr/local/sbin/zabbix_server
    10644 ? SN 0:00 /usr/local/sbin/zabbix_server
  1. zabbix_server -c /etc/zabbix/zabbix_server.conf -R config_cache_reload
    cannot send command to PID [105994]: [3] No such process
Comment by Aleksandrs Saveljevs [ 2011 Jul 12 ]

This is highly interesting. What are the contents of your PID file?

Comment by Oleksii Zagorskyi [ 2011 Jul 12 ]

because zabbix_server was restarted, i type again many of lines

  1. ps ax | grep zabbix_server
    13697 ? SN 0:00 /usr/local/sbin/zabbix_server
    13702 ? SN 0:08 /usr/local/sbin/zabbix_server
    13704 ? SN 0:40 /usr/local/sbin/zabbix_server
    13705 ? SN 0:40 /usr/local/sbin/zabbix_server
    13706 ? SN 0:39 /usr/local/sbin/zabbix_server
    13707 ? SN 0:39 /usr/local/sbin/zabbix_server
    13708 ? SN 0:39 /usr/local/sbin/zabbix_server
    13709 ? SN 0:11 /usr/local/sbin/zabbix_server
    13710 ? SN 0:00 /usr/local/sbin/zabbix_server
    13712 ? SN 0:00 /usr/local/sbin/zabbix_server
    13713 ? SN 0:00 /usr/local/sbin/zabbix_server
    13714 ? SN 0:00 /usr/local/sbin/zabbix_server
    13715 ? SN 0:00 /usr/local/sbin/zabbix_server
    13716 ? SN 0:13 /usr/local/sbin/zabbix_server
    13722 ? SN 0:04 /usr/local/sbin/zabbix_server
    13724 ? SN 2:04 /usr/local/sbin/zabbix_server
    13726 ? SN 0:39 /usr/local/sbin/zabbix_server
    13727 ? SN 0:08 /usr/local/sbin/zabbix_server
    13728 ? SN 0:49 /usr/local/sbin/zabbix_server
    13729 ? SN 0:20 /usr/local/sbin/zabbix_server
    13730 ? SN 0:23 /usr/local/sbin/zabbix_server
    13739 ? SN 0:24 /usr/local/sbin/zabbix_server
    13741 ? SN 0:20 /usr/local/sbin/zabbix_server
    13743 ? SN 0:08 /usr/local/sbin/zabbix_server
    13745 ? SN 0:02 /usr/local/sbin/zabbix_server
    13747 ? SN 0:04 /usr/local/sbin/zabbix_server
  1. cat /tmp/zabbix_server.pid
    13697
    (yes - only 5 numbers !!!)
  1. zabbix_server -c /etc/zabbix/zabbix_server.conf -R config_cache_reload
    cannot send command to PID [136974]: [3] No such process
Comment by Aleksandrs Saveljevs [ 2011 Jul 12 ]

Thanks, Oleksiy! We had a problem with reading PIDs. Fixed in development branch in r20527.

Comment by Alexander Vladishev [ 2011 Jul 12 ]

Tested successfully.

Comment by Oleksii Zagorskyi [ 2011 Jul 12 ]

yes, r20527 helps for CentOS

Comment by Aleksandrs Saveljevs [ 2011 Jul 12 ]

Fixed in pre-1.8.6 in r20530.

Generated at Sat Apr 20 17:55:35 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.