Upgrade stuck on rebuilding assets

Technical Support
  • I'm trying to upgrade nodebb to 1.13 from 1.6 and the update process updates schema (yay!) but then gets stuck on assets:

    
    Updating NodeBB...
    
    1. Updating package.json file with defaults...  OK
    
    2. Bringing base dependencies up to date...  started
    npm WARN [email protected] requires a peer of nodebb-plugin-emoji@^2.0.0 but none is installed. You must install peer dependencies yourself.
    npm WARN [email protected] requires a peer of textcomplete@^0.14.2 but none is installed. You must install peer dependencies yourself.
    
    audited 4084 packages in 9.988s
    found 15 vulnerabilities (4 low, 2 moderate, 9 high)
      run `npm audit fix` to fix them, or `npm audit` for details
    
    3. Checking installed plugins for updates...  OK
    4. Updating NodeBB data store schema...[benchpressjs] Unable to build or find a suitable native module, falling back to JS version
    
    Parsing upgrade scripts... 
    OK | 0 script(s) found, 82 skipped
    Schema update complete!
    
    
    5. Rebuilding assets...  started
    

    Is there any way to ask for more logs to understand what is going on?
    Thanks!

  • And I seem to have this hanging on multiple commands:

    ./nodebb build
    [benchpressjs] Unable to build or find a suitable native module, falling back to JS version
      started
    

    (hangs)

  • Only error I see is:

    2019-11-24T11:47:32.340Z [4567/1551] - error: db.initSessionStore is not a function
    

    on trying to run it, but I presume this is caused by incomplete build..

  • Nevermind. Fixed by repo reset..


Suggested Topics


  • 1 Votes
    6 Posts
    810 Views

    I just noticed that after upgrading the calendar is now blank and says: "Error the last argument must be of type function. Received type object"

  • 0 Votes
    3 Posts
    1k Views

    @btw6391 are you using Nginx in front? Search this forum for the error and check those posts for a tweak to Nginx.

  • 0 Votes
    1 Posts
    710 Views

    I hope it helps someone:

    I wanted to do this, so I landed upon this thread. I had already created nginx proxy for my domain. So I basically just added /discuss (or whatever location you want)

    server { listen 443; listen [::]:443; server_name site.com; access_log off; error_log /var/log/nginx/site.com-error.log; open_file_cache max=2000 inactive=20s; open_file_cache_valid 60s; open_file_cache_min_uses 5; open_file_cache_errors off; ###################################################################### ## SSL Configuration ## ## Only use this block if you are setting up the SSL (HTTPS) server ## definition of your site. ###################################################################### ssl on; ssl_certificate /etc/letsencrypt/live/site/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/site/privkey.pem; ssl_session_timeout 5m; ssl_protocols SSLv3 TLSv1; ssl_ciphers ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv3:+EXP; ssl_prefer_server_ciphers on; location /discuss { proxy_pass http://127.0.0.1:4567/; proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; } # Custom 404 error_page 404 = /404.html; }

    However, there are many other issues.

    If I specify in config.json url as site.com/forum or something, css files don't load.

    If I don't, if you click on anything, it will try to go to site.com/post/2/something instead of site.com/forum/post/2 etc.

  • Unable to login after upgrade

    Solved Technical Support
    0 Votes
    11 Posts
    5k Views

    Glad to hear it is resolved 🙂

  • 0 Votes
    2 Posts
    2k Views

    Looks like a warning, but not a serious one. We don't use that package in NodeBB itself so it is likely one of its dependencies