The issue I describe in this blog are related to my XenServer, my lab at home, be very careful with the modification I explain if you plan to make this change in your own environment... As always, do it on a test environment before please ! Since last week and my XenServer @ home crash, I chose to install the latest XenServer version, 5.6 FP1 (more info here) to try out some new features like Intellicache / open vSwitch / VM Protection and Recovery and the self service portal. The installation was as smooth as usual, just one question more than the previous version about the installation of Intellicache. I've been able to reinstall all my VMs, configure everything and check all these new features. The only issue was my file system was running out of space very very very quickly... I didn't understand why at first because I'm not that skilled with XenServer with command line stuff but I needed to find out what was happening. The first place to check when something wrong is going on, are the log files, you can find XenServer logs files here : /var/log , and the size of my log files were huge ! in less than 24hour I had 3 rotations of log on kern.log and messages log files... To buy me some time and allow me to continue to connect to the XenServer with XenCenter, I made some change in the rotation log configuration file /etc/logrotate.conf : I made the following change, rotate value was 20 I changed it to 5, I activated the compression of log file archives. It did give me some more time to work on this weird issue but not enough, in less than 12 hours my file system was full again... XenCenter wasn't able to connect and the xsconsole command line wasn't working as well. The only way to recover the interface was to kill the xapi process and restart it by using : xe-toolstack-restart command line (I needed to free as much space as possible before). Then I've been able to use XenCenter and xsconsole. I got the message bellow after all these troubleshooting stuffs but still no clue why my log files were becoming so big so quickly... Of course I looked the log file and I saw : Ok... I didn't catch everything, I knew it was something about network but I…