Errors in Server Error Log

[mj00712]

Hi. I am getting these errors in server error log. How to fix these errors?

2023-11-28 16:08:38.029378 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/modsec/owasp-modsecurity-crs-3.0-master/rules/RESPONSE-950-DATA-LEAKAGES.conf
2023-11-28 16:08:38.029378 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/modsec/owasp-modsecurity-crs-3.0-master/rules/RESPONSE-950-DATA-LEAKAGES.conf
2023-11-28 16:08:38.029477 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/modsec/owasp-modsecurity-crs-3.0-master/rules/RESPONSE-951-DATA-LEAKAGES-SQL.conf
2023-11-28 16:08:38.029477 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/modsec/owasp-modsecurity-crs-3.0-master/rules/RESPONSE-951-DATA-LEAKAGES-SQL.conf
2023-11-28 16:08:38.030431 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/modsec/owasp-modsecurity-crs-3.0-master/rules/RESPONSE-952-DATA-LEAKAGES-JAVA.conf
2023-11-28 16:08:38.030431 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/modsec/owasp-modsecurity-crs-3.0-master/rules/RESPONSE-952-DATA-LEAKAGES-JAVA.conf
2023-11-28 16:08:38.030648 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/modsec/owasp-modsecurity-crs-3.0-master/rules/RESPONSE-953-DATA-LEAKAGES-PHP.conf
2023-11-28 16:08:38.030648 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/modsec/owasp-modsecurity-crs-3.0-master/rules/RESPONSE-953-DATA-LEAKAGES-PHP.conf
2023-11-28 16:08:38.033103 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/modsec/owasp-modsecurity-crs-3.0-master/rules/RESPONSE-954-DATA-LEAKAGES-IIS.conf
2023-11-28 16:08:38.033103 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/modsec/owasp-modsecurity-crs-3.0-master/rules/RESPONSE-954-DATA-LEAKAGES-IIS.conf
2023-11-28 16:08:38.033315 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/modsec/owasp-modsecurity-crs-3.0-master/rules/RESPONSE-959-BLOCKING-EVALUATION.conf
2023-11-28 16:08:38.033315 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/modsec/owasp-modsecurity-crs-3.0-master/rules/RESPONSE-959-BLOCKING-EVALUATION.conf
2023-11-28 16:08:38.033387 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/modsec/owasp-modsecurity-crs-3.0-master/rules/RESPONSE-980-CORRELATION.conf
2023-11-28 16:08:38.033387 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/modsec/owasp-modsecurity-crs-3.0-master/rules/RESPONSE-980-CORRELATION.conf
2023-11-28 16:08:38.033517 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/modsec/owasp-modsecurity-crs-3.0-master/rules/RESPONSE-999-EXCLUSION-RULES-AFTER-CRS.conf
2023-11-28 16:08:38.033517 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/modsec/owasp-modsecurity-crs-3.0-master/rules/RESPONSE-999-EXCLUSION-RULES-AFTER-CRS.conf
2023-11-28 16:08:38.033554 [ERROR] [239363] [T0] [/usr/local/lsws/conf/modsec.conf:20] Failed to get absolute path for [/usr/local/lsws/conf/rules.conf/(null)]!
2023-11-28 16:08:38.033554 [ERROR] [239363] [T0] [/usr/local/lsws/conf/modsec.conf:20] Failed to get absolute path for [/usr/local/lsws/conf/rules.conf/(null)]!
2023-11-28 16:08:38.033571 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/vhosts/filectory.com/vhost.conf
2023-11-28 16:08:38.033571 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/vhosts/filectory.com/vhost.conf
2023-11-28 16:08:38.033619 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/vhosts/mail.filectory.com/vhost.conf
2023-11-28 16:08:38.033619 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/vhosts/mail.filectory.com/vhost.conf
2023-11-28 16:08:38.033653 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/vhosts/jobs.filectory.com/vhost.conf
2023-11-28 16:08:38.033653 [INFO] [239363] [T0] Processing config file: /usr/local/lsws/conf/vhosts/jobs.filectory.com/vhost.conf
2023-11-28 16:08:38.037750 [ERROR] [239363] [T0] [/usr/local/lsws/conf/vhosts/jobs.filectory.com/vhost.conf:33] Listener for _default_ is not available.
2023-11-28 16:08:38.037750 [ERROR] [239363] [T0] [/usr/local/lsws/conf/vhosts/jobs.filectory.com/vhost.conf:33] Listener for _default_ is not available.
[Tue Nov 28 16:08:38 2023] [notice] Finish reading Apache configuration, server configured -- resuming normal operations
2023-11-28 16:08:38.038196 [NOTICE] [239363] [T0] Litespeed is ready to serve...
2023-11-28 16:08:38.039032 [NOTICE] [239363] [T0] [AutoRestarter] new child process with pid=239368 is forked!
2023-11-28 16:08:38.039346 [INFO] [239368] [T0] registered RT signal 38
2023-11-28 16:08:38.039399 [INFO] [239368] [T0] [UDP 0.0.0.0:443] initPacketsIn: allocated 100 packets
2023-11-28 16:08:38.039454 [INFO] [239368] [T0] [UDP [::]:443] initPacketsIn: allocated 100 packets
2023-11-28 16:08:38.039769 [NOTICE] [239368] [T0] [Child: 239368] Setup swapping space...
2023-11-28 16:08:38.039800 [NOTICE] [239368] [T0] Successfully change current user to nobody
2023-11-28 16:08:38.039805 [NOTICE] [239368] [T0] Core dump is enabled.
2023-11-28 16:08:38.040016 [INFO] [239368] [T0] [SSL_APK] created offloader with 1 workers.
2023-11-28 16:08:38.040069 [INFO] [239368] [T0] [MODSEC] created offloader with 10 workers.
2023-11-28 16:08:38.041895 [INFO] [239368] [T0] [MODSEC_BODY] created offloader with 50 workers.
2023-11-28 16:08:38.041899 [ALERT] [239368] [T0] LiteSpeed/6.0 Enterprise starts successfully!
2023-11-28 16:08:38.080533 [NOTICE] [239253] [T0] New litespeed process is ready, stops listeners
2023-11-28 16:08:38.080554 [INFO] [239253] [T0] Stop all listeners.
2023-11-28 16:08:38.080558 [INFO] [239253] [T0] Stop listener *:443.
2023-11-28 16:08:38.080564 [INFO] [239253] [T0] Stop listener *:80.
2023-11-28 16:08:38.080567 [INFO] [239253] [T0] Stop listener [::]:443.
2023-11-28 16:08:38.080570 [INFO] [239253] [T0] Stop listener [::]:80.
2023-11-28 16:08:38.080573 [INFO] [239253] [T0] Stop listener *:7080.
2023-11-28 16:08:38.080576 [NOTICE] [239253] [T0] QuicEngine::startCoolDown(), active connections: 7
2023-11-28 16:08:39.850857 [NOTICE] [239253] [T0] Event-loop lingering done.
2023-11-28 16:08:39.850872 [NOTICE] [239253] [T0] Shut down successfully!
2023-11-28 16:08:39.851467 [NOTICE] [239253] [T0] [APVH_filec8149_Sulsphp80:] stop worker processes, detached: 1

 

[Unique_Eric]

It seems you have OWASP enabled, and LSWS just loads those rules, it's not an issue.

 

[mj00712]

How to allow these via Modsecurity or Litespeed

/wp-json/rankmath/v1/updateMeta
/wp-json/rankmath/v1/saveModule

 

[serpent_driver]

How to allow these via Modsecurity or Litespeed

This is ModSecurity, but not LiteSpeed related, so it is up to you to modify ModSecurity rules.

 

[mj00712]

Sir, I am encountering issues with Rank Math. I have attempted various solutions, but I am unable to resolve the problem of Rank Math taking too long to update posts, eventually leading to a 503 error (server busy). The Rank Math support team has suggested that this issue may be related to firewall problems or ModSecurity. Therefore, I would like to know how to whitelist these URLs.

 

[serpent_driver]

Whitelisting a URL does not solve the problem and is not caused by RankMath. There must be deeper causes for overload. A 503 error code can also be caused by exceeding the max_execution_time. The relevant error logs should provide information about this. Without appropriate error logs it is impossible to find out the cause.

FYI: "Nothing happens without any reason"

 

[mj00712]

Some errors from wordpress.

 

[serpent_driver]

You should use LiteSpeed's cache plugin suppport at WordPress. Only there you will get qualified support for this issue because this forum doesn't support cache plugin for WordPress any longer.

https://www.litespeedtech.com/support/forum/threads/please-use-the-official-wordpress-forum.16028/

However, there is a likelihood that the cause of your problem is caused by either a security plugin or a custom rewrite rule in a .htaccess rule.

 

[KeeganFeeney]

Thank you for the WordPress link.