vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/ces/umn/ces_faq_0037.html
gtema f6f2ca6fa5 Update CES UMN 
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: gtema <artem.goncharov@gmail.com>
Co-committed-by: gtema <artem.goncharov@gmail.com>
2022-12-07 15:46:48 +00:00

3.1 KiB
Raw Permalink Blame History

What Should I Do If the Service Port Is Used by the Agent?

Cloud Eye Agent uses HTTP requests to report data. Any port in the range obtained from path /proc/sys/net/ipv4/ip_local_port_range may be occupied. If any service port is used by the Agent, you can modify path /proc/sys/net/ipv4/ip_local_port_range and restart the Agent to solve the problem.

Procedure

  1. Log in an ECS or BMS as user root.
  2. Open the sysctl.conf file:

    vim /etc/sysctl.conf

  3. (Permanent change) Add new ports to the sysctl.conf file:

    net.ipv4.ip_local_port_range=49152 65536

  4. Make the modification take effect:

    sysctl -p /etc/sysctl.conf

    • The permanent change still takes effect after the ECS or BMS is restarted.
    • For temporary modification (which expires after the ECS or BMS is restarted), run # echo 49152 65536 > /proc/sys/net/ipv4/ip_local_port_range.
  5. Run the following command to restart the Agent:

    /usr/local/telescope/telescoped restart

    For Windows, in the directory where the Agent installation package is stored, double-click the shutdown.bat script to stop the Agent, and execute the start.bat script to start the Agent.

Parent topic: Server Monitoring