[repl writer worker 11] ERROR: warning: log line attempted (126k) over max size(10k), printing beginning and end

404 views
Skip to first unread message

Vishesh Singhal

unread,
Jan 5, 2016, 1:31:16 AM1/5/16
to mongodb-user
Hi,

I have cluster with 3 nodes, and running the MongoDB as a windows service as:
"C:\MongoDB\bin\mongod.exe" --service --config="C:\MongoDB\Scripts\mongod.conf"

with mongod.conf file:

port=27017
dbpath=E:\MongoDB\data\db
logpath=D:\logs\MongoDB\mongo.log
keyFile=C:\MongoDB\scripts\keyfile.txt
logappend=true
replSet=tf4
smallfiles=true
oplogSize=10240
directoryperdb=true


I found that the Mongodb service was crashed. I checked the logs and found alot of Error/warning as:
Mon Jan 04 13:08:44.399 [repl writer worker 11] ERROR: warning: log line attempted (126k) over max size(10k), printing beginning and end

Can you please help me what that error is and how can I fix this error.

Stephen Steneker

unread,
Jan 5, 2016, 2:14:23 AM1/5/16
to mongodb-user
On Tuesday, 5 January 2016 17:31:16 UTC+11, Vishesh Singhal wrote:
I found that the Mongodb service was crashed. I checked the logs and found alot of Error/warning as:
Mon Jan 04 13:08:44.399 [repl writer worker 11] ERROR: warning: log line attempted (126k) over max size(10k), printing beginning and end

Can you please help me what that error is and how can I fix this error.

Hi Vishesh,

Can you provide some more details:
  • What specific version of MongoDB server and Windows are you running?
  • Did the MongoDB service crash on all of your nodes, or a specific node?
  • What is the current state of your replica set -- did the crashed nodes recover successfully, or are you still trying to restart them?
  • What role did the node(s) have immediately prior to the crash (eg. primary or secondary)?
The particular log line you have highlighted is actually a warning, not an error. The warning relates to log entries that have been truncated (in the mongod log), which may be common if you generate large queries using $in. You should see part of the query logged (beginning and end), but the full content of the query is larger than 10k so there will be a "..." replacing the middle part of the query.

If your MongoDB service crashed, there should be a more descriptive error prior to the service stopping - try searching for "Assertion". If you can post a gist/pastebin with more of the log immediately prior to the crash, that would be helpful.

Regards,
Stephen
Reply all
Reply to author
Forward
0 new messages