Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
Hi All, when running the status script on my installation that seems to be working fine, I get a 401 from the various status calls. Here is the output of the status command:
Detected Appian version 19.4.150.0 from build.info GET request sent to appian-rt-wb-03.hc-sc.gc.ca:7070/.../status returned a 401 status code GET request sent to appian-rt-wb-03.hc-sc.gc.ca:7070/.../status returned a 401 status code GET request sent to appian-rt-wb-03.hc-sc.gc.ca:7070/.../status returned a 401 status code The service manager is not running. All engines are unavailable.
I have no problem using this installation and looking at processes, everything seems to be running (15 K processes, 4 q processes etc).
Has anyone seen this before and what to do to correct?
Thanks,
Jeff
Discussion posts and replies are publicly visible
Hi Jeff!
Could you confirm if you're running the status script as the user who installed Appian on the server?Could you also confirm if there is any network or firewall issues that would be blocking these requests?
Thanks!
I did confirm those things. When I looked up 401 I became suspicious of the password I was using and found that it had fallen out of date. With the right password the error went away.
Is this the service manager password? I stopped my services, changed it, and started them again. Still getting the 401s. (windows environment). Though my Kafka and Zookeeper both say reachable.
Apparently someone was messing with my config. Restored the repo and it's working now.