> For the complete documentation index, see [llms.txt](https://docs.portainer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.portainer.io/sts/faqs/troubleshooting/logs-errors-and-debugging/failed-logging-user-activity-error-in-portainer.md).

# “Failed logging user activity” error in Portainer

#### **Issue**

You may encounter the following error in Portainer:

> **“Failed logging user activity”**

#### **Cause**

This error typically occurs when the useractivity.db file is missing or inaccessible within the Portainer Server’s volume. This can impact:

* Viewing **activity logs** within Portainer
* **Creating backups**, as logging is part of the process

#### **Solution**

To resolve this issue:

1. **Restart the Portainer Server container**

   Restarting the container will regenerate the useractivity.db file if it is missing and restore normal logging functionality.

#### **Steps to Restart (Docker Example)**

```
docker restart portainer
```

If this happens frequently, consider checking your volume mappings and file system permissions to ensure Portainer can consistently access and write to its data volume.


---

# 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.portainer.io/sts/faqs/troubleshooting/logs-errors-and-debugging/failed-logging-user-activity-error-in-portainer.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.