Page 1 of 1

Server Looping after Map Image Upload?

Posted: 23 Oct 2014 21:38
by markolbert
I tried to upload my own map image file. The upload worked, but the image was way too big (I didn't know how big to make it).

After trying to upload a couple of smaller image files I've apparently somehow munged the server. The spinning "busy" icon displays constantly in the expert UI, no map image of any kind displays, and I can no longer execute commands (e.g., turn lights on and off).

I tried restarting z-way-server. No joy. I tried restarting z-way-server and mongoose. No joy. I tried copying the default map image over from the install directory and restarting z-way-server. No joy.

I even tried rebooting the pi. No joy.

Other than doing a complete re-install, how do I resolve this problem?

Re: Server Looping after Map Image Upload?

Posted: 24 Oct 2014 09:42
by pz1
I did/do observe this behaviour several times. In one occasion I could read the SD card to find out that quite a bit of the /opt directory was overwritten. So far I haven't been able to run my rig for more than a week and a half without problems

Re: Server Looping after Map Image Upload?

Posted: 24 Oct 2014 16:24
by markolbert
Do you do a complete reinstall? Have you reported this as a bug?

Re: Server Looping after Map Image Upload?

Posted: 24 Oct 2014 17:37
by markolbert
I noticed that a different client machine didn't have problems accessing the expert map page. So I tried clearing the cache and image files under Google Chrome (Windows) where I was having one of the looping problems. That didn't fix anything. But a deeper cleaning -- everything but passwords and content licenses -- did the trick.

Re: Server Looping after Map Image Upload?

Posted: 24 Oct 2014 17:55
by pz1
markolbert wrote:Do you do a complete reinstall?
Well once I have a version that basically works, I do take the SD card from Pi, and make an backup image that I can write back after a crash.
Have you reported this as a bug?
Yes I have mentioned several times. At the moment my main suspect is OpenRemote which does rather heavy polling on the Pi. It is difficult to push status changes to OR.

note: Under RECIPES I have described how to make a "clean" install for versin 2.x. That is partially applicable for earlier versions