Search results

This because the long downtime has the log named was not listening in the time where downtime starts and also user are reporting the same: https://talk.plesk.com/threads/named-service-stop-randomly.360328/ Thanks anyway for the reply :) I appreciate that

@AYamshanov thanks for the answer. The last dowtime of two minutes of curse can be caused by the sw-engine consumed huge amount of memory and when the memory ran out, the oom-killer came and killed sw-engine. I believe the same but the dowtime that I have for two days before did not resolve in...

I need Node.js ^_^

Thanks ... I will need to try this, seems my only solution right now.

I also don't think the issue is related to IONOS when the issue come from a service, maybe managed by Plesk (is maybe the Bind component) and IONOS just provide the virtual VPS. There is no evidence of the issue by the service provided by IONOS, the issue seems come from a server service that is...

Thanks for the reply @Maarten. I don't know what is Passenger and no I don't think I'm using it As for your request the output: Click here to see the output for memory

Currently I have no other money to pay a support subscription so probably this issue will be not resolved. Any help about creating a script that restart the service is the service is broken?

Today new downtime of two minutes at 07:13 AM https://stato.peopleinside.it/report/uptime/64b017e5e65ca2dab3cddd36dc940c56/ The log say: PrivateBin Any idea how can log means? PassengerAgent invoked oom-killer: gfp_mask=0x1100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0

Today new downtime of two minutes at 07:13 AM https://stato.peopleinside.it/report/uptime/64b017e5e65ca2dab3cddd36dc940c56/ The log say: PrivateBin Any idea how can log means? PassengerAgent invoked oom-killer: gfp_mask=0x1100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0

I tried to ask to the team a sort out about this issue. https://talk.plesk.com/threads/named-service-stop-to-work-randomly.369837/ 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...

I tried to ask to the team a sort out about this issue. https://talk.plesk.com/threads/named-service-stop-to-work-randomly.369837/ 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...

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

I get also this error this morning: Some problems occurred with the System Updates tool on your server peopleinside.it. Please resolve them manually. Reason: 2023-05-17 06:26:30 INFO: pum is called with arguments: ['--list', '--repo-info', '--json'] 2023-05-17 06:26:31 ERROR: Failed to lock...

I have the same issue, server has been unreachable and logs say the issue come from the name service. https://talk.plesk.com/threads/how-to-understand-why-server-went-down.369824/ In the /etc/network I have not the file interfaces Reading this topic I'm not sure the issue has been resolved...

Yes, I'm using IONOS. From the thread seems the issue has not really been resolved. I'm on IONOS since long time and in a more then a year this issue happen sometimes, no to often so I'm asking why happen only sometimes. Maybe I had two day of downtime and now for another few mount I will never...

Today at 18:07 my server went down for 27 minutes (until I never restart manually) If I look into the logs I see nothing, I see logs continue also after 18:07. The downtime start at 18:07 and ends at 18:34 after my manual reboot from the hosting VPS website. Logs stille xist in this lass of...

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

Finally get this is not working for me so I have to manually do the job all times.

I agree, I'm surrendered... I had to update manually domain for domain, this is terrible... but is how work Plesk now. I dont agree with this. When there is a button called update and sync I expect sync change the new default but is not so I need manually do domain for domain, very unproductive...

Thanks but I have already done this and still get the swarp email. Now today I disabled the swarp monitoring in the monitoring extension, let's see of this resolve. Unfortunately email receved by Plesk doesn't have a direct link to turn them off :)