2.7.0.beta2 upgrade failed

I’ve just upgraded to 2.7.0.Beta2
You have to do this particular upgrade from the command line.

cd /var/discourse
git pull
 ./launcher rebuild app

My apologies for this asynchronous discussion - I started my question and had to suddenly leave my office. To prevent losing my unfinished message, I saved it - and it gave you the opportunity to answer my question before I fully posted it :wink:

The DO console would work if you don’t use a terminal.

The buttons in the screenshot are initially disabled forcing you to upgrade Docker first.

An aside:You could have left your reply as it saves automatically as a draft.

Spoke too soon

Thanks, @geoff777 - it all makes sense now

Trying to run

cd /var/discourse
git pull
 ./launcher rebuild app

The rebuild app script failed two times in the row, at the precise same place:

This cannot be random networking interference. Please advise

1 Like

In my case rebuild stucked at plugin discourse-vk-auth. Currently my instance works without this plugin.

gem install rrule -v 0.4.2 -i /var/www/discourse/plugins/discourse-calendar/gems/2.7.2 --no-document --ignore-dependencies --no-user-install
Successfully installed rrule-0.4.2
1 gem installed
gem install omniauth-vkontakte -v 1.6.1 -i /var/www/discourse/plugins/discourse-vk-auth/gems/2.7.2 --no-document --ignore-dependencies --no-user-install
Successfully installed omniauth-vkontakte-1.6.1
1 gem installed

I, [2021-01-22T17:13:51.391038 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate'
rake aborted!
Gem::ConflictError: Unable to activate omniauth-vkontakte-1.6.1, because omniauth-oauth2-1.7.1 conflicts with omniauth-oauth2 (>= 1.5, <= 1.7.0)
1 Like

I’ve also run into trouble with that vk plugin in previous releases. My recommendation is to remove it, plus paste the error log to that plugin’s topic on the forum so it can be addressed. :+1:


Hard to say from the screenshot. Do you have enough disk space?

You have edited both your previous posts after I have interacted.

The second time I ‘liked’ a positive post but you edited it and now it’s a post about a problem.
Which apparently I like?

My apologies @geoff777 - without much thinking I reclassified your “like” comment (my intent was to keep the number of my posts small, thus lowering the chance of miscommunication)

I believe that I have enough space:

 System information as of Fri Jan 22 20:56:56 UTC 2021

  System load:  0.02               Users logged in:          0
  Usage of /:   39.7% of 24.06GB   IPv4 address for docker0:
  Memory usage: 50%                IPv4 address for eth0:    xxx.xxx.xxx.xxx
  Swap usage:   1%                 IPv4 address for eth0:    
  Processes:    107                IPv4 address for eth1:    

However, I suspect that my problem has to do with the Digital Ocean console - it times out very quickly , so it is possible that my update succeeded and I am just not aware of that. Will contact DO support and report my findings back here.


You can check on your forum’s dashboard that you have successfullu upgraded.
I hope it worked.

Your wish / hope @geoff777 did not help. I tried to login - and the discourse server was not responding.

I decided to run discourse-doctor from the DO console, launched from PuTTY tool (I am running on a Windows 10 machine), - and my console stopped at the same place.

Note this beginning of this run: - app not running!

root@discourse-server:/var/discourse# ./discourse-doctor
DISCOURSE DOCTOR Fri Jan 22 22:14:45 UTC 2021
OS: Linux discourse-server 5.4.0-62-generic #70-Ubuntu SMP Tue Jan 12 12:45:47 U              TC 2021 x86_64 x86_64 x86_64 GNU/Linux

Found containers/app.yml

==================== YML SETTINGS ====================

==================== DOCKER INFO ====================
DOCKER VERSION: Docker version 20.10.2, build 2291f61

DOCKER PROCESSES (docker ps -a)

CONTAINER ID   IMAGE                              COMMAND                  CREAT              ED          STATUS                      PORTS     NAMES
4e0150995f6a   discourse/base:2.0.20201221-2020   "/bin/bash -c 'cd /p…"   16 mi              nutes ago   Exited (1) 14 minutes ago             mystifying_fermat
271aff6b3bce   discourse/base:2.0.20201221-2020   "/bin/bash -c 'cd /p…"   5 hou              rs ago      Exited (1) 5 hours ago                modest_brown
30ed32bab133   discourse/base:2.0.20201221-2020   "/bin/bash -c 'cd /p…"   5 hou              rs ago      Exited (1) 5 hours ago                laughing_lalande
add2d921333a   local_discourse/app                "/sbin/boot"             2 wee              ks ago      Exited (5) 5 hours ago                app

==================== SERIOUS PROBLEM!!!! ====================
app not running!
Attempting to rebuild
==================== REBUILD LOG ====================
Ensuring launcher is up to date
Fetching origin
Launcher is up-to-date
Stopping old container
+ /usr/bin/docker stop -t 60 app

Here is the complete log up to the point of failure, saved in my Github repository, to save the space here.

The fact that I repeated this upgrade several times and after each failure (reported to me as a “console network failure”) it is obvious that this upgrade kills the existing discourse instance.

Please advise. I am happy to pass you my certs in case you want to run this yourselves

Both times you got that PuTTY Fatal Error?

That seems like a putty problem, though I can’t imagine why.

Yes, @pfaffman I do get that same error. If the execution of the ./discourse-doctor causes some catastrophic failure is it not possible that this failure results with the PuTTY fatal error - at least for my own (remote) view of his failure?

It does not seem very likely, but I will create a support ticket for DO, hoping that they might have a better view of this problem.

I guess I world try the digital ocean console next (actually, I would use a terminal in Ubuntu, but that’s not what I’d recommend to you).

Since yesterday, I observed a lot of weird behavior. Before sharing them here, please do let me know if continuing this thread is useful for anyone (the alternative is that I am just stepping on my own d… and this is all a waste of everyone’s time). I found that:

  • resetting the root password (from DO control panel) resulted in the ability to use digital ocean’s console (as @pfaffman suggested above)
  • next I run the discourse-doctor in that console and it found nothing wrong (before that resetting event) the https://forum.congral.tech failed to respond - now all works just fine)
  • All of my attempts to upgrade discourse (like this one) failed multiple times (the PuTTY console showing Network Error as the reason), and today I can verify that the upgrade failed:
content="Discourse 2.7.0.beta1 - https://github.com/discourse/discourse version 1cf92310456fb6e6424f6b532770461c56378d53"

Changing the root password and then using digital ocean’s console is a significant change that might be of interest to Discourse team to understand better. Should I continue digging and sharing my findings here, @pfaffman ?

Could you be running out of RAM and then having oom killer knock off some random processes such as sshd, thus disconnecting you and causing problems?

There should be something in dmesg output, /var/log/messages or the journalctl output if oom killer is running.

1 Like

I doubt that running out of RAM is my problem, it’s rather me stubbornly using PuTTY console instead of the DO console.

So, I am going to switch to @pfaffman’s suggestion above, particularly since my discovery that PuTTY console gets disconnected even when I am using it for something completely different from Discourse management.

Ram could be it. Do you have swap?

1 Like

Have you tried adjusting the keep alive setting, something like this?

@pfaffman I did not specify anything - using all droplet defaults, relying on DO folks to ensure reasonable behavior.

First, I am going to try to set the keep-alive as @omarfilip suggested above, then I will look at the swap space situation, followed by the @pfaffman’s suggestion to use the DO original console (if the keep-alive setting will allow me to continue using the PuTTY console, I will use it as it’s a lot more user friendly than the DO’s equivalent.

1 Like

Having so many friendly people helping me, I wish to restate my reasons for trying to put together Ghost and Discourse: it’s in my view ideal tool for someone to write technical documents and offer the best support for discussing these documents. My plan is to address Identity and Account Management (IAM) using several interesting PaaS IAM providers; this subject is not sufficiently well documented (at least in my opinion, based on years of using such services myself).

In order to “beta test” my Ghost/Discourse integrated tool, I decided to describe all details of the creation process of creating and testing this tool. So, all people helping me should know that this effort is intended to help Discourse, Ghost and Digital Ocean community.

1 Like