Check on the specific node and look at docker inspect ID and docker logs ID. Check lsof to see if any open connections are open to github. I don't know if node has a signal that will cause it to dump a stack to stderr, but that might help if it does.
On Jul 15, 2017, at 11:58 AM, Gary Franczyk <[email protected]> wrote: I wouldn’t be surprised if it were a proxy issue. I added the proxy settings and it isn’t any different. The last message is about “waiting for container xxxx to stop”. [root@agltstosm01 ~]# oc env --list bc node # buildconfigs node HTTP_PROXY=http://proxy:8080 HTTPS_PROXY=http://proxy:8080 http_proxy=http://proxy:8080 https_proxy=http://proxy:8080 [root@agltstosm01 ~]# Here is the tail of the logs of the build pod: … I0715 15:55:22.250334 1 docker.go:801] Base directory for S2I scripts is '/usr/libexec/s2i'. Untarring destination is '/tmp'. I0715 15:55:22.250482 1 docker.go:935] Creating container with options {Name:"s2i_registry_access_redhat_com_rhscl_nodejs_4_rhel7_sha256_a225ccca591aeb338e4d628973d1db273c61dff44df628755ffbeebeeefb0082_c4e2f05d" Config:&{Hostname: Domainname: User: AttachStdin:false AttachStdout:true AttachStderr:false ExposedPorts:map[] Tty:false OpenStdin:true StdinOnce:true Env:[OPENSHIFT_BUILD_NAME=node-7 OPENSHIFT_BUILD_NAMESPACE=abc OPENSHIFT_BUILD_SOURCE= https://github.com/openshift/nodejs-ex.git OPENSHIFT_BUILD_REFERENCE=master HTTP_PROXY=http://proxy:8080 HTTPS_PROXY=http://proxy:8080 http_proxy= http://proxy:8080 https_proxy=http://proxy:8080 BUILD_LOGLEVEL=4 NO_PROXY=.cluster.local,10.92.138.67,agltstosh01.availity.net, agltstosh02.availity.net,agltstosh03.availity.net,agltstosi01.availity.net, agltstosi02.availity.net,agltstosm01.availity.net,agltstosm02.availity.net, agltstosm03.availity.net,agt-master.availity.net,ccp.ag.tst.availity.net, ccp.availity.net,devsrv.availity.net ,docker-registry.default.svc.cluster.local,jenkins.availity.com, jenkins2.availity.com,tst-services.availity.com no_proxy=.cluster.local,10.92.138.67,agltstosh01.availity.net, agltstosh02.availity.net,agltstosh03.availity.net,agltstosi01.availity.net, agltstosi02.availity.net,agltstosm01.availity.net,agltstosm02.availity.net, agltstosm03.availity.net,agt-master.availity.net,ccp.ag.tst.availity.net, ccp.availity.net,devsrv.availity.net ,docker-registry.default.svc.cluster.local,jenkins.availity.com, jenkins2.availity.com,tst-services.availity.com] Cmd:[/bin/sh -c tar -C /tmp -xf - && /usr/libexec/s2i/assemble] ArgsEscaped:false Image: registry.access.redhat.com/rhscl/nodejs-4-rhel7@sha256:a225ccca591aeb338e4d628973d1db273c61dff44df628755ffbeebeeefb0082 Volumes:map[] WorkingDir: Entrypoint:[] NetworkDisabled:false MacAddress: OnBuild:[] Labels:map[] StopSignal:} HostConfig:&{Binds:[] ContainerIDFile: LogConfig:{Type: Config:map[]} NetworkMode:container:359478f0ee3ee75721f45b0aa49edb0c97fbcd549ef093172a65f1193cb57f10 PortBindings:map[] RestartPolicy:{Name: MaximumRetryCount:0} AutoRemove:false VolumeDriver: VolumesFrom:[] CapAdd:[] CapDrop:[KILL MKNOD SETGID SETUID SYS_CHROOT] DNS:[] DNSOptions:[] DNSSearch:[] ExtraHosts:[] GroupAdd:[] IpcMode: Cgroup: Links:[] OomScoreAdj:0 PidMode: Privileged:false PublishAllPorts:false ReadonlyRootfs:false SecurityOpt:[] StorageOpt:map[] Tmpfs:map[] UTSMode: UsernsMode: ShmSize:0 Sysctls:map[] ConsoleSize:[0 0] Isolation: Resources:{CPUShares:51 Memory:92233720368547 CgroupParent: BlkioWeight:0 BlkioWeightDevice:[] BlkioDeviceReadBps:[] BlkioDeviceWriteBps:[] BlkioDeviceReadIOps:[] BlkioDeviceWriteIOps:[] CPUPeriod:100000 CPUQuota:5000 CpusetCpus: CpusetMems: Devices:[] DiskQuota:0 KernelMemory:0 MemoryReservation:0 MemorySwap:92233720368547 MemorySwappiness:<nil> OomKillDisable:<nil> PidsLimit:0 Ulimits:[] CPUCount:0 CPUPercent:0 IOMaximumIOps:0 IOMaximumBandwidth:0 NetworkMaximumBandwidth:0}}} ... I0715 15:55:22.733401 1 docker.go:969] Attaching to container "a978eaafd74681538dd51168b1832a5cc914386301483635c23c06472d4b3c1c" ... I0715 15:55:22.750985 1 docker.go:1007] Starting container "a978eaafd74681538dd51168b1832a5cc914386301483635c23c06472d4b3c1c" ... I0715 15:55:23.256829 1 docker.go:1033] Waiting for container "a978eaafd74681538dd51168b1832a5cc914386301483635c23c06472d4b3c1c" to stop ... *Gary Franczyk* Senior Unix Administrator, Infrastructure Availity | 10752 Deerwood Park Blvd S. Ste 110, Jacksonville FL 32256 W 904.470.4953 | M 561.313.2866 *[email protected] <[email protected]>* *From: *Ben Parees <[email protected]> *Date: *Friday, July 14, 2017 at 3:56 PM *To: *Gary Franczyk <[email protected]> *Cc: *"[email protected]" <[email protected]> *Subject: *Re: [EXTERNAL] Re: Build from github doesn't start 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:a225ccca591aeb338e4d628973d1db273c61dff44df628755ffbeebeeefb0082 <https://urldefense.proofpoint.com/v2/url?u=http-3A__registry.access.redhat.com_rhscl_nodejs-2D4-2Drhel7-40sha256-3Aa225ccca591aeb338e4d628973d1db273c61dff44df628755ffbeebeeefb0082&d=DwMFaQ&c=OICO5LaDH-Xi2CSZAJgmTQ&r=DWo_ijwFGqBf00dIEKrMRiq5JjUOT-29YI7Con8CGIc&m=RSKKJW05V2U5BgFKwlf39Kpa4Y8KYgbrD2hItZMSYuA&s=EVMPpJNxCOCzY4zM4BuEvZGwExaLFH694qaLNadzhEU&e=> "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 <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_sclorg_s2i-2Dnodejs-2Dcontainer_blob_master_6_s2i_bin_assemble-23L25-2DL43&d=DwMFaQ&c=OICO5LaDH-Xi2CSZAJgmTQ&r=DWo_ijwFGqBf00dIEKrMRiq5JjUOT-29YI7Con8CGIc&m=RSKKJW05V2U5BgFKwlf39Kpa4Y8KYgbrD2hItZMSYuA&s=KqNHL6avAakvexT0GK_KgWWsq-dXJxGdaXB5HS5Ex8s&e=> 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
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
