Usage logs not deleted on SharePoint 2010

In this case SharePoint 2010 server was running on Windows Server 2008 R2 and was filling up disk space with usage logs. Default location for usage logs is in %programfiles%\common files\Microsoft Shared\Web Server Extensions\14\LOGS. Usage logs were not deleted because they were locked by the SharePoint Timer Service. Restarting the service will release the locks and usage files will be deleted.
Because of this behavior you will also have event id 6398 in Application Log from source SharePoint Foundation with following description:

The Execute method of job definition Microsoft.SharePoint.Administration.SPTimerRecycleJobDefinition  

The timer service was not recycled because the following jobs were still running: Microsoft SharePoint Foundation Usage Data Import

The reason for this behavior is the following update KB2882822.Uninstalling the update will fix the locking usage files issue.
This behavior is also fixed with SharePoint 2010 December 2013 CU KB2849971.
 

Error Event ID 1511 on SharePoint 2010

In this post I'll write about how I've resolved the following error event with id 1511 from User Profile Service source with following description on SharePoint 2010 server :

Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.

Several IIS application pools were running with regular domain user account on this SharePoint 2010 server. For some of these application pools identities local profile was not created instead temporary profile was used. Domain user account with temporary profile created for that application pool is logged in the same event id 1511 under user section.
Fixing this behavior is simple, and the point is to create the user's profile before application pool is started. I guess, the easiest way to achieve that, is to start the command prompt under that "problematic" domain user account.
So, after stopping the SharePoint services and IIS, and deleting the temp profile from C:\Users folder, I ran the runas command:

runas /user:domain\apooluser cmd

After typing the correct password for that domain user, command prompt will open under user's context and local profile will be created for that user in C:\Users folder. Reboot the server and error event with 1511 id will not be log since IIS application pool will start and will use the previously created local profile in C:\Users folder.