Difference between revisions of "UBC Monitoring"
(New page: Monitoring the /proc/user_beancounters to see if any VEs are hitting limits is an important part of managing an OpenVZ installation. VEs that are hitting key limits can have applications m...) |
m |
||
| Line 1: | Line 1: | ||
| − | Monitoring | + | Monitoring /proc/user_beancounters to see if any VEs are hitting limits is an important part of |
managing an OpenVZ installation. VEs that are hitting key limits can have applications malfunction in strange | managing an OpenVZ installation. VEs that are hitting key limits can have applications malfunction in strange | ||
ways that can only be diagnosed by realising that it is a UBC configuration issue. | ways that can only be diagnosed by realising that it is a UBC configuration issue. | ||
| Line 6: | Line 6: | ||
This script, when run periodically (using cron) will detect changes in the failcnt field of /proc/user_beancounters | This script, when run periodically (using cron) will detect changes in the failcnt field of /proc/user_beancounters | ||
| − | [[http://img.cs.montana.edu/linux/openvz/failcnt.py]] | + | [[failcnt.py http://img.cs.montana.edu/linux/openvz/failcnt.py]] |
[[Category: Troubleshooting]] | [[Category: Troubleshooting]] | ||
Revision as of 02:11, 9 March 2008
Monitoring /proc/user_beancounters to see if any VEs are hitting limits is an important part of managing an OpenVZ installation. VEs that are hitting key limits can have applications malfunction in strange ways that can only be diagnosed by realising that it is a UBC configuration issue.
This script, when run periodically (using cron) will detect changes in the failcnt field of /proc/user_beancounters
failcnt.py http://img.cs.montana.edu/linux/openvz/failcnt.py
