On Fri, Jul 14, 2017 at 3:42 PM, Gary Franczyk <[email protected]> wrote:
> Thanks The new verbose log ends with this: > > > > > > I0714 18:14:38.264960 1 tar.go:320] Adding to tar: > /tmp/s2i-build238536132/upload/src/server.js as src/server.js > > I0714 18:14:38.265009 1 tar.go:320] Adding to tar: > /tmp/s2i-build238536132/upload/src/tests/app_test.js as > src/tests/app_test.js > > I0714 18:14:38.265067 1 tar.go:320] Adding to tar: > /tmp/s2i-build238536132/upload/src/views/index.html as > src/views/index.html > > I0714 18:14:38.698613 1 docker.go:1033] Waiting for container " > 0c433cbbeb93c90897b221d6e35f784b3f99329398246f7276d0b0b9f72ab43e" to stop > ... > > > > > > I see that this container is there: > > > > *0c433cb*beb93 registry.access.redhat.com/ > rhscl/nodejs-4-rhel7@sha256:a225ccca591aeb338e4d628973d1db > 273c61dff44df628755ffbeebeeefb0082 "container-entrypoint" 3 minutes > ago Up 3 minutes > s2i_registry_access_redhat_com_rhscl_nodejs_4_rhel7_sha256_ > a225ccca591aeb338e4d628973d1db273c61dff44df628755ffbeebeeefb0082_ba9daac3 > > > > > > > > Why would it be waiting for it to stop? > given your use of a proxy, i'm guessing npm is stuck trying to download dependencies, so it's waiting for the container to stop because the assemble script is blocked on npm trying to download content. Have you set HTTP/HTTPS proxy env variabls on your buildconfig? https://github.com/sclorg/s2i-nodejs-container/blob/master/6/s2i/bin/assemble#L25-L43 Also can you run docker logs on that hung container itself? I would have expected to see a bit more output in your build log, in part from the logs of that stuck container. > > > > > *Gary Franczyk* > > Senior Unix Administrator, Infrastructure > > > > Availity | 10752 Deerwood Park Blvd S. Ste 110, Jacksonville FL 32256 > W 904.470.4953 <%28904%29%20470-4953> | M 561.313.2866 > <%28561%29%20313-2866> > > *[email protected] <[email protected]>* > > > > *From: *Ben Parees <[email protected]> > *Date: *Friday, July 14, 2017 at 11:32 AM > *To: *Gary Franczyk <[email protected]> > *Cc: *"[email protected]" <[email protected] > > > *Subject: *[EXTERNAL] Re: Build from github doesn't start > > > > WARNING: This email originated outside of the Availity email system. > DO NOT CLICK links or open attachments unless you recognize the sender and > know the content is safe. > ------------------------------ > > > > > > On Fri, Jul 14, 2017 at 11:06 AM, Gary Franczyk < > [email protected]> wrote: > > I have a pretty newly built test installation of openshift that is giving > me a problem. > > > > When I try to use one of the example node4 builds, it hangs immediately > after (apparently) cloning the repo. > > > > This is shown in the logs for about 10 minutes before giving up: > > > > Using HTTP proxy http://proxy.ag.qua.availity.net:8080 and HTTPS proxy > http://proxy.ag.qua.availity.net:8080 for script download > > Cloning "https://github.com/openshift/nodejs-ex.git > <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openshift_nodejs-2Dex.git&d=DwMFaQ&c=OICO5LaDH-Xi2CSZAJgmTQ&r=DWo_ijwFGqBf00dIEKrMRiq5JjUOT-29YI7Con8CGIc&m=K3uDmvNte8ZyyRdvzwXHAYpP7rT5nmORQ9tH0NTATEI&s=i4k2ufzX5iySR5Xzb7nnuvliSLzy6luqn3OdBftew4o&e=>" > ... > > Commit: f12494cff0ee3a347551e288782d95019df124d8 (Merge pull > request #128 from coreydaley/bugzilla_1365656_github_webhook_descri..) > > Author: Ben Parees <[email protected]> > > Date: Sun Jun 25 23:27:32 2017 -0400 > > > > How do I tell what it is hung on? > > > > try rerunning with build loglevel 5 (oc start-build foo --build-loglevel=5) > > > > > > OpenShift > > > > > > *Gary Franczyk* > > Senior Unix Administrator, Infrastructure > > > > Availity | 10752 Deerwood Park Blvd S. Ste 110, Jacksonville FL 32256 > W 904.470.4953 <%28904%29%20470-4953> | M 561.313.2866 > <%28561%29%20313-2866> > > *[email protected] <[email protected]>* > ------------------------------ > > The information contained in this e-mail may be privileged and > confidential under applicable law. It is intended solely for the use of the > person or firm named above. If the reader of this e-mail is not the > intended recipient, please notify us immediately by returning the e-mail to > the originating e-mail address. Availity, LLC is not responsible for errors > or omissions in this e-mail message. Any personal comments made in this > e-mail do not reflect the views of Availity, LLC. > > > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openshift.redhat.com_openshiftmm_listinfo_users&d=DwMFaQ&c=OICO5LaDH-Xi2CSZAJgmTQ&r=DWo_ijwFGqBf00dIEKrMRiq5JjUOT-29YI7Con8CGIc&m=K3uDmvNte8ZyyRdvzwXHAYpP7rT5nmORQ9tH0NTATEI&s=MASR9SvE7EqQ56G6zkdNPOVJEcaia02LfK3Lw17RZXY&e=> > > > > > -- > > Ben Parees | OpenShift > -- Ben Parees | OpenShift
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
