transfer was staying in timout

transfer was staying in timout

Post by Hans Voc » Sat, 25 Mar 2000 04:00:00

At 7.3.00 16h32 the file, coming from svzvxx, W0IMG2xxx was send to
svudine and given to Asid, but this transfer C80897a4a391720xxxx7163 was
not delivred by Asid.
transfer was staying  in timout, after Tranfer Done. We have never seen
the Delivery Start msg. I have look on local asilog on svudine, Coord
has became the file, but service 1032 was not started, and file was
staying in spool, but with no maps. Asistop et start has brought
(The file was resend the next day, because file described above define
any   Nacht  ZVOUTPUT distributions on svudine and the distribution was

I think Asid has managed the file not correctly.

Whats the Problem ?



1. Causes for "0" bytes transferred in the transfer log

I have had a couple of occurances in my transfer log (access_log) where the
"bytes transferred field is 0.  I was wondering what the possible causes of
this may be and how to avoid this from occurring.  Obviously, when the data
that was supposed to be transferred was the input for a cgi, there are big

Any help would greatly appreciated..........

2. Netscape and Java

3. This clone I stupid, or am I right?

4. setting the priority in threads (solaris 2

5. help: mix parity /w non parity RAM?

6. I am with the following error, when i am running lilo...

7. ppp problem

8. Am I touchy? Or am I right?

9. Am I seeing IPv5, or am I hallucinating?

10. I am buying an Ultra 5 but am lost in part numbers ....

11. I am in text mode, what browser am I running....

12. I am si**y am I?