Aldweb

Well-Known Member
Feb 18, 2004
66
0
156
Last updated cpanel with the current version (11.50). After this update can not enter the whm, the following message appears:

Internal Server Error

500

No response from subprocess (whostmgr (whostmgr)): The subprocess died from signal 11 (SEGV).

I can not open support ticket, because when I run the command to get the Support ID access, the error:

[email protected] [~]# /usr/local/cpanel/cpanel -S
DBD::SQLite object version 1.42 does not match $DBD::SQLite::VERSION 1.46.

I've tried updating again, but the error 500 problem continues.

Does anyone know what can be?

Thanks
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,904
2,218
463

Aldweb

Well-Known Member
Feb 18, 2004
66
0
156
Hello,

I changed the cpupdate.conf, but continue 11.50.0.4
[email protected] [~]# cat /etc/cpupdate.conf
CPANEL=release
RPMUP=manual
SARULESUP=daily
STAGING_DIR=/usr/local/cpanel
UPDATES=manual

[email protected] [~]# cat /usr/local/cpanel/version
11.50.0.4

/usr/local/cpanel/logs/error_log

[2015-05-22 17:58:02 -0300] info [purge_modsec_log] Purged stale records from modsec database.
[2015-05-22 17:58:07 -0300] info [rebuild_sprites] File "/usr/local/cpanel/base/frontend/x3/branding/motor_city/bg.gif" has 400 x 400 dimensions with 160000 pixels.
This is exceeding 8192 pixels and color palette issue may be expected when its associated sprite file is used:
"/usr/local/cpanel/base/frontend/x3/branding/motor_city/ui_sprites_bg_snap_to_smallest_width.png".

[2015-05-22 17:58:07 -0300] info [rebuild_sprites] File "/usr/local/cpanel/base/frontend/x3/branding/crimson_smoke/bottom_bg.gif" has 783 x 23 dimensions with 18009 pixels.
This is exceeding 8192 pixels and color palette issue may be expected when its associated sprite file is used:
"/usr/local/cpanel/base/frontend/x3/branding/crimson_smoke/heading_sprites_bg_snap_to_smallest_width.png".

[2015-05-22 17:58:09 -0300] info [rebuild_sprites] File "/usr/local/cpanel/base/frontend/x3/branding/the_beach/bottom_bg.gif" has 783 x 23 dimensions with 18009 pixels.
This is exceeding 8192 pixels and color palette issue may be expected when its associated sprite file is used:
"/usr/local/cpanel/base/frontend/x3/branding/the_beach/heading_sprites_bg_snap_to_smallest_width.png".

[2015-05-22 17:58:12 -0300] info [rebuild_sprites] File "/usr/local/cpanel/base/frontend/x3mail/branding/motor_city/bg.gif" has 400 x 400 dimensions with 160000 pixels.
This is exceeding 8192 pixels and color palette issue may be expected when its associated sprite file is used:
"/usr/local/cpanel/base/frontend/x3mail/branding/motor_city/ui_sprites_bg_snap_to_smallest_width.png".

[2015-05-22 17:58:12 -0300] info [rebuild_sprites] File "/usr/local/cpanel/base/frontend/x3mail/branding/crimson_smoke/bottom_bg.gif" has 783 x 23 dimensions with 18009 pixels.
This is exceeding 8192 pixels and color palette issue may be expected when its associated sprite file is used:
"/usr/local/cpanel/base/frontend/x3mail/branding/crimson_smoke/heading_sprites_bg_snap_to_smallest_width.png".

[2015-05-22 17:58:13 -0300] info [rebuild_sprites] File "/usr/local/cpanel/base/frontend/x3mail/branding/the_beach/bottom_bg.gif" has 783 x 23 dimensions with 18009 pixels.
This is exceeding 8192 pixels and color palette issue may be expected when its associated sprite file is used:
"/usr/local/cpanel/base/frontend/x3mail/branding/the_beach/heading_sprites_bg_snap_to_smallest_width.png".

[2015-05-22 17:58:34 -0300] info [updateuserdatacache] Virtual host configuration not found for user perches, domain UNKNOWN
[2015-05-22 17:58:41 -0300] info [email_archive_maintenance] Email archiving is disabled per Tweak Settings.
[2015-05-22 17:58:44 -0300] info [setup_modsec_db] Initialized ModSecurityâ„¢ database.
[2015-05-22 17:58:44 -0300] info [modsec_vendor] Updates are in progress for all of the installed ModSecurity vendors with automatic updates enabled.
[2015-05-22 17:59:38 -0300] info [check_mysql] starting mysqlcheck on cphulkd (PID 25211)
[2015-05-22 17:59:38 -0300] info [check_mysql] mysqlcheck of cphulkd is finished (PID 25211)
[2015-05-22 17:59:38 -0300] info [check_mysql] mysqlcheck found no errors on cphulkd
[2015-05-22 17:59:38 -0300] info [check_mysql] starting mysqlcheck on eximstats (PID 25211)
[2015-05-22 18:00:33 -0300] warn [restartsrv_tailwatchd] The service 'tailwatchd' may not have successfully stopped: 0 at /usr/local/cpanel/Cpanel/ServiceManager/Manager/Initd.pm line 224
Cpanel::ServiceManager::Manager::Initd::stop(Cpanel::ServiceManager::Manager::Initd=HASH(0x8935e54), Cpanel::ServiceManager::Services::Tailwatchd=HASH(0x88da9bc)) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 825
Cpanel::ServiceManager::Base::stop(Cpanel::ServiceManager::Services::Tailwatchd=HASH(0x88da9bc)) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 677
Cpanel::ServiceManager::Base::restart(Cpanel::ServiceManager::Services::Tailwatchd=HASH(0x88da9bc), 'graceful', undef) called at /usr/local/cpanel/Cpanel/ServiceManager/Base.pm line 524
Cpanel::ServiceManager::Base::run_from_argv(Cpanel::ServiceManager::Services::Tailwatchd=HASH(0x88da9bc), '--verbose') called at /usr/local/cpanel/scripts/restartsrv_tailwatchd line 48
main::try {...} () called at /usr/local/cpanel/3rdparty/perl/514/lib/perl5/cpanel_lib/Try/Tiny.pm line 81
eval {...} called at /usr/local/cpanel/3rdparty/perl/514/lib/perl5/cpanel_lib/Try/Tiny.pm line 72
Try::Tiny::try(CODE(0x83960c4), Try::Tiny::Catch=REF(0x8409ab4)) called at /usr/local/cpanel/scripts/restartsrv_tailwatchd line 67
[2015-05-22 18:02:46 -0300] info [check_mysql] mysqlcheck of eximstats is finished (PID 25211)
[2015-05-22 18:02:46 -0300] info [check_mysql] mysqlcheck found no errors on eximstats
[2015-05-22 18:02:46 -0300] info [check_mysql] starting mysqlcheck on horde (PID 25211)
[2015-05-22 18:02:48 -0300] info [check_mysql] mysqlcheck of horde is finished (PID 25211)
[2015-05-22 18:02:48 -0300] info [check_mysql] mysqlcheck found no errors on horde
[2015-05-22 18:02:48 -0300] info [check_mysql] starting mysqlcheck on leechprotect (PID 25211)
[2015-05-22 18:02:48 -0300] info [check_mysql] mysqlcheck of leechprotect is finished (PID 25211)
[2015-05-22 18:02:48 -0300] info [check_mysql] mysqlcheck found no errors on leechprotect
[2015-05-22 18:02:48 -0300] info [check_mysql] starting mysqlcheck on modsec (PID 25211)
[2015-05-22 18:02:48 -0300] info [check_mysql] mysqlcheck of modsec is finished (PID 25211)
[2015-05-22 18:02:48 -0300] warn [check_mysql] mysqlcheck found errors on modsec: error : Size of datafile is: 53448704 Should be: 53448740
error : Corrupt
at /usr/local/cpanel/scripts/check_mysql line 52
eval {...} called at /usr/local/cpanel/scripts/check_mysql line 37
main::__ANON__() called at /usr/local/cpanel/Cpanel/Daemonizer/Tiny.pm line 26
Cpanel::Daemonizer::Tiny::__ANON__() called at /usr/local/cpanel/Cpanel/ForkAsync.pm line 36
eval {...} called at /usr/local/cpanel/Cpanel/ForkAsync.pm line 36
Cpanel::ForkAsync::do_in_child(CODE(0x966adf8)) called at /usr/local/cpanel/Cpanel/Daemonizer/Tiny.pm line 28
Cpanel::Daemonizer::Tiny::run_as_daemon(CODE(0x8e55bb8)) called at /usr/local/cpanel/scripts/check_mysql line 76
[2015-05-22 18:02:48 -0300] info [check_mysql] starting mysqlcheck on mysql (PID 25211)
[2015-05-22 18:02:48 -0300] info [check_mysql] mysqlcheck of mysql is finished (PID 25211)
[2015-05-22 18:02:48 -0300] warn [check_mysql] mysqlcheck found errors on mysql: mysql.general_log
Error : You can't use locks with log tables.
mysql.slow_log
Error : You can't use locks with log tables.
at /usr/local/cpanel/scripts/check_mysql line 52
eval {...} called at /usr/local/cpanel/scripts/check_mysql line 37
main::__ANON__() called at /usr/local/cpanel/Cpanel/Daemonizer/Tiny.pm line 26
Cpanel::Daemonizer::Tiny::__ANON__() called at /usr/local/cpanel/Cpanel/ForkAsync.pm line 36
eval {...} called at /usr/local/cpanel/Cpanel/ForkAsync.pm line 36
Cpanel::ForkAsync::do_in_child(CODE(0x966adf8)) called at /usr/local/cpanel/Cpanel/Daemonizer/Tiny.pm line 28
Cpanel::Daemonizer::Tiny::run_as_daemon(CODE(0x8e55bb8)) called at /usr/local/cpanel/scripts/check_mysql line 76
[2015-05-22 18:02:48 -0300] info [check_mysql] starting mysqlcheck on roundcube (PID 25211)
[2015-05-22 18:02:48 -0300] info [check_mysql] mysqlcheck of roundcube is finished (PID 25211)
[2015-05-22 18:02:48 -0300] info [check_mysql] mysqlcheck found no errors on roundcube
[2015-05-22 18:02:48 -0300] info [check_mysql] starting mysqlcheck on whmxfer (PID 25211)
[2015-05-22 18:02:48 -0300] info [check_mysql] mysqlcheck of whmxfer is finished (PID 25211)
[2015-05-22 18:02:48 -0300] info [check_mysql] mysqlcheck found no errors on whmxfer
 
Last edited:

Aldweb

Well-Known Member
Feb 18, 2004
66
0
156
Really did not get to go back to work the whm, the error 500 continues. I needed a support, but I can not access the Support ID:

[email protected] [~]# /usr/local/cpanel/cpanel -S
DBD::SQLite object version 1.42 does not match $DBD::SQLite::VERSION 1.46.


There is another way to get the Support access ID?

Thanks
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,904
2,218
463
Hello,

You can now run "/scripts/upcp --force" for the current build tier. Does that help to address the issue?

Thank you.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,904
2,218
463
I am happy to see the issue is now resolved. Thank you for updating us with the outcome.
 

Waltenydsam lemos

Registered
PartnerNOC
Jun 16, 2015
1
0
1
Brazil
cPanel Access Level
Root Administrator
Hi.
I try update with /scripts/upcp --force, but not still works.

I run:
cat /usr/local/cpanel/version
11.50.0.10
And run:
cat /etc/cpupdate.conf
CPANEL=release
RPMUP=daily
SARULESUP=daily
STAGING_DIR=/home
UPDATES=daily
When i try get support ID:
/usr/local/cpanel/cpanel -S
DBD::SQLite object version 1.42 does not match $DBD::SQLite::VERSION 1.46.
Falha de segmentação
I try fix with
/scripts/check_cpanel_rpms. But not still work.

I've read all:
https://forums.cpanel.net/threads/current-was-11-50-then-disabled-now-11-48.473301/
https://forums.cpanel.net/threads/c...back-from-restart-during-11-50-update.473181/

Please help.


 

Aldweb

Well-Known Member
Feb 18, 2004
66
0
156
I changed the /etc/cpupdate.conf

CPANEL=release to CPANEL=11.48
RPMUP=daily
SARULESUP=daily
STAGING_DIR=/home
UPDATES=daily


/scripts/upcp --force

After the upgrade, I returned to CPANEL=release and updated the cpanel again

works fine now
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,904
2,218
463
I try update with /scripts/upcp --force, but not still works.
Hello,

Could you verify if the issue persists after forcing another update of cPanel using the instructions in the previous post?

Thank you.