Cannot upgrade due to old version of docker


(Vaping Community) #1

Went to admin/upgrade and was greeted with

You are running an old version of the Discourse image.
Upgrades via the web UI are disabled until you run the latest image.

To do so log in to your server using SSH and run:

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

More info on our support site

Followed the instructions and waited… I’m still seeing the same message. git pull says im up to date.

In SSH I saw this…

2018-06-19 19:45:04.832 UTC [68] LOG:  received fast shutdown request
I, [2018-06-19T19:45:04.832881 #13]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 184
184:signal-handler (1529437504) Received SIGTERM scheduling shutdown...
2018-06-19 19:45:04.835 UTC [68] LOG:  aborting any active transactions
2018-06-19 19:45:04.838 UTC [68] LOG:  worker process: logical replication launcher (PID 77) exited with exit code 1
2018-06-19 19:45:04.842 UTC [72] LOG:  shutting down
2018-06-19 19:45:04.861 UTC [68] LOG:  database system is shut down
#<Thread:0x00005565fc8b97e8@/pups/lib/pups/exec_command.rb:87 run> terminated with exception (report_on_exception is true):
/pups/lib/pups/exec_command.rb:88:in `wait': No child processes (Errno::ECHILD)
        from /pups/lib/pups/exec_command.rb:88:in `block in spawn'
184:M 19 Jun 19:45:04.891 # User requested shutdown...
184:M 19 Jun 19:45:04.892 * Saving the final RDB snapshot before exiting.
184:M 19 Jun 19:45:05.154 * DB saved on disk
184:M 19 Jun 19:45:05.155 # Redis is now ready to exit, bye bye...
#<Thread:0x00005565fc89db60@/pups/lib/pups/exec_command.rb:87 run> terminated with exception (report_on_exception is true):
/pups/lib/pups/exec_command.rb:88:in `wait': No child processes (Errno::ECHILD)
        from /pups/lib/pups/exec_command.rb:88:in `block in spawn'

What is the problem?


(Rafael dos Santos Silva) #2

Can you expand the logs? I don’t see an actionable item from the few lines you provided.


(Vaping Community) #3

Running

./launcher rebuild app

Again, I’ll post more when it’s done, thanks


(Vaping Community) #4

The rebuild fixed it, must have ended early for some reason… thanks anyway :confused:


(Vaping Community) #5

Just in case anyone else has issues refer to this post - How do I manually update Discourse and Docker image to latest?


(Régis Hanol) #6