rsyslog consumes excessive memory when forwarding logs with compression
Issue:
rsyslog consumed growing amounts of memory when forwarding over TCP with compression enabled.
Cause:
The compression flag causes the rsyslog process to allocate, and never release, memory. I have not determined root cause but the likely culprits are zlib or TLS (both involved when compression is enabled in this situation).
Resolution:
Do not use compression when forwarding with rsyslog. With the compression flag dropped, I was unable to reproduce the errant behavior.
References:
http://www.rsyslog.com/doc/rsyslog_conf_actions.html
The device, \Device\Ide\iaStor0, did not respond within the timeout period
Issue:
After an updated release of Intel's Matrix Storage Manager [v.8.9.0.1023] and chipset drivers for Windows, you experience unexpected system timeouts, lockups, pausing, or freezing. The following event is recorded in the System event log:
Source: iaStor
EventID: 9
Level: Error
The device, \Device\Ide\iaStor0, did not respond within the timeout period.
Cause:
The issue is the result of Aggressive Link State Power Management (ALPM) on the PCI-Express bus negotiating a lower power state for the link between the controller and disk when there is no activity. When ALPM works, disk requests are queued, the serial link revived, and the queued requests are sent to the relevant disk; this requires a disk that supports ALPM.
Resolution:
Modify the advanced settings of your active power management scheme in Windows to turn PCI Express Link State Power Management off.
Commentary:
Searching for a solution yielded a number of possibilities.
Setting the value of:
as discussed by Derek Seaman did not resolve my issue.
Renaming:
to
as suggested by Paul's Computer Service was also ineffective. At the time I was running the latest set of drivers for my platform. Caveat emptor: the solution I outlined in this article worked for me.
References:
Intel CS-025783 - Possible issues with Windows Vista* and Intel® RAID
Windows 7 Intel SATA/AHCI Lockups
Intel® Matrix Storage Manager Bug
Acronis True Image Home 2010 Freezes During Backup on Windows 7
Issue:
When running backup jobs in Acronis True Image Home 2010 under Windows Vista or Windows 7, the backup job appears to stall and the operating system becomes unresponsive. The system will encounter a bugcheck condition and recover with an unclean shutdown.
Cause:
From Acronis:
Because of the latest major changes in Windows Vista and Windows 7 native snapshot driver (VolSnap), there were some modifications introduced in Acronis True Image Home 2010 (starting from Build 6029). The Acronis native snapshot driver (snapman) was moved from UpperFilters to LowerFilters to avoid conflicts with VolSnap (which could have lead to backups failure or data corruption in backups). This change may sometimes manifest itself in a freezing Windows Vista or Windows 7 operating system on machines with rare software and hardware configurations.
Resolution:
Download an updated SnapAPI build from Acronis. Unpack it and install with the Disable Logging option set. See Acronis KB6529 for the appropriate link.
Commentary: My hardware configuration is not esoteric; my software configuration is equally banal: an Intel Core i7 X58 system with 6GB of RAM, RAID1 on an ICH10R, and Windows 7 Ultimate 64-bit.
Reference: http://kb.acronis.com/content/6529