> For the complete documentation index, see [llms.txt](https://docs.flopsar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flopsar.com/3.0/faq/troubleshooting.md).

# Troubleshooting

## Manager stops periodically

I see the following message in the `Manager` log file:

```
[FATAL ][PID] Flopsar cannot run any longer. No license control file found. Shutdown initiated.
```

`Manager` creates a license lock file in `/tmp` directory. If this file is deleted, then `Manager` stops. It occurs on Red Hat-like distributions usually. In order to prevent the operating system from deleting this file, you can create a file `/usr/lib/tmpfiles.d/flopsar.conf` with the following contents:

```
x       /tmp/*.flp
```

{% hint style="info" %}
Please, refer to `tmpfiles.d(5)` man page for details.
{% endhint %}

## I see DROPPED in the Parameters column in `Workstation`

This means that instrumented JVM drops parameters due to memory pressure. Either, increase memory limits for your application or decrease instrumentation.


---

# 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://docs.flopsar.com/3.0/faq/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.