I/O shows 'could not connect' after 254 update
12 November, 2010 - 03:37
I just updated to 254 and now all my I/O shows 'could not connect'.
RF, relay, input, temp, and LCD. (LCD does display IP)
I've tried rebooting several times and got it back very briefly once for a few secs but then it went again... is this just a coincident hardware fail with the update or could it be a firmware issue ?
K
12 November, 2010 - 12:16
#3
Yup ... it's gone
OK. So, the xap-livebox process is indeed dead.
Next thing is to re-start it, in the foreground, in debug mode.
From a telnet session use ...
/usr/bin/xap-livebox -d 7 -s /dev/ttyS0 -i br0
Hopefully, this might give some info re why the process is having a panic.
12 November, 2010 - 13:00
#5
Killer xAP message on the wire
Yes. The thing to do would be to drop Brett an email with the exact message that is giving the problem.
Then, this issue should be reproducable and a fix could be rolled into xaplib2.
It's good to have somebody with a variety of xAP enabled kit helping out on the testing.
Derek.
12 November, 2010 - 13:17
#6
Large packets
If you could capture the entire xAP packet and post it I'll use this as a tester to find out why its breaking. Failing that I'll just make a large packet up and try it out.
12 November, 2010 - 14:28
#7
A couple of bugs
The segmentation fault was due to me having an > instead of >= in my parse code when detecting when I can't store any more key/value pairs. Having said that I only stored 50 which wouldn't have been enough for your message anyway so it wuold have silently overwritten you data which would have been harder to figure out. So the SEGV was a lucky break in the end.
I've increased the number of key=value pairs to 150. When I run out a storage a message will be logged so at least if this does happen you can find out why.
Pushed 255.
This bug only affects those with LARGE xAP messages which is why it went unnoticed during my testing.
Brett
254 is good on my HAH. If the LCD is showing the IP address, it's unlikely that it's a hardware failure.
You will have a lot more xAP traffic on your LAN than either Brett or I. I'm thinking that perhaps something on your network is exposing a bug in the new xaplib2 and causing the HAH process that drives the interface to the UI to panic and die.
After you see the '?'s on the UI, can you telnet into the HAH, issue a 'ps' command and post the results here?
Then, we'll be able to narrow this one down.
Derek.