[SERVER-10935] Warning message when snmp config file is not sent to mongod log file Created: 27/Sep/13  Updated: 25/Oct/14  Resolved: 02/Oct/14

Status: Closed
Project: Core Server
Component/s: Admin, Logging
Affects Version/s: 2.5.2
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Sridhar Nanjundeswaran Assignee: Unassigned
Resolution: Done Votes: 0
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

MongoDB enterprise edition on Windows


Issue Links:
Related
Participants:

 Description   

This is particularly a problem when running mongod as a windows service since the message is lost.

When starting with just --logpath but on the shell the warning is sent to the current shell as opposed to the log path.

.\mongod.exe --snmp-master --logpath C:\data\mongod.log
2013-09-26T17:04:03.891-0700 log file "C:\data\mongod.log" exists; moved to "C:\data\mongod.log.2013-09-27T00-04-03".
Warning: no access control information configured.
(Config search path: c:/Utils/snmp/etc/snmp;c:/Utils/snmp/share/snmp;c:/Utils/snmp/lib;c:\Users\Sridhar/.snmp)
It's unlikely this agent can serve any useful purpose in this state.
Run "snmpconf -g basic_setup" to help you configure the mongod.conf file for this agent.



 Comments   
Comment by James Wahlin [ 02/Oct/14 ]

This problem no longer exists. Work done under SERVER-8998 redirected net-snmp logging to the mongod.log file.

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