DrWho
I have a Raspberry PI 2 B v1.1 and a Raspberry PI 1 B rev2.
On each of these, I used NOOBS v3.0.1 to install Raspbian.
I updated Raspbian with:
sudo apt-get update
sudo apt-get dist-upgrade
After a restart, I installed OpenPLC_v3 with:
git clone https://github.com/thiagoralves/OpenPLC_v3.git
cd OpenPLC_v3
./install.sh rpi
After a restart
ps aux | grep openplc
does not show any OpenPLC processes running.

I saw a similar report on
https://openplc.discussion.community/post/fresh-install-and-cant-open-openplc-webpage-10065610

What should I try next?
Quote 0 0
thiagoralves
Maybe something failed on the installation, it’s hard to tell. Have you tried to launch it manually by running ./start_ openplc.sh ?
Quote 0 0
DrWho
The result suggests that something is wrong:
============================
pi@raspberrypi:~/OpenPLC_v3 $ ./start_ openplc.sh
* Serving Flask app "webserver" (lazy loading)
* Environment: production
WARNING: Do not use the development server in a production environment.
Use a production WSGI server instead.
* Debug mode: off
Traceback (most recent call last):
File "webserver.py", line 1894, in <module>
app.run(debug=False, host='0.0.0.0', threaded=True, port=8080)
File "/home/pi/.local/lib/python2.7/site-packages/flask/app.py", line 943, in run
run_simple(host, port, self, **options)
File "/home/pi/.local/lib/python2.7/site-packages/werkzeug/serving.py", line 1009, in run_simple
inner()
File "/home/pi/.local/lib/python2.7/site-packages/werkzeug/serving.py", line 962, in inner
fd=fd,
File "/home/pi/.local/lib/python2.7/site-packages/werkzeug/serving.py", line 805, in make_server
host, port, app, request_handler, passthrough_errors, ssl_context, fd=fd
File "/home/pi/.local/lib/python2.7/site-packages/werkzeug/serving.py", line 698, in __init__
HTTPServer.__init__(self, server_address, handler)
File "/usr/lib/python2.7/SocketServer.py", line 417, in __init__
self.server_bind()
File "/usr/lib/python2.7/BaseHTTPServer.py", line 108, in server_bind
SocketServer.TCPServer.server_bind(self)
File "/usr/lib/python2.7/SocketServer.py", line 431, in server_bind
self.socket.bind(self.server_address)
File "/usr/lib/python2.7/socket.py", line 228, in meth
return getattr(self._sock,name)(*args)
socket.error: [Errno 98] Address already in use
pi@raspberrypi:~/OpenPLC_v3 $ ps all | grep openplc
0 1000 740 723 20 0 4364 1796 pipe_w S+ pts/0 0:00 grep --color=auto openplc
pi@raspberrypi:~/OpenPLC_v3 $
============================
This was on a Raspberry PI 1 B rev2. I recall receiving a similar result on a Raspberry PI 2 B v1.1
Quote 0 0
DrWho

Based on the experience shared in this thread:
https://openplc.discussion.community/post/fresh-install-and-cant-open-openplc-webpage-10065610
I am going to try to try running the install script again.

Quote 0 0
thiagoralves
The error is that the address is already in use. So, either OpenPLC is in fact running, or something else is running on your port 8080 preventing OpenPLC to start. Have you tried to launch your browser on the Pi and type localhost:8080 to see what pops up?
Quote 0 0
DrWho
After running the install script a second time on the Raspberry PI 1 B rev2., sudo netstat -pln shows that a python process is listening on port 8080.
The local chromium browser was able to open localhost:8080. I was able to start OpenPLC and see processes with ps aux | grep openplc.
I tried things again on the Raspberry PI 2 B v1.1.
============
pi@raspberrypi:~/OpenPLC_v3 $ ./start_ openplc.sh
Traceback (most recent call last):
File "webserver.py", line 15, in <module>
import flask_login
ImportError: No module named flask_login
pi@raspberrypi:~/OpenPLC_v3 $
============
After I ran the install script again on the Raspberry PI 2 B v1.1, sudo netstat -pln shows that a python process is listening on port 8080.
The local chromium browser was able to open localhost:8080. I was able to start OpenPLC and see processes with ps aux | grep openplc.

So I guess that for the current state of the build process, "The Postman Always Rings Twice."
Quote 0 0
DrWho

Both second installs shows it updating some packages at the beginning.
on the Raspberry PI 1 B rev2:
=======
Installing OpenPLC on Raspberry Pi
+ linux_install_deps sudo
+ sudo apt-get update
Get:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease [15.0 kB]
Hit:2 http://archive.raspberrypi.org/debian stretch InRelease
Fetched 15.0 kB in 4s (3,090 B/s)
Reading package lists... Done
=======
on the Raspberry PI 2 B v1.1:
=======
Installing OpenPLC on Raspberry Pi
+ linux_install_deps sudo
+ sudo apt-get update
Hit:1 http://archive.raspberrypi.org/debian stretch InRelease
Get:2 http://raspbian.raspberrypi.org/raspbian stretch InRelease [15.0 kB]
Get:3 http://raspbian.raspberrypi.org/raspbian stretch/main armhf Packages [11.7 MB]
Fetched 11.7 MB in 27s (420 kB/s)
Reading package lists... Done
=======
If it helps, I can post the complete output from both installs.
Quote 0 0
DrWho
Summary:
I did not experience problems installing OpenPLC_v3 on Raspberry PI 3+.
I experienced problems installing OpenPLC_v3 on Raspberry PI 1 B rev 2 and Raspberry PI 2 B v1.1. Those problems seemed to be fixed by running the installation a second time.
--------
I tried the install on a Raspberry PI 3+ with a 32 G Byte Sandisk Extreme Pro microSDHC card.
I used NOOBS v3.0.1 to install Raspian, then used apt-get to update.
Installing OpenPLC only took 20 minutes!
After the install running ./start_ openplc.sh interactively allowed me to browse to localhost:8080.
Restarting the Raspberry PI caused start_ openplc.sh to run non-interactively.
Quote 0 0