Anybody Else - Unrecognized message type 'login' ??

Hello,

As I type (2041Z), my stats page says “Last Seen: Today - about 2 hours ago” and there is an accompanying anomaly report stating that “ADS-B positions were last received from this feeder a while ago”. However, piaware.out indicates that messages are currently being sent to FA:



11/14/2014 19:41:58 554795 msgs recv'd from dump1090 via faup1090 (3111 in last 5m); 555011 msgs sent to FlightAware
11/14/2014 19:46:58 557734 msgs recv'd from dump1090 via faup1090 (2939 in last 5m); 557951 msgs sent to FlightAware
11/14/2014 19:51:58 560352 msgs recv'd from dump1090 via faup1090 (2618 in last 5m); 560570 msgs sent to FlightAware
11/14/2014 19:56:58 563069 msgs recv'd from dump1090 via faup1090 (2717 in last 5m); 563288 msgs sent to FlightAware
11/14/2014 20:01:58 566046 msgs recv'd from dump1090 via faup1090 (2977 in last 5m); 566266 msgs sent to FlightAware
11/14/2014 20:06:58 569032 msgs recv'd from dump1090 via faup1090 (2986 in last 5m); 569253 msgs sent to FlightAware
11/14/2014 20:11:58 572065 msgs recv'd from dump1090 via faup1090 (3033 in last 5m); 572287 msgs sent to FlightAware
11/14/2014 20:16:58 575081 msgs recv'd from dump1090 via faup1090 (3016 in last 5m); 575304 msgs sent to FlightAware
11/14/2014 20:21:58 578145 msgs recv'd from dump1090 via faup1090 (3064 in last 5m); 578369 msgs sent to FlightAware
11/14/2014 20:26:58 581127 msgs recv'd from dump1090 via faup1090 (2982 in last 5m); 581352 msgs sent to FlightAware
11/14/2014 20:31:58 584170 msgs recv'd from dump1090 via faup1090 (3043 in last 5m); 584396 msgs sent to FlightAware
11/14/2014 20:36:58 587028 msgs recv'd from dump1090 via faup1090 (2858 in last 5m); 587255 msgs sent to FlightAware


Is this cause for concern?

Mine got updated just a few minutes ago. Looks like they are still working with the move to the new infrastructure. Things like this will happen until it is completely done.

So based off the wiki recommendations I did some upgrades… and now I’m here:

11/14/2014 22:18:43 ****************************************************
11/14/2014 22:18:43 piaware version 1.16 is running, process ID 2351
11/14/2014 22:18:43 your system info is: Linux piaware 3.12.32+ #721 PREEMPT Fri
Nov 7 16:50:31 GMT 2014 armv6l GNU/Linux
11/14/2014 22:18:43 ADS-B data program ‘dump1090’ is listening on port 30005, so
far so good
11/14/2014 22:18:43 i see dump1090 serving on port 10001
11/14/2014 22:18:43 connecting to dump1090 on port 10001…
11/14/2014 22:18:43 piaware is connected to dump1090 on port 10001
11/14/2014 22:18:43 dump1090 is listening for connections on FA-style port 10001
11/14/2014 22:18:44 piaware received a message from the ADS-B source!
11/14/2014 22:18:44 logged in to FlightAware as user jimcander
11/14/2014 22:18:44 unrecognized message type ‘login’ from server, ignoring…
11/14/2014 22:18:44 unrecognized message type ‘log’ from server, ignoring…
11/14/2014 22:18:44 unrecognized message type ‘log’ from server, ignoring…
11/14/2014 22:18:44 unrecognized message type ‘log’ from server, ignoring…
11/14/2014 22:18:44 unrecognized message type ‘log’ from server, ignoring…
11/14/2014 22:18:44 unrecognized message type ‘log’ from server, ignoring…
11/14/2014 22:18:44 unrecognized message type ‘log’ from server, ignoring…
11/14/2014 22:18:44 error handling message ‘_c 1416003541 _s 0002 airGround
tA alt 35000 clock 1416003522 facility fAT-b827ebdd1c05 hexid A0F4F6 ip
108.44.36.24 mac b8:27:eb:dd:1c:05 user jimcander’ from server (can’t read
“row(type)”: no such element in array), (can’t read “row(type)”: no such elemen
t in array
while executing
"switch $row(type) {
“login_response” {
n handle_login_response_message row
}

		"notice" {
		\

thandle_notice_message row
}

		"alive" {
..."
(object "::a

dept" method “::fa_adept::AdeptClient::handle_response” body line 4)
invoke
d from within
“handle_response response”), continuing…
11/14/2014 22:18:44 unrecognized message type ‘log’ from server, ignoring…
11/14/2014 22:18:44 unrecognized message type ‘log’ from server, ignoring…
11/14/2014 22:18:44 unrecognized message type ‘log’ from server, ignoring…
11/14/2014 22:18:44 unrecognized message type ‘log’ from server, ignoring…

Comments?

I am using piaware_1.15-1. For about the last 2 hours I have not been able to feed to FA. I am still feeding OK to FR24, PP and VRS-world.

Every time I try to start piaware, this is what I am seeing:

11/14/2014 22:38:33 error handling message ‘_c 1416004712 _s 0003 airGround A alt 2700 clock 1416004713 facility fAT-b827ebf01b32 heading 315 hexid 7C4270 ident NEQ ip 124.187.32.3 lat-27.54671 lon 152.95171 mac b8:27:eb:f0:1b:32 speed 149 squawk 4407 user Lyndale’ from server (can’t read “row(type)”: no such element in array), continuing…

Is this the same problem?

Thank you,

Maybe you broke it, maybe not. Checked mine, and it was working fine.
Rebooted to restart piaware to check. Piaware.out shows AFU notices. I think will will have something soon.

Anybody else getting this, please?

cat piaware.out

11/15/2014 00:26:12 ****************************************************
11/15/2014 00:26:12 piaware version 1.15 is running, process ID 3032
11/15/2014 00:26:12 your system info is: Linux RpiBplus 3.12.29+ #714 PREEMPT Wed Oct 1 23:11:38 BST 2014 armv6l GNU/Linux
11/15/2014 00:26:13 connecting to FlightAware eyes.flightaware.com/1200
11/15/2014 00:26:15 FlightAware server SSL certificate validated
11/15/2014 00:26:15 encrypted session established with FlightAware
11/15/2014 00:26:16 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
11/15/2014 00:26:16 i see nothing serving on port 10001, starting faup1090…
11/15/2014 00:26:16 started faup1090 (process ID 3046)
11/15/2014 00:26:19 connecting to faup1090 on port 10001…
11/15/2014 00:26:19 piaware is connected to faup1090 on port 10001
11/15/2014 00:26:19 logged in to FlightAware as user Lyndale
11/15/2014 00:26:19 unrecognized message type ‘login’ from server, ignoring… ****************<<<<<<<<<<
11/15/2014 00:26:20 piaware received a message from the ADS-B source!
11/15/2014 00:26:20 piaware has successfully sent several msgs to FlightAware!
11/15/2014 00:26:20 error handling message ‘_c 1416011179 _s 0000 airGround A alt 24925 clock 1416011178 facility fAT-b827ebf01b32 hexid 7C6C52 ip 124.187.32.3 mac b8:27:eb:f0:1b:32 user Lyndale’ from server (can’t read “row(type)”: no such element in array), continuing…

Just rebooted my RPi, now receiving the same type of messages that are quickly filling the piaware.out file. Also running 1.16-1, which I have stopped until this is resolved. Presumably similar server issues that occurred last Tuesday.

I noticed that /tmp/piaware.out is growing quite rapidly. Even with a 16 GB card, space will run out unless /tmp has quota set.
I executed “sudo piaware-config -stop” to shut down piaware. Dump1090 continues to upload to Planeplotter.

Yes, check
ads-b-flight-tracking-f21/i-broke-it-t19473.html

I’m in the same state. dump1090 is up feeding fr24. piaware is down.

Thanks guys we are looking into it now.

And thanks for merging the threads.

Here’s to the joys of new releases!!!

yes the same over here
login as: pi
pi@192.168.1.8’s password:
Linux piaware 3.12.30+ #717 PREEMPT Fri Oct 17 18:46:31 BST 2014 armv6l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Nov 15 08:47:04 2014 from 192.168.1.2
pi@piaware ~ $ cd /tmp
pi@piaware /tmp $ ls
piaware.out
pi@piaware /tmp $ ls -l
total 16
-rw-r–r-- 1 root root 13451 Nov 15 09:38 piaware.out
pi@piaware /tmp $ cat piaware.out
11/15/2014 09:36:17 ****************************************************
11/15/2014 09:36:17 piaware version 1.15 is running, process ID 2125
11/15/2014 09:36:17 your system info is: Linux piaware 3.12.30+ #717 PREEMPT Fri Oct 17 18:46:31 BST 2014 armv6l GNU/Linux
11/15/2014 09:36:18 connecting to FlightAware eyes.flightaware.com/1200
11/15/2014 09:36:19 FlightAware server SSL certificate validated
11/15/2014 09:36:19 encrypted session established with FlightAware
11/15/2014 09:36:19 ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
11/15/2014 09:36:19 i see dump1090 serving on port 10001
11/15/2014 09:36:19 connecting to dump1090 on port 10001…
11/15/2014 09:36:19 piaware is connected to dump1090 on port 10001
11/15/2014 09:36:20 dump1090 is listening for connections on FA-style port 10001
11/15/2014 09:36:20 piaware received a message from the ADS-B source!
11/15/2014 09:36:20 logged in to FlightAware as user jackoneill
11/15/2014 09:36:20 unrecognized message type ‘login’ from server, ignoring…
11/15/2014 09:36:20 error handling message ‘_c 1416044196 _s 0000 airGround A alt 38950 clock 1416044178 facility fAT-b827ebdf56e7 hexid 40093F ident BAW15PZ ip 62.235.167.61 lat 50.37003 lon 4.22996 mac b8:27:eb:df:56:e7 squawk 0355 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:36:37 error handling message ‘_c 1416044196 _s 0001 airGround A alt 38975 clock 1416044179 facility fAT-b827ebdf56e7 heading 106 hexid 3C6442 ident DLH3RJ ip 62.235.167.61 lat 50.83681 lon 4.27261 mac b8:27:eb:df:56:e7 speed 421 squawk 2001 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:36:37 error handling message ‘_c 1416044196 _s 0002 airGround A alt 33800 clock 1416044178 facility fAT-b827ebdf56e7 hexid 484C59 ip 62.235.167.61 lat 50.79743 lon 3.86452 mac b8:27:eb:df:56:e7 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:36:42 error handling message ‘_c 1416044201 _s 0000 airGround A alt 33850 clock 1416044202 facility fAT-b827ebdf56e7 heading 208 hexid 484C59 ip 62.235.167.61 lat 50.78893 lon 3.85761 mac b8:27:eb:df:56:e7 speed 407 squawk 2126 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:36:50 5 msgs recv’d from dump1090; 4 msgs sent to FlightAware
11/15/2014 09:36:52 piaware has successfully sent several msgs to FlightAware!
11/15/2014 09:36:52 error handling message ‘_c 1416044211 _s 0000 airGround A alt 36000 clock 1416044201 facility fAT-b827ebdf56e7 hexid C023AA ident ACA876 ip 62.235.167.61 mac b8:27:eb:df:56:e7 squawk 2014 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:36:52 error handling message ‘_c 1416044211 _s 0001 airGround A alt 38975 clock 1416044211 facility fAT-b827ebdf56e7 heading 106 hexid 3C6442 ident DLH3RJ ip 62.235.167.61 lat 50.82741 lon 4.32320 mac b8:27:eb:df:56:e7 speed 420 squawk 2001 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:36:52 error handling message ‘_c 1416044211 _s 0002 airGround A alt 33950 clock 1416044210 facility fAT-b827ebdf56e7 heading 207 hexid 484C59 ip 62.235.167.61 lat 50.78893 lon 3.85761 mac b8:27:eb:df:56:e7 speed 407 squawk 2126 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:37:02 error handling message ‘_c 1416044221 _s 0000 airGround A alt 36000 clock 1416044221 facility fAT-b827ebdf56e7 heading 106 hexid C023AA ident ACA876 ip 62.235.167.61 lat 50.85762 lon 3.94333 mac b8:27:eb:df:56:e7 speed 450 squawk 2014 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:37:02 error handling message ‘_c 1416044221 _s 0001 airGround A alt 38950 clock 1416044217 facility fAT-b827ebdf56e7 hexid 40093F ident BAW15PZ ip 62.235.167.61 lat 50.37003 lon 4.22996 mac b8:27:eb:df:56:e7 squawk 0355 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:37:02 error handling message ‘_c 1416044221 _s 0002 airGround A alt 34150 clock 1416044221 facility fAT-b827ebdf56e7 heading 207 hexid 484C59 ip 62.235.167.61 lat 50.78893 lon 3.85761 mac b8:27:eb:df:56:e7 speed 407 squawk 2126 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:37:12 error handling message ‘_c 1416044231 _s 0000 airGround A alt 34300 clock 1416044230 facility fAT-b827ebdf56e7 heading 207 hexid 484C59 ip 62.235.167.61 lat 50.78893 lon 3.85761 mac b8:27:eb:df:56:e7 speed 407 squawk 2126 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:37:22 error handling message ‘_c 1416044241 _s 0000 airGround A alt 38950 clock 1416044237 facility fAT-b827ebdf56e7 heading 106 hexid 3C6442 ident DLH3RJ ip 62.235.167.61 lat 50.81261 lon 4.40231 mac b8:27:eb:df:56:e7 speed 421 squawk 2001 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:37:22 error handling message ‘_c 1416044241 _s 0001 airGround A alt 34450 clock 1416044239 facility fAT-b827ebdf56e7 heading 207 hexid 484C59 ip 62.235.167.61 lat 50.78893 lon 3.85761 mac b8:27:eb:df:56:e7 speed 407 squawk 2126 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:37:27 error handling message ‘_c 1416044246 _s 0000 airGround A alt 33000 clock 1416044246 facility fAT-b827ebdf56e7 hexid 4008F2 ip 62.235.167.61 mac b8:27:eb:df:56:e7 squawk 7612 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:37:32 error handling message ‘_c 1416044251 _s 0000 airGround A alt 36000 clock 1416044251 facility fAT-b827ebdf56e7 heading 106 hexid C023AA ident ACA876 ip 62.235.167.61 lat 50.83960 lon 4.03970 mac b8:27:eb:df:56:e7 speed 450 squawk 2014 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:37:32 error handling message ‘_c 1416044251 _s 0001 airGround A alt 38975 clock 1416044251 facility fAT-b827ebdf56e7 heading 116 hexid 40093F ident BAW15PZ ip 62.235.167.61 lat 50.37003 lon 4.22996 mac b8:27:eb:df:56:e7 speed 419 squawk 0355 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:37:32 error handling message ‘_c 1416044251 _s 0002 airGround A alt 34675 clock 1416044251 facility fAT-b827ebdf56e7 heading 201 hexid 484C59 ip 62.235.167.61 lat 50.70039 lon 3.80394 mac b8:27:eb:df:56:e7 speed 403 squawk 2126 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:37:36 server is sending alive messages; we will expect them
11/15/2014 09:37:42 error handling message ‘_c 1416044261 _s 0000 airGround A alt 33000 clock 1416044262 facility fAT-b827ebdf56e7 heading 113 hexid 4008F2 ip 62.235.167.61 lat 50.55620 lon 3.76616 mac b8:27:eb:df:56:e7 speed 396 squawk 7612 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:37:42 error handling message ‘_c 1416044261 _s 0001 airGround A alt 34725 clock 1416044256 facility fAT-b827ebdf56e7 heading 201 hexid 484C59 ip 62.235.167.61 lat 50.69696 lon 3.80194 mac b8:27:eb:df:56:e7 speed 403 squawk 2126 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:37:52 error handling message ‘_c 1416044271 _s 0000 airGround A alt 38950 clock 1416044268 facility fAT-b827ebdf56e7 heading 106 hexid 3C6442 ident DLH3RJ ip 62.235.167.61 lat 50.81261 lon 4.40231 mac b8:27:eb:df:56:e7 speed 421 squawk 2001 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:37:52 error handling message ‘_c 1416044271 _s 0001 airGround A alt 34925 clock 1416044268 facility fAT-b827ebdf56e7 heading 201 hexid 484C59 ip 62.235.167.61 lat 50.67339 lon 3.78754 mac b8:27:eb:df:56:e7 speed 403 squawk 2126 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:38:02 error handling message ‘_c 1416044281 _s 0000 airGround A alt 36000 clock 1416044281 facility fAT-b827ebdf56e7 heading 106 hexid C023AA ident ACA876 ip 62.235.167.61 lat 50.83169 lon 4.08195 mac b8:27:eb:df:56:e7 speed 451 squawk 2014 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:38:02 error handling message ‘_c 1416044281 _s 0001 airGround A alt 38975 clock 1416044263 facility fAT-b827ebdf56e7 heading 116 hexid 40093F ident BAW15PZ ip 62.235.167.61 lat 50.37003 lon 4.22996 mac b8:27:eb:df:56:e7 speed 419 squawk 0355 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:38:02 error handling message ‘_c 1416044281 _s 0002 airGround A alt 35125 clock 1416044282 facility fAT-b827ebdf56e7 heading 201 hexid 484C59 ip 62.235.167.61 lat 50.64862 lon 3.77315 mac b8:27:eb:df:56:e7 speed 403 squawk 2126 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:38:12 error handling message ‘_c 1416044291 _s 0000 airGround A alt 33000 clock 1416044292 facility fAT-b827ebdf56e7 heading 113 hexid 4008F2 ip 62.235.167.61 lat 50.53413 lon 3.84449 mac b8:27:eb:df:56:e7 speed 396 squawk 7612 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:38:12 error handling message ‘_c 1416044291 _s 0001 airGround A alt 35250 clock 1416044292 facility fAT-b827ebdf56e7 heading 201 hexid 484C59 ident TRA5749 ip 62.235.167.61 lat 50.63627 lon 3.76594 mac b8:27:eb:df:56:e7 speed 403 squawk 2126 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:38:22 error handling message ‘_c 1416044301 _s 0000 airGround A alt 38950 clock 1416044275 facility fAT-b827ebdf56e7 heading 106 hexid 3C6442 ident DLH3RJ ip 62.235.167.61 lat 50.81261 lon 4.40231 mac b8:27:eb:df:56:e7 speed 421 squawk 2001 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:38:22 error handling message ‘_c 1416044301 _s 0001 airGround A alt 35350 clock 1416044301 facility fAT-b827ebdf56e7 heading 201 hexid 484C59 ident TRA5749 ip 62.235.167.61 lat 50.63627 lon 3.76594 mac b8:27:eb:df:56:e7 speed 403 squawk 2126 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:38:27 error handling message ‘_c 1416044306 _s 0000 airGround A alt 39025 clock 1416044304 facility fAT-b827ebdf56e7 hexid 3C6DCF ip 62.235.167.61 lat 50.54356 lon 3.67478 mac b8:27:eb:df:56:e7 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:38:32 error handling message ‘_c 1416044311 _s 0000 airGround A alt 36000 clock 1416044311 facility fAT-b827ebdf56e7 heading 106 hexid C023AA ident ACA876 ip 62.235.167.61 lat 50.80421 lon 4.22684 mac b8:27:eb:df:56:e7 speed 453 squawk 2014 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:38:37 error handling message ‘_c 1416044316 _s 0000 airGround A alt 39050 clock 1416044317 facility fAT-b827ebdf56e7 heading 114 hexid 3C6DCF ident GWI2463 ip 62.235.167.61 lat 50.53487 lon 3.70529 mac b8:27:eb:df:56:e7 speed 434 squawk 2072 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:38:42 error handling message ‘_c 1416044321 _s 0000 airGround A alt 33025 clock 1416044322 facility fAT-b827ebdf56e7 heading 113 hexid 4008F2 ident BAW416 ip 62.235.167.61 lat 50.51127 lon 3.92613 mac b8:27:eb:df:56:e7 speed 396 squawk 7612 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:38:42 error handling message ‘_c 1416044321 _s 0001 airGround A alt 35600 clock 1416044317 facility fAT-b827ebdf56e7 heading 201 hexid 484C59 ident TRA5749 ip 62.235.167.61 lat 50.63627 lon 3.76594 mac b8:27:eb:df:56:e7 speed 403 squawk 2126 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:38:47 error handling message ‘_c 1416044326 _s 0000 airGround A alt 37000 clock 1416044326 facility fAT-b827ebdf56e7 hexid 4CA4F0 ip 62.235.167.61 mac b8:27:eb:df:56:e7 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:38:52 error handling message ‘_c 1416044331 _s 0000 airGround A alt 35950 clock 1416044332 facility fAT-b827ebdf56e7 heading 106 hexid C023AA ident ACA876 ip 62.235.167.61 lat 50.79166 lon 4.29321 mac b8:27:eb:df:56:e7 speed 453 squawk 2014 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
11/15/2014 09:38:52 error handling message ‘_c 1416044331 _s 0001 airGround A alt 35825 clock 1416044331 facility fAT-b827ebdf56e7 heading 201 hexid 484C59 ident TRA5749 ip 62.235.167.61 lat 50.55964 lon 3.72080 mac b8:27:eb:df:56:e7 speed 403 squawk 2126 user jackoneill’ from server (can’t read “row(type)”: no such element in array), continuing…
pi@piaware /tmp $

Enhancement Request #1 for PiAware: Add a command to control where the PiAware logs go.

With computers that have a Flash Drive, such as a Raspberry Pi, it is bad idea to be constantly writing to the Flash. What I do when recording data is to direct my program’s log files to a RAM drive that is associated with tempfs. So I would like to be able to “tell” PiAware where to put the PiAware Log Files as the tempfs RAM drive actually is not always located at /dev/shm for all Debian Linux distributions. Something like “-ld /dev/shm” where -ld means “Log Directory”. The default Log Directory would be /tmp as it is now.

Enhancement Request #2 for PiAware: Limit the number of bytes that goes to the PiAware log file.

Recently, PiAware has gone “hog wild” writing out data continuously to the PiAware log files resulting in files that are 800 Megabytes long!!! Here is the log message that is being repeated.

“11/14/2014 23:59:59 unrecognized message type ‘log’ from server, ignoring…”

This problem is being discussed in another posting, so I don’t expect nor want it to be addressed here. My main concern is the Size of the Log Files.

As PiAware wrote to piaware.out, it filled up the /tmp directory and crashed several other applications running on my Linux Computer that use /tmp. A maximum limit of 5 Megabytes for the PiAware Log Size seems reasonable to me. You may want to have very large log sizes for your own testing or when you work with a user that is having major problems. If this is the case then you may want to add a command that indicates the maximum size log file. Something like “-ls 50” where -ls means “Log Size” in megabytes. The default Log Size would be 5 megabytes or some default size that you think would be useful to all users.

John Carroll

I have the same. I stopped feeding for now as nothing was getting uploaded according to my stats, just my /tmp/piaware.out was growing and growing.

Anything we need/can do locally?

Hi,

Is FA having a server issue ? Its that stats, do not update, and my piaware.out og file is getting a huge number of error messages :



11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 error handling message '_c	1416057645	_s	0032	airGround	A	alt	5275	clock	1416057643	facility	fAT-b827eb940333	heading	141	hexid	392AF9	ident	AF644QI 	ip	88.172.100.193	lat	45.63007	lon	4.83934	mac	b8:27:eb:94:03:33	speed	275	squawk	1000	user	subsy' from server (can't read "row(type)": no such element in array), (can't read "row(type)": no such element in array
    while executing
"switch $row(type) {
			"login_response" {
				handle_login_response_message row
			}

			"notice" {
				handle_notice_message row
			}

			"alive" {
	..."
    (object "::adept" method "::fa_adept::AdeptClient::handle_response" body line 4)
    invoked from within
"handle_response response"), continuing...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 error handling message '_c	1416057645	_s	0035	airGround	A	alt	35200	clock	1416057645	facility	fAT-b827eb940333	heading	327	hexid	398495	ident	CCM503E 	ip	88.172.100.193	lat	47.17680	lon	4.22953	mac	b8:27:eb:94:03:33	speed	487	squawk	1000	user	subsy' from server (can't read "row(type)": no such element in array), (can't read "row(type)": no such element in array
    while executing
"switch $row(type) {
			"login_response" {
				handle_login_response_message row
			}

			"notice" {
				handle_notice_message row
			}

			"alive" {
	..."
    (object "::adept" method "::fa_adept::AdeptClient::handle_response" body line 4)
    invoked from within
"handle_response response"), continuing...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 error handling message '_c	1416057645	_s	0037	airGround	A	alt	37000	clock	1416057645	facility	fAT-b827eb940333	heading	241	hexid	400EFB	ident	EZY2713 	ip	88.172.100.193	lat	45.34479	lon	4.20201	mac	b8:27:eb:94:03:33	speed	403	squawk	5707	user	subsy' from server (can't read "row(type)": no such element in array), (can't read "row(type)": no such element in array
    while executing
"switch $row(type) {
			"login_response" {
				handle_login_response_message row
			}

			"notice" {
				handle_notice_message row
			}

			"alive" {
	..."
    (object "::adept" method "::fa_adept::AdeptClient::handle_response" body line 4)
    invoked from within
"handle_response response"), continuing...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...
11/15/2014 13:20:49 unrecognized message type 'log' from server, ignoring...


All seems to be ok now

Greets pirate

I just restarted my pi and it looks like things have been fixed. I’m logging and no error messages.

Restarted piaware, all seemed good. Rebooted, and it seems happy as a clam at high tide. Stats showing active, logging uploads. Was it a problem with one/ some of the scripts?

We are actively digging into this. Expect a 1.17-1 beta very soon. In the mean time, a restart of PiAware when it occurs is probably a good idea.

Once it’s tested and deployed to the site, we’ll email everyone to upgrade.

Beyond this fundamental problem/bug, we’re working to fix over-logging problems.