The other day I installed Ghost 5.26.3 on a subdomain using Virtualmin Pro’s Install Scripts feature. It worked great, I set up a few pages on my new Ghost website with it.
Today I noticed there was an update to the Ghost Install Script version, so I dutifully clicked the Upgrade button in Virtualmin to upgrade to Ghost 5.40.2.
Now though, when I go to visit my Ghost website, I simply get a 503 Service Unavailable message. I tried restarting Ghost in Virtualmin’s Install Script area, to no avail. I SFTP’d in and looked at ghost.err but that file is blank. I peeked into ghost.log and it just had the original welcome message with no errors shown.
How might I go about getting my Ghost website back online after the update? I’m not sure quite how to troubleshoot, since the Install Scripts usually handle upgrades smoothly.
A quick note to add that according to Virtualmin Pro’s Install Scripts view of Ghost for my subdomain, it shows Ghost’s “server status” as “running”. Restarting the script here also shows Ghost as stopping and starting, without error.
But when I look in Webmin > System > Running Processes I don’t see Ghost running on this subdomain (though the older version of Ghost as an Install Script is running on a couple other domains that I haven’t yet upgraded).
I think it’s helpful to compare two Ghost installations on my server. One is functional (not yet upgraded), and the other is identical other than that I clicked the Upgrade button for the Install Script:
$ sudo systemctl | grep -i g
ghost-beemuse.com-3000.service loaded active running Start Ghost server for beemuse.com (Virtualmin)
ghost-redacted.com-3001.service loaded active running Start Ghost server for redacted.com (Virtualmin)
The above shows my expected two Ghost 5.26.3 servers running.
The third Ghost instance that was running on a subdomain (on port 3002) right up until I clicked the Upgrade button to Ghost 5.40.2 is no longer appearing here as a service, despite being reported as Running by Virtualmin.
Of note, when I clicked Upgrade in Virtualmin, it not only reported no errors, but showed the service as stopping and starting properly. And when I click Restart in Virtualmin’s Install Scripts (on the upgraded one that’s not working), it reports this:
Shutting down the server process for Ghost ..
Starting up the server process for Ghost ..
But rechecking with sudo systemctl | grep -I g still shows no such service running.
I just realized I missed one of your replies above about version Ghost 5.41.0
At worst, I can simply delete this Ghost instance, I’d set it up for staging… thankfully! It’d be really cool to have a safe upgrade path for the two that are still running on 5.26.3 though, via Virtualmin’s Install Scripts.
However, it will not restore deleted service file. You should copy it, and then tweak it manually using the working as example. When done, run systemctl daemon-reload. I’m not sure what made it disappear, however, if the service file is deleted, it shouldn’t be showing Running. I will check to fix that.
So for the two live sites currently running on 5.26.3, I should be able simply to upgrade “to unsupported version” 5.41.0 and not have these troubles, I’m hoping? Thanks again for your time on this and quick responses