Community

Stupid q of the day restart

General Discussion

Suggested Topics

  • K

    I cannot restart redis

    General Discussion
    0 Votes
    1 Posts
    1288 Views
    K

    I cannot restart Redis in my NodeBB to apply a password change to the /etc/redis/6379.conf. I've already installed Redis and created a systemctl unit file:

    /etc/systemd/system/redis.service

    Contents:

    [Unit]
    Description=Redis In-Memory Data Store
    After=network.target
    **
    [Service]
    User=redis
    Group=redis
    ExecStart=/usr/local/bin/redis-server /etc/redis/redis.conf
    ExecStop=/usr/local/bin/redis-cli shutdown
    Restart=always**

    It returns if I do systemctl status redis:

    Started Redis In-Memory Data Store.
    Oct 18 20:30:25 server3 systemd[11199]: redis.service: Failed at step USER spawning /usr/local/bin/redis-server:
    Oct 18 20:30:25 server3 systemd[1]: redis.service: Main process exited, code=exited, status=217/USER
    Oct 18 20:30:25 server3 systemd[1]: redis.service: Control process exited, code=exited status=217
    Oct 18 20:30:25 server3 systemd[1]: redis.service: Unit entered failed state.
    Oct 18 20:30:25 server3 systemd[1]: redis.service: Failed with result 'exit-code'.
    Oct 18 20:30:25 server3 systemd[1]: redis.service: Service hold-off time over, scheduling restart.
    Oct 18 20:30:25 server3 systemd[1]: Stopped Redis In-Memory Data Store.
    Oct 18 20:30:25 server3 systemd[1]: redis.service: Start request repeated too quickly.
    Oct 18 20:30:25 server3 systemd[1]: Failed to start Redis In-Memory Data Store.

    Thanks.

  • Alexander ElliottA

    Set session timeout to 1 day

    General Discussion
    0 Votes
    3 Posts
    1192 Views
    Alexander ElliottA

    I think I may have found my own solution . https://github.com/NodeBB/NodeBB/issues/5334

  • julianJ

    Happy Canada Day!

    General Discussion
    4 Votes
    2 Posts
    934 Views
    exodoE

    Just waiting for 1.1.0 lol

  • P

    why may be restarted?

    General Discussion
    0 Votes
    1 Posts
    517 Views
    P

    Why was such a problem? I wonder why.

    21/5 16:38 [3769] - error: TypeError: Cannot read property '0' of undefined
    at makeObject (/home/user/nodebb/src/database/redis/hash.js:55:27)
    at Array.map (native)
    at Multi.callback (/home/user/nodebb/src/database/redis/hash.js:65:22)
    at Multi.execute_callback (/home/user/nodebb/node_modules/redis/index.js:1224:14)
    at Command.callback (/home/user/nodebb/node_modules/redis/index.js:1169:14)
    at RedisClient.return_reply (/home/user/nodebb/node_modules/redis/index.js:664:25)
    at JavascriptReplyParser.reply_parser.send_reply (/home/user/nodebb/node_modules/redis/index.js:332:14)
    at JavascriptReplyParser.run (/home/user/nodebb/node_modules/redis/lib/parsers/javascript.js:132:18)
    at JavascriptReplyParser.execute (/home/user/nodebb/node_modules/redis/lib/parsers/javascript.js:107:10)
    at Socket.<anonymous> (/home/user/nodebb/node_modules/redis/index.js:131:27)
    TypeError: Cannot read property '0' of undefined
    at makeObject (/home/user/nodebb/src/database/redis/hash.js:55:27)
    at Array.map (native)
    at Multi.callback (/home/user/nodebb/src/database/redis/hash.js:65:22)
    at Multi.execute_callback (/home/user/nodebb/node_modules/redis/index.js:1224:14)
    at Command.callback (/home/user/nodebb/node_modules/redis/index.js:1169:14)
    at RedisClient.return_reply (/home/user/nodebb/node_modules/redis/index.js:664:25)
    at JavascriptReplyParser.reply_parser.send_reply (/home/user/nodebb/node_modules/redis/index.js:332:14)
    at JavascriptReplyParser.run (/home/user/nodebb/node_modules/redis/lib/parsers/javascript.js:132:18)
    at JavascriptReplyParser.execute (/home/user/nodebb/node_modules/redis/lib/parsers/javascript.js:107:10)
    at Socket.<anonymous> (/home/user/nodebb/node_modules/redis/index.js:131:27)
    21/5 16:38 [3769] - info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
    21/5 16:38 [3769] - info: [app] Database connection closed.
    21/5 16:38 [3769] - info: [app] Web server closed to connections.
    21/5 16:38 [3769] - info: [app] Shutdown complete.
    [cluster] Child Process (3769) has exited (code: 1, signal: null)
    [cluster] Spinning up another process...
    21/5 16:38 [30524] - info: Time: Sat May 21 2016 16:38:43 GMT-0400 (EDT)
    21/5 16:38 [30524] - info: Initializing NodeBB v1.0.3
    21/5 16:38 [30524] - warn: [plugins/nodebb-plugin-2factor] Hook action:user.loggedOut is deprecated, please use static:user.loggedOut instead.

    21/5 16:38 [30524] - warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run ./nodebb reset -p PLUGINNAME to disable it.

    nodebb-plugin-youtube nodebb-plugin-leaderboard nodebb-plugin-blog-comments

    21/5 16:39 [30524] - info: NodeBB Ready
    21/5 16:39 [30524] - info: Enabling 'trust proxy'
    21/5 16:39 [30524] - info: NodeBB is now listening on: 0.0.0.0:4567
    21/5 16:39 [30524] - info: [plugins/spam-be-gone] Settings loaded

  • X

    HELP ME - I think ive done a stupid :P

    General Discussion
    0 Votes
    4 Posts
    1321 Views
    X

    All working thanks @baris npm install did the trick

Copyright © 2023 NodeBB | Contributors