wget agent fails on file
|Assignee:||larry shi||% Done:||
using svn 5571 on the snape cluster the file Fedora-16-source-DVD.iso was uploaded from url (from snape), the wget_agent failed the log message says:
It would be really great if the error had some sort of description other than just a number. Why did wget_agent fail on this file?
Updated by Mark Donohoe about 1 year ago
I just duplicated this defect on a single system (randos64.ostt) using svn 5571, wget_agent still failed but with a different error/message:
2012-03-06 18:15:35 scheduler  :: JOB14.wget_agent[27381.localhost]: received: "FATAL wget_agent.c.371: upload 3 Download failed; Return code 3 from: /usr/bin/wget -q --no-check-certificate --progress=dot -rc -np -e robots=off -k -P '/srv/fossology/repository/randos64/wget/wget.27381.dir' 'http://snape.ostt/Fedora/Fedora16/Fedora-16-source-DVD.iso' -l 1 -R index.html* 2>&1"
2012-03-06 18:15:36 scheduler  :: JOB14.wget_agent[27381.localhost]: received: "HEART: 1 0"
2012-03-06 18:15:36 scheduler  :: JOB14.wget_agent[27381.localhost]: received: "BYE 12"
2012-03-06 18:15:36 scheduler  :: JOB14.wget_agent[27381.localhost]: agent failed with error code 12
running the command wget 'http://snape.ostt/Fedora/Fedora16/Fedora-16-source-DVD.iso' -l 1 -R index.html* as markd on randos64.ostt works just fine.
Updated by larry shi about 1 year ago
- Status changed from New to Feedback
we download this iso, then put it on one http server in beijing, then upload from url on the cluster in beijing,can not reproduce the error on the cluster in beijing.
when I go to snape.ostt cluster, I can not start the schuduler.
if the schuduler worked, I want to try again. can you look into why the scheduler can not work? thanks
on randos64.ostt, it seems that the failed reason is have no disk space, this iso file is 5.9G.
Updated by Bob Gobeille about 1 year ago
- Status changed from Feedback to New
- Target version changed from 2.0.0 to 2.1.0
The issue is to make the error more descriptive. The specific test case is not the issue.
Updated by Bob Gobeille 8 months ago
- Rank set to 99
Change unranked issues to rank 99 so they show up in a ranking report at the bottom. Otherwise, they show up on top.