Race condition starting new binary log about cosmos HOT 7 CLOSED

I don't thnk there is a race condition within packet_log_writer. There may be somewhere in the code where close is being called twice within same second. Are you only seeing this at shutdown?

from cosmos.

Unfortunately no it was during normal running. I'll dig up the server log messages for that time period.

Question label?

from cosmos.

:) Question label is just because I'm not sure this is an actual bug or not.

from cosmos.

I found several instances of this occurring in the sever message log. The signature is basically this:

2015/02/02 16:35:58.088  INFO: Log File Opened : 2015_02_02_16_35_58_tlm.bin
2015/02/02 16:35:58.089  INFO: Log File Closed : 2015_02_02_16_35_58_tlm.bin
2015/02/02 16:35:58.090  INFO: Log File Opened : 2015_02_02_16_35_58_tlm_1.bin

When I open the first file it always has just a single packet in it. I've had this happen with both command and telemetry logs. Frequency seems to be about once a day although it's a bit sporadic.

I have 7 loggers which are all basically setup as follows:

PACKET_LOG_WRITER DEFAULT meta_packet_log_writer.rb COSMOS META config/data/default_meta_pri.txt true true cosmos true 600

from cosmos.

Is there another "Log File Closed" line immediately before your first "Log File Opened" ?

from cosmos.

In most cases the last log file was closed 2s or so before. However in one command log it was closed 2 hours before.

from cosmos.

Ok I see the problem. Fix in a minute.

from cosmos.