Forum Replies Created
-
AuthorPosts
-
DaveAZMemberTwo other notes:
I’m not using the beta version of the UI, just the standard version.
Also, when I have let it run overnight and the web interface stops working with the error I mentioned above, I also see that the SSH connection has also dropped in the command window.
Dave
DaveAZMemberHi Dan,
I installed the latest version of Raspian on the RPi and then installed OSPi from Github. I’m not using the new interface.
I did just notice a difference when I start up OSPi via the SSH command window vs having it run at boot by way of adding lines to the /etc/rc.local file:
When I disable it from starting at boot time and just it from the command line (via SSH and after a fresh reboot) with “sudo python ospi.py &” and then I check that it’s running via “ps aux | grep ospi”, there are two entries for ospi as follows:
root 2528 0.5 0.3 4584 1484 pts/0 S 20:03 0:00 sudo python ospi.py
root 2529 18.0 1.8 103828 8316 pts/0 Sl 20:03 0:01 python ospi.py
pi 2542 0.0 0.1 3544 812 pts/0 S+ 20:03 0:00 grep –color=auto ospiWhereas, if I set it up to run at boot via the /etc/rc.local file, and run the same “ps … ” command, I get:
root 2277 4.5 1.8 102320 8272 ? Sl 19:52 0:01 python ospi.py
pi 2549 0.0 0.1 3548 868 pts/0 S+ 19:53 0:00 grep –color=auto ospiI’ll try letting it run overnight and see if starting it via rc.local fixes the problem.
Thanks,
Dave
DaveAZMemberHi Dan,
Yes I can still access the RPi via SSH when it is in this state. Also, yes it fails the same way either when I do a refresh or I when I open a new browser window and access the same address (192.168.1.210:8080 in my case). I even tried a different browser (Safari) and I get the same error text.
Dave
-
AuthorPosts