Cannot restore database
-
Hello
I'm a docker user. Today I have done an update of my nodebb docker image.
Unfortunately, the forum didn't want to restart and I am forced to try to create a new empty one.
But since a month, I save the dump generated from my redis database. So I have try to use this dump and place it into the new folder created for the new forum.And when nodebb ask me the address and password to access to the database I have hope! But when nodebb access to datas from the database he crashed. All time!
Do you know why? An idea?
Is there any other way to save nodebb datas and restore them? Because the next time I have this kind of problem I want to restore them easily..
-
@julian
That's the problem, their is not lot of informations:27/4 08:01 [7] - info: NodeBB v1.0.3 Copyright (C) 2013-2014 NodeBB Inc. 27/4 08:01 [7] - info: This program comes with ABSOLUTELY NO WARRANTY. 27/4 08:01 [7] - info: This is free software, and you are welcome to redistribute it under certain conditions. 27/4 08:01 [7] - info: 27/4 08:01 [7] - info: NodeBB Setup Triggered via Command Line Welcome to NodeBB! This looks like a new installation, so you'll have to answer a few questions about your environment before we can proceed. Press enter to accept the default setting (shown in brackets). npm info it worked if it ends with ok npm info using [email protected] npm info using [email protected] npm info prestart [email protected] npm info start [email protected] URL used to access this NodeBB (https://forum.<mydomain>.com) > [email protected] start /usr/src/app > node loader.js NodeBB v1.0.3 Copyright (C) 2013-2014 NodeBB Inc. This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. For the full license, please visit: http://www.gnu.org/copyleft/gpl.html Clustering enabled: Spinning up 1 process(es). 27/4 08:01 [49] - info: Time: Wed Apr 27 2016 08:01:16 GMT+0000 (UTC) 27/4 08:01 [49] - info: Initializing NodeBB v1.0.3 27/4 08:01 [49] - warn: Your NodeBB schema is out-of-date. Please run the following command to bring your dataset up to spec: 27/4 08:01 [49] - warn: ./nodebb upgrade [cluster] Child Process (49) has exited (code: 0, signal: null) npm info poststart [email protected] npm info ok 27/4 08:01 [6] - info: NodeBB v1.0.3 Copyright (C) 2013-2014 NodeBB Inc. 27/4 08:01 [6] - info: This program comes with ABSOLUTELY NO WARRANTY. 27/4 08:01 [6] - info: This is free software, and you are welcome to redistribute it under certain conditions. 27/4 08:01 [6] - info: 27/4 08:01 [6] - info: NodeBB Setup Triggered via Command Line Welcome to NodeBB! This looks like a new installation, so you'll have to answer a few questions about your environment before we can proceed. Press enter to accept the default setting (shown in brackets). npm info it worked if it ends with ok npm info using [email protected] npm info using [email protected] npm info prestart [email protected] npm info start [email protected] URL used to access this NodeBB (https://forum.<mydomain>.com) > [email protected] start /usr/src/app > node loader.js NodeBB v1.0.3 Copyright (C) 2013-2014 NodeBB Inc. This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. For the full license, please visit: http://www.gnu.org/copyleft/gpl.html Clustering enabled: Spinning up 1 process(es). 27/4 08:01 [32] - info: Time: Wed Apr 27 2016 08:01:20 GMT+0000 (UTC) 27/4 08:01 [32] - info: Initializing NodeBB v1.0.3 27/4 08:01 [32] - warn: Your NodeBB schema is out-of-date. Please run the following command to bring your dataset up to spec: 27/4 08:01 [32] - warn: ./nodebb upgrade [cluster] Child Process (32) has exited (code: 0, signal: null) npm info poststart [email protected] npm info ok
Because the container died quickly, I cant do
./nodebb upgrade
.And sometimes I have this :
27/4 08:12 [33] - error: Error: Ready check failed: NOAUTH Authentication required. at JavascriptReplyParser._parseResult (/usr/src/app/node_modules/redis/lib/parsers/javascript.js:43:16) at JavascriptReplyParser.try_parsing (/usr/src/app/node_modules/redis/lib/parsers/javascript.js:114:21) at JavascriptReplyParser.run (/usr/src/app/node_modules/redis/lib/parsers/javascript.js:126:22) at JavascriptReplyParser.execute (/usr/src/app/node_modules/redis/lib/parsers/javascript.js:107:10) at Socket.<anonymous> (/usr/src/app/node_modules/redis/index.js:131:27) at emitOne (events.js:77:13) at Socket.emit (events.js:169:7) at readableAddChunk (_stream_readable.js:153:18) at Socket.Readable.push (_stream_readable.js:111:10) at TCP.onread (net.js:531:20) [cluster] Child Process (33) has exited (code: 1, signal: null) [cluster] Spinning up another process...