content-sync - KNW-2134 translation finished, pick-25

Author: thomaskoslowski

src/common/en/agent_linux.asciidoc

@@ -16,7 +16,6 @@ xref:agent_deployment#[Automatic Agent Updates]
 {related-end}
 
 
-
 [#intro]
 == The Linux agent
 
@@ -99,7 +98,6 @@ The Agent Controller is started as a daemon of `systemd` and is coupled to it as
 In pull mode, it listens on TCP port 6556 for incoming connections from the {CMK} xref:glossar#site[site] and queries the agent script via a Unix socket (of a `systemd` unit).
 
 
-// start proofreading
 [#slideout]
 == Quick installation
 
@@ -111,12 +109,11 @@ The xref:intro_setup_monitor#linux[Beginner's Guide] describes the process in de
 
 The main advantage of the slideout is that it displays directly in the GUI the appropriate commands for downloading, installing, and registering a Linux host.
 You can copy any command to the clipboard and then run it on the host.
-For a Linux host, the agent package is downloaded using curl via the REST API, installed with the `dpkg` or `rpm` commands, and the host is finally registered with `cmk-agent-ctl`.
+For a Linux host, the agent package is downloaded using curl via the REST API, installed with the `dpkg` or `rpm` commands, and finally, the host is registered with `cmk-agent-ctl`.
 endif::[]
 
-
 ifdef::saas[]
-{CMK} guides you through the user interface to download, install, and register the {CMK} agent on a host — and even add it to monitoring.
+{CMK} guides you through the user interface to download, install, and register the {CMK} agent on a host -- and even add it to monitoring.
 To do this, {CE} provides two assistants that guide you through the necessary steps in a _slideout_.
 
 * One slideout helps you to automatically add a host to the xref:glossar#configuration_environment[configuration environment] and the xref:glossar#monitoring_environment[monitoring environment]. +
@@ -125,20 +122,18 @@ This uses the agent packages prepared for auto-registration for Linux and Window
 * The other slideout guides you through the manual process of adding a host to the configuration environment.
 Here, the standard packages available for Windows and Linux are used. 
 
-Both slideouts — one for xref:intro_setup_monitor#first_auto[automatic creation] and one for xref:intro_setup_monitor#first[manual creation] — are described in the Beginner's Guide.
+Both slideouts -- one for xref:intro_setup_monitor#first_auto[automatic creation] and one for xref:intro_setup_monitor#first[manual creation] -- are described in the Beginner's Guide.
 
 The main advantage of the slideouts is that they display directly in the GUI the appropriate commands for downloading, installing, and registering a Linux host.
 You can copy any command to the clipboard and then run it on the host.
 endif::[]
 
-
 To make the process as simple as possible, authentication in the commands required for download and registration is performed using a _one-time token_.
 This token is valid for successful execution within a limited time period.
-It is generated first before being used in the aforementioned commands.
+The token is first generated before being used in the aforementioned commands.
 
 Quick download, installation, and registration via slideout are particularly well-suited for quickly creating the first hosts in {CMK}.
 Detailed information on all possible methods for installing a standard agent (for example, without a one-time token, using xref:glossar#agent_plugin[agent plug-ins], and with troubleshooting) is provided in the following chapters.
-// end proofreading
 
 
 [#install]
@@ -182,14 +177,12 @@ Whether you need RPM or DEB depends on the Linux distribution on which you want
 
 Before installation you will need to get the package and bring it to the host (for example with `scp` or WinSCP) where you want the agent to run.
 
-// start proofreading
 [IMPORTANT]
 ====
 As of March 31, 2026, the agent packages provided by {CMK} do not yet include an Agent Controller for `aarch64` (ARM with a 64-bit instruction set).
 Use the xref:glossar#agent_bakery[Agent Bakery] to create custom packages that include the Agent Controller for `aarch64` or both architectures.
 You can specify the included architecture of the Agent Controller via the rule [.guihint]#Setup > Agents > Windows, Linux, Solaris, AIX > Agent rules > Customize agent package (Linux)#.
 ====
-// end proofreading
 
 
 [#download_gui]
@@ -624,18 +617,16 @@ Confirm with `Y` to complete the process.
 If no error message is displayed, the encrypted connection will have been established.
 All data will now be transmitted in compressed form via this connection.
 
-If you want to disable the interactive check of the certificate--for example to fully automate the registration--you might use the additional parameter `--trust-cert`.
+If you want to disable the interactive check of the certificate -- for example to fully automate the registration -- you might use the additional parameter `--trust-cert`.
 The transferred certificate will be automatically trusted in this case.
 Keep in mind that you should take other measures to verify the integrity of the certificate.
 This can be performed (manually or scripted) by inspecting the xref:files[file] `/var/lib/cmk-agent/registered_connections.json`.
 
-// start proofreading
 [TIP]
 ====
 Using the `cmk-agent-ctl` command, you can register the Agent Controller and the xref:glossar#agent_updater[Agent Updater] _at the same time_.
 You can learn how this works in the article on xref:agent_deployment#one_registration[automatic agent updates].
 ====
-// end proofreading
 
 
 [#autoregister]
@@ -913,87 +904,11 @@ So that you can work with `less` here, you must combine standard output (STDOUT)
 [#networkrequirements]
 === Network environment for registration
 
-If registering a host fails even before a certificate is presented, knowledge about the ways of communication can help identifying the problem -- and of course solving it.
-
-// This block is outdated
-// delete from here
-After entering the `cmk-agent-ctl register` command, the Agent Controller first asks the {CMK} server for the Agent Receiver port using the REST API.
-As second step a connection to the Agent Receiver is established to request the certificate.
-You can simulate the first request on the host with a program like `curl`:
+If registering a host fails even before a certificate is presented, knowledge about the connections used for communication can help in identifying the problem -- and of course in solving it.
 
-[{shell-raw}]
-----
-{c-root} curl -v --insecure https://mycmkserver/mysite/check_mk/api/1.0/domain-types/internal/actions/discover-receiver/invoke
-----
-
-The parameter `--insecure` instructs `curl` to skip the certificate check.
-This behavior reflects the behavior of the Agent Controller in this step. 
-The response is only a few bytes, containing the port number of the Agent Receiver.
-For the first site this is usually just `8000`, for the second `8001` and so on.
-
-ifdef::onprem[]
-Common problems regarding this request are:
-
-* The {CMK} server is unreachable from the host.
-* The port used by the REST API differs from the default ports 443 (https) or 80 (http).
-endif::[]
-
-ifdef::saas[]
-A common problem with this request is that the {CMK} server is unreachable from the host.
-endif::[]
-
-When the above request fails you might change routing or firewall settings to enable access.
-
-In case the host you are trying to register uses an HTTP proxy, `curl` will use it, but `cmk-agent-ctl` won't do so with default settings.
-Use the additional `--detect-proxy` option to instruct `cmk-agent-ctl` to use a proxy configured via system settings.
-
-ifdef::onprem[]
-However often it may be easier to find out the port of the Agent Receiver and note it down.
-To do so, on the {CMK} server run, logged in as site user:
-
-[{shell-raw}]
-----
-{c-omd} omd config show | grep AGENT_RECEIVER
-AGENT_RECEIVER: on
-AGENT_RECEIVER_PORT: 8000
-----
-endif::[]
-
-Now you can specify the port when entering the command for registration.
-This skips the first request to the REST API.
-Communication then takes place directly with the Agent Receiver without any detours:
-
-[{shell}]
-----
-{c-root} cmk-agent-ctl register \
-             --hostname mynewhost \
-             --server mycmkserver:8000 \
-             --site mysite \
-             --user agent_registration \
-             --password 'PTEGDYXBFXVGNDPRL'
-----
-
-Port 8000 also must be reachable from the host.
-In case it is not, you will get this error message:
-
-[{shell-raw}]
-----
-ERROR [cmk_agent_ctl] Connection refused (os error 111)
-----
-
-Equivalent to port 443
-ifdef::onprem[]
-(respectively 80)
-endif::[]
-mentioned above, you can now adjust routing or firewall settings so that the host to be registered can reach the {CMK} server on the Agent Receiver's port (8000 or 8001...)
-// delete to here
-
-// This block is new
-// start translation
-////
-Um herauszufinden, warum die Registrierung nicht erfolgreich war, führen Sie die Registrierung noch einmal mit der zusätzlichen Option `-vv` durch.
-Dadurch werden Ihnen nicht nur Fehler, sondern auch zusätzliche Informationen und Debug-Meldungen ausgegeben.
-Ist beispielsweise der {CMK}-Server vom Host aus nicht erreichbar, wird die Ausgabe etwa folgendermaßen aussehen:
+To find out why the registration failed, run the registration again with the additional option `-vv`.
+This will display not only errors but also additional information and debugging messages.
+For example, if the {CMK} server is not accessible from the host, the output will look something like this:
 
 [{shell}]
 ----
@@ -1013,18 +928,18 @@ DEBUG [cmk_agent_ctl::site_spec] http error: "Failed to discover agent receiver
 ERROR [cmk_agent_ctl] Failed to discover agent receiver port from Checkmk REST API, both with http and https. Run with verbose output to see errors.
 ----
 
-Nach Absetzen des Befehls `cmk-agent-ctl register` fragt der Agent Controller zunächst über die REST-API den {CMK}-Server nach dem Port des Agent Receivers.
-In der oben gezeigten Ausgabe ist zu erkennen, dass die Verbindung über die REST-API fehlgeschlagen ist, und zwar sowohl über HTTPS als auch über HTTP.
-Logischerweise kann es an dieser Stelle mit der Registrierung nicht weitergehen.
+After executing the `cmk-agent-ctl register` command, the Agent Controller first queries the {CMK} server via the REST API to determine the port used by the Agent Receiver.
+The output shown above indicates that the connection via the REST API failed, both over HTTPS and HTTP.
+Consequently, the registration process cannot proceed at this point.
 
-An diesem Punkt können Sie die Routing- oder Firewall-Einstellungen so verändern, dass der Zugriff vom Host auf den {CMK}-Server möglich ist.
-Wenn der zu registrierende Host einen HTTP-Proxy verwendet, weisen Sie `cmk-agent-ctl` mit der zusätzlichen Option `--detect-proxy` an, den systemweit konfigurierten Proxy zu nutzen.
+In such a situation you can modify the routing or firewall settings to allow access from the host to the {CMK} server.
+If the host to be registered uses an HTTP proxy, instruct `cmk-agent-ctl` to use the system-wide configured proxy with the additional option `--detect-proxy`.
 
-Ist der {CMK}-Server erreichbar und die Registrierung schlägt dennoch fehl, dann liegt das Problem an einer anderen Stelle.
-Möglicherweise ist die REST-API nicht erreichbar oder antwortet nicht mit dem richtigen Port für den Agent Receiver.
+If the {CMK} server is reachable and registration still fails, the problem lies elsewhere.
+The REST API may be unreachable or may not be responding on the correct port for the Agent Receiver.
 
 ifdef::onprem[]
-Sie können auf dem {CMK}-Server als Instanzbenutzer prüfen, welchem Port der Agent Receiver zugeordnet ist:
+As a site user you can check which port the Agent Receiver is assigned to on the {CMK} server:
 
 [{shell-raw}]
 ----
@@ -1035,18 +950,17 @@ AGENT_RECEIVER_PORT: 8000
 endif::[]
 
 ifdef::saas[]
-In {CE} wird dem Agent Receiver normalerweise der Port 8000 zugewiesen.
+In {CE}, port 8000 is normally assigned to the Agent Receiver.
 endif::[]
-Den korrekten Port können Sie bei der Registrierung zusammen mit dem {CMK}-Server explizit angeben (`--server mycmkserver:8000`), um sicherzustellen, dass der Agent Receiver erreicht wird.
-So wird die erste Anfrage via REST-API übersprungen, und die Kommunikation findet ohne Umwege direkt mit dem Agent Receiver statt.
+You can explicitly specify the correct port during registration, along with the {CMK} server (`--server mycmkserver:8000`) to ensure that the Agent Receiver can be reached.
+This skips the first request via the REST API, and communication takes place directly with the Agent Receiver without any detours.
 
-Möglicherweise erhalten Sie trotz korrekter Port-Angabe die Fehlermeldung `Connection refused`.
-In diesem Fall können Sie wiederum die Routing- oder Firewall-Einstellungen so anpassen, dass der zu registrierende Host den {CMK}-Server auf dem benötigten Port (hier `8000`) erreichen kann.
-
-////
-// end translation
+You may receive the error message `Connection refused` even though the port was specified correctly.
+In this case, you can configure the routing or firewall settings so that the host to be registered can reach the {CMK} server on the required port (here `8000`).
 
+ifdef::onprem[]
 In the case of a registration in push mode the following applies:
+endif::[]
 If the registration has worked, the minute-by-minute transfer of the agent output will also be successful.
 
 ifdef::onprem[]