I want to add that this never happened me before with 2.6.32-25-server or earlier.
This happened me for first time after upgrading to 2.6.32-26-server a few days ago (only happened once for the moment)
Perhaps is a bug introduced in 2.6.32-26-server
I want to add that this never happened me before with 2.6.32-25-server or earlier.
This happened me for first time after upgrading to 2.6.32-26-server a few days ago (only happened once for the moment)
Perhaps is a bug introduced in 2.6.32-26-server