שדרוג נכשל קונסולת מנהל

[kdmilelr45 (Keith DeWayne Miller)]

when I used the admin console I got this message before it was working fine.
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

and when I followed the simple instructions I got this error message

FAILED

Pups::ExecError: cd /var/www/discourse && su discourse -c ‘bundle exec rake them es:update assets:precompile’ failed with return #<Process::Status: pid 518 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn’
exec failed with the params {“cd”=>“$home”, “hook”=>“assets_precompile”, “cmd”=> [“su discourse -c ‘bundle exec rake themes:update assets:precompile’”]}
e3eb2969bd230aeaf5a9405901e7059aa898c61b41eec2156960a6bd2e08dd33
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.

when I perform the ./discourse-doctor it starts rebuilding and I still have the same issue with the admin upgrade console

[IAmGav (Gavin Perch)]

The error is higher up in the log.

Can you check or post the log file

[kdmilelr45 (Keith DeWayne Miller)]

Not sure how far up to go, here is some more

Error response from daemon: driver failed programming external connectivity on endpoint app (1e145a00615964e521bbfcec584bb3adf14171590767841a1eaa58e04b064615): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use
Error: failed to start containers: app
Failed to restart the container.

[kdmilelr45 (Keith DeWayne Miller)]

Here is the log file attached
discourse-debug.txt (167.5 KB)

[pfaffman (Jay Pfaffman)]

@kdmilelr45

Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use

That looks like you have some other web server running. You can check to see if something has a port open and or see if apache or nginx is running.

@kdmilelr45

Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn’
exec failed with the params {“cd”=>“$home”, “hook”=>“assets_precompile”, “cmd”=> [“su discourse -c ‘bundle exec rake themes:update assets:precompile’”]}

That looks like you have a theme that has an error. You might do a

 ./launcher start app

To restart the server (which won’t work if something else is on port 443) and see about removing themes and then adding them back after the upgrade.

[kdmilelr45 (Keith DeWayne Miller)]

these are the only two protocols looking at port 443

root@geeksove:/var/discourse# sudo lsof -i:443
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
docker-pr 44758 root 4u IPv4 926438 0t0 TCP *:https (LISTEN)
docker-pr 44764 root 4u IPv6 926445 0t0 TCP *:https (LISTEN)
root@geeksove:/var/discourse#

[pfaffman (Jay Pfaffman)]

Then what does this say

    docker ps

[kdmilelr45 (Keith DeWayne Miller)]

@pfaffman

docker ps

root@geeksove:/var/discourse# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8bf07ae47872 local_discourse/app “/sbin/boot” 7 weeks ago Up 2 hours 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp app

Thank you for the help

Keith

[pfaffman (Jay Pfaffman)]

So discourse is already running.

[kdmilelr45 (Keith DeWayne Miller)]

Yes, and works except the upgrade module, it keep going to the original message–

[pfaffman (Jay Pfaffman)]

I think that you have a theme component that is the issue. You need to remove it, upgrade, and then add back the themes until you find the problem. Or, so I think.