[Help]: 5.15.20 - Wouldn't start

[PappyChappy1]

Controller Version

5.15.20

Describe Your Issue or Question

Has anyone had success upgrading to the latest beta on 5.15.20? It took my whole system down and while I was able to downgrade, I lost a lot of settings like client names, port names, my heat map, etc. I'm back on 5.15.8.2 at the moment. In the release notes it mentioned updates to Java that I wonder if it broke, or if it was just for me. For reference I'm running in Docker on a Mac.

Expected Behavior

For it to work

Steps to Reproduce

Install the beta

How You're Launching the Container

Using the provided docker compose file

Container Logs

did not save them

MongoDB Logs

No response

Additional Context

No response

[mbentley]

What tag were you using? How did you map your persistent data? To Docker volumes? If so, were the volumes deleted at some point?

I had yet to see a scenario where a controller just completely reset on it's own without something happening to the persistent data. I've seen situations where the controller is functionally broken due to upgrade and rollback attempts but that was a specific scenario.

[PappyChappy1]

I used the beta tag. It was using the standard docker volumes in the normal setup instructions. Volumes were not deleted - and not ALL persistent data was lost, which is odd.

…

On Feb 7, 2025, at 10:35 AM, Matt Bentley ***@***.***> wrote: What tag were you using? How did you map your persistent data? To Docker volumes? If so, were the volumes deleted at some point? I had yet to see a scenario where a controller just completely reset on it's own without something happening to the persistent data. I've seen situations where the controller is functionally broken due to upgrade and rollback attempts but that was a specific scenario. — Reply to this email directly, view it on GitHub <#536 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASXW6WG7EJARJRGEGUZSOYT2OTOGBAVCNFSM6AAAAABWWIO346VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMBZGYZTSMI>. You are receiving this because you authored the thread.

[PappyChappy1]

To clarify - the DHCP reservations (for example) remained intact, but maybe those are stored in the router and not the controller?

[mbentley]

I am not entirely sure about how and where data is stored when you have a connected router to a controller as I only have access points. I might suggest posting on the TP-Link forums and/or the beta thread on the forums in case it is a bug.

Regarding the deprecation of Java older than Java 17, in the docker image, it's been running Java 17 (openjdk-17-jre-headless) for a while so that hasn't changed in the controller.