Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Service starts too early and doesn't work right #35

Closed
GoogleCodeExporter opened this issue Jul 18, 2015 · 4 comments
Closed

Service starts too early and doesn't work right #35

GoogleCodeExporter opened this issue Jul 18, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Install WebIOPi
2. Schedule to run at startup as per the instructions
3. Reboot

At this point I observe the service running, but non responsive on port 8000. 

WebIOPi version used?
=> Unknown, one from the store

Python version used?
=> Unknown, one that came with the distro

Distro used? (WebIOPi has only been tested on Raspbian Wheezy)
=> Wheezy

Raspberry Pi board revision? (1 or 2)
=> Rev 2

For Javascript side bugs, Browser?
=> N/A

Please provide any additional information below.


Suggested fix:
* Add $network to the startup dependancies, fixed it for me.

Original issue reported on code.google.com by wolfen...@gmail.com on 27 Feb 2013 at 7:38

@GoogleCodeExporter
Copy link
Author

#! /bin/sh
### BEGIN INIT INFO
# Provides:          webiopi
# Required-Start:    $remote_fs $syslog $network
# Required-Stop:     $remote_fs $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: WebIOPi initscript
# Description:       WebIOPi initscript
### END INIT INFO

# Author: trouch <trouch@trouch.com>
WEBIOPI_PORT=8000


Original comment by wolfen...@gmail.com on 27 Feb 2013 at 7:42

@GoogleCodeExporter
Copy link
Author

thanks for report and fix
do you use wifi connection ?

Original comment by tro...@trouch.com on 27 Feb 2013 at 8:26

@GoogleCodeExporter
Copy link
Author

This issue was closed by revision r991.

Original comment by tro...@trouch.com on 27 Feb 2013 at 9:11

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Hi there
Thanks for the fix! 

No this was a wired connection..

Original comment by wolfen...@gmail.com on 2 Mar 2013 at 11:26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant