Blooooomin IOSTAT Errors...

[meep]

Right, ive had it with these errors now.

Just been collecting up the last 5 days FAD jobs, and have had loads of IOSTAT=107 errors.

Now, I have had one of these once before, where the job was in the live think servers queue, shown as exported, but it would not let me import it for upload. FAD forums etc could not come up with a definitive answer. Re-exporting, using dif media etc etc did not work - so as it was just 1 job I wrote it off.

But, I have just collected up about 70 jobs (ish) maybe a few more, and about 10 of them have errored (IOSTAT=107). Due to exporting/importing the completed jobs in groups I had to go back to each individual farm and export them individually so that I could collect the ones that were duff (lovely task).

Question is, does anyone know of a way that I can get these jobs uploaded, via my live queue or otherwise? So that I can collect the points due for this batch of work. Half the jobs are 200 hitters and are about a weeks work on p4's so I do not want what is probably 150k to go to waste...

Cheers, ta.

[Fozzie]

is your Net connected client ticked for Beta test.

If so you may have a problem.

I would suggest backing up your find-a-drug directory and then reinstalling 1.25G over the top of the beta'd install.

If this is not the case then I don't know matey.

[meep]

nah its not beta.... checked that after seeing a post the other day.

its a pain in the you know what.

I have emailed FAD support with the history/error/jobs - see if they can check them out and perhaps shed any light on it. I have also asked if they can manually import them from their side, if that is at all possible.

Any other ideas are welcome...

[Vester]

THINK posted (http://www.find-a-drug.org.uk/forums/viewtopic.php?p=122250) at Find-a-Drug:
Quote:
[WIMPORT] (10036) Cannot open results file (IOSTAT = 107) r65.smi


Sorry, I should have jumped in on this earlier. IOSTAT=107 means that the file r65.smi already exists. This should not be the case unless you also attempted to run the job elsewhere and imported it ... looks very odd.

[meep]

Cheers Vester - I did see this, however I do not think that is the reason for these failures.

I believe it is impossible for the jobs to be duplicated.

Jobs is downloaded onto live server.
Job is exported onto offline server and gets marked exported.
Job runs and completes.
Job gets exported from offline server and imported onto live server.
Job gets uploaded then removed from queue.

As this process is the same each time, if i did export the same job onto 2 offline servers, the first one to complete it, would mean the job would be removed from the online servers queue. This is not the case as the job is sitting there marked as exported...

Odd.

[Vester]

Some people have deleted exported jobs from the THINK Server (Queue) list to "keep it neat". Bad. If a job is not in the queue, then the results for that job cannot be imported. If a job should be run on two different sneakernetted computers, the results can only be imported and returned once. If it could be done, the stats server would only count the results once. The online computer's installation cannot be moved from one computer to another or duplicated. The exported job has an "marker" identifying it with the computer which exported it. Error number 107 is very specific.Should you continue to have IOSTAT errors, post in Member to Member Support at FaD. THINK wrote the most of the program and has worked with it for over 20 years. He will see your post at FaD. (I was just passing through, myself.)

[meep]

Have posted in the FAD Forum again, following on from my previous post. Hopefully a way round this problem...

[Fozzie]

Gonna have to start using a different machine as my Net machine as I have to give this laptop back soon.

I was just going to transfer the installation.

[meep]

Yes i thought that, but, renaming a suitable replacement to match your laptop will do just nicely.

Standalone workstation on the net would do.

[meep]

Well, I had an email back from FAD suggesting deleting the smi files within the FAD dir, this did then allow me to import the jobs then upload them. I tried this before for the 1 random failure I had previously but it made no difference, this time it did.

Time will tell whether the results show up at the next update.