Sun Dec 25 11:28:23 EST 2016: port AGWPE[CALLSIGN] failed
Sun Dec 25 11:28:23 EST 2016: try#0: connection to localhost:0 lost: inactive too long
Sun Dec 25 11:28:23 EST 2016: port AGWPE[Callsign] failed
how do i stop this from happening. its frigging up my day
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is unusual. YAAC expects to hear from the AGWPE server at least every 60 seconds; if no APRS traffic is incoming for 30 seconds, YAAC sends a request to AGWPE for its current version number just to make the AGWPE server respond and prove the YAAC<->AGWPE server connection is still working.
So, the only reasons this error could happen is:
1. your AGWPE server has crashed or the network link has failed (note the latter can happen even with a local AGWPE server if you don't use the localhost (127.0.0.1) IP address and your computer's IP address is changed by DHCP or failover between wireless and wired or different wireless networks).
2. your AGWPE compatible software isn't fully compatible and doesn't respond to the version query message as defined in the AGWPE client protocol specification (so the pinging during low-traffic times isn't working).
Which program and version are you using? (AGWPE, DireWolf, soundmodem)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmmm... have you gotten any errors in the YAAC error log? I just re-read the AGWPE specification, and YAAC was assuming that certain pad fields were always zero. If AGWPE was sending random memory instead of zeros in those fields, it could have caused YAAC to malfunction. However, such malfunctions would have been logged with a "unrecognized AGWPE frame datakind='char'" error message.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2019-10-18
I'm seeing this now with Direwolf 1.5 and YACC 1.0beta142
it worked yesteray but now I can't transmit my postion and see the direwolf error each time.
Receive works fine.
Error getting message header from AGW client application 0.
Tried to read 36 bytes but got only 0.
Closing connection.
and a Socket Closed message from YACC unhandled exception
receiveAGWPEFrame. AGWPEConnector.java 804)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Sun Dec 25 11:28:23 EST 2016: port AGWPE[CALLSIGN] failed
Sun Dec 25 11:28:23 EST 2016: try#0: connection to localhost:0 lost: inactive too long
Sun Dec 25 11:28:23 EST 2016: port AGWPE[Callsign] failed
how do i stop this from happening. its frigging up my day
This is unusual. YAAC expects to hear from the AGWPE server at least every 60 seconds; if no APRS traffic is incoming for 30 seconds, YAAC sends a request to AGWPE for its current version number just to make the AGWPE server respond and prove the YAAC<->AGWPE server connection is still working.
So, the only reasons this error could happen is:
1. your AGWPE server has crashed or the network link has failed (note the latter can happen even with a local AGWPE server if you don't use the localhost (127.0.0.1) IP address and your computer's IP address is changed by DHCP or failover between wireless and wired or different wireless networks).
2. your AGWPE compatible software isn't fully compatible and doesn't respond to the version query message as defined in the AGWPE client protocol specification (so the pinging during low-traffic times isn't working).
Which program and version are you using? (AGWPE, DireWolf, soundmodem)
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
direwolf
I am using Direwolf.
this is the direwolf error
Error getting message header from AGW client application 0.
Tried to read 36 bytes but got only 0.
Closing connection.
it has timed out using the UZ7HO Soundmodem also
I have had that happen a lot in the past, so I just use the KISS port.
Hmmm... have you gotten any errors in the YAAC error log? I just re-read the AGWPE specification, and YAAC was assuming that certain pad fields were always zero. If AGWPE was sending random memory instead of zeros in those fields, it could have caused YAAC to malfunction. However, such malfunctions would have been logged with a "unrecognized AGWPE frame datakind='char'" error message.
I'm seeing this now with Direwolf 1.5 and YACC 1.0beta142
it worked yesteray but now I can't transmit my postion and see the direwolf error each time.
Receive works fine.
Error getting message header from AGW client application 0.
Tried to read 36 bytes but got only 0.
Closing connection.
and a Socket Closed message from YACC unhandled exception
receiveAGWPEFrame. AGWPEConnector.java 804)