Resolved named service stop randomly

[Svente04]

Thank you very much, I really appreciate your help.

Alright, I'll try this solution. See you after 12 hours

Regards!

@Alakide Did it work?

 

[Alakide]

@Alakide Did it work?

Hello again!!

I haven't been able to configure it yet. My VNC console doesn't work and I'm waiting for an answer from IONOS to fix it, I didn't want to risk losing access to the server without the console working because is a production server, I hope they don't take too long to give me an answer.
As soon as they answer me, I will try the solution and I will return with you with the result.

Thank you very much for your message.

Regards!

 

[Alakide]

@Alakide Did it work?

Hello again.

Fianally I've been able to try the solution and it works!! The server have at now 24 hours working with any issue.
Thank you mate for your help

Best Regards

 

[Alakide]

@Alakide Did it work?

Hello mate, my plesk installation was just upgraded to Plesk 18.0.46 Update 2 and the problem came back again the file I had was changed to a new one with this information:

# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# Generated by debian-installer.

# The loopback interface
auto lo eth0

iface eth0 inet6 manual
pre-up sleep 5
up dhclient -6 -nw -v eth0
post-up sleep 5; /sbin/ip -family inet6 route add default via fe80::1 dev eth0
pre-down /sbin/ip -family inet6 route del default via fe80::1 dev eth0
down dhclient -6 -r -v eth0
iface eth0:1 inet static
address 74.208.233.65
netmask 255.255.255.255
auto eth0:1
iface eth0:2 inet static
address 74.208.233.123
netmask 255.255.255.255
auto eth0:2
iface eth0:3 inet static
address 74.208.27.55
netmask 255.255.255.255
auto eth0:3

Of course the server was unable to reach.

I hope this info helps you to prevent this issue on your server.

Best Regards
Emmanuel Delgado

 

[Svente04]

Hi, thank you. I just installed the update - fortunately everything still works after the update. Strange ...sometimes it happens - sometimes not...

Anyway - good that we found a solution and know how to fix it

Best regards
Sven Stienemann

 

[ghazestor]

I actually try it, but my Plesk license is linked to my servers provider because they gave it to me and in this way Plesk does not give support.

 

[PeopleInside]

I have the same issue, server has been unreachable and logs say the issue come from the name service.

Question - How to understand why server went down?

Ubuntu 22.04.2 LTS Plesk Obsidian Version 18.0.51 Update #1, last updated on April 6, 2023 06:27 AM --- Is two days that my VPS went down. I need log in in my hosting provider website and restart the VPS. From the hosting monitors I can see the CPU and the RAM never reach 100% so I don't think...

talk.plesk.com

In the /etc/network I have not the file interfaces


Reading this topic I'm not sure the issue has been resolved.
I don't know what to do for fix the issue.

 

[PeopleInside]

I tried to ask to the team a sort out about this issue.

Named service stop to work randomly

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...

talk.plesk.com

Seems I'm not the only one that has this issue and this is happening also on more powerful server with 32 GB of RAM so is not a resource server issue.

Any suggestion to how I can create a script that check if named service stop to listening and restart the service will be appreciated, this can be the only automatism that save me.

I don't see any other fix currently.
I have external DNS at CloudFlare but seems if this service stop my email and web server stop to work as well.

 

[PeopleInside]

Seems Ubuntu need a particular manual network configuration to avoid the dynamic IP even if the server has just one static IP.
More info can be found at my post here.