Post by jwmacc on Jul 20, 2014 7:04:50 GMT -8
I have spent a lot of time and encountered many problems trying to run this software - these are summarised below, and I would welcome comments on what I've done wrong - obviously many other people have run the same software without problems.
I have installed the RasPiConnectServer (RPCS in future to save space !) a number of times on four different SD cards. In all cases the OS is raspbian 3.12.22 June 18 2014, with update and upgrade applied; and I have set the IP address to a (different) static value on each system.
The problems met depend whether I
(1) run the server from the command line,
(2) run the server in the background from the command line, or
(3) arrange to run the server on start-up (one success, two disasters !)
1.1 After starting the RPi system and logging in, the instructions in your documentation say enter cd /home/pi/RPCS, and then python RPCS.py. However, after login the system is already in directory /home/pi/, so I only need cd RPCS ; and I have to enter sudo python RPCS.py ; when I do this, the server runs and links to the iPad Ap.
1.2. Next experiment is to open a second terminal window, either using CTRL-ALT-F2, or in the GUI. In both cases, I can get the server running as above, and it continues to run if I minimise the window. However, if I shut the window, then try to restart the server, I get 'socket error', presumably because I have not shut down the server properly. How should I do this ?
2. To run in background mode from the command line, your documents say enter nohup python RPCS.py &; again I find this only works if prefaced with sudo. Then indeed I can close the window, and the server still runs.
3. To run RSCS on startup: In my first installation I succeeded in setting this up, and it worked well. Unfortunately, on this SD card I have an old version of GPIO which I cannot update, which is why I went on the install the system on other two other cards. This resulted in DISASTER: when I modified the /etc/rc.local file as you describe, and then restarted the system, the reboot hangs after the lines
My IP address is 192.168.1.90
nohup: ignoring input and appending output to 'nohup.out'
The only action to produce any result is to input CTRL-ALT-DEL, but this just restarts the system and it stops at the same point.
One card was a NOOBS installation, where the reinstall option saved the day; the second card seems to be a write-off.
Why this worked on the first card and failed on the next two is hard to understand.
This looks like a really nice system, but the documentation instructions for running the server are surely not accurate ?
I have installed the RasPiConnectServer (RPCS in future to save space !) a number of times on four different SD cards. In all cases the OS is raspbian 3.12.22 June 18 2014, with update and upgrade applied; and I have set the IP address to a (different) static value on each system.
The problems met depend whether I
(1) run the server from the command line,
(2) run the server in the background from the command line, or
(3) arrange to run the server on start-up (one success, two disasters !)
1.1 After starting the RPi system and logging in, the instructions in your documentation say enter cd /home/pi/RPCS, and then python RPCS.py. However, after login the system is already in directory /home/pi/, so I only need cd RPCS ; and I have to enter sudo python RPCS.py ; when I do this, the server runs and links to the iPad Ap.
1.2. Next experiment is to open a second terminal window, either using CTRL-ALT-F2, or in the GUI. In both cases, I can get the server running as above, and it continues to run if I minimise the window. However, if I shut the window, then try to restart the server, I get 'socket error', presumably because I have not shut down the server properly. How should I do this ?
2. To run in background mode from the command line, your documents say enter nohup python RPCS.py &; again I find this only works if prefaced with sudo. Then indeed I can close the window, and the server still runs.
3. To run RSCS on startup: In my first installation I succeeded in setting this up, and it worked well. Unfortunately, on this SD card I have an old version of GPIO which I cannot update, which is why I went on the install the system on other two other cards. This resulted in DISASTER: when I modified the /etc/rc.local file as you describe, and then restarted the system, the reboot hangs after the lines
My IP address is 192.168.1.90
nohup: ignoring input and appending output to 'nohup.out'
The only action to produce any result is to input CTRL-ALT-DEL, but this just restarts the system and it stops at the same point.
One card was a NOOBS installation, where the reinstall option saved the day; the second card seems to be a write-off.
Why this worked on the first card and failed on the next two is hard to understand.
This looks like a really nice system, but the documentation instructions for running the server are surely not accurate ?
