Community

It is a big problem with Redis

Technical Support

Suggested Topics

  • JaredBuschJ
    ●

    How can I migrate from redis to postgresql/mongodb

    Unsolved Technical Support
    0 Votes
    12 Posts
    533 Views

    JaredBuschJ

    @JaredBusch said in How can I migrate from redis to postgresql/mongodb:

    Found a pull request for nodebb-plugin-import that gives it postgresql capability.

    Well, it seem that I cannot install v1.12.1 as required by this plugin.

    npm never successfully builds.

    [[email protected] nodebb]$ sudo -u nodebb ./nodebb setup package.json not found. Populating package.json... OK Dependencies outdated or not yet installed. Installing them now... npm notice npm notice New minor version of npm available! 8.3.1 -> 8.12.2 npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.12.2 npm notice Run npm install -g [email protected] to update! npm notice npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree npm ERR! npm ERR! While resolving: [email protected] npm ERR! Found: [email protected] npm ERR! node_modules/pg npm ERR! [email protected]"^7.4.0" from the root project npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer [email protected]"^8" from [email protected] npm ERR! node_modules/pg-cursor npm ERR! [email protected]"^2.0.0" from the root project npm ERR! npm ERR! Fix the upstream dependency conflict, or retry npm ERR! this command with --force, or --legacy-peer-deps npm ERR! to accept an incorrect (and potentially broken) dependency resolution. npm ERR! npm ERR! See /home/nodebb/.npm/eresolve-report.txt for a full report. npm ERR! A complete log of this run can be found in: npm ERR! /home/nodebb/.npm/_logs/2022-06-18T01_31_52_584Z-debug-0.log Error installing dependencies! message: Command failed: npm install --production stdout: null stderr: null /opt/nodebb/src/cli/package-install.js:54 throw e; ^ Error: Command failed: npm install --production at checkExecSyncError (node:child_process:828:11) at Object.execSync (node:child_process:902:15) at Object.installAll (/opt/nodebb/src/cli/package-install.js:45:9) at Object.<anonymous> (/opt/nodebb/src/cli/index.js:60:18) at Module._compile (node:internal/modules/cjs/loader:1103:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1155:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at Module.require (node:internal/modules/cjs/loader:1005:19) at require (node:internal/modules/cjs/helpers:102:18) { status: 1, signal: null, output: [ null, null, null ], pid: 1461, stdout: null, stderr: null } [[email protected] nodebb]$

    Built just fine to v2.2.0 though.

    [[email protected] nodebb]$ sudo -u nodebb ./nodebb setup Dependencies outdated or not yet installed. Installing them now... npm WARN deprecated [email protected]: this library is no longer supported npm WARN deprecated [email protected]: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10. npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated [email protected]: support for ECMAScript is superseded by `uglify-js` as of v3.13.0 npm WARN deprecated [email protected]: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1 added 922 packages, and audited 923 packages in 2m 76 packages are looking for funding run `npm fund` for details 5 high severity vulnerabilities Some issues need review, and may require choosing a different dependency. Run `npm audit` for details. OK 2022-06-18T01:40:58.599Z [1600] - info: NodeBB Setup Triggered via Command Line Welcome to NodeBB v2.2.0! 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).

    7d8a5a66-30f5-4d65-a5ec-ac395ecd0178-image.png

  • S
    ●

    Websocket connection problems via ssl on special port

    Technical Support
    1 Votes
    7 Posts
    3032 Views

    yariplusY

    @suparomana said in Websocket connection problems via ssl on special port:

    Apache 2.2 can not handle websockets

    Ahh, thanks. Okay, that makes sense now. It sounds like it's failing because of the special port. Since that port is sending directly to NodeBB and not through the Apache proxy, NodeBB does not know the SSL key, so it will fail the connection.

    I think there used to be a way to feed the SSL Key path to NodeBB in config.json, but I don't see any docs on it anymore, and I'm not even sure if that would work.

    I think your best bet is to try getting websockets to work through Apache2, there seems to be several methods even though there's no official support.

  • PilvinenP
    ●

    How to export from Redis to MongoDB? (My database got wiped)

    Technical Support
    0 Votes
    72 Posts
    27589 Views

    Charly86C

    I had back this problem a 2nd time 2 days ago, I don't know if it's related but I was doing iptables FW settings on the VM, I had nodeBB running, and also redis and from my computer desktop redis desktop manager connected to DB.
    Then I made a mistake in iptables, blocked all redis port (even local), saying nodebb unable to connect to redis (so as redis desktop manager) then when I openned back 6379 port, all data was gone, not sure if it's related, just an information.

  • K
    ●

    Problem installing NodeBB

    Technical Support
    0 Votes
    3 Posts
    1242 Views

    BriB

    Also it looks like the redis version is a little old, you might want to upgrade that too: https://community.nodebb.org/topic/5935/problem-with-redis-upgrade

  • XiphX
    ●

    Read and Write from different Redis instances

    Feature Requests
    0 Votes
    1 Posts
    1814 Views

    XiphX

    Considering Redis' clustering is strictly master-slave and doesn't support multi-master, it would be nice to be able to read and write from different Redis instances.

    A very basic example: reading from the local Redis slave while writing to an external Redis master. Compared to the current situation (reading from and writing to the same Redis instance, which has to be the master because you can't write to slaves), this would result in data being returned faster from the local slave and the load on the remote master would be lowered.

    Some potential failover situations:

    Master up, slave(s) down: Read from the Master instead of the slaves Master up, one of many slaves down: Read from the node specified in the config as failover for this one, if not configured read from other slave, if all slaves are down read from master. Master down, slave(s) up: Enter a StackOverflow-esque read-only mode, 503 all requests to the yet-to-be-written Write API.
| | | |
Copyright © 2023 NodeBB | Contributors