Error looking up account info
-
This prevents getting a spammer's IP address in order to report them to StopForumSpam.
attn: @ben_lubar I see RedisClient in the stack trace, and I thought you said you'd set something up for this, so I wanted to run this past you before reporting it to NodeBB.
-
@boomzilla said in Error looking up account info:
This prevents getting a spammer's IP address in order to report them to StopForumSpam.
attn: @ben_lubar I see RedisClient in the stack trace, and I thought you said you'd set something up for this, so I wanted to run this past you before reporting it to NodeBB.
Nope, that doesn't look like anything related to what I've done. Paging @julianlam / @barisu
-
Seems like
session.meta
is undefined causing a crash, https://github.com/NodeBB/NodeBB/commit/ee398d397943642f8ffae60826950d3e9fb771f7.FWIW I haven't seen this happen on our instances .
-
@barisu said in Error looking up account info:
Seems like
session.meta
is undefined causing a crash, https://github.com/NodeBB/NodeBB/commit/ee398d397943642f8ffae60826950d3e9fb771f7.FWIW I haven't seen this happen on our instances .
@boomzilla this has now been stealth-applied.
-
@ben_lubar Thank you. And now I've reported our latest would be spammer.
-
@barisu said in Error looking up account info:
FWIW I haven't seen this happen on our instances .
This was a spammer who had managed to register but got stuck in the post queue, if that helps.
-
@boomzilla Can you access their page now that the fix is applied?
-
@barisu Yes.
-
This is happening again, @ben_lubar. Spammer: @2WeekDiets
20/12 14:44:57 [7310] - error: [4570/7310] TypeError: Cannot read property 'datetime' of undefined at /usr/src/app/src/user/auth.js:132:55 at Array.map (<anonymous>) at /usr/src/app/src/user/auth.js:131:25 at nextTask (/usr/src/app/node_modules/async/dist/async.js:5310:14) at next (/usr/src/app/node_modules/async/dist/async.js:5317:9) at /usr/src/app/node_modules/async/dist/async.js:958:16 at /usr/src/app/src/user/auth.js:127:6 at /usr/src/app/node_modules/async/dist/async.js:473:16 at eachOfArrayLike (/usr/src/app/node_modules/async/dist/async.js:1043:9) at eachOf (/usr/src/app/node_modules/async/dist/async.js:1103:5) at Object.eachLimit (/usr/src/app/node_modules/async/dist/async.js:3158:5) at /usr/src/app/src/user/auth.js:124:11 at nextTask (/usr/src/app/node_modules/async/dist/async.js:5310:14) at next (/usr/src/app/node_modules/async/dist/async.js:5317:9) at /usr/src/app/node_modules/async/dist/async.js:958:16 at /usr/src/app/node_modules/async/dist/async.js:1126:9 at /usr/src/app/node_modules/async/dist/async.js:473:16 at iteratorCallback (/usr/src/app/node_modules/async/dist/async.js:1050:13) at /usr/src/app/node_modules/async/dist/async.js:958:16 at /usr/src/app/node_modules/async/dist/async.js:1123:13 at Command.callback (/usr/src/app/node_modules/connect-redis/lib/connect-redis.js:167:14) at normal_reply (/usr/src/app/node_modules/redis/index.js:726:21) at RedisClient.return_reply (/usr/src/app/node_modules/redis/index.js:824:9) at JavascriptRedisParser.returnReply (/usr/src/app/node_modules/redis/index.js:192:18) at JavascriptRedisParser.execute (/usr/src/app/node_modules/redis-parser/lib/parser.js:574:12) at Socket.<anonymous> (/usr/src/app/node_modules/redis/index.js:274:27) at emitOne (events.js:116:13) at Socket.emit (events.js:211:7) at addChunk (_stream_readable.js:263:12) at readableAddChunk (_stream_readable.js:250:11) at Socket.Readable.push (_stream_readable.js:208:10) at TCP.onread (net.js:594:20)
-
@boomzilla said in Error looking up account info:
This is happening again, @ben_lubar.
Whoops! Re-applied the fix.
For future reference, the command is:
docker exec -ti wtdwtf-nodebb bash curl https://github.com/NodeBB/NodeBB/commit/ee398d397943642f8ffae60826950d3e9fb771f7.diff | patch -p1 [ctrl+D or "exit"]
And then click the orange button in the admin panel to restart the server without rebuilding assets.