Aias00 opened a new issue, #2359:
URL: https://github.com/apache/hertzbeat/issues/2359

   ### Is there an existing issue for this?
   
   - [X] I have searched the existing issues
   
   ### Current Behavior
   
   hi, my laptop is macos operation system 
   <img width="280" alt="image" 
src="https://github.com/user-attachments/assets/77d23bd6-6e0a-472a-a6d9-f0aaa1bfc918";>
   
   when i set up a collect task, which is centos, i got this error notification.
   <img width="1573" alt="image" 
src="https://github.com/user-attachments/assets/849d64d1-422f-4741-ad56-7af93c3d0dc3";>
   
   i tried several servers, and i got difference results. not all servers will 
connect error . but if one is error , it is allways occurs error first.
   <img width="1569" alt="image" 
src="https://github.com/user-attachments/assets/c9f23fcf-b7b6-43e7-ac71-4d68adc68939";>
   <img width="1089" alt="image" 
src="https://github.com/user-attachments/assets/065434dc-da7b-4957-9cf6-f73472b16a69";>
   
   i found if i try 3 or 4 more times, it can connect successfully 
   <img width="1328" alt="image" 
src="https://github.com/user-attachments/assets/c2812480-5bc4-41e6-bf78-ffa08c78c734";>
   
   thie error may cause by my centos server; but when i changed the sshd-core 
dependencies version to 2.13.1, the error will never happens
   
   
   ### Expected Behavior
   
   _No response_
   
   ### Steps To Reproduce
   
   _No response_
   
   ### Environment
   
   ```markdown
   HertzBeat version(s): master
   ```
   
   
   ### Debug logs
   
   _No response_
   
   ### Anything else?
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to