Available in VPC
This page lists problems you might run into when using WebShell Behavior Detector Service. Click on the error to see more details.
Common errors
The following are examples of common errors you might encounter:
Web shell file isolation or file recovery failed
Web shell file quarantine or file recovery was not performed.
Web shell file quarantine or file recovery failed.
Detection alert interval adjustment
The detection alerts are coming too frequently.
Agent error
The agent has been installed, but it is shown as not installed.
The agent was installed first before registering as a detection target.
Troubleshoot error messages
The following are examples of error messages you might encounter:
"[5002] The specified path could not be found" error message
"[5002] The specified path could not be found" error message is displayed.
"[5005] Unable to find the web server environment/path settings for the Pod" error message
"[5005] Unable to find the web server environment/path settings for the Pod" error message is displayed.
"[5101] file quarantine or recovery failed. There are no files to quarantine or recover" error message
"[5101] file quarantine or recovery failed. No files to quarantine or recovery" error message is displayed.
"[5102] file quarantine or recovery failed. Quarantine or recovery file name already exists" error message
"[5102] file quarantine or recovery failed. Files to quarantine or recovery already exist" error message is displayed.
"[5103] file recovery failed. Check the server" error message
"[5103] file recovery failed. It is recommended to check the server" error message is displayed.
"[5104] file quarantine failed. Check the server" error message
"[5104] file quarantine failed. It is recommended to check the server" error message is displayed.
"[5401] WAS process could not be found. Check the WAS execution status. Disable the agent if you do not wish to use it" error message
"[5401] WAS process could not be found. Check the WAS execution status. Disable the agent if you do not wish to use it" error message is displayed.
"[5402] WAS process could not be found. Check the WAS execution status. Disable the agent if you do not wish to use it" error message
"[5402] WAS process could not be found. Check the WAS execution status. Disable the agent if you do not wish to use it" error message is displayed.
"[5403] cannot access the Access Log file of the WAS process. Some information collection may be omitted. Check Access Log file" error message
"[5403] cannot access the Access Log file of the WAS process. Some information collection may be omitted. Check Access Log file" error message is displayed.
"[5404] Inotify limit has exceeded. Refer to user guide" error message
"[5404] Inotify limit has exceeded. Refer to user guide" error message is displayed.
"[5405] Cannot access the following path. Some features may not work properly. Check and take action" error message
"[5405] Cannot access the following path. Some features may not work properly. Check and take action" error message is displayed.
"[6007] Unable to connect to the agent. Check the agent's running status or the server network" error message
"[6007] Unable to connect to the agent. Check the agent's running status or the server network" error message is displayed.
"[6008] Failed to update the agent. Check the agent's running status or the server network" error message
"[6008] Agent update failed. Check the agent's running status or the server network" error message is displayed.
"[6021] The requested command has timed out. Try again later" error message
"[6021] The requested command has timed out. Try again later" error message is displayed.
"[6023] Unable to connect to the agent. Check the agent's running status or the server network" error message
"[6023] Unable to connect to the agent. Check the agent's running status or the server network" error message is displayed.
"[8003] file quarantine commands failed. Check the agent's running status or the server network" error message
"[8003] file quarantine commands failed Check the agent's running status or the server network" error message is displayed.
"[8004] Invalid request. Proceed after refreshing'" error message
"[8004] Invalid request. Proceed after refreshing" error message is displayed.
"[8005] Invalid request. Proceed after refreshing'" error message
"[8005] Invalid request. Proceed after refreshing" error message is displayed.
"[8008] The file has already been quarantined/recovered. Proceed after refreshing'" error message
"[8008] The file has already been quarantined/recovered. Proceed after refreshing" error message is displayed.
"[8009] file recovery commands failed. Check the agent's running status or the server network" error message
"[8009] file recovery commands failed Check the agent's running status or the server network" error message is displayed.
"[8010] Failed to send the agent enable command. Check the agent's running status or the server network" error message
"[8010] Failed to send the agent enable command. Check the agent's running status or the server network" error message is displayed.
"[8012] The range that can be queried or accessed at once has been exceeded. Adjust the query period or conditions and proceed" error message
"[8012] The range that can be queried or accessed at once has been exceeded. Proceed by adjusting the search period or conditions" error message is displayed.
"[8013] The modified detection target setting information was sent, but it failed. Check the agent's running status or the server network" error message
"[8013] The modified detection target setting information was sent, but it failed. Check the agent's running status or the server network" error message is displayed.
"[8023] Unable to find the web server environment/path settings for the Pod" error message
"[8023] Unable to find the web server environment/path settings for the Pod" error message is displayed.
Learning resources
We offer various materials for you to explore. To learn more about WebShell Behavior Detector, check out these helpful links:
- FAQs: WebShell Behavior Detector FAQs
- The NAVER Cloud Platform blog: Experience simple and precise web shell detection with the Webshell Behavior Detector (WBD)!
If you're still having trouble finding what you need, click on the feedback icon and send us your thoughts and requests. We'll use your feedback to improve this guide.