[Krydos] Log Page (Tommy vs Morty)

[ahuckphin]

I'm currently on the Tommy plan. The log page in Plesk takes >5 mins to load when my Node.js is enabled. Would upgrading to the Morty have a log page that loads more instantaneous? If I disable my node.js app, the log page will go back to loading quickly but enabling back on my node.js app is another pain point. 

[wolstech]

You're the first person to report that the logs are slow only when node is enabled... that's an interesting observation.

Morty would likely make it faster since the entire server is quite a bit faster than Tommy, but I'm actually kind of curious as to why this only happens to you when node is enabled.

Maybe Krydos has some input on this?

[Krydos]

I tested this a bit

Morty logs loading on Node.js enabled domain = 3.43 seconds

Tommy logs loading on Node.js enabled domain = 20.01 seconds

So, yes Morty is quite a bit faster, but it shouldn't take more than 30 seconds. Perhaps you need to reset your account first regardless of whether you move to Morty or not. I think this is an issue specific to your account, not a server-wide issue.

[ahuckphin]

Thanks for getting back. 

 

The reset page (https://heliohost.org/dashboard/reset/) says to open a support ticket for resting an account. Can I just request here to reset my account? I acknowledge it is a permanent change involving deleting data. 

[Krydos]

I have started the reset process. If you need any of your files from before the reset I created a full backup which can be downloaded from https://heliohost.org/backup In a few minutes you'll receive an email with a link to continue with the reset process. After recreating your account and enabling Node.js again let us know if the logs page loads faster.

[ahuckphin]

The log page doesn't load faster after the reset with node.js enabled. Received 504 gateway time-out error once. I reckon perhaps it's something to do with my website code (?).  

The reset did resolve an unrelated issue I had with 404 errors. However, this issue came back later (after the reset). My website works as expected. I then disable, then enabled node.js, with no change to code or file structure, my website stops working as expected with 404 errors . I'm not sure if this is hosting related or my code related. 

At this point, I am looking into switching to VPS upon further review of Passenger limitations. 

Edited Friday at 01:17 PM by ahuckphin
added clarification

[wolstech]

Quote

My website works as expected. I then disable, then enabled node.js, with no change to code or file structure, my website stops working as expected with 404 errors . I'm not sure if this is hosting related or my code related. 

Are you waiting up to 2 hours for an apache restart? Node doesn't fully disable/enable immediately. It needs an apache restart to take effect.