title: CloudWatch logs acting weird
body: <p>I have two log files with multi-line log statements. Both of them have same datetime format at the begining of each log statement. The configuration looks like this:</p>
  
  <pre><code>state_file = /var/lib/awslogs/agent-state
  
  [/opt/logdir/log1.0]
  datetime_format = %Y-%m-%d %H:%M:%S
  file = /opt/logdir/log1.0
  log_stream_name = /opt/logdir/logs/log1.0
  initial_position = start_of_file
  multi_line_start_pattern = {datetime_format}
  log_group_name = my.log.group
  
  
  [/opt/logdir/log2-console.log]
  datetime_format = %Y-%m-%d %H:%M:%S
  file = /opt/logdir/log2-console.log
  log_stream_name = /opt/logdir/log2-console.log
  initial_position = start_of_file
  multi_line_start_pattern = {datetime_format}
  log_group_name = my.log.group
  </code></pre>
  
  <p>The cloudwatch logs agent is sending log1.0 logs correctly to my log group on cloudwatch, however, its not sending log files for log2-console.log.</p>
  
  <p>awslogs.log says:</p>
  
  <pre><code>2016-11-15 08:11:41,308 - cwlogs.push.batch - WARNING - 3593 - Thread-4 - Skip event: {'timestamp': 1479196444000, 'start_position': 42330916L, 'end_position': 42331504L}, reason: timestamp is more than 2 hours in future.
  2016-11-15 08:11:41,308 - cwlogs.push.batch - WARNING - 3593 - Thread-4 - Skip event: {'timestamp': 1479196451000, 'start_position': 42331504L, 'end_position': 42332092L}, reason: timestamp is more than 2 hours in future.
  </code></pre>
  
  <p>Though server time is correct. Also weird thing is Line numbers mentioned in start_position and end_position does not exist in actual log file being pushed.</p>
  
  <p>Anyone else experiencing this issue?</p>