[SERVER-4824] Problem implementing authentication on an existing cluster Created: 31/Jan/12  Updated: 11/Jul/16  Resolved: 31/Jan/12

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

Type: Question Priority: Minor - P4
Reporter: Brett Goldstein Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Trying to implement above on existing cluster unsuccessfully. Took down all mongod and see following:

-bash-4.1$ chmod 700 ./mongodb-linux-x86_64-2.0.2/sec/key1
-bash-4.1$ ./mongodb-linux-x86_64-2.0.2/bin/mongod --dbpath /app/data/db/ --fork --logpath /app/mongolog/mongodb.log --shardsvr --keyFile ./mongodb-linux-x86_64-2.0.2/sec/key1
-bash-4.1$ forked process: 11235
all output going to: /app/mongolog/mongodb.log

-bash-4.1$ tail -f /app/mongolog/mongodb.log
Tue Jan 31 08:20:30 dbexit:
Tue Jan 31 08:20:30 shutdown: going to close listening sockets...
Tue Jan 31 08:20:30 shutdown: going to flush diaglog...
Tue Jan 31 08:20:30 shutdown: going to close sockets...
Tue Jan 31 08:20:30 shutdown: waiting for fs preallocator...
Tue Jan 31 08:20:30 shutdown: lock for final commit...
Tue Jan 31 08:20:30 shutdown: final commit...
Tue Jan 31 08:20:30 shutdown: closing all files...
Tue Jan 31 08:20:30 closeAllFiles() finished
Tue Jan 31 08:20:30 dbexit: really exiting now



 Comments   
Comment by Brett Goldstein [ 31/Jan/12 ]

was able to resolve – silly reason. thx!

Comment by Eliot Horowitz (Inactive) [ 31/Jan/12 ]

You need to attach the entire log, not just the last 10 lines

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