Subj : Error:  "tty_write: hanged_up flag"
To   : Rj Clay
From : Vince Coen
Date : Tue Sep 27 2016 17:19:02

Hello Rj!

Monday September 26 2016 12:27, you wrote to All:

 > All,

 > Has anyone seen an error like that come up before? I'm now running
 > v1.0.6.8 for my 1:120/544 hub node and that error is coming up for
 > when just one of my downlinks attempts to connect:

 > + 26-Sep-2016 00:14:54 mbcico[24206] Binkp: send
 > "/opt/mbse/var/bso/outbound/0000ffa0.tu3" as "0000ffa0.tu3"
 > + 26-Sep-2016 00:14:54 mbcico[24206] Binkp: size 210469 bytes, dated
 > Sep 20
 > 23:34:29, comp No
 > ? 26-Sep-2016 00:14:54 mbcico[24206] tty_write: hanged_up flag
 > + 26-Sep-2016 00:14:54 mbcico[24206] Binkp: transmitter failure
 > + 26-Sep-2016 00:14:54 mbcico[24206] Binkp: session finished, rc=108
 > + 26-Sep-2016 00:14:56 mbcico[24206] Incoming call failed (rc=108)
 > + 26-Sep-2016 00:14:56 mbcico[24206] Terminated with error 108


 > The '0000ffa0.tu3' file itself does not appear to have any permissions
 > issues. That '108' error appears to be a "File Transfer Error"...

 > The other system uses this (which I'm not familiar with...):
 > BinkIT/1.39,JSBinkP/1.54/Win32 binkp/1.1


 > Also;  depending on the intent of that error message, it may actually
 > be mis-spelled...


If it is a system defined in your set up try marking it as BINKD v1.0 and see
what happens.





Vince

--- Mageia Linux v5/Mbse v1.0.6/GoldED+/LNX 1.1.501-b20150715
 * Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)

.