blogs

0x00000051 after Windows 2003 SP1 upgrade

We recently had a client who applied Windows 2003 Server Service Pack 1 on their Dell Poweredge 420SC server. On reboot, they were greeted with the dreaded blue screen of death (BSOD) with the error message.

STOP 0x00000051 (REGISTRY_ERROR)

The server would then reboot and then do it all again. Safe mode and Last Known good configuration made no difference.

After searching the net, it turns out that this is a known problem on older Dell Poweredges that have had a factory install of Windows on.

Subjects: 

Noisy logging from SASL2 SQL library

There's a bug in the current SASL2 SQL library (libsasl2-modules-sql) which means it logs at debug level all the time, and there's no way of switching it off. This fills up auth.log with junk because the default syslog configuration on Debian logs all auth output including debug which makes logcheck unusable.

Until SASL2 is fixed, the only way I've found to work around this is to reduce the logging level for auth and authpriv to exclude debug messages. For syslog-ng this requires the following change to /etc/syslog-ng/syslog-ng.conf

Subjects: 

Pages