Buy Hosting

why may be restarted?

General Discussion
  • 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

    0

Suggested Topics

  • L

    I can't restart redis

    General Discussion
    0 Votes
    1 Posts
    520 Views
    L

    nice. i fixed

  • K

    I cannot restart redis

    General Discussion
    0 Votes
    1 Posts
    1k 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.

  • assameseA

    Why do I need to restart my NodeBB every couple of hours ?

    General Discussion
    0 Votes
    9 Posts
    3k Views
    Rahul DasR

    Hello there, i am looking to use NodeBB in one of my community portal. Just curious after seeing this post, is it right choice to use NodeBB?
    Please let us know if this issue was solved and how you did that?
    Thanks,
    DD

  • xinshoukeX

    May the user only delete the topic in one category?

    General Discussion
    0 Votes
    2 Posts
    1k Views
    KowlinK

    Its possible to assign a group the moderating power on just one category, However be aware that this will also include other moderation powers such as Forking, Closing and Moving topics.

  • K

    Nodebb constantly restarting!

    General Discussion
    0 Votes
    7 Posts
    3k Views
    TaLocheT

    Bloody hell! I took out the recent replies option on the category causing trouble. I changed it from 2 to 0 and that solved the issue. I was able to activate the category again and everything is back to normal.

    I'm guessing the poll was bothering the preview on the homepage.

Copyright © 2023 NodeBB | Contributors