cambler@polyslo.CalPoly.EDU (Fubar) (01/02/90)
Here's yet another debug script from hell. I'm really making progress
with all the help you netlanders are providing, those people who will
use this all thank you. I thank you. My dog thanks you. woof.
as always, comments in /* */ are mine.
--- cut here ---
g protocol startup
: OP_OPEN
SENDING PACKET: xxx = 7 yyy = 1 size = 0
k = 9 tt = 0 ctrl = 57 sum = aa71
DATA...
PACKET IN: tt = 0, xxx = 7, yyy = 7, need = 6
reporting TT_CTRL
X_INITA: swindow: 7
: OP_OPEN
SENDING PACKET: xxx = 6 yyy = 1 size = 0
k = 9 tt = 0 ctrl = 49 sum = aa79
DATA...
calling grpack
PACKET IN: tt = 0, xxx = 6, yyy = 1, need = 6
reporting TT_CTRL
X_INITB: spktsize: 64
: OP_OPEN
SENDING PACKET: xxx = 5 yyy = 1 size = 0
k = 9 tt = 0 ctrl = 41 sum = aa81
DATA...
PACKET IN: tt = 0, xxx = 5, yyy = 7, need = 6
reporting TT_CTRL
X_INITC: swindow: 7
startup: open complete
/* open goes nicely... */
scanning for work for system [polyslo]
scanning for work with path [polyslo/*.C]
scanning for work with path [polyslo/*.C]
g_put_s: type = [H] str = []
/* there is no work. Let's send an "H" */
g_put_s: calling sendpkt. thislen = 1
sendpkt entry.
: Sending long data packet 1 (next)
SENDING PACKET: xxx = 1 yyy = 0 size = 64
k = 2 tt = 2 ctrl = 136 sum = 8afb
DATA...
H
/* There goes the "H" */
g_get_s entry
g_get_s top data loop 1
PACKET IN: tt = 0, xxx = 4, yyy = 0, need = 6
g_get_s top data loop 2
PACKET IN: tt = 0, xxx = 4, yyy = 1, need = 6
g_get_s top data loop 3
/* This is where I start to get confused. Here comes an RR0 and RR1.
The RR1 is from my "H". Where did the RR0 come from? The machine likes to
send them at the WEIRDEST times for no apparent reason. Question one: IS
THERE SOMETHING I SHOULD KNOW HERE?
*/
PACKET IN: tt = 2, xxx = 1, yyy = 1, need = 70
PACKET IN: [4 #HN]
g_get_s: got [HN]
/* control characters removed. Here I get their xxx=1 packet, with an "HN"
in it. they have work for me (i know, i sent it :-))
From here, I am sitting and waiting for their "S" message. Now, you're
probably wondering, why I didn't ACK their packet one. Well, I do in
another try, and i STILL get the same thing. They just keep sending me
the HN.
*/
g_get_s entry
g_get_s top data loop 1
PACKET IN: tt = 2, xxx = 1, yyy = 1, need = 70
PACKET IN: [4 #HN]
g_get_s: got [HN]
g_get_s entry
g_get_s top data loop 1
PACKET IN: tt = 2, xxx = 1, yyy = 1, need = 70
PACKET IN: [4 #HN]
g_get_s: got [HN]
g_get_s entry
g_get_s top data loop 1
PACKET IN: tt = 2, xxx = 1, yyy = 1, need = 70
PACKET IN: [4 #HN]
g_get_s: got [HN]
g_get_s entry
g_get_s top data loop 1
/* NOW... Here is what it looks like at the OTHER END, the machine that
I am CALLING...
*/
ufubar polyslo (12/31-20:42-13691) DEBUG (Local Enabled)
imsg sync<\020>got it
imsg input<Sfubarsys\000>got 9
Using \0 as End of message char
omsg <\020ROK\000>
Rmtname fubarsys, Role SLAVE, Ifn - 0, Loginuser - ufubar
wmesg 'P' tfxg
omsg <\020Ptfxg\000>
rmesg - 'U' imsg sync<\020>got it
imsg input<Ug\000>got 2
got Ug
send 077
rec h->cntl 071
send 061
state - 01
rec h->cntl 061
send 057
state - 03
rec h->cntl 051
state - 010
Proto started g
/* everyone's happy... */
Protocol Ug
ufubar fubarsys (12/31-20:43-13691) OK (startup ttyi48 9600 bps)
*** TOP *** - role=SLAVE
rmesg - '' pkcget: alarm 4001
/* This ALWAYS happens. They NEVER see my message right away! So they
send that damned RR0. WHAT IS the lalrm line? What is SYN?
*/
Alarm while reading SYN - RXMIT
send 040
rec h->cntl 0210
end pksack 00
PKCGET stall for 0.060400 sec
PKCGET stall for 0.035400 sec
send 041
got H
PROCESS: msg - H
HUP:
/* they got my "H" and decide on a file to send me... */
bldflst rejects .
bldflst rejects ..
bldflst returns 1
wmesg 'H' N
send 0211
/* there goes the "HN" as packet 1 */
*** TOP *** - role=MASTER
bldflst rejects .
bldflst rejects ..
bldflst accepts C.fubarsyAZC74 as Filent[0]
bldflst accepts C.fubarsyAZG54 as Filent[1]
/* other tries removed... */
bldflst accepts C.fubarsyAZFv4 as Filent[1]
bldflst returns 1
root fubarsys (12/31-20:43-13691) REQUEST (S D.polysloBZC72 D.polysloSZC72 root)
expfile type - 0, wrktype - S
wmesg 'S' D.polysloBZC72 D.polysloSZC72 root - D.polysloBZC72 0666
/* now, you can see that they send me the S command, but I never saw it.
My guess is that they never actually TRANSMITTED it, but were waiting for
something that they don't get here, as in the alarm 4001, so they keep
sending the "HN" until they do get it, at which time they WOULD send the
S command. WHAT ARE THEY WAITING FOR? and RR? I DUNNO!!!
*/
pkcget: alarm 4001
Alarm while reading SYN - RXMIT
send 0211
pkcget: alarm 6002
Alarm while reading SYN - RXMIT
send 0211
pkcget: alarm 8003
Alarm while reading SYN - RXMIT
send 0211
pkcget: alarm 10004
Alarm while reading SYN - RXMIT
send 0211
root fubarsys (12/31-20:43-13691) CAUGHT (SIGNAL 1)
root fubarsys (12/31-20:43-13691) FAILED (conversation complete 0 sent 0 received)
exit code 1
/* so the send the "HN" a few times until i hung up. */
--- cut here ---
Help? :-)
--
Sig: ++Christopher(); | Fubar Systems BBS
Internet: cambler@polyslo.calpoly.edu | (805) 544-9234 3/12/24 8-N-1
Also: chris@fubarsys.slo.ca.us | San Luis Obispo, California
Bix: cambler | "G Protocol Sucks" -- Me.