Hangs during upgrade


(Pirat) #1

Hangs during upgrade

wwwwwwwwwww/admin/upgrade

Bundle complete! 99 Gemfile dependencies, 177 gems now installed.
Gems in the group development were not installed.
Bundled gems are installed into ./vendor/bundle.
$ bundle exec rake multisite:migrate

if you can rollback the update will error
502 Bad Gateway

Constantly have to use ssh

./launcher rebuild app

Notifications got stuck a week ago
Notifications got stuck a week ago
(Régis Hanol) #2

This also happened to me. I think it might be related to our backup issue (cc. @sam)


#3

I also tried upgrading today, halted at rake multisite:migrate line and currently logged in for rebuild…

Nggh. There’s a lot of problems:

Launcher is up-to-date
Stopping old container
+ /usr/bin/docker stop -t 10 app
app
cd /pups && git pull && /pups/bin/pups --stdin
/usr/bin/docker: Failed to create the container ID file: open cids/app_bootstrap.cid: permission denied.
See '/usr/bin/docker run --help'.
cat: cids/app_bootstrap.cid: No such file or directory
"docker rm" requires at least 1 argument(s).
See 'docker rm --help'.

Usage:  docker rm [OPTIONS] CONTAINER [CONTAINER...]

Remove one or more containers
rm: cannot remove ‘cids/app_bootstrap.cid’: No such file or directory
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

What to do?


(Régis Hanol) #4

/usr/bin/docker: Failed to create the container ID file: open cids/app_bootstrap.cid: permission denied.

Did you change the permissions on the cids folder by any chances?


#5

Nope.

Folder:

drwxr-xr-x  2 root root 4.0K Aug 28 00:25 cids

Folder contents:

drwxr-xr-x  2 root root 4.0K Aug 28 00:25 .
drwxr-xr-x 11 root root 4.0K Aug 28 00:16 ..
-rw-r--r--  1 root root    0 Jun  3 09:49 .gitkeep

#6

Hmm. Maybe I should’ve done this with sudo?

Edit: ok, that seems to be doing the trick. Yeah, sorry, I forgot the ssh root@domain part… :frowning:


(Régis Hanol) #7

You should be root to use the ./launcher.


#8

sudo is enough instead of root, right? Or should I just login as root?

Edit: went sudo su and continued :stuck_out_tongue:


#9

Rebuild complete. Upgrade was finished, notifications have started working, emails are being sent. Everything works fine now.


(Ty Is I) #10

Seconded. The upgrade failed for me as well. It took a rebuild to get things working again.

@zogstrip: Take this as a headsup. This failed with the update of today: “v1.7.0.beta7 +1”


(Régis Hanol) #13

So it will hung, even after sam’s latest fix?


#14

i just upgraded and it hung, rebuild got it going again.


(Jose C Gomez) #15

same issue hangs at the same spot


(Régis Hanol) #16

Did you upgrade using the web browser or via ssh?

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

#17

browser first, then console, back to browser where it was still stuck, restarted that and it finished fine.


(Jeff Atwood) #18