> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.206/help-center-index/faqs/installer-faqs/logs-generated-during-oim-installation.md).

# Where to find the logs generated during the application's installation?

### Description

Where to find the logs generated during <code class="expression">space.vars.SITENAME</code> installation?

Logs generated during <code class="expression">space.vars.SITENAME</code> installation are useful in identifying the reason for failure (if any).

### Solution

<code class="expression">space.vars.SITENAME</code> installation progress gets logged in an `Install.log` file. It contains details of all the steps performed in the process, along with the details of failures (if any).\
This file is located under the 'logs' folder in <code class="expression">space.vars.SITENAME</code> installation path.

For example:

Operating System: **Windows**

* Installation Path: `C:\Program Files\OpsHub`
* Location of log file: `C:\Program Files\OpsHub\logs\Install.log`

Operating System: **Linux**

* Installation Path: `/usr/local/OpsHub`
* Location of log file: `/usr/local/OpsHub/logs/Install.log`


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.opshub.com/v7.206/help-center-index/faqs/installer-faqs/logs-generated-during-oim-installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.