yous / pinpoint-docker

Docker for Pinpoint
https://hub.docker.com/r/yous/pinpoint/
MIT License
37 stars 12 forks source link

collector doesn't start #6

Closed tatonki1 closed 7 years ago

tatonki1 commented 7 years ago

Hi - trying to leverage your docker stack for pinpoint...

The 1st two startup scripts worked fine, but the collector one keeps timing out...

I have gotten the pinpoint stack to run on my local computer w/o docker, but really want to use the docker version...any assistance would be most appreciated! Thanks!

root@99a564ad8b38:/pinpoint# quickstart/bin/start-collector.sh ---check pinpoint-quickstart-collector process status.--- ---initialize pinpoint-quickstart-collector logs.--- rm /pinpoint/quickstart/logs/quickstart.collector.log. rm /pinpoint/quickstart/logs/pid/quickstart.collector.pid. ---pinpoint-quickstart-collector initialization started. pid=10421.--- starting pinpoint-quickstart-collector. 0 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 5 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 10 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 15 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 20 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 25 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 30 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 35 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 40 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 45 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 50 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 55 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 60 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 65 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 70 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 75 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 80 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 85 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 90 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 95 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 100 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 105 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 110 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 115 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 120 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 125 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 130 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 135 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 140 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 145 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 150 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 155 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 160 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 165 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 170 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 175 /180 sec(close wait limit). starting pinpoint-quickstart-collector. 180 /180 sec(close wait limit). ---pinpoint-quickstart-collector initialization failed. pid=10421.--- root@99a564ad8b38:/pinpoint# vi quickstart/bin/start-collector.sh

yous commented 7 years ago

Hi, can you tell me the version of image you used? I just tried on yous/pinpoint:1.6.0 and succeeded. Please give me the log created at /pinpoint/quickstart/logs/quickstart.collector.log. You can use docker cp command.

docker cp CONTAINER:/pinpoint/quickstart/logs/quickstart.collector.log DEST_PATH
tatonki1 commented 7 years ago

Hi - thanks for responding! Ok, I did get the collector running now; but still having similar issues with the web script.... it's just timing out...I'm using yous/pinpoint:1.6 as well.

quickstart.web.txt

This timeout thing seems to happen sporadically, I'd like to understand why. I don't think I'm having any proxy issues...thanks!

yous commented 7 years ago

Hi, it seems to work actually. This is my log, similar to yours.

quickstart.web.log.txt

This can be some computing power issues, so try changing CHECK_COUNT value in quickstart/bin/start-web.sh and quickstart/bin/start-collector.sh. These values are hard-coded, actually.

tatonki1 commented 7 years ago

Hi Yous - i'm facing this same issue again. It's odd; I was able to successfully launch all 5 scripts using your pinpoint docker and hit the localhost urls last week; left it up and running, everything was fine. I needed to restart the image to allow ports 9994-9996 to be available to the localhost, but now I get the same error as my first post - just won't start up again. I don't understand the intermittency of this issue. Do the scripts need to access anything via the web that may not be up and running sometimes?

tatonki1 commented 7 years ago

Yous - here is the latest cat of the collector log file i just ran...

root@d26290017de5:/pinpoint/quickstart# cat logs/quickstart.collector.log [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for com.navercorp.pinpoint:pinpoint-quickstart-collector:war:1.6.0 [WARNING] 'version' contains an expression but should be a constant. @ com.navercorp.pinpoint:pinpoint-quickstart-collector:${maven.pinpoint.version}, /pinpoint/quickstart/collector/pom.xml, line 11, column 14 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-war-plugin is missing. @ com.navercorp.pinpoint:pinpoint-quickstart-collector:${maven.pinpoint.version}, /pinpoint/quickstart/collector/pom.xml, line 41, column 21 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.2/maven-war-plugin-2.2.pom [WARNING] Failed to retrieve plugin descriptor for org.apache.maven.plugins:maven-war-plugin:2.2: Plugin org.apache.maven.plugins:maven-war-plugin:2.2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-war-plugin:jar:2.2 Downloading: https://repo.maven.apache.org/maven2/org/codehaus/mojo/properties-maven-plugin/1.0-alpha-2/properties-maven-plugin-1.0-alpha-2.pom [WARNING] Failed to retrieve plugin descriptor for org.codehaus.mojo:properties-maven-plugin:1.0-alpha-2: Plugin org.codehaus.mojo:properties-maven-plugin:1.0-alpha-2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.codehaus.mojo:properties-maven-plugin:jar:1.0-alpha-2 Downloading: https://repo.maven.apache.org/maven2/org/apache/tomcat/maven/tomcat7-maven-plugin/2.2/tomcat7-maven-plugin-2.2.pom

tatonki1 commented 7 years ago

Got it! Had to re-edit the maven settings.xml file to put in my proxy creds again! :) Always something to remember!

yous commented 7 years ago

That was it! Thank you for letting me know. :smiley: