Ports for api and authentication services can't be changed

[hagay3]

Hi,
I'm trying to change the port for authentication module with no luck, the port remains on '9100' .
After the change I did also st2ctl restart.

I tried to edit this section, with new port 9109

[auth]
port = 9109
host = 0.0.0.0
use_ssl = True

Stackstrom process still listens on 9100 port

tcp        0      0 127.0.0.1:9100          0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:9101          0.0.0.0:*               LISTEN
tcp        0      0 127.0.0.1:9102          0.0.0.0:*               LISTEN

I checked also the api and it's the same issue.

[Kami]

To change listening ports on production installation (where installed using packages and services are managed by service manager and not running in a standalone mode), you need to change ports in the service manager files.

For example, for Ubuntu, that is in the upstart file - https://github.com/StackStorm/st2-packages/blob/master/packages/st2/debian/st2.st2api.upstart

Note to us: We should either document this or also utilize st2.conf when services are managed by a service manager.

[hagay3]

I'm not sure what you meant by saying
"services are managed by service manager and not running in a standalone mode".
What is exactly standalone mode?

[hagay3]

I still cant get how to change the port.
OS is Ubuntu 14.04

[arm4b]

@hagay3 For Ubuntu14, edit the upstart init file located at: /etc/init/st2auth.conf.
You'll find the port definition there.

When you're done with modifying, don't forget to reload upstart configuration: sudo initctl reload-configuration and restart your service.

Hope that answers your question. Let us know if that worked or not.

[estee-tew]

https://stackstorm.slack.com/archives/community/p1492346619722875

[hagay3]

Thanks @armab it did the magic.
I still think one conf file should utilize the port as it does in many other products (mysql, cassandra etc..)

[mbrannigan]

I was having this issue with CentOS 7 and fixed it this way:

1. Edit /usr/lib/systemd/system/st2api.socket
   Change ListenStream=127.0.0.1:9101 to ListenStream=0.0.0.0:9101

2. Reload systemd
   # systemctl daemon-reload

3. Reload st2api
   # st2ctl restart-component st2api

4. Check to see if it's re-bound

# ss -lnt | grep 9101
LISTEN     0      128          *:9101                     *:*

[arm4b]

Cross-linking related issue: #2676

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically marking is as stale. If this issue is not relevant or applicable anymore (problem has been fixed in a new version or similar), please close the issue or let us know so we can close it. On the contrary, if the issue is still relevant, there is nothing you need to do, but if you have any additional details or context which would help us when working on this issue, please include it as a comment to this issue.

[nicholasamorim]

Yeah, this is a problem indeed. I wasn't lucky with setting up ST2 on the Swarm. Or rather.. I actually was but the complexity was too much.

So I decided to simply register ST2's services on Consul so that I can have dynamic DNS to use on nginx upstream section. So that if ST2 suddenly spawns on another server due to failure in the previous one, nginx would still route nicely.

But it only binds to 127.0.0.1 making this impossible.