warn [cpaneld] safelock: Failed to create a lockfile
Hello,
Starting to see quite a bit of this randomly in the error_log, lines and lines of it relating to cpaneld and webmaild
Is anyone else seeing a similar thing on their servers and give me an idea exactly what would cause this? It's a fairly recent thing and has happened several times before on a random basis. Thank you!
---
CloudLinux v8.10.0 standard
cPanel Version 134.0.25
---
This line repeats 90 times in each case.
[2026-05-13 18:03:38 +1000] warn [cpaneld] safelock: Failed to create a lockfile '/var/cpanel/cache/404/cpaneld.lock-17694b851f782-1e5c08d03-b2ac7' in the directory '/var/cpanel/cache/404' that isn't writable: Permission denied
[2026-05-13 18:18:42 +1000] warn [webmaild] safelock: Failed to create a lockfile '/var/cpanel/cache/404/webmaild.lock-17694b851f782-84f54de3-2b469' in the directory '/var/cpanel/cache/404' that isn't writable: Permission denied
There are then a number of entries containing the following:
[2026-05-13 18:03:38 +1000] warn [cpaneld] safelock: waited for lock (/var/cpanel/cache/404/cpaneld.lock) 90 times
cpsrvd 1e20252f18a5e: Cpanel::Exception::IO::FileCreateError/(XID ryd2rz) The system failed to create the file “/var/cpanel/cache/404/cpaneld.lock” (as [asis,EUID]: 985, [asis,EGID]: 979 979) because of the following error: Permission denied
at /usr/local/cpanel/Cpanel/SafeFile.pm line 429, <GEN137> line 4.
Cpanel::SafeFile::_safelock("/var/cpanel/cache/404/cpaneld") called at /usr/local/cpanel/Cpanel/SafeFile.pm line 619
Cpanel::SafeFile::_safe_open(undef, "<", "/var/cpanel/cache/404/cpaneld", CODE(0x2167320), "safeopen") called at /usr/local/cpanel/Cpanel/SafeFile.pm line 175
Cpanel::SafeFile::safeopen(undef, "<", "/var/cpanel/cache/404/cpaneld") called at cpsrvd.pl line 3583
cpanel::cpsrvd::_send_cached_404_or_generate() called at cpsrvd.pl line 3554
cpanel::cpsrvd::dofourohfour("document", "./unprotected/cpanel/style_v2_optimized.css.map", "user", "cpanellogin") called at cpsrvd.pl line 4975
cpanel::cpsrvd::handle_unprotected_docs() called at cpsrvd.pl line 1366
cpanel::cpsrvd::handle_one_connection(3) called at cpsrvd.pl line 1159
cpanel::cpsrvd::script() called at cpsrvd.pl line 450
and
[2026-05-13 18:18:42 +1000] warn [webmaild] safelock: waited for lock (/var/cpanel/cache/404/webmaild.lock) 90 times
cpsrvd 1e20252f18a5e: Cpanel::Exception::IO::FileCreateError/(XID n6ntzk) The system failed to create the file “/var/cpanel/cache/404/webmaild.lock” (as [asis,EUID]: 985, [asis,EGID]: 979 979) because of the following error: Permission denied
at /usr/local/cpanel/Cpanel/SafeFile.pm line 429, <GEN188> line 4.
Cpanel::SafeFile::_safelock("/var/cpanel/cache/404/webmaild") called at /usr/local/cpanel/Cpanel/SafeFile.pm line 619
Cpanel::SafeFile::_safe_open(undef, "<", "/var/cpanel/cache/404/webmaild", CODE(0x2167320), "safeopen") called at /usr/local/cpanel/Cpanel/SafeFile.pm line 175
Cpanel::SafeFile::safeopen(undef, "<", "/var/cpanel/cache/404/webmaild") called at cpsrvd.pl line 3583
cpanel::cpsrvd::_send_cached_404_or_generate() called at cpsrvd.pl line 3554
cpanel::cpsrvd::dofourohfour("document", "./unprotected/json-minified.js.map", "user", "cpanellogin") called at cpsrvd.pl line 4975
cpanel::cpsrvd::handle_unprotected_docs() called at cpsrvd.pl line 1366
cpanel::cpsrvd::handle_one_connection(11) called at cpsrvd.pl line 1159
cpanel::cpsrvd::script() called at cpsrvd.pl line 450
-
Hey there! This is a known issue that we're working on as part of case CPANEL-53195, although I don't have a resolution or workaround just yet. With the recent security push a lot of non-security work has been lowered in priority for a few weeks, but I've linked your thread to the case and I'll post if I hear something on my end!
0 -
Update - this is a wild guess, but I'm wondering if your server runs Cyberark? Something like
ps aux | grep -i cyberarkshould show the process.
0 -
Thanks cPRex
Thank you for highlighting this as being a recognised open case, appreciated.
As for Cyberark ... we have never integrated it.
Thanks again.
0 -
Thanks for the confirmation!
0 -
Update - it looks like there is a potential fix for this planned as part of version 138. If I hear any other updates I'll be sure to post!
1
Please sign in to leave a comment.
Comments
5 comments