1 Title: Reworked Livestatus Proxy to be more scalable
10 The livestatus proxy daemon has been reworked to use a multi process
11 architecture. It now has a master process that mainly cares about
12 monitoring the site processes. Each connected site has an own subprocess
13 that manages all channels to this site and the clients that use these
14 channels to communicate with the sites.
16 When you have a look at ps/top you should see something like this:
19 OMD[heute]:~$ ps -ef | grep liveproxyd
20 UID PID PPID C STIME TTY TIME CMD
21 heute 9261 1 0 11:40 ? 00:00:00 liveproxyd[master]
22 heute 9262 9261 0 11:40 ? 00:00:00 liveproxyd[heute_slave_1]
23 heute 9263 9261 0 11:40 ? 00:00:00 liveproxyd[heute_slave_2]
26 As you can may see there is the master process that has the process <tt>1</tt>
27 as parent process. The site processes have the master as parent.
29 When one site process terminates for some reason the master will restart it.
30 When the master is terminated all site processes will terminate too. In case
31 of a restart or config reload the master will restart itself and stop
32 all site processes and restart them again.
34 With this change the load of the livestatus proxy will now spread over
37 Side note: There is a new global setting <i>Logging of the Livestatus Proxy</i>
38 that can be used to control the detail level of the log entries written to the
39 <tt>var/log/liveproxyd.log</tt> log file. In case you experience any issues
40 with the livestatus proxy daemon take a look at this log file and maybe increase
41 the log level to get more details.