You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the Bug
Our scenario is to persist nacos data in mysql.
We deployed nacos serivce and mysql service, and mysql is used as nacos storage db.
It ran normally for the first few times. After restarting the kubesphere cluster, nacos connected to mysql timed out.
For abnormal messages, please refer to the following screenshot
Versions Used
KubeSphere: v3.4.1
Kubernetes: v1.26.14
Environment
How many nodes and their hardware configuration:
CentOS 7.9 / 1 masters: 4cpu/10g; 2 nodes: 4cpu/16g
Please tell me whether it is a problem with DNS resolution or a problem with network connection. How to solve this problem?
Very urgent, please help Expected behavior
all service ok
The text was updated successfully, but these errors were encountered:
Describe the Bug
![1](https://private-user-images.githubusercontent.com/18350673/336153346-d113e734-5ac5-4d52-9468-cd8b56c49edb.PNG?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE0OTA1MzAsIm5iZiI6MTcyMTQ5MDIzMCwicGF0aCI6Ii8xODM1MDY3My8zMzYxNTMzNDYtZDExM2U3MzQtNWFjNS00ZDUyLTk0NjgtY2Q4YjU2YzQ5ZWRiLlBORz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzIwVDE1NDM1MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWQzYjg3ZGQ2YmE1ODAxOGI4ZjU2OTVmOTBiMTVhOGE4ZWI4M2I2MTQyNWU4Mzc3MDY4OWUxYTRkZDQ1NGQ5YjAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.9BGsx-_DqoMOwpyBVtVnOQEy_CD7woSHMoPvp5bCevg)
![2](https://private-user-images.githubusercontent.com/18350673/336153588-367b59b1-18af-4106-bf3d-289c8e076402.PNG?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE0OTA1MzAsIm5iZiI6MTcyMTQ5MDIzMCwicGF0aCI6Ii8xODM1MDY3My8zMzYxNTM1ODgtMzY3YjU5YjEtMThhZi00MTA2LWJmM2QtMjg5YzhlMDc2NDAyLlBORz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzIwVDE1NDM1MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWIzMjQ0YzQyZTI3N2NiZDRlZTM0NTljNTgxYWQ2NDhkMGE2Njc2MGQ1NGQ4NjQ5YzdiZjQ1NjMzYzI2ZTE1NmMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.w8C2ozl8ptSB3LdPn8Tt1Z30W1HK6iWdV2QPdtJdQv0)
![3](https://private-user-images.githubusercontent.com/18350673/336153652-7ba0bb8e-d4b1-46ae-ac6a-4b925e0e74f1.PNG?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE0OTA1MzAsIm5iZiI6MTcyMTQ5MDIzMCwicGF0aCI6Ii8xODM1MDY3My8zMzYxNTM2NTItN2JhMGJiOGUtZDRiMS00NmFlLWFjNmEtNGI5MjVlMGU3NGYxLlBORz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzIwVDE1NDM1MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWEyMjc1MDI2NDVmNWQwMzllYTMzMzE0NGFiZmMwNTc0NmEzOTAwNjIwNzI5Mjk0ZTllN2ViMWNlZmFhZWI0OTMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.31QQ3iFJx2KMhdF2fPhfknKtiRl6vXwml5qulyAWswc)
Our scenario is to persist nacos data in mysql.
We deployed nacos serivce and mysql service, and mysql is used as nacos storage db.
It ran normally for the first few times. After restarting the kubesphere cluster, nacos connected to mysql timed out.
For abnormal messages, please refer to the following screenshot
Versions Used
KubeSphere: v3.4.1
Kubernetes: v1.26.14
Environment
How many nodes and their hardware configuration:
CentOS 7.9 / 1 masters: 4cpu/10g; 2 nodes: 4cpu/16g
Please tell me whether it is a problem with DNS resolution or a problem with network connection. How to solve this problem?
Very urgent, please help
Expected behavior
all service ok
The text was updated successfully, but these errors were encountered: