Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Redis oder MongoDB?

Redis

307

FrankM last edited by FrankM

Ich hatte mich bei meiner damaligen Installation für Redis entschieden, diese DB hält die Daten im Speicher vor. Sollte das mal in Zukunft ein Problem werden, wenn ich mal 100000 User habe , dann bräuchte man evt. mal ein Tool um die Redis Datenbank in eine MongoDB zu migrieren.

Hier ist so ein Tool https://github.com/BenLubar/nodebb-postgres-converter

Thread zum Thema https://community.nodebb.org/topic/7286/redis-or-mongodb
1. RockPro64 v2.1 / PCIe SATA 5 Ports / Boot direct from port 5 SSD / 2 * 3,5 Zoll 4TB HDD (raid1) / 2 * 2,5 Zoll 2 TB (raid 1) using as NAS / Kernel Linux NASrp64 5.6.0-1137-ayufan-ge57f05e7bf8f
2. RockPro64 v2.1 for testing ;)
3. Quartz64 Model A
1 Reply Last reply
Reply Quote 0

Redis Replication über Wireguard
Redis • redis wireguard • • FrankM

5

0
Votes

5
Posts

134
Views

K

👍
spart bischen zeit
Debian Buster 10.9 released
Linux • debian linux • • FrankM

1

0
Votes

1
Posts

44
Views

No one has replied
Wireguard
Wireguard • linux rockpro64 wireguard • • FrankM

4

0
Votes

4
Posts

452
Views

Etwas schnellerer Weg den Tunnel aufzubauen, Voraussetzung
wireguard modul installiert Keys erzeugt
Danach dann einfach
ip link add wg0 type wireguard wg setconf wg0 /etc/wireguard/wg0.conf Datei /etc/wireguard/wg0.conf [Interface] PrivateKey = <Private Key> ListenPort = 60563 [Peer] PublicKey = <Public Key Ziel> Endpoint = <IPv4 Adresse Zielrechner>:58380 AllowedIPs = 10.10.0.1/32
Die Rechte der Dateien von wireguard müssen eingeschränkt werden.
sudo chmod 0600 /etc/wireguard/wg0.conf
Das ganze per rc.local beim Booten laden. Datei /root/wireguard_start.sh
############################################################################################### # Autor: Frank Mankel # Startup-Script # Wireguard # Kontakt: frank.mankel@gmail.com # ############################################################################################### ip link add wg0 type wireguard ip address add dev wg0 10.10.0.1/8 wg setconf wg0 /etc/wireguard/wg0.conf ip link set up dev wg0
Danach Datei ausführbar machen
chmod +x /root/wireguard_start.sh
In rc.local
/root/wireguard_start.sh
eintragen - Fertig!
NodeBB - Update auf 1.13.3
NodeBB • nodebb • • FrankM

1

0
Votes

1
Posts

54
Views

No one has replied
Ubuntu 20.04 Focal - Einrichtung
Linux • ubuntu linux • • FrankM

16

0
Votes

16
Posts

1045
Views

@reiner-zufall sagte in Ubuntu 20.04 Focal - Einrichtung:

auto-save-session

Interessant. Bitte poste, wenn Du was findest.
Redis Replication
Redis • linux redis • • FrankM

3

1
Votes

3
Posts

165
Views

In den Logs sieht das so aus.
Master 855:M 10 May 2020 07:51:45.458 * DB loaded from disk: 0.563 seconds 855:M 10 May 2020 07:51:45.458 * Ready to accept connections 855:M 10 May 2020 07:51:45.713 * Replica 10.0.0.2:6379 asks for synchronization 855:M 10 May 2020 07:51:45.713 * Partial resynchronization not accepted: Replication ID mismatch (Replica asked for 'd6042ec68cc9b4e3ccd8ebd8e28012133c24efb4', my replication IDs are '071743$ 855:M 10 May 2020 07:51:45.713 * Starting BGSAVE for SYNC with target: disk 855:M 10 May 2020 07:51:45.716 * Background saving started by pid 859 859:C 10 May 2020 07:51:46.107 * DB saved on disk 859:C 10 May 2020 07:51:46.111 * RDB: 24 MB of memory used by copy-on-write 855:M 10 May 2020 07:51:46.162 * Background saving terminated with success 855:M 10 May 2020 07:51:46.324 * Synchronization with replica 10.0.0.2:6379 succeeded 855:M 10 May 2020 07:51:50.674 # Connection with replica 10.0.0.2:6379 lost. 855:M 10 May 2020 07:51:51.254 * Replica 10.0.0.2:6379 asks for synchronization 855:M 10 May 2020 07:51:51.255 * Partial resynchronization request from 10.0.0.2:6379 accepted. Sending 0 bytes of backlog starting from offset 1. 855:M 10 May 2020 07:56:47.021 * 10 changes in 300 seconds. Saving... 855:M 10 May 2020 07:56:47.023 * Background saving started by pid 978 978:C 10 May 2020 07:56:47.426 * DB saved on disk 978:C 10 May 2020 07:56:47.428 * RDB: 28 MB of memory used by copy-on-write 855:M 10 May 2020 07:56:47.529 * Background saving terminated with success 855:M 10 May 2020 07:56:52.961 # Connection with replica 10.0.0.2:6379 lost. 855:M 10 May 2020 07:56:53.649 * Replica 10.0.0.2:6379 asks for synchronization 855:M 10 May 2020 07:56:53.649 * Partial resynchronization request from 10.0.0.2:6379 accepted. Sending 0 bytes of backlog starting from offset 6413. 855:M 10 May 2020 08:01:48.089 * 10 changes in 300 seconds. Saving... 855:M 10 May 2020 08:01:48.091 * Background saving started by pid 1044 1044:C 10 May 2020 08:01:48.502 * DB saved on disk 1044:C 10 May 2020 08:01:48.505 * RDB: 24 MB of memory used by copy-on-write 855:M 10 May 2020 08:01:48.594 * Background saving terminated with success Slave 1324:S 10 May 2020 07:56:53.651 * DB loaded from disk: 0.638 seconds 1324:S 10 May 2020 07:56:53.651 * Before turning into a replica, using my master parameters to synthesize a cached master: I may be able to synchronize with the new master with just a partia$ 1324:S 10 May 2020 07:56:53.651 * Ready to accept connections 1324:S 10 May 2020 07:56:53.651 * Connecting to MASTER 10.0.0.4:6379 1324:S 10 May 2020 07:56:53.651 * MASTER <-> REPLICA sync started 1324:S 10 May 2020 07:56:53.652 * Non blocking connect for SYNC fired the event. 1324:S 10 May 2020 07:56:53.653 * Master replied to PING, replication can continue... 1324:S 10 May 2020 07:56:53.654 * Trying a partial resynchronization (request 86ba864a2575c203a4eddd80bd6f4b058ebe1fb7:6413). 1324:S 10 May 2020 07:56:53.655 * Successful partial resynchronization with master. 1324:S 10 May 2020 07:56:53.655 * MASTER <-> REPLICA sync: Master accepted a Partial Resynchronization. 1324:S 10 May 2020 08:01:54.077 * 10 changes in 300 seconds. Saving... 1324:S 10 May 2020 08:01:54.080 * Background saving started by pid 1494 1494:C 10 May 2020 08:01:54.523 * DB saved on disk 1494:C 10 May 2020 08:01:54.527 * RDB: 0 MB of memory used by copy-on-write 1324:S 10 May 2020 08:01:54.582 * Background saving terminated with success
Linux Mint Cinnamon 20.2 "Uma" released
Linux • linuxmint linux • • FrankM

3

0
Votes

3
Posts

32
Views

Was noch gestört hatte, war der Scrollbalken im FF. Der war zu schmal, konnte man schlecht erwischen.

8e403120-11e2-413f-a479-0ebc3002e6d4-grafik.png

Quelle: https://forums.linuxmint.com/viewtopic.php?f=47&t=330849&sid=1c7c71850931d5c34d8a0dd41ff57679
NanoPI R2S - Snapshot aktualisieren
NanoPi R2S • nanopir2s openwrt linux • • FrankM

3

0
Votes

3
Posts

122
Views

@thrakath1980 Das kann ich Dir leider nicht beantworten. Denke aber, das es sinnvoll ist neu anzufangen. Welche Settings meinst Du?

Ich würde mal /etc/config sichern. Da sollte das Meiste ja drin sein.

Notifications? Hmm, ich hoffe das das funktioniert. Ich schau zur Sicherheit mal nach.

1 / 1

Redis oder MongoDB?

Redis Replication über Wireguard Redis • redis wireguard • • FrankM

Debian Buster 10.9 released Linux • debian linux • • FrankM

Wireguard Wireguard • linux rockpro64 wireguard • • FrankM

NodeBB - Update auf 1.13.3 NodeBB • nodebb • • FrankM

Ubuntu 20.04 Focal - Einrichtung Linux • ubuntu linux • • FrankM

Redis Replication Redis • linux redis • • FrankM

Linux Mint Cinnamon 20.2 "Uma" released Linux • linuxmint linux • • FrankM

NanoPI R2S - Snapshot aktualisieren NanoPi R2S • nanopir2s openwrt linux • • FrankM

Redis Replication über Wireguard
Redis • redis wireguard • • FrankM

Debian Buster 10.9 released
Linux • debian linux • • FrankM

Wireguard
Wireguard • linux rockpro64 wireguard • • FrankM

NodeBB - Update auf 1.13.3
NodeBB • nodebb • • FrankM

Ubuntu 20.04 Focal - Einrichtung
Linux • ubuntu linux • • FrankM

Redis Replication
Redis • linux redis • • FrankM

Linux Mint Cinnamon 20.2 "Uma" released
Linux • linuxmint linux • • FrankM

NanoPI R2S - Snapshot aktualisieren
NanoPi R2S • nanopir2s openwrt linux • • FrankM