Bugzilla – Full Text Bug Listing
| Summary: | Signing process appears hung? Or, incomplete? | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | David Williams <david_williams> | ||||
| Component: | Servers | Assignee: | Eclipse Webmaster <webmaster> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 190950 [details]
files as exist in incomplete signing
In case it gives any insight, here's the full list of files "left" in the signing directory.
FWIW, I did browse around /opt/public/download-staging.priv/arch/signer.log I didn't see any errors in there. Seemed as though 'temp-I-3.3.0-20110310182754-jst-sdk.zip' was being worked on, along with many other heavy hitters, like platform, birt, others ... but then, appeared as if processing of 'temp-I-3.3.0-20110310182754-jst-sdk.zip' just ended. Prematurely, but no error msgs, that I could see. Is there any "timeout" enforced in the signing process? Such as, if a particular request isn't done in 2 hours, its killed? Or anything similar? Five jarsigner calls did not complete, and I don't know why. Either the call to the external TSA failed, or something else happened. jarsigner seems to have gotten stuck but didn't timeout or fail. I was able to sign a jar file successfully. Let's chalk it up as a glitch. I cleared the dangling processes. (In reply to comment #3) > Five jarsigner calls did not complete, and I don't know why. Either the call > to the external TSA failed, or something else happened. > > jarsigner seems to have gotten stuck but didn't timeout or fail. > > I was able to sign a jar file successfully. Let's chalk it up as a glitch. I > cleared the dangling processes. Thanks for taking a look. I agree, glitch. No big deal if happens rarely. I did mean to say the next build I tried ran just fine, faster than usual even. Thanks again. I saw this, or some similar hang today. It was the zip in this directory of webtools signing directory: drwxrwsr-x+ 2 david_williams webtoolsadmin 1K 2011-05-19 10:09 temp-I-3.3.0-20110519123016-wst4x.tests.zip/ in case that time frame helps. File went in about 10, by around 3 or 4, still had not been signed, so I just killed that build. Next signing attempt it worked fine. Just wanted to make a note, to help keep track of how often this happens ... or, in case you need to check if there's any dangling jarsigner processes to kill? |
While waiting several hours longer than usual for a build to complete, I investigated and found that our script that "copies and wait for signing to complete" was still "waiting". I looked looking at the signing directory and it appears odd. It appears there are still "genie" owned files on file system, normally created during signing, but seems there is no signing taking place. The "signing log" shows no activity. I'll likely kill this build in a few minutes, and start over, but thought I'd report the anomaly. At least, an anomaly in my experience. I think our script that "copies and wait for signing to complete" waits for the (new) zip to exist again, by itself, to know that signing is done, and ready to copy back to build area to continue the build. [20:41:45] david_williams@build:/opt/public/download-staging.priv/webtools $ ll ./temp-I-3.3.0-20110310182754-jst-sdk.zip/ total 62409K -rw-rw-rw-+ 1 david_williams webtoolsadmin 61731K 2011-03-10 17:12 temp-I-3.3.0-20110310182754-jst-sdk.zip -rw-rw-r--+ 1 genie webtoolsadmin 613K 2011-03-10 17:41 temp-I-3.3.0-20110310182754-jst-sdk.zip.temp drwxrwsr-x+ 4 genie webtoolsadmin 1K 2011-03-10 17:41 temp_temp-I-3.3.0-20110310182754-jst-sdk.zip/