You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the port that st2auth listens on is defined in st2.conf and in the systemd service file as a hardcoded value. I was wondering if it was possible to get the port number changes to something else, like 9105, before its setup as a service so that when the service is created, it'll reflect that new port?
Reason for the change is node_exporter uses 9100 to allow Prometheus to scrape the metrics from it. Installation of the exporter is done during our VM provisioning process so its something that would be less likely to change.
I'd like to avoid directly modifying the systemd file, if possible.
The text was updated successfully, but these errors were encountered:
@nzlosh Is the port that is in the systemd service file relevant any more (ST2 3.7 onwards)? I thought the value in st2.conf was the only value now needed to be changed, but the systemd file still shows:
But if I change st2.conf to use a different port, the systemd file is unchanged, but it does indeed listen on the port that is specified in st2.conf.
So I'm wondering if for @rdancel001's query he can ignore the value in the systemd file, and just needs to configure the port in st2.conf now. And perhaps we have a tidy-up issue that we have the bind address in the DAEMON_ARGS in the systemd file?
After looking into this further, it appears the service files will need to be automatically generated too, I'll prepare a patch next week when I return from holiday.
I noticed that the port that st2auth listens on is defined in st2.conf and in the systemd service file as a hardcoded value. I was wondering if it was possible to get the port number changes to something else, like 9105, before its setup as a service so that when the service is created, it'll reflect that new port?
Reason for the change is node_exporter uses 9100 to allow Prometheus to scrape the metrics from it. Installation of the exporter is done during our VM provisioning process so its something that would be less likely to change.
I'd like to avoid directly modifying the systemd file, if possible.
The text was updated successfully, but these errors were encountered: