Lockup's

5 replies [Last post]
g7pkf
Offline
United Kingdom
Joined: 11 Jan 2011

i have a problem.

 

i have 3 jogglers all running xapflash.

sometimes (once every 2-3 days) they stop responding to commands a restart of joggler does not resolve problem.

 

if i go to we pagei can then control rf devices so HAH is sending out commands correctly, even xapflash on webpage does not respond but from admin it works fine.

 

a reboot solves problem or if i wait for 10-20 minutes problem seems to be resolved.

 

i have run xfx viewer and all looks fine BUTno rf on/off is detected whilst problem is exhibited, also if i swith rf on/off several times whilst problem is occuringsaiditem will within 5-10 minutes switch on/off a corresponding number of times.

 

1 how do i debug this

2 anyone else with joggler/xapflash noticed this?

 

driving SWMBO  nuts

 

oh and a rebootof HAH instantly fixes it.

 

Dean

brett
Offline
Providence, United States
Joined: 9 Jan 2010
Dean just reading about your

Dean just reading about your problem.  So you are saying that your jogglers don't reponds to commands but you know the HAH is send these out as xfx viewer see them on the wire. 

Rebooting the HAH resolves the issue!?   I would say this is happening.

An xAP message is being sent out of from the HAH via the xap-hub and this is what you are seeing and saying..

BUT the jogglers get their messages via the iServer, and this is receiving its message also from the xap-hub so it should be getting the message.  Perhaps its jamming trying to send it out back as this would affect all 3.

I take it you are using a single iServer on the HAH.  What you can try is installing a local iServer on each and point their xapconfig.xml into 127.0.0.1 instead.   At least this way a failure of iServer (if this is what it is) will not take out all 3.

Alternatively update to the 307 build (if you can) as I made a number of iServer tweaks with regards to messages being lost.  Transmission to each joggler now happens in a separate thread from the receiver side thread.  This should alleviate issues with messages being lost whilst processing outbound packets.

Brett

g7pkf
Offline
United Kingdom
Joined: 11 Jan 2011
So you are saying that your

So you are saying that your jogglers don't reponds to commands but you know the HAH is send these out as xfx viewer see them on the wire.

 

No there is no sign on xfx, it seems to q them. then send them out after a period in a batch. for example wife goes to turn lounge lights on she presses it nowt so being a wife she presses it again and again and again and then phones me and moans (a lot) then the lights go on/off as many times as she has pressed the button-this can take 1-20 minutes to happen then all jogglers behave as they should.

 

all 3 are affected at the same time (and flash ob pc)

 

will try installing iserver on 1 to eliminate iserver on hah.

 

I have just updated to 307 will give that a whiz first.

 

Dean

brett
Offline
Providence, United States
Joined: 9 Jan 2010
Oh so the joggler MAY be

Oh so the joggler MAY be queuing them up and not sending them - that would be an xapflash issue then.  Pester Kevin :)

Or a transmission onto the wire from the iServer - pester me.  Given each joggler misbehaves the same way is sounds more like my problem.  :(

Do try putting a local iServer on one of them and see how that goes --- NOTE:  the version on the joggler is from an older code base.  This code is what you currently have with 306 but I've not updated the joggler binary with the changes I made for 307.

http://www.dbzoo.com/livebox/xapflash#iserver_installation

This should at least isolate any iServer issue to a single joggler - I would update with 307 before doing this.

Brett

kevin
Offline
Huddersfield, United Kingdom
Joined: 17 May 2010
xAP message queing

Dean... did you fix this ?

I don't believe this is a xAP Flash issue but you never know... it's not one that has cropped up elsewhere or that I experience in a similar setup.  I assume the Joggler still shows as connected to the iServer ?   Is this WiFi or wired ?  Do remote changes in any xAP devices update their status on the Joggler instantly still  ?

The messages between the Joggler and the HAH iServer are passed via TCP so you don't see those in xFX Viewer until the HAH iServer pushes them out as UDP.   As such it is difficult to ascertain just where they are being queued (Joggler or HAH).

Another diagnostic would be to temporarily run the Windows based iServer application and see if the problem remains, if so then it's my issue.  If you are familiar with Wireshark that would help diagnose it too.

 

K

g7pkf
Offline
United Kingdom
Joined: 11 Jan 2011
Sort of

Updated to 307 running wireshark on a pc connected to a hub to one of the jogglers.

it matters not wired or wireless.

and sod's law i have had a couple of lock ups but big ones on the HAH (RF stops working etc) but am putting these down to the amount of power cuts we are experiancing at present (4-5 a day-just blips but i monitor my mains)

will keep you posted, and try the windows iserver idea.

 

hard to nail as i am away a lot at present as well.

 

dean

Hardware Info