Forum Discussion
CirrusRelation between mcpd and linux
Employeemcpd is one of several F5 daemons/processes that run on the linux host to make up TMOS. The mcpd process handles configuration information and communication between TMM (the primary F5 process that does all the traffic processing) and the rest of the processes on the system. The following article describes all the daemons/processes running on a BIG-IP system. It includes F5 developed TMOS processes such as sod, bigd, mcpd, and TMM as well as 3rd party processes such as alertd and httpd:
K05645522: BIG-IP daemons (13.x)
Doing an AskF5 Search with keywords "mcpd" and "uptime" and the article filter of "Known Issue" resulted in the following KI article that applies to 12.0.0 and 11.x:
K39500465: Displaying virtual server statistics may cause an mcpd process memory leak
You can search just for "uptime" with the "Known Issue" filter to see all the uptime related bugs.
NoctilucentHi Adi,
If I may add, yes there were long uptime bugs in the older versions (below 10.x). So once it had crossed the threshold uptime period, it was advised to go for scheduled stability reboot.
Above 10.2.x versions, I haven't seen any uptime limit issues. But its always good to do scheduled reboot after a certain threshold period.
The threshold can differ as per needs, sometimes it could be 6months or 1 year.
But as you know, the servers are capable of running up for more than 5years without issues.
