> For the complete documentation index, see [llms.txt](https://documentation.ocsinventory-ng.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.ocsinventory-ng.org/administrator-docs/server-setup/troubleshooting.md).

# Troubleshooting

### Log files

OCS generates several log files to help you diagnose issues and monitor application state. Log verbosity depends on the settings in [General configuration](/administrator-docs/server-setup/configuration/basics/general-configuration.md#server-core-server-configuration-settings).

These logs are available in the backend server `logs` directory:

* **ocs\_backend.log**: Logs activity related to the OCS application.
* **ocs\_django.log**: Contains Django-related logs.
* **ocs\_collection.log**: Contains inventory collection logs.
* **ocs\_management.log**: Contains management command logs, such as automation tasks.
* **ocs\_auth.log**: Contains authentication logs (local account, CAS, LDAP and OIDC login).

### Server information

The **Server information** page gives you a snapshot of your OCS environment. Use it when troubleshooting an issue or opening a support request or GitHub issue.

It is accessible via **Configurations → General → Server information**.

**Interface**

| Field              | Description                               |
| ------------------ | ----------------------------------------- |
| `frontend_version` | Web console version                       |
| `browser`          | Browser name detected from the user agent |
| `browser_version`  | Version of the detected browser           |

**Server**

| Field                      | Description                                     |
| -------------------------- | ----------------------------------------------- |
| `backend_version`          | Backend API version                             |
| `authentication_type`      | Authentication methods configured on the server |
| `infrastructure_type`      | Deployment infrastructure type                  |
| `operating_system`         | Host operating system                           |
| `operating_system_version` | OS version                                      |
| `db_engine`                | Database engine in use                          |
| `ocs_configuration`        | Active OCS configuration options                |
| `python_version`           | Python runtime version                          |
| `python_libs_version`      | Versions of key Python libraries                |

#### Copying diagnostic information

Each panel includes a **Copy** button that copies its content as JSON. The **Copy all** button copies both panels at once. Include this output when you open a GitHub issue or submit a support request.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.ocsinventory-ng.org/administrator-docs/server-setup/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.