• Trainings are intended to give you a general idea. You need to reinforce what you’ve learned by applying it. Some of the features mentioned in the training may not be included in your license.

Problem Diagnosis

We will start the training with the problem diagnosis method. Then we will review the Troubleshooting sections for Discovery, Classification, and others. It will be very useful for you to review these sections separately.

Sometimes the problem is an obvious error message, an Agent not seeing the GEODI server, perhaps a warning message, or a process that is not working as you expect. Diagnosing is half the solution. Attempting to find a solution without identifying the source of the problem is usually a waste of time.

Support Site Troubleshooting​ Shooting Sections → The troubleshooting sections on the support site are the biggest help for monitoring and troubleshooting. Before you encounter any problems, you should read these sections to get an idea about the topics.

Support Q → It will answer many questions. According to these answers, you can find the answer and solution you are looking for on the relevant pages.

System Problems → The solution to many problems is outside of GEODI. You need basic system and diagnostic knowledge to solve problems such as no network access and disk fullness. You can understand the answer to the question of why a client cannot see the GEODI server with Ping and Telnet.

Logs → Logs are among the most valuable resources for diagnosing a problem. The operating system and GEODI record many logs. GEODI Logs

GEODI Reports → Settings/System Reports contains reports on errors, indexes, and system health. In some cases, these reports reveal possible causes.

Assumptions

Assumptions or bias are often among the most important factors that make it difficult to detect errors. When you encounter an error or an unexpected situation, if your first candidate is the software, GEODI, it is very likely that you will be wrong.

Although GEODI is not completely error-free like many enterprise software, it is free from errors that may disrupt the process. The first possible reason why a process that works flawlessly for thousands of users may fail in a certain environment is the environment or configuration.

Reading Error Logs

We can consider GEODI Error logs in a few main categories.

1. Application logs

2. Discovery/Indexing logs

GEODI also keeps logs for tasks such as application and classification.

Application Error Logs

<geodidatafolder>\Dece\Logs\GEODI\AppError

Application logs include situations encountered during GEODI operation. Many situations such as a location not being accessible due to disk full or authorization issues, a json file with inappropriate format/ encoding , a macro definition that does not work are logged here.

Discovery/Indexing Logs

They are in <geodidatafolder>\Dece\Geodi\Workspaces\SampleDiscoveryProject\Logs directory under every project/workspace. SampleDiscoveryProject is used in the example.

Logs are in Warning, Information and Error categories.

Information and Warning messages are generally about content types and access permissions. Corrupt or encrypted files, unopenable ZIPs , inaccessible web pages; Authorizations that occur in subdirectories of the source you introduce as a source are logged as information.

Some of the error messages are configuration related, like a bad json file or a bad macro.

..

Authority Issues

An issue that needs to be managed from the installation phase. Possible problems with the authorizations of the establishing user and service user, and the authorizations of users accessing the resources will be returned as errors.

Network-Related Situations

This is the most common problem group. You will often encounter situations such as agents not seeing GEODI , closed ports, content blocked by firewall .

The ports that must be open and access conditions are specified in the relevant document. You must ensure that these conditions are met.

You should have basic knowledge of Ping, Telnet and other tools.

Disk and Other Resources

Disk insufficiency is a common situation. Make sure that there is enough disk for indexing and backups.

CPU usage may increase depending on content types and indexing speed. You can either reduce the speed or wait for the usage to decrease.

Performance

We include situations such as a slow progressing discovery or an unresponsive server as a performance problem . There can be several reasons for performance problems . Most of them will not be reflected in the logs.

1. Server capacity → insufficient CPU/Memory/Disk → You can reduce the discovery speed.

2. Slow source → a source that cannot deliver data fast enough

3. Network problems → You access all resources via the network. Slowness and other possible network problems can cause general problems.

4. Simultaneous usage → Usage such as intensive search while discovery is ongoing. → You should reduce the discovery speed or separate the operations to separate servers.