Installation from bash script doesn't work #1362
Comments
|
Did you test running "Raspbian Stretch / Lite" ? |
|
Yes, I used this one: Raspberry Pi OS (32-bit) Lite |
Use Stretch instead of Buster |
|
I attempted to run on Stretch, but I'm then getting: TASK [screenly : Install pip dependencies] ***************************************************************************************************************************************************************************************** An insane blob og error. Seems like it's attempting to delete some folders and failing. |
|
I commented out that task in the ansible playbook, let's see if it moves past that now. |
|
Can someone let us know if OSE is working in stable manner on Raspbeery pi4? I received this response from Screenly support: Hi We are, unfortunately, unable to provide one-on-one support for Screenly OSE as it is a free product. This help page will point you towards available resources: You should note that the Raspberry Pi 4 board has had some well publicised issues with video and wifi; with this in mind, if reliability is important for your signs, we advise that you use the 3B+ variant. This is low cost and very reliable. Best, Nick -- |
Can you remove that directory? also, can you edit your then run that install.sh file. |
Nope, that didn't help. Same problem. The only way to get past that is by commenting out the task in the playbook. |
You had to comment out this task: Which branch are you selecting when running the install script? Something is not allowing the packages to install properly, before running the installer again just to test, can you remove all pip packages by running this line: or if starting fresh, can you confirm this install script being ran is on a fresh raspbian stretch image from: http://downloads.raspberrypi.org/raspbian_lite/images/raspbian_lite-2019-04-09/ if you decide to just start fresh with raspbian stretch lite image and then running the bash install script, note down the exact steps you are taking with details in case it doesnt work so that i can try to reproduce the issue. |
Correct. If I let it run once, then it has already performed the pip installation and I can then just omit that step. I'm also wondering why the ansible task is taking several minutes, while running
Most "stable like" setup. No to everything.
This is the one I was using for the pi3: 2019-04-08-raspbian-stretch-lite.zip
I'll see what I can do. I am currently using pi4 to install now, but I'll see if I can make another stab at the 3. |
|
The exact same thing happens when installing on a Pi4. This is with the most recent buster image. Just booted and gotten the Pi online and then run: So it should be very easily reproducible. |
ansible doesnt do anything except the task at hand, ansible is installing all of the packages in the requirements.txt file for the first time, remember that upon first installing of python packages pip installs the source distributions and most dont have wheels and need to be compiled so your installation will need to build wheels for each one that is not in the form of a wheel package to begin with.. btw, how are you getting the logs to show what pip is installing during the ansible task if that doesnt normally show or even in journalctl? i dont think you are doing a normal installation, you are leaving out exact steps you are taking for your installation, and you mentioned this RPi will be used for more than just screenly so which part are you doing first, your screenly-ose install or your other thing first?
I dont have an rpi4 to test with but I dont think production branch or even exp/dev branch is compatible without some modifications to the installer and the dependencies/packages.. So I grabbed one of my test rpi3b and flashed the stretch lite image, and set up localization with sudo raspi-config because i always do that first and foremost, and then i ran the installer script. (well mine but its basically the same with just the two small PR changes I've requested.. but you said you tried the force option and it didn't make a difference so doesnt matter.. anyway after adding a website the screen started to display it and worked as expected, so I will assume again that you are not doing the normal steps to install screenly-ose. |
|
This is the COMPLETE output of the installation. The command to install screenly is literally the first command entered (after bootstrapping the installation with the WPA SSID and PSK and enabling ssh headless): https://paste.ubuntu.com/p/hJrg7KSKwY/ I chose Y, N, N, N, N. But then afterwards editing that task and uncommenting the pip installation then works and screenly happily installs. |
|
On your original post you said you were using rpi3b, and then later on mentioned you tried raspbian stretch lite, and that you had the same issue, and I thought we were testing on the same thing, these lines from your pastebin tell me you're using newer kernel (most likely rpi4 hardware) and debian buster, and I have not been testing on that, I have been testing on debian stretch and rpi3b... If you were to try on rpi3b again with debian stretch lite, I am sure the installer would work perfectly fine. Now, if you want to help with rpi4/buster installation then you would need to edit your own installation script and fork the screenly repo because I cannot test with rpi4 hardware and others have opened issues that cannot get the screenly image to work with rpi4 specifically as far as i know. I will do some tests with buster and let you know. |
|
@mflage
Please report back any of the error logs like you previously did on pastebin, that would help. |
I got OSE running on Pi 4 about a year ago. Back then I used Raspbian and manually installed the development version of OSE by running It was running pretty stable, but I had a hell of a time getting it to work in the first place. Things may have changed since then, but I can't test, because that Pi4 has been stolen and wasn't replaced. |
|
@mflage |
|
I believe most if not all of these issues have been addressed in the master (development) branch already. For Pi 4/Buster specific issues, see #1389. |
Overview of the Issue
Installing using 'bash <(curl -sL https://www.screenly.io/install-ose.sh)' method doesn't yield a working Screenly installation after finishing. The reason I need to use this installation method is that we need to use the Pi for something else than just Screenly.
Upon reboot I see no running screenly instance. I just see the console screen to log into the Pi.
Reproduction Steps
Environment
The text was updated successfully, but these errors were encountered: