![]() ![]() ![]() I can “enter” the container and it seems like most of the services are running. Weird name resolution issue I, INFO - : > cd /var/www/discourse & git fetch -depth 1 origin tests-passedįatal: unable to access '': Could not resolve host: Redis is already listening on port 6379 (which definitely is not possible) 129:M 21:43:58.413 # Warning: Could not create server TCP listening socket *:6379: bind: Address already in useġ29:M 21:43:58.413 # Failed listening on port 6379 (TCP), aborting. Or even downgrade to 2.8.0.beta10.Ĭonfirmation of Discourse versions Hooray, a new version of Discourse is available!Ĭonfirmation of Ubuntu version lsb_release -aĭuring the upgrade/rebuild process, I encountered a few warnings but I’m not sure what’s actually causing the bootstrap failure. However, I only have a database backup from a week ago so I’d at least like to figure out whether there’s a way to start postgres within the container so I can take a manual backup. My self-hosted discourse instance is running on a digital ocean droplet on an EOL’d version of Ubuntu 16.04 so I’m ok if there’s no way to come back from this. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |