ustcweizhou opened a new pull request #4384:
URL: https://github.com/apache/cloudstack/pull/4384


   ## Description
   <!--- Describe your changes in detail -->
   
   when upgrade to cloudstack 4.14 or 4.15, there is no process ends with 
"/run/haproxy.pid" after reload haproxy.
   so haproxy is reloaded -> restarted -> reloaded -> restarted -> and so on
   
   After restarting haproxy
   ```
   root@r-2040-VM:~# ps aux |grep /usr/sbin/haproxy
   root     24894  0.3  1.3  20492 13352 ?        Ss   09:14   0:00 
/usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid
   root     24895  0.1  1.1  22332 11372 ?        Ss   09:14   0:00 
/usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid
   ```
   
   After reloading haproxy
   ```
   root@r-2040-VM:~# systemctl reload haproxy
   root@r-2040-VM:~# ps aux |grep /usr/sbin/haproxy
   root     24894  0.0  1.3  20492 13300 ?        Ss   09:14   0:00 
/usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -sf 24895
   root     26694  0.0  0.9  22196  9488 ?        Ss   09:16   0:00 
/usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -sf 24895
   ```
   
   so use 'grep' to find if haproxy is running.
   
   
   <!-- For new features, provide link to FS, dev ML discussion etc. -->
   <!-- In case of bug fix, the expected and actual behaviours, steps to 
reproduce. -->
   
   <!-- When "Fixes: #<id>" is specified, the issue/PR will automatically be 
closed when this PR gets merged -->
   <!-- For addressing multiple issues/PRs, use multiple "Fixes: #<id>" -->
   <!-- Fixes: # -->
   
   ## Types of changes
   <!--- What types of changes does your code introduce? Put an `x` in all the 
boxes that apply: -->
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to change)
   - [ ] New feature (non-breaking change which adds functionality)
   - [X] Bug fix (non-breaking change which fixes an issue)
   - [ ] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   
   ## Screenshots (if appropriate):
   
   ## How Has This Been Tested?
   <!-- Please describe in detail how you tested your changes. -->
   <!-- Include details of your testing environment, and the tests you ran to 
-->
   <!-- see how your change affects other areas of the code, etc. -->
   
   
   <!-- Please read the 
[CONTRIBUTING](https://github.com/apache/cloudstack/blob/master/CONTRIBUTING.md)
 document -->
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to