Cpanel::Logger::invalid called in dnsadmin-ssl

[mikelegg]

I've started receiving an email each day from one of my cPanel servers with the subject "Cpanel::Logger::invalid called in dnsadmin-ssl"

The email says ....

2010-04-28 15:17:33 +1000 [dnsadmin-ssl] Invalid lockfile /var/cpanel/dnsrequests.lock detected (zero size) [UID]: 0 [MTIME]: 1272431852 at /usr/local/cpanel/Cpanel/SafeFile.pm line 229
Cpanel::SafeFile::_lock_wait('/var/cpanel/dnsrequests') called at /usr/local/cpanel/Cpanel/SafeFile.pm line 100
Cpanel::SafeFile::safelock('/var/cpanel/dnsrequests') called at /usr/local/cpanel/Cpanel/SafeFile.pm line 27
Cpanel::SafeFile::safeopen(GLOB(0x9ac42b4), '>', '/var/cpanel/dnsrequests') called at whostmgr/bin/dnsadmin-ssl line 1551
main::writereqdb(HASH(0x9c02e08)) called at whostmgr/bin/dnsadmin-ssl line 174

Everything appears to be working fine and there is no /var/cpanel/dnsrequests.lock file.

Does anyone know what this is about?

 

[cPanelKenneth]

I've started receiving an email each day from one of my cPanel servers with the subject "Cpanel::Logger::invalid called in dnsadmin-ssl"

The email says ....

2010-04-28 15:17:33 +1000 [dnsadmin-ssl] Invalid lockfile /var/cpanel/dnsrequests.lock detected (zero size) [UID]: 0 [MTIME]: 1272431852 at /usr/local/cpanel/Cpanel/SafeFile.pm line 229
Cpanel::SafeFile::_lock_wait('/var/cpanel/dnsrequests') called at /usr/local/cpanel/Cpanel/SafeFile.pm line 100
Cpanel::SafeFile::safelock('/var/cpanel/dnsrequests') called at /usr/local/cpanel/Cpanel/SafeFile.pm line 27
Cpanel::SafeFile::safeopen(GLOB(0x9ac42b4), '>', '/var/cpanel/dnsrequests') called at whostmgr/bin/dnsadmin-ssl line 1551
main::writereqdb(HASH(0x9c02e08)) called at whostmgr/bin/dnsadmin-ssl line 174

Everything appears to be working fine and there is no /var/cpanel/dnsrequests.lock file.

Does anyone know what this is about?

Whenever two or more processes attempt to lock the same file concurrently we log that fact. Usually the problem resolves itself and there is nothing to worry about. It's when the problem doesn't resolve itself that is an issue. Without the logging information it can be rather difficult to track down the cause of an issue due to locking race conditions.

 

[mikelegg]

Whenever two or more processes attempt to lock the same file concurrently we log that fact. Usually the problem resolves itself and there is nothing to worry about. It's when the problem doesn't resolve itself that is an issue. Without the logging information it can be rather difficult to track down the cause of an issue due to locking race conditions.

Thanks Kenneth