[rtmpdump] Connection dropping out

[Howard Chu]

Stef wrote:
> Hi.
> 
> A user in our forum (whirlpool.net.au) is having an issue with a 
> particular file that just refuses to download completely.  This is from 
> an Akamai server.  Sometimes it eventually downloads if you continue to 
> resume (5+ times) according to other users.  But other times it just 
> doesn't resume at all - mostly ending with the same "ERROR: 
> RTMP_ReadPacket, failed to read RTMP packet header" message.  This is 
> happening on the metered-quota server (Akamai).  On the unmetered-quota 
> server there are no issues at all (Hostworks).
> 
> You can find the full debug log here:
> 
> http://www.4shared.com/file/190322876/22bd2477/dumpdb.html
> 
> It is ~8MB compressed and expands to ~20MB.

Sorry, looks like a server problem. Aside from the fact that the client keeps
retrying instead of quitting after the first retry fails (which I would
consider a bug, but it was actually helpful here) the only problem is that the
server simply decided to quit talking to you.

Toward the end of the log you see this:

^MDEBUG: Invoking pause
Resuming download at: 3838.412 kB
^MINFO: RTMP_ReadPacket: fd=1760
  0000:  45 00 02 dc 00 00 00 08                            E.......
^MINFO: RTMP_ReadPacket: fd=1760
  0000:  45 00 00 00 00 00 66 12                            E.....f.
  0000:  02 00 0c 6f 6e 50 6c 61  79 53 74 61 74 75 73 03   ...onPlayStatus.
  0010:  00 04 63 6f 64 65 02 00  17 4e 65 74 53 74 72 65   ..code...NetStre
  0020:  61 6d 2e 50 6c 61 79 2e  43 6f 6d 70 6c 65 74 65   am.Play.Complete
  0030:  00 05 6c 65 76 65 6c 02  00 06 73 74 61 74 75 73   ..level...status
  0040:  00 08 64 75 72 61 74 69  6f 6e 00 40 a8 0e 00 00   ..duration. at ....
  0050:  00 00 00 00 05 62 79 74  65 73 00 41 4d fd b7 00   .....bytes.AM...
  0060:  00 00 00 00 00 09                                  ......
^MDEBUG: RTMP_ClientPacket, received: notify 102 bytes
^MDEBUG: (object begin)
^MDEBUG: Property: <Name:                  no-name., STRING:    onPlayStatus>
^MDEBUG: Property: <Name:                  no-name., OBJECT>
^MDEBUG: (object begin)
^MDEBUG: Property: <Name:                      code, STRING:
NetStream.Play.Complete>
^MDEBUG: Property: <Name:                     level, STRING:    status>
^MDEBUG: Property: <Name:                  duration, NUMBER:    3079.00>
^MDEBUG: Property: <Name:                     bytes, NUMBER:    3930990.00>
MDEBUG: (object end)
^MDEBUG: (object end)
^MINFO: RTMP_ReadPacket: fd=1760
  0000:  02 00 00 00 00 00 06 04  00 00 00 00               ............
  0000:  00 01 00 00 00 01                                  ......
^MDEBUG: HandleCtrl, received ctrl. type: 1, len: 6
^MDEBUG: HandleCtrl, Stream EOF 1

The client has received 3838.412KB of data, or ~3930534 bytes. And the server
reports that it has sent 3930990 bytes and isn't going to send any more, it
thinks that the stream is Complete already and has sent an EOF marker to
indicate that there's nothing left to send.

As far as I can see, there are no bugs in our side of this log, just an
uncooperative/buggy server.