[SERVER-5041] Incorrect parameter in mongod.conf oplog Created: 22/Feb/12  Updated: 15/Aug/12  Resolved: 22/Feb/12

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 2.0.2
Fix Version/s: None

Type: Bug Priority: Trivial - P5
Reporter: Sergejs Degtjars Assignee: Michael A. Fiedler
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

CentOS http://downloads-distro.mongodb.org/repo/redhat/os/x86_64 stable


Operating System: Linux
Participants:

 Comments   
Comment by Michael A. Fiedler [ 22/Feb/12 ]

This is a duplicate of SERVER-5009. This has been resolved 2.1.1 and higher packages.

Comment by Scott Hernandez (Inactive) [ 22/Feb/12 ]

The full section is this in the conf file by default:

# Set oplogging level where n is
#   0=off (default)
#   1=W
#   2=R
#   3=both
#   7=W+some reads
#diaglog = 0

As you can see, the valid name is "diaglog" not "oplog" (which doesn't exist).

This diaglog is not something which should be used unless you are debugging and developing the server. It is not a general user feature.

Comment by Sergejs Degtjars [ 22/Feb/12 ]

In mongodb.conf:

# Set oplogging level where n is
#   0=off (default)
#   1=W
#   2=R
#   3=both
#   7=W+some reads
oplog = 0

cause
[root@mongo1 init.d]# ./mongod start
Starting mongod: error command line: unknown option oplog
use --help for help

Comment by Scott Hernandez (Inactive) [ 22/Feb/12 ]

Which parameter(s) are you talking about? Can you provide the logs from the server and the mongodb.conf?

Generated at Thu Feb 08 03:07:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.