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

PiCAST does run, but not listening to anything. #44

Open
angristan opened this issue Nov 11, 2016 · 5 comments
Open

PiCAST does run, but not listening to anything. #44

angristan opened this issue Nov 11, 2016 · 5 comments

Comments

@angristan
Copy link

pi@picast:~/PiCAST $ bash picast_stop.sh
Stopping PiCAST...
error:   Forever cannot find process with id: picast.js
pi@picast:~/PiCAST $ bash picast_start.sh
Starting PiCAST3...
warn:    --minUptime not set. Defaulting to: 1000ms
warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info:    Forever processing file: picast.js
pi@picast:~/PiCAST $ sudo netstat -tlp
Connexions Internet actives (seulement serveurs)
Proto Recv-Q Send-Q Adresse locale          Adresse distante        Etat        PID/Program name
tcp        0      0 localhost:8953          *:*                     LISTEN      515/unbound
tcp        0      0 localhost:domain        *:*                     LISTEN      515/unbound
tcp        0      0 *:ssh                   *:*                     LISTEN      409/sshd
tcp6       0      0 localhost:8953          [::]:*                  LISTEN      515/unbound
tcp6       0      0 [::]:ssh                [::]:*                  LISTEN      409/sshd

And I can't acess IP:3000.

@GraemeFulton
Copy link

I have the same @angristan issue, did you find any solution?

@GraemeFulton
Copy link

I noticed there was a package.json, so ran (from the PiCAST directory):
sudo npm install
followed by:
sudo sh picast_start.sh
and it works:
screen shot 2016-11-20 at 21 28 58

@angristan
Copy link
Author

No I haven't found anything, thanks for the tip, I'll test when I can.

However it's still a bug, but I don't know why

@Kisty
Copy link

Kisty commented Jan 31, 2017

Ah, I ran into this. After running forever manually, it needed the express module.

@solvaholic
Copy link

I noticed the same symptom @angristan reported and npm install got me through it.

For what it's worth, npm install told me it added 49 packages (not just express).

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

No branches or pull requests

4 participants