Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with the log stream #354

Closed
sebastiankirsch opened this issue Dec 9, 2015 · 3 comments
Closed

Problem with the log stream #354

sebastiankirsch opened this issue Dec 9, 2015 · 3 comments

Comments

@sebastiankirsch
Copy link
Contributor

We have the problem that when starting our application with docker:start, the log stream is usually incomplete or randomly fails to parse some data like

Invalid log format for '��2015-12-09T14:39:45.6445' (expected: "<timestamp> <txt>")

or

Invalid log format for '��2015-12-09T14:53:15.738164970Z 2015-12-09 14:53:15,737 INFO  d.i.c.i.c.ResourceServerConfiguration - enable OAuth2 resource server ��201' (expected: "<timestamp> <txt>")

and then seizes to transfer the output of our application.

When writing the application output to a local file (via | tee /tmp/log), everything is complete and those funny characters (or the timestamp) are lacking; so this seems to be related to the mechanics of the plugin.

I'm running Docker version 1.9.1, build a34a1d5 on Ubuntu 14.04LTS. A colleague of mine has the same setup and the same problems, another colleague uses Docker 1.8.1, Mac OS X 10.10.5, docker machine 0.4.1 and does not experience those problems.

Our maven configuration is

        <plugin>
            <groupId>org.jolokia</groupId>
            <artifactId>docker-maven-plugin</artifactId>
            <version>0.13.6</version>
            <configuration>
                <logDate>default</logDate>
                <autoPull>true</autoPull>
                <images>
                    ...
                </images>
                <authConfig>
                   ...
                </authConfig>
            </configuration>
        </plugin>
@rhuss
Copy link
Collaborator

rhuss commented Dec 9, 2015

Which version of the plugin are you using ? There was a fix recently for this chunked encoding issue ...

@rhuss
Copy link
Collaborator

rhuss commented Dec 9, 2015

See #259 for details.

@rhuss
Copy link
Collaborator

rhuss commented Dec 9, 2015

Ok, seems not really to be fixed, so I will pick up this.

Let's continue at #259 since its the older issue ....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants