mongo-connector don't read oplog_progress.txt about mongo-connector HOT 4 CLOSED

@neorand - When you say "and second run , mongo-connector can't read oplog_progress.txt file" what error do you get?

from mongo-connector.

I think I got the same issue regarding to oplog file
Mine didn't event write/find the oplog file, what I'm doing wrong? I'm using single replica set btw..

Here is the log:

2013-07-19 04:21:02,433 - INFO - Beginning Mongo Connector
2013-07-19 04:21:02,433 - INFO - No doc manager specified, using simulator.
2013-07-19 04:21:03,435 - CRITICAL - MongoConnector: Can't find OplogProgress file!
2013-07-19 04:21:03,439 - INFO - OplogManager: Initializing oplog thread
2013-07-19 04:21:03,441 - INFO - MongoConnector: Starting connection thread MongoClient('localhost', 27017)
2013-07-19 04:21:03,441 - INFO - MongoConnector: Stopping all OplogThreads
2013-07-19 04:21:03,445 - INFO - OplogManager: Collection(Database(MongoClient('localhost', 27017), u'local'), u'oplog.rs') Dumped collection into target system

from mongo-connector.

@dimaspriyanto What happens if you give it the full name of the config file? Also, do you have RW access in the directory that it's located or wherever you are running the connector from? What arguments are you passing to the connector?

from mongo-connector.

mongo-connector used to expect the oplog progress file (called "config.txt" by default) to exist already before being run. Even the scripts in the test directory touch the config.txt file before attempting to use mongo-connector. I consider this a bug, and this behavior is fixed (mongo-connector creates the oplog progress file if it doesn't exist) in commit 26abf7a38674f98e31630834a1e7cd2b1b535595

from mongo-connector.