Ziti Controller Update to 2+ Breaks Service

Support General Questions
1

Hi all. I finally had the time and decided to start updating my Ziti stack. I started with the controller, under the assumption that the controller would maintain compatibility to outdated ziti routers while ziti routers can hit a state where they're newer than what's supported by the ziti controller.

Anyway, the update ran and I am now on 2+. But, after the update, the ziti controller service fails to start with a 217/User exit code. I wasn't aware that the ziti controller service was running in any specific user context by default. Has anyone else run into this or an easy fix? (This was a non-docker install.)

image
image959×140 30.3 KB

2

Not sure about a an error.

But could try get more logs?
Try journalctl -fu ziti-controller command

3

image
image1116×475 159 KB

Here's the output. I haven't gotten a chance to dig back into any of my notes from the installation, but I don't remember setting a user context on original install for the service.

4

Maybe dummy questions, but have you rebooted server?

5

Yep. First thing I did after the update. Part of me knew that wouldn't fix it but wanted to hold out hope.