User story #7549
closed
Allow cfengine to use a different port than 5309
Description
Please allow the configuration of which port cf-serverd should use.
5309 might be blocked/reserved internally for some reasons by other application, and one might want to run in on a higher but free port (like 65309)
Updated by Janos Mattyasovszky about 9 years ago
- Subject changed from Allow cfengine to use a different port than 5309 to Allow cfengine to use a different port than 5308
- Description updated (diff)
Updated by Janos Mattyasovszky about 9 years ago
- Subject changed from Allow cfengine to use a different port than 5308 to Allow cfengine to use a different port than 5309
- Description updated (diff)
Updated by Nicolas CHARLES about 9 years ago
Isn't the entry in file /opt/rudder/etc/rudder-web.properties doing what you need ?
rudder.community.port=5309
Updated by Janos Mattyasovszky about 9 years ago
Nicolas CHARLES wrote:
Isn't the entry in file /opt/rudder/etc/rudder-web.properties doing what you need ?
[...]
Yes, it is. However... Have you ever tried to change that on a full-blown system? :-)
- you change the port
- you restart rudder-jetty
- rudder regenerates the promises for the server
- policy downloads fail since all cf-execd's are running on port 5309
what would be the advised way to change it in an existing environment?
Updated by François ARMAND almost 9 years ago
- Assignee set to Benoît PECCATTE
Benoit, or Alexis maybe, have you an idea on that one ?
Updated by Benoît PECCATTE almost 9 years ago
Changing the port of an existing infra can be tricky.
We might not be able to support it at all.
Having a specific port for a new installation is doable, but we need to change the port value to a variable (not very hard) and to change the default port for agents.
The second part need a specific package or a large change in the way we connect from an agent.
Updated by Benoît PECCATTE over 8 years ago
- Target version set to Ideas (not version specific)
Updated by