These are chat archives for aws/aws-cli

5th
Oct 2017
Krishna Gara
@krishna-gara
Oct 05 2017 06:02
Hello
Can I get ref to integrate the cognitoo ask in java
SDK*
Henrik Huitti
@henkka
Oct 05 2017 15:10

Hello, anyone else noticed problems with CloudWatch Logs not being updated with yesterdays update of awscli (1.11.165) && awscli-cwlogs (1.4.3)? With one log group we are receiving

ERROR - 3487 - Thread-599 - Exception caught in <FileEventBatchReader(Thread-599, started daemon 140256703665920)>
Traceback (most recent call last):
  File "/var/awslogs/local/lib/python2.7/site-packages/cwlogs/threads.py", line 58, in run
    self._run()
  File "/var/awslogs/local/lib/python2.7/site-packages/cwlogs/push.py", line 1024, in _run
    self._push_event()
  File "/var/awslogs/local/lib/python2.7/site-packages/cwlogs/push.py", line 1084, in _push_event
    str(self.temp_event.message[0:self.MAX_LENGTH_FOR_TIMESTAMP_FIELD]))
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position 32: ordinal not in range(128)

After that error log forwarding stops working for the log group in question - receiving next warnings every few seconds:

2017-10-05 14:00:05,807 - cwlogs.push.publisher - WARNING - 3482 - Thread-27 - Caught exception: An error occurred (DataAlreadyAcceptedException) when calling the PutLogEvents operation: The given batch of log events has already been accepted. The next batch can be sent with sequenceToken: 49577392232629262819892340232275967281555875721946077311
2017-10-05 14:01:15,876 - cwlogs.push.publisher - WARNING - 3482 - Thread-31 - Caught exception: An error occurred (InvalidSequenceTokenException) when calling the PutLogEvents operation: The given sequenceToken is invalid. The next expected sequenceToken is: 49577392232629262819892340232275967281555875721946077311
CloudWatch Logs has been working for us over two years so we're pretty confident that something in newest update broke it. It's however strange that it's only for one Log Group which contains Java application log