upgrade always fails with "has no method 'map'"

  • Every single update I did within the last weeks failed like that

    $ git fetch
    remote: Counting objects: 1214, done.
    remote: Compressing objects: 100% (103/103), done.
    remote: Total 1214 (delta 826), reused 819 (delta 819), pack-reused 292
    Receiving objects: 100% (1214/1214), 522.88 KiB | 0 bytes/s, done.
    Resolving deltas: 100% (878/878), completed with 408 local objects.
    From https://github.com/NodeBB/NodeBB
       ff70f36..c0a4bf9  v1.x.x     -> origin/v1.x.x
       b3b2d81..8a107c8  master     -> origin/master
     * [new branch]      user-flairs -> origin/user-flairs
       7646170..69f9c7f  weekly     -> origin/weekly
     * [new tag]         v1.1.2     -> v1.1.2
     * [new tag]         v1.1.3-auto.0 -> v1.1.3-auto.0
    $ git reset --hard v1.1.2
    HEAD is now at c0a4bf9 Incremented version number
    $ ./nodebb upgrade
    1. Bringing base dependencies up to date... OK
    2. Checking installed plugins for updates... OK
    TypeError: Object <html>
    <head><title>404 Not Found</title></head>
    <body bgcolor="white">
    <center><h1>404 Not Found</h1></center>
     has no method 'map'
        at Request._callback (/home/marqualy/bin/nodebb/nodebb:155:25)
        at Request.self.callback (/home/marqualy/bin/nodebb/node_modules/request/request.js:187:22)
        at Request.emit (events.js:98:17)
        at Request.<anonymous> (/home/marqualy/bin/nodebb/node_modules/request/request.js:1044:10)
        at Request.emit (events.js:95:17)
        at IncomingMessage.<anonymous> (/home/marqualy/bin/nodebb/node_modules/request/request.js:965:12)
        at IncomingMessage.emit (events.js:117:20)
        at _stream_readable.js:944:16
        at process._tickCallback (node.js:458:13)

    I then have to start from scratch by checking out the release, installing deps and so on. Which is annoying but in the end I can use my old files and database and get a working setup. But what is wrong here?

    thanks in advance!

  • @spicewiesel sounds to me like you have a plugin that might be broken. Try resetting plugins first?

  • thanks, I will reset all plugins for the next update to test which one causes the trouble.

Suggested Topics

| | | |