XenServer Xensource.log continues to grow

Reprint: http://blog.sina.com.cn/s/blog_4ca83f830100xded.html

Believe that a lot of people are xenserver log filled with disk space, causing the problem of the final machine hangs, I met 2 times (once the pool master hung off, No. 200 people 1 hours can not work).

A few days ago, three pools of pool master also appeared/var/log/xensource.log*, almost 1 hours will eat 150MB of disk space

This 2GB free space, a day will be filled, Pool master hangs off but the most deadly, more than 500 virtual machines will be all hung up!

The XenSource log is temporarily stopped by the following method

1, modify the/etc/xensource/log.conf, comment out the following 4 lines (preceded by a # number)

2, restart the service before the log is continuously incremented, and then restart the corresponding daemon and XAPI service with Xe-toolstack-restart

3. Xensource.log* stopped growing

Observe the log content is the program exception debug information, opened a case, now tasted no conclusion.

------------------------------

[20110913t14:49:03.922z|debug|hqcnctxxsd022l|2627576 Inet_rpc|dispatch:host.get_uuid D:08622df260d0|backtrace] Raised at Pervasiveext.ml:26.22-25, server_helpers.ml:152.10-106, server.ml:10336.19-171, Server_ Helpers.ml:118.4-7

[20110913t14:49:03.962z|debug|hqcnctxxsd022l|2627576 Inet_rpc|host.get_uuid D:f8d52f8467ec|xapi] Raised at db_cache_types.ml:75.27-76, db_cache_types.ml:118.2-40, pervasiveext.ml:22.2-9

[20110913t14:49:03.962z|debug|hqcnctxxsd022l|2627576 Inet_rpc|host.get_uuid D:f8d52f8467ec|backtrace] Raised at Pervasiveext.ml:26.22-25, db_actions.ml:4271.26-67, rbac.ml:227.16-23, rbac.ml:236.10-15 Server_helpers.ml:74.11-23

[20110913t14:49:03.962z|debug|hqcnctxxsd022l|2627576 Inet_rpc|host.get_uuid D:f8d52f8467ec|dispatcher] Server_helpers.exec Exception_handler:got exception handle_invalid: [Host; Opaqueref:null]

[20110913t14:49:03.962z|debug|hqcnctxxsd022l|2627576 Inet_rpc|host.get_uuid D:f8d52f8467ec|dispatcher] Raised at string.ml:150.25-34-stringext.ml:108.13-29

[20110913t14:49:03.962z|debug|hqcnctxxsd022l|2627576 Inet_rpc|host.get_uuid D:f8d52f8467ec|backtrace] Raised at string.ml:150.25-34-stringext.ml:108.13-29

[20110913t14:49:03.962z|debug|hqcnctxxsd022l|2627576 Inet_rpc|host.get_uuid D:f8d52f8467ec|xapi] Raised at Server_helpers.ml:92.14-15-pervasiveext.ml:22.2-9

[20110913t14:49:03.962z|debug|hqcnctxxsd022l|2627576 Inet_rpc|host.get_uuid D:f8d52f8467ec|xapi] Raised at pervasiveext.ml:26.22-25-pervasiveext.ml:22.2-9

-------------------------------

You can use the DU command to view the amount of space in subdirectories under the current directory

If you use MB as the unit, you can use the command du-hm--max-depth=1

Sometimes the log grows faster than the messages or daemon logs under/var/log, and you can stop them by using service syslog stop to avoid running out of space.

I usually keep the first 2 logs when I delete a log (such as./messages is the log that is currently being written and./messages.1 previous archived logs), but if the current log is large to delete, you can rename them first and then service syslog start again To automatically generate the current log, just like this:

XenServer Xensource.log continues to grow