PeopleInside
Regular Pleskian
Username:
TITLE
Named service stop to work randomly
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Ubuntu 22.04.2 LTS
Plesk Obsidian Version 18.0.51
6 vCore RAM: 8 GB SSD: 160 GB
PROBLEM DESCRIPTION
This issue is not happening only to me and is happening also on more powerful server with 32 GB of RAM as reported here.
I'm facing this issue since a year, it doesn't happen often but when it does cause downtime on more sequential days and need a manual action to restart the VPS from my VPS hosting IONOS.
The issue:
The service named stop randomly to work.
I host my DNS on CloudFlare, I don't know what named service is but I can read is about BIND if I'm not wrong and this is related to the DNS management, if I'm not wrong.
I reported my downtime issue here: How to understand why server went down?
As you can see I don't have no RAM and CPU overload issues.
but checking /var/log/syslog I can found the following logs:
The downtime has started as soon the named service no longer listening so I get down email alert at 18:07 after 3 minutes of downtime.
Seems this issue is not just mine, has been discussed here, the topic is marked as solved but I see the issue has return back sometimes to users and I'm experiencing the issue too.
I never found a solution that works to resolve this issue, can the team maybe look into this and found maybe some issue or solution?
Could you maybe suggest a script to check the named service and restart automatically if this service is not listening? This will avoid me to have long downtime that I cannot resolve if I'm not at home or in the office in front a PC that can login in my hosting panel to restart my VPS. I'm not a developer and I don't know hot to create the file and what code I need.
This issue create downtime since a year or more, is always an issue with named service also on different VPS with Plesk.
I hope in the future your software can avoid this issue.
Thanks
STEPS TO REPRODUCE
It's a randoom issue so I have not any step to provide, sorry for this.
I know steps to reproduce are important!
ACTUAL RESULT
Randomly named service stop to listening and cause all service email and web to be down.
EXPECTED RESULT
Named service should not stop listening.
I don't have no RAM and CPU overload issues so why this service should turn my server down?
This should not happen. I expect a way to restart automatically this service if went down again and for sure will be.
ANY ADDITIONAL INFORMATION
Could you please help me with a script that resolve the issue of the log:
May 16 18:05:45 peo named[976]: no longer listening on (MY VPS IP)#53
Seems the fix will be check if the named stop to listening then if so restart the service #service named-chroot restart but I need do this with a cronjob if you don't know why this service create issue not only to me.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Help with sorting out
TITLE
Named service stop to work randomly
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Ubuntu 22.04.2 LTS
Plesk Obsidian Version 18.0.51
6 vCore RAM: 8 GB SSD: 160 GB
PROBLEM DESCRIPTION
This issue is not happening only to me and is happening also on more powerful server with 32 GB of RAM as reported here.
I'm facing this issue since a year, it doesn't happen often but when it does cause downtime on more sequential days and need a manual action to restart the VPS from my VPS hosting IONOS.
The issue:
The service named stop randomly to work.
I host my DNS on CloudFlare, I don't know what named service is but I can read is about BIND if I'm not wrong and this is related to the DNS management, if I'm not wrong.
I reported my downtime issue here: How to understand why server went down?
As you can see I don't have no RAM and CPU overload issues.
but checking /var/log/syslog I can found the following logs:
Code:
May 16 18:05:45 peo named[976]: no longer listening on (MY VPS IP)#53
May 16 18:06:05 peo plesk_saslauthd[97254]: select timeout, exiting
The downtime has started as soon the named service no longer listening so I get down email alert at 18:07 after 3 minutes of downtime.
Seems this issue is not just mine, has been discussed here, the topic is marked as solved but I see the issue has return back sometimes to users and I'm experiencing the issue too.
I never found a solution that works to resolve this issue, can the team maybe look into this and found maybe some issue or solution?
Could you maybe suggest a script to check the named service and restart automatically if this service is not listening? This will avoid me to have long downtime that I cannot resolve if I'm not at home or in the office in front a PC that can login in my hosting panel to restart my VPS. I'm not a developer and I don't know hot to create the file and what code I need.
This issue create downtime since a year or more, is always an issue with named service also on different VPS with Plesk.
I hope in the future your software can avoid this issue.
Thanks
STEPS TO REPRODUCE
It's a randoom issue so I have not any step to provide, sorry for this.
I know steps to reproduce are important!
ACTUAL RESULT
Randomly named service stop to listening and cause all service email and web to be down.
EXPECTED RESULT
Named service should not stop listening.
I don't have no RAM and CPU overload issues so why this service should turn my server down?
This should not happen. I expect a way to restart automatically this service if went down again and for sure will be.
ANY ADDITIONAL INFORMATION
Could you please help me with a script that resolve the issue of the log:
May 16 18:05:45 peo named[976]: no longer listening on (MY VPS IP)#53
Seems the fix will be check if the named stop to listening then if so restart the service #service named-chroot restart but I need do this with a cronjob if you don't know why this service create issue not only to me.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Help with sorting out