Opcode Caching: Disabled
- Thread starter cool_recep
- Start date
Normally ea4 just install opcode module/ uninstall opcode module, not disabled, you can check further
/opt/cpanel/ea-phpxx/root/etc/php.d/opcache.ini
maybe someone disable opcode cache from the settings.
https://www.knownhost.com/wiki/developmental/php-opcode-caching-guide
/opt/cpanel/ea-phpxx/root/etc/php.d/opcache.ini
maybe someone disable opcode cache from the settings.
https://www.knownhost.com/wiki/developmental/php-opcode-caching-guide
It looks enabled:
Code:
; Enable Zend OPcache extension module
zend_extension=opcache.so
; Determines if Zend OPCache is enabled
opcache.enable=1
; Determines if Zend OPCache is enabled for the CLI version of PHP
;opcache.enable_cli=0
; The OPcache shared memory storage size.
opcache.memory_consumption=128
; The amount of memory for interned strings in Mbytes.
opcache.interned_strings_buffer=8
; The maximum number of keys (scripts) in the OPcache hash table.
; Only numbers between 200 and 100000 are allowed.
opcache.max_accelerated_files=4000
; The maximum percentage of "wasted" memory until a restart is scheduled.
;opcache.max_wasted_percentage=5
; When this directive is enabled, the OPcache appends the current working
; directory to the script key, thus eliminating possible collisions between
; files with the same name (basename). Disabling the directive improves
; performance, but may break existing applications.
;opcache.use_cwd=1
; When disabled, you must reset the OPcache manually or restart the
; webserver for changes to the filesystem to take effect.
;opcache.validate_timestamps=1
; How often (in seconds) to check file timestamps for changes to the shared
; memory storage allocation. ("1" means validate once per second, but only
; once per request. "0" means always validate)
;opcache.revalidate_freq=2
; Enables or disables file search in include_path optimization
;opcache.revalidate_path=0
; If disabled, all PHPDoc comments are dropped from the code to reduce the
; size of the optimized code.
;opcache.save_comments=1
; If enabled, a fast shutdown sequence is used for the accelerated code
;opcache.fast_shutdown=0
; Allow file existence override (file_exists, etc.) performance feature.
;opcache.enable_file_override=0
; A bitmask, where each bit enables or disables the appropriate OPcache
; passes
;opcache.optimization_level=0xffffffff
;opcache.inherited_hack=1
;opcache.dups_fix=0
; The location of the OPcache blacklist file (wildcards allowed).
; Each OPcache blacklist file is a text file that holds the names of files
; that should not be accelerated.
opcache.blacklist_filename=/opt/cpanel/ea-php74/root/etc/php.d/opcache*.blacklist
; Allows exclusion of large files from being cached. By default all files
; are cached.
;opcache.max_file_size=0
; Check the cache checksum each N requests.
; The default value of "0" means that the checks are disabled.
;opcache.consistency_checks=0
; How long to wait (in seconds) for a scheduled restart to begin if the cache
; is not being accessed.
;opcache.force_restart_timeout=180
; OPcache error_log file name. Empty string assumes "stderr".
;opcache.error_log=
; All OPcache errors go to the Web server log.
; By default, only fatal errors (level 0) or errors (level 1) are logged.
; You can also enable warnings (level 2), info messages (level 3) or
; debug messages (level 4).
;opcache.log_verbosity_level=1
; Preferred Shared Memory back-end. Leave empty and let the system decide.
;opcache.preferred_memory_model=
; Protect the shared memory from unexpected writing during script execution.
; Useful for internal debugging only.
;opcache.protect_memory=0
; Allows calling OPcache API functions only from PHP scripts which path is
; started from specified string. The default "" means no restriction
;opcache.restrict_api=
; Enables and sets the second level cache directory.
; It should improve performance when SHM memory is full, at server restart or
; SHM reset. The default "" disables file based caching.
; RPM note : file cache directory must be owned by process owner
; for mod_php, see /etc/httpd/conf.d/php.conf
; for php-fpm, see /etc/php-fpm.d/*conf
opcache.file_cache=""
; Enables or disables opcode caching in shared memory.
;opcache.file_cache_only=0
; Enables or disables checksum validation when script loaded from file cache.
;opcache.file_cache_consistency_checks=1
; Enables or disables copying of PHP code (text segment) into HUGE PAGES.
; This should improve performance, but requires appropriate OS configuration.
opcache.huge_code_pages=0
; Leads OPcache to check file readability on each access to cached file.
; This directive should be enabled in shared hosting environment, when few
; users (PHP-FPM pools) reuse the common OPcache shared memory.
opcache.validate_permission=1Do you use ea-phpxx? or alt-phpxx? Which one?
Does LiteSpeed have exactly the same php as apache? (you can switch between apache and litespeed and compare phpinfo.php)
If ea-phpxx, try to uninstall opcode cache from WHM easy apache 4 (check phpinfo.php with apache to make sure it is gone ) and then resintall opcode cache from WHM easy apache 4( check phpinfo.php with apache to make sure it is back), if it works on apache, it should just work with LiteSpeed. if problem persists on apache even, I would recommend you to log a ticket with cpanel support to take a look.
Does LiteSpeed have exactly the same php as apache? (you can switch between apache and litespeed and compare phpinfo.php)
If ea-phpxx, try to uninstall opcode cache from WHM easy apache 4 (check phpinfo.php with apache to make sure it is gone ) and then resintall opcode cache from WHM easy apache 4( check phpinfo.php with apache to make sure it is back), if it works on apache, it should just work with LiteSpeed. if problem persists on apache even, I would recommend you to log a ticket with cpanel support to take a look.
Yes, still. I was told to disable suEXEC. Today I disabled it. And then immediately, I got errors in Xenforo:
I've chmodded internal_data and data but still got this image problem:
And on the Wordpress site, I started getting this error:
Solved this error with pasting
So, my first attempt at disabling suEXEC failed. I might give it a try if you can help me more. XenForo admins told me that I should have also performed chown.
Code:
All directories under ....public_html/sosyal/internal_data must be writable. Please change the permissions on these directories to be world writable (chmod 0777).And on the Wordpress site, I started getting this error:
Code:
Warning: ftp_fget() expects parameter 1 to be resource, null given in /home/technopa/public_html/wp-admin/includes/class-wp-filesystem-ftpext.php on line 146
Warning: Cannot modify header information - headers already sent by (output started at /home/technopa/public_html/wp-admin/includes/class-wp-filesystem-ftpext.php:146) in /home/technopa/public_html/wp-includes/functions.php on line 6274
Warning: Cannot modify header information - headers already sent by (output started at /home/technopa/public_html/wp-admin/includes/class-wp-filesystem-ftpext.php:146) in /home/technopa/public_html/wp-admin/includes/misc.php on line 1310
Warning: Cannot modify header information - headers already sent by (output started at /home/technopa/public_html/wp-admin/includes/class-wp-filesystem-ftpext.php:146) in /home/technopa/public_html/wp-admin/admin-header.php on line 9define('FS_METHOD','direct'); code into config.php but still could not install add-ons...So, my first attempt at disabling suEXEC failed. I might give it a try if you can help me more. XenForo admins told me that I should have also performed chown.
