Skip to content

Trouble Shooting

Agent Installation Troubleshooting

When a "httpd / nginx / JAVA Not Found" Error Occurs

The Agent installation script automatically detects running web server processes. If the web server is stopped, the error above will occur. In this case, you must start the web server first and then retry the installation, or proceed with the relevant settings manually.

Installation Error Example

[root@localhost DeepFinder]# ./setup.sh 1.1.1.1 1***
SERVER IP : 1.1.1.1
AGENT ID : 1***
SYSTEM KERNEL : 2.6
CHECK OS : Linux
CHECK OS BIT : x86_64 (64 bit)

HTTPD Not found


When Large File Uploads Fail in an Apache-Tomcat Integrated Environment

In an environment where requests are forwarded to Tomcat via Apache's mod_proxy, the file transfer method may be changed to chunked transfer encoding after the DeepFinder module is applied.
If this causes issues with large file uploads, add the option below to the Apache configuration file (httpd.conf) and then gracefully restart the service.

# It allows request bodies to be sent to the backend using chunked transfer encoding.
SetEnv proxy-sendchunked 1


When an Antivirus Program Blocks DeepFinder

Some antivirus programs may misdiagnose key files or processes of the DeepFinder Agent as threats and quarantine or block them.
Before installation, add the following items to the exception (trusted) list in your antivirus program's settings to ensure the Agent can operate correctly. * Installation Path: C:\DeepFinder (including subfolders) * Main Processes: agent.exe, starter.exe, updater.exe, etc.


When Korean Characters in Parameters are Broken After WAS Installation

The issue of broken Korean characters in web application parameters after applying the Agent can occur due to a mismatch in encoding methods between the JVM and the web service.
In this case, resolve the problem by changing the filter_encoding value in the config.xml file to match your web service environment.

config.xml Filter_Encoding Values
<Filter
 localhost="127.0.0.1"
 filter_alive_check_time="1800"
 policy_update_time="30"
 filter_encoding=”UTF-8”
 bypass="0"
/>		 1) filter_encoding="utf-8"
2) filter_encoding=”_utf-8”
3) filter_encoding=”euc-kr”
4) filter_encoding=”_euc-kr”
5) filter_encoding=”ms949”


When Pages are Duplicated or Broken After WAS Installation

Due to differences in how some WAS platforms handle response data, pages may appear broken or be duplicated after the Agent filter is applied.
In this case, the issue can be resolved by changing the res_type value in the config.xml file (to 0 or 1).

config.xml Available res_type Settings
<Filter
 ...
 filter_encoding=”UTF-8”
 res_type="0"
/>		 1) 0 (default)
2) 1


When Communication with the Manager Server Fails After Agent Installation

  • Check the Firewall: Verify that outbound communication from the server where the Agent is installed to the Manager server is allowed in the firewall.
    (Example verification command: telnet {Manager IP} 10012)

  • Check the Configuration File: Open the Agent configuration file (conf/config.xml) to verify that the Manager connection information (aid, authdata, svrip, etc.) is entered correctly. If incorrect, modify the file and restart the Agent service.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<Agent
*aid=""                                    // Agent ID
*authdata=""                               // Auth Key (Domain Group Key)
    ssl_pemfile="deepfinder.pem"            // ssl pem file name (certs directory)
    ssl_password="isdwsx"                   // pem file password
*svrip=""                                   // Manager Server IP
    svrproto="tcp"                          // protocol  tcp/ssl
    svrport="10012"                         // server port
    filter_check_url="http://localhost/"    //filtercheck url : default http://localhost/
    debug="0"
    logfilesize="2"                         // size per log file (default 2MB)
/>

Note

If you attempt to connect more Agents than the number permitted by your license, a License MaxAgent over error will be recorded in the Manager's server.log, and the connection will be refused.
In this case, please renew your license to match the required number of Agents.


When a Website Failure Occurs After Agent Installation

If issues such as being unable to access the website occur after Agent installation, please take the following steps for accurate cause analysis before contacting the technical support team.
1. Back up the entire DeepFinder installation directory.
2. Uninstall the DeepFinder Agent or stop the related services.

When a "404 Not Found" Response Occurs After Applying the WAS Agent

If a 404 Not Found error occurs after applying the Agent filter, the cause may be that the WAS cannot find the DfFilter.jar file.
Please re-verify that the two paths below are set correctly.
1. Check if the DfFilter.jar file was actually copied to the WAS library path.
2. Check if the jarfile path in the <Filter> section of the config.xml file is correct.

When a "Server Process Alert" Popup Appears After Manager Login

If a "Process Down" alert popup appears when you log in to the Manager, it means that some services that constitute the Manager have stopped.
First, go to the [Settings] > [Server Restart] tab and try restarting the process that is in a 'Down' state to see if it recovers.


If the problem persists after restarting, please contact the technical support team.