mongod's oplog size flag is --oplogSize on the command line
Build / Build (push) Successful in 8m26s
Deploy / privapub.thepra.dev (push) Successful in 8m53s

--oplogSizeMB is the configuration file's key (replication.oplogSizeMB); mongod refuses it as a flag, so setup.sh's
replica-set step left the unit restarting until the flag was fixed on Max.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LsXgEaXee4GCU1hwYgPJXw
This commit is contained in:
thepraandClaude Opus 5.5 committed 2026-10-07 17:32:02 +02:00
1 parent 163f7e4e2b
commit 4eda3da75d
1 file changed
+1 -1
+1 -1
View File
@@ -7,7 +7,7 @@ Type=exec
User=www-data User=www-data
Group=www-data Group=www-data
# a one-member replica set (rs0), so a backup reads every collection at one instant; its oplog kept small # a one-member replica set (rs0), so a backup reads every collection at one instant; its oplog kept small
ExecStart=/usr/bin/mongod --dbpath /var/lib/privapub/mongo --port 27022 --bind_ip 127.0.0.1 --noauth --wiredTigerCacheSizeGB 0.25 --replSet rs0 --oplogSizeMB 990 --quiet ExecStart=/usr/bin/mongod --dbpath /var/lib/privapub/mongo --port 27022 --bind_ip 127.0.0.1 --noauth --wiredTigerCacheSizeGB 0.25 --replSet rs0 --oplogSize 990 --quiet
Restart=always Restart=always
RestartSec=5 RestartSec=5
LimitNOFILE=64000 LimitNOFILE=64000