Error in "Tweak Settings" after saving settings

nyol

Registered
Jun 26, 2012
2
0
1
cPanel Access Level
Reseller Owner
Hi
I have the latest version of cpanel installed on a VPS, all done cleanly.
However, any changes I make in "Tweak Settings" generates an error when I click in button save.

[a fatal error or timeout occurred while processing this directive]

This message shows a log

Code:
flock LOCK_EX timeout at /usr/local/cpanel/Cpanel/SafeFile.pm line 56.
	Cpanel::SafeFile::__ANON__('ALRM') called at /usr/local/cpanel/Cpanel/SafeFile.pm line 58
	eval {...} called at /usr/local/cpanel/Cpanel/SafeFile.pm line 55
	Cpanel::SafeFile::safeopen('IO::Handle=GLOB(0x4fa8fb0)', '<', '/var/cpanel/cpanel.config') called at /usr/local/cpanel/Cpanel/Config/LoadConfig.pm line 142
	Cpanel::Config::LoadConfig::loadConfig('/var/cpanel/cpanel.config', 'HASH(0x545cc90)', undef, undef, undef, 1, 'HASH(0x5479c50)') called at /usr/local/cpanel/Cpanel/Config/LoadCpConf.pm line 157
	Cpanel::Config::LoadCpConf::loadcpconf() called at /usr/local/cpanel/Cpanel/Rlimit.pm line 129
	Cpanel::Rlimit::get_server_setting_or_default() called at /usr/local/cpanel/Cpanel/Rlimit.pm line 108
	Cpanel::Rlimit::set_rlimit_to_infinity() called at /usr/local/cpanel/Whostmgr/Config.pm line 49
	Whostmgr::Config::apply_tweaks('newvalues', 'HASH(0x24cef90)', 'rejects', 'HASH(0x24cefa0)', 'cpconf', 'HASH(0x5220c00)', 'force', 0) called at whostmgr/bin/whostmgr2 line 4630
	main::dotweaksettings() called at whostmgr/bin/whostmgr2 line 1131
Someone can tell me why this is happening? I'd like to fix that.

Thanks guys
 

nyol

Registered
Jun 26, 2012
2
0
1
cPanel Access Level
Reseller Owner
:( Hi guys

No help yet, my hopes are already depleted.

I really can not find an answer on google.

If someone has gone through this please share the solution.

thank you
 

cPanelKenneth

cPanel Development
Staff member
Apr 7, 2006
4,607
79
458
cPanel Access Level
Root Administrator
From the error message it seems cPanel & WHM is unable to obtain a lock on the /var/cpanel/cpanel.config file. This is not something we've encountered in our testing. In order to resolve, or diagnose, the issue we need access to a machine that encounters this symptom. Please open a support ticket with us next time it occurs.