On 9/3/19 9:57 AM, Daan Hoogland wrote:
> Can you find/look at the line before in the log. It is probably the one
> containing the hindering data. Or otherwise it *might* be a clue where in
> the flow it happens.
>
Do you have any idea what the easiest way might be?
I checked agent.log.1.gz and after I decompress is that file is not
binary, text only.
The binary data only seems to be present in the current file.
Wido
> On Tue, Sep 3, 2019 at 8:22 AM Wido den Hollander <w...@widodh.nl> wrote:
>
>>
>>
>> On 9/2/19 10:18 PM, Wei ZHOU wrote:
>>> Hi Wido,
>>>
>>> I had similar issue (not agent.log). It is probably caused by one or
>> few> lines with special characters.
>>
>> And I'm trying to figure out what causes it :-)
>>
>>> "grep -a" should work.
>>
>> I know, but other tools which analyze the logfile might also have
>> trouble reading the file due to binary characters.
>>
>> Wido
>>
>>>
>>> -Wei
>>>
>>> On Mon, 2 Sep 2019 at 19:35, Wido den Hollander <w...@widodh.nl> wrote:
>>>
>>>> Hi,
>>>>
>>>> I've seen this on multiple occasions with Ubuntu 18.04 (and maybe
>>>> 16.04?) hypervisors where according to 'grep' the agent.log is a binary
>>>> file:
>>>>
>>>> root@n06:~# grep security_group /var/log/cloudstack/agent/agent.log
>>>> Binary file /var/log/cloudstack/agent/agent.log matches
>>>> root@n06:~#
>>>>
>>>> If I open the file with 'less' I indeed see binary data.
>>>>
>>>> Tailing the file works just fine.
>>>>
>>>> Does anybody know where this is coming from? What in the CloudStack
>>>> agent causes it to write binary data to the logfile?
>>>>
>>>> Wido
>>>>
>>>
>>
>>
>>
>
