[GH-ISSUE #792] Unable to turn on AOF after version updates #499

New issue

Closed

opened 2026-03-02 02:16:50 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 02:16:50 +03:00

Owner

Originally created by @evolantechnology on GitHub (Nov 8, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/792

Originally assigned to: @wh1te909 on GitHub.

Server Info (please complete the following information):

OS: Ubuntu 20.04
Browser: Chrome
RMM Version (as shown in top left of web UI): 0.9.1

Installation Method:

[ x] Standard

Agent Info (please complete the following information):

Agent version (as shown in the 'Summary' tab of the agent from web UI): 1.6.2
Agent OS: Win 10

Describe the bug
"ERR Unable to turn on AOF. Check server logs." Getting this error at the end of a version update, after all services are automatically started back up.

To Reproduce
Steps to reproduce the behavior:

After running ./update.sh and waiting for it to complete, the above error displays after the update completes and services start up.

Expected behavior
The update should complete successfully with no errors.

Screenshots

Additional context
Add any other context about the problem here.

Originally created by @evolantechnology on GitHub (Nov 8, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/792 Originally assigned to: @wh1te909 on GitHub. **Server Info (please complete the following information):** - OS: Ubuntu 20.04 - Browser: Chrome - RMM Version (as shown in top left of web UI): 0.9.1 **Installation Method:** - [ x] Standard **Agent Info (please complete the following information):** - Agent version (as shown in the 'Summary' tab of the agent from web UI): 1.6.2 - Agent OS: Win 10 **Describe the bug** "ERR Unable to turn on AOF. Check server logs." Getting this error at the end of a version update, after all services are automatically started back up. **To Reproduce** Steps to reproduce the behavior: 1. After running ./update.sh and waiting for it to complete, the above error displays after the update completes and services start up. **Expected behavior** The update should complete successfully with no errors. **Screenshots** ![Screen Shot 2021-11-07 at 8 02 38 PM](https://user-images.githubusercontent.com/79764766/140674421-a48d524d-4640-48d4-957c-f116f619137c.png) **Additional context** Add any other context about the problem here.

kerem

2026-03-02 02:16:50 +03:00

closed this issue
added the
dev-triage
label

kerem commented

2026-03-02 02:16:51 +03:00

Author

Owner

@silversword411 commented on GitHub (Nov 8, 2021):

I get the same here. I think it's something to do with redis and log replaying feature. Haven't found a side-effect from it yet.

@silversword411 commented on GitHub (Nov 8, 2021): I get the same here. I think it's something to do with redis and log replaying feature. Haven't found a side-effect from it yet.

kerem commented

2026-03-02 02:16:51 +03:00

Author

Owner

@silversword411 commented on GitHub (Dec 3, 2021):

We're going to close this, you can ignore. Let us know if you see something come of it

@silversword411 commented on GitHub (Dec 3, 2021): We're going to close this, you can ignore. Let us know if you see something come of it

kerem referenced this issue

2026-03-14 03:14:33 +03:00

[GH-ISSUE #499] Automation Manager - Policy Exclusions for Excluded agents add description in display #2255