Server Error 503 after upgrade to 2.2.16

[sponna1]

Hi,

We have a site which is giving 503 server errors after upgrade to 2.2.16. Site config is given below. The error appears to be related to cached files as the error can be cleared when the cache is cleared - we needed to do this via FTP as the admin and front end were taken down. This has happened several times in the last couple of weeks - no other changes have been made to the site.

Is there anything specific we need to be looking for please as this is a new occurrence, seemingly related to the upgrade.

The site does have a couple of older modules (FEU etc) which we have avoided updating as some bespoking was done when the site was first built several years ago. However, this hasn't caused problems historically.

I suppose we could disable caching (how is this done please?) albeit this seems to be an undesirable work-around as it will affect site performance.

Thanks for your help.

----------------------------------------------

Cms Version: 2.2.16

Installed Modules:

AdminSearch: 1.0.6
CGExtensions: 1.62.1
CGGoogleMaps2: 1.1.1
CGSimpleSmarty: 2.2.1
CGSmartImage: 1.22.5
CMSContentManager: 1.1.9
CMSMailer: 6.2.14
Captcha: 1.0
CmsJobManager: 0.1.3
CompanyDirectory: 1.23.5
CustomContent: 1.9
DesignManager: 1.1.9
FileManager: 1.6.12
FilePicker: 1.0.5
FormBuilder: 1.1.1
FrontEndUsers: 2.5.2
Gallery: 2.3.2
JQueryTools: 1.4.0.4
MenuManager: 1.50.3
MicroTiny: 2.2.5
ModuleManager: 2.1.8
Navigator: 1.0.9
News: 2.51.11
Search: 1.53
ThemeManager: 1.1.8


Config Information:

php_memory_limit:
max_upload_size: 60000000
url_rewriting: mod_rewrite
page_extension:
query_var: page
auto_alias_content: true
locale:
set_names: true
timezone: Europe/London
permissive_smarty: false


Php Information:

phpversion: 7.3.33
md5_function: On (True)
json_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_ALL: 32759
E_STRICT: 2048
E_DEPRECATED: 8192
test_file_timedifference: No time difference found
test_db_timedifference: No time difference found
create_dir_and_file: 1
memory_limit: 128M
max_execution_time: 30
register_globals: Off (False)
output_buffering: On
disable_functions:
open_basedir:
test_remote_url: Success
file_uploads: On (True)
post_max_size: 60M
upload_max_filesize: 60M
session_save_path: /var/cpanel/php/sessions/ea-php73 (0700)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)
check_ini_set: On (True)
curl: On


Performance Information:

allow_browser_cache: Off (False)
browser_cache_expiry: 60
php_opcache: On (True)
smarty_cache: Off (False)
smarty_compilecheck: Off (False)
auto_clear_cache_age: On (True)

Server Information:

Server Software: LiteSpeed
Server Api: litespeed
Server Os: Linux 4.18.0-348.lve.el8.x86_64 On x86_64
Server Db Type: MySQL (mysqli)
Server Db Version: 8.0.28
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable


Permission Information:

tmp: /home/xxxxx/public_html/tmp (0755)
tmp_cache: /home/xxxxxxx/public_html/tmp/cache (0755)
templates_c: /home/xxxxxxx/public_html/tmp/templates_c (0755)
modules: /home/xxxxxxx/public_html/modules (0755)
uploads: /home/xxxxxxxx/public_html/uploads (0755)
File Creation Mask (umask): /home/xxxxxxxx/public_html/tmp/cache (0755)
config_file: 0644

----------------------------------------------

[DIGI3]

Can you get the specific 503 error message from the error log? It sounds like perhaps something is infinitely looping or a similar overload, but it's hard to tell without investigating.

You can disable browser caching, but I don't think you can disable the cmsms cache entirely, as that's where the files are assembled for serving. Clearing the cache just triggers a rebuild when each page is revisited, so if that fixes it then it eventually goes down again, there's a particular page or section that's causing the error.

[sponna1]

Hi there,

We'll ask our server guys to see if they can identify anything specific from the server logs. If so, I'll come back to you.

Thanks for your help.

[sponna1]

Hi,

Our server guys haven't identified anything specific in the logs but they have increased the php execution limit. I'm not convinced about that but we'll monitor to see what happens.

Thanks again.