cycledude
asked on
wamp server timeout
Hi
I have a network of Raspberry PI's displaying information on various screens around the workplace.
the pi's are displaying web pages from an internal server, and are displaying them like a powerpoint presentation, in a loop.
I am using the meta refresh to move to the next page after x seconds
works fine mostly, however on the odd occasion the network must get too congested or something, because the page sometimes fails to display, and I see the firefox 'this is embarassing' page. I then have to physically go to the offending device, and connect a mouse to click 'restore' and it re-connects.
The pages are being served from an internal server with WAMP installed.
How can I increase the timeout for the site?
or can I detect if the server is not responding and try to refresh again, to prevent the system collapse?
Cheers
I have a network of Raspberry PI's displaying information on various screens around the workplace.
the pi's are displaying web pages from an internal server, and are displaying them like a powerpoint presentation, in a loop.
I am using the meta refresh to move to the next page after x seconds
<meta http-equiv="refresh" content="<?php echo $delay; ?>;url=<?php echo $nextpage; ?>" />
works fine mostly, however on the odd occasion the network must get too congested or something, because the page sometimes fails to display, and I see the firefox 'this is embarassing' page. I then have to physically go to the offending device, and connect a mouse to click 'restore' and it re-connects.
The pages are being served from an internal server with WAMP installed.
How can I increase the timeout for the site?
or can I detect if the server is not responding and try to refresh again, to prevent the system collapse?
Cheers
Usually, the "This is embarrassing" message is not caused by a timeout, but a crash of some sort.
ASKER
thanks for the ideas
The network is busy, but I have never seen a page take more than 4 or 5 seconds to load on a pi, and on a desktop iti is instant...
the pi's do get 100% cpu useage with very little effort, i guess they are just not that powerful...
I am using raspbian on the pi, is there any way to tweak more power out of it? I think I set them up with medium overclocking (it was a long ago!)
The network is busy, but I have never seen a page take more than 4 or 5 seconds to load on a pi, and on a desktop iti is instant...
the pi's do get 100% cpu useage with very little effort, i guess they are just not that powerful...
I am using raspbian on the pi, is there any way to tweak more power out of it? I think I set them up with medium overclocking (it was a long ago!)
Especially if you have a normal desktop PC (with a respectable CPU like i3 or higher), and that PC will NEVER give that error, you know it's the Pi's problem. I'm afraid overclocking won't do that much good (small sub digit percentage faster, but more prone to overheating/system freezing), if it's a slow CPU, it's just a slow CPU.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Cheers
Probably both are set at 300 seconds which seems more than enough for your simple pages. I suspect the problem might be somewhere else, maybe a general networking error (unless you really see your page load so slowly, it takes more than 5 minutes to load).
Other possible causes
- Pi's are overloaded, cpu at 100%, page fails to load because the Pi is too busy with something else)
- networking issue, some switch is overloaded, or you don't even get max speed (could also be cabling problem)
- WAMP server problem, not enough CPU/mem/bandwidth to handle the requests