ECS：登入或驗證特定節點時遇到延遲

Summary: 使用 ssh 登入系統或執行需要驗證遠端工作階段的命令時，發生延遲或回應緩慢。

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

建立 SSH 連線至節點、執行 sudo 或任何其他需要驗證的命令時，發生延遲。延遲后，命令正常運行。  節點負載並不嚴重，正常運行時間顯示正常負載平均值。

如果使用 -vvv 為 ssh 連線啟用詳細資料，登入延遲會在「pledge： exec」

之後發生： 
admin:~> ssh 169.254.1.2 -vvv
OpenSSH_7.2p2, OpenSSL 1.0.2p-fips  14 Aug 2018
debug1: Reading configuration data /home/admin/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 25: Applying options for *
debug2: resolving "169.254.1.2" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 169.254.1.2 [169.254.1.2] port 22.
debug1: Connection established.
... <truncated debugging>
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug3: send packet: type 90
debug1: Requesting no-more-sessions@openssh.com
debug3: send packet: type 80
debug1: Entering interactive session.
debug1: pledge: exec

暫停 20+ 秒後，登錄將正常進行。


在發生問題的節點上，如果 dbus 服務狀態為檢查狀態，它會報告逾時： 
admin:~> sudo systemctl status dbus
● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
   Active: active (running) since Fri 2024-01-23 04:56:00 UTC; 1 months 2 days ago
     Docs: man:dbus-daemon(1)
 Main PID: 3060 (dbus-daemon)
    Tasks: 1 (limit: 512)
   Memory: 5.8M
      CPU: 10h 45min 897ms
   CGroup: /system.slice/dbus.service
           └─3060 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

Mar 22 18:28:54 <ecs-node-fqdn> dbus[3060]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 30000ms)
Mar 22 18:28:54 <ecs-node-fqdn> dbus[3060]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 30000ms)
Mar 22 18:28:54 <ecs-node-fqdn> dbus[3060]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 30000ms)
Mar 22 18:28:54 <ecs-node-fqdn> dbus[3060]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 30000ms)
Mar 22 18:28:54 <ecs-node-fqdn> dbus[3060]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 30000ms)
Mar 22 18:28:54 <ecs-node-fqdn> dbus[3060]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 30000ms)
Mar 22 18:29:22 <ecs-node-fqdn> dbus[3060]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 30009ms)
Mar 22 18:29:24 <ecs-node-fqdn> dbus[3060]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 30002ms)
Mar 22 18:29:54 <ecs-node-fqdn> dbus[3060]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 30000ms)
Mar 22 18:30:01 <ecs-node-fqdn> dbus[3060]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 30000ms)

在 /var/log/messages 中也能找到類似的逾時訊息




Cause

已達到 dbus 服務的連線限制，導致登入和/或驗證延遲

Resolution

此問題可透過重新啟動 dbus 服務來修正，若為主要節點，亦可重新啟動 dnsmasq 服務。預期不會有任何影響，但請視需要取得客戶核准。

從發生問題的節點，使用以下命令重新開機 dbus：  
  
sudo systemctl restart dbus
admin:~> sudo systemctl restart dbus
這個命令預期不會有輸出。

命令完成後，請執行下列命令，檢查 dbus 服務的狀態，以確保其為「作用中 （running）」：
  
sudo systemctl status dbus
admin ~> sudo systemctl status dbus
● dbus.service - D-Bus System Message Bus
   Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
   Active: active (running) since Fri 2024-07-19 18:07:00 UTC; 5s ago
     Docs: man:dbus-daemon(1)
 Main PID: 19340 (dbus-daemon)
    Tasks: 1 (limit: 512)
   Memory: 884.0K
      CPU: 22ms
   CGroup: /system.slice/dbus.service
           └─19340 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

如果節點是主要節點 （通常是節點 1），則也需要使用以下命令重新啟動 dnsmasq： 
  
sudo systemctl restart dnsmasq
admin:~> sudo systemctl restart dnsmasq
這個命令預期不會有輸出。

重新啟動 dnsmasq 後，請使用命令驗證服務為「作用中 （執行中）」：
  
sudo systemctl status dnsmasq
admin~> sudo systemctl status dnsmasq
● dnsmasq.service - DNS caching server.
   Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; disabled; vendor preset: disabled)
  Drop-In: /run/systemd/generator/dnsmasq.service.d
           └─50-insserv.conf-$named.conf
   Active: active (running) since Fri 2024-07-19 18:14:47 UTC; 2s ago
  Process: 61272 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS)
 Main PID: 61297 (dnsmasq)
    Tasks: 1 (limit: 512)
   Memory: 2.1M
      CPU: 8ms
   CGroup: /system.slice/dnsmasq.service
           └─61297 /usr/sbin/dnsmasq --log-async --enable-dbus --keep-in-foreground

服務重新啟動後，請使用 ssh 或執行 sudo 命令測試節點的存取，以觀察延遲是否已解決。 

Affected Products

ECS, ECS Appliance, ECS Appliance Gen 1, ECS Appliance Gen 2, ECS Appliance Gen 3, ECS Appliance Hardware Gen1 U-Series, ECS Appliance Hardware Gen1 C-Series, ECS Appliance Hardware Gen2 C-Series, ECS Appliance Hardware Gen2 D-Series , ECS Appliance Hardware Gen2 U-Series ...

Products

ECS Appliance Hardware Gen3 EX5000, ECS Appliance Hardware Gen3 EX300, ECS Appliance Hardware Gen3 EX3000, ECS Appliance Hardware Gen3 EX500, ECS Appliance Hardware Gen3 EXF900, ECS Appliance Hardware Series, ECS Appliance Software with Encryption , ECS Appliance Software without Encryption, ECS Software ...
Article Properties
Article Number: 000227096
Article Type: Solution
Last Modified: 02 Aug 2024
Version:  1
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.