rPi4 install not working

Frustration upon frustration. I have been working this on my own for about 8 hours
I install Raspberry OS lite
I run
$ bash <(curl -sL https://www.screenly.io/install-ose.sh)
i see tons of errors and the a request for reboot
The only file in the pi folder is version.md with this for the contents
Distributor ID: Raspbian
Description : Raspbian GNU/Linux 11 (bullseye)
Release : 11
Codename : bullseye

so I go through the errors
I install python3-pip as python-pip is unavailable
i then install the following by hand
git-core
libffi-dev
libssl-dev
python-dev
python-pip
python-setuptools
whois

I then run $ bash <(curl -sL https://www.screenly.io/install-ose.sh)
I now have the folders. I reboot
not sure what to do from here. I try running server.py and get no module named pydbus
when I try running host_agent.py and viewe.py… same error
so I run pip install pydbus
server.py produces same error and the other two py files get connection refused.

HELP!!! please

Hi,
Same problem.
I’m unable to install Screenly OSE on my rasperrypi 4.
It works perfectly on a RP3 B+.

Help!

I had the same problem.
My solution was to install Buster OS Lite (Legacy) which included Python.
After them the Screenly installation works

1 Like

Thanks, I will try it soon!

I tried twice to install it as you said.
each time it result a ‘internal server error’.
Everything seems to be installed correctly but i can not access to screenly paramater and i lose my wifi connection when i reboot my rpi4;
Someone can help me?

Did y’all install the developement version?

Hi

Same here :
As 2020-07-17-Screenly-OSE-lite doesn’t seem to boot on my RPi 4 B 2GB, I tried bash <(curl -sL https://www.screenly.io/install-ose.sh) - (development (master) branch, then No to the rest of questions) - after installing 2022-01-28-raspios-buster-armhf-lite
.
Play recap seems ok, but all I get is a blank screen after the splash screen.
WiFi, Ping and SSH ok, but HTTP access gives me Internal Server Error.

Any ideas please ?

Internal server error would mean the web server is not being reached or the docker container/instance is not running… Have you tried to check the status of all this? got any logs to show?

Without logs and maybe screenshots, it’s hard to help troubleshoot.

Also, bullseye is not supported last time I checked.

I have the Pi 4 B v1.5 that has this same issue - if you can guide me as to how to do the logs i can get some across - i get the splash screen - then black.

I can get to the schedule overview to add assets but nothing plays at all.

I ran into the same issues you all have. I think the problem is that raspberrypi moved to a different version that is based off of the newer version of debian. I downloaded and installed raspberrypi version buster from 2021-05-07 and the install script ran fine. It’s a bit un-nerving that I am having to run a version of raspberrypi os that is over a year old. However, this version should be supported for years to come. Is screenly ose stilly being developed at all?

If it is, it’s not by Screenly developers, as they can’t or won’t answer any questions about OSE.

Hmm… why would it be un-nerving that the open source Raspbian OS you are using on a raspberry Pi is over a year old? how old is the OS on your current computer? or the average age of OSs? see where I’m going with this…?
The RaspiOS or Raspbian Buster could be 5 years old, doesn’t matter, what matters most is if the packages that the system uses are all patched for security vulnerabilities.

For reference on this topic: Raspberry PI OS support and release schedule - Raspberry Pi Forums

@SirPaul ,
what kind of questions would OSE devs not be able to answer?

Any. As I’ve already stated, Screenly developers aren’t maintaining OSE and won’t or can’t answer any question relating to OSE.

Well, we should remember that OSE is open source and contributors/volunteers are the ones that mostly maintain it. The Screenly developers as a resource are focused on the commercial version, thus I would imagine everyone would understand that resources aren’t free and it should be expected that any open source software is at the hands of the available contributors/volunteers that would maintain it.

Also, just an FYI, there is someone from Screenly that is helping to maintain it, but one person cannot possibly help hundreds.

Do you yourself though have an actual question to ask that was not answered by someone from Screenly or you are just letting the people that are posting questions here know that they are pretty much on their own with these issues?

Some of the instructions supplied on the Screenly website for using OSE are out-of-date and simply don’t work. From which I did have questioned that no-one answered, so I was pretty much on my own.
So I sympathise will all those people asking similar questions that get no answers.

One person could help hundreds - just by looking at the broken documentation and updating it - with maybe some solutions to the common problems.

And to refer to your earlier post about old OS code; it is easier to keep something in step with the latest (unless it fundamentally breaks something) than hoping that it keep working. Few people choose an old OS if they don’t have to.

For anyone still having an issue installing on RPi4, if you are seeing the black screen and journalctl shows screenly-host-agent.service errors not connecting to redis or something like that, check if the containers are running by getting to the pi console and typing:
docker ps
If there are no images showing under Container ID, simply run the upgrade containers script like this:
./screenly/bin/upgrade_containers.sh

Let me know if that helps.

@SirPaul ,

I dont think spending time on documentation is the solution when there are so many different issues that different users encounter, that it is better to tackle those problems and document those solutions on the Issues page because it is more dynamic and many more people can chime in, documentation does not provide solutions, think of the hundreds of unknown problems that someone can encounter, how would you post that on a documentation page? the Issues page in Github and this Forum is the best way to troubleshoot and help users, not spending time writing documentation.

About the OS topic, Screenly does not control when and how Raspbian will update their OS, what they will change, what packages they support or dont support which will break everything, so your point about keeping in step with them or OS releases is not feasible for an open source / mostly contributor supported software. Do you think systems that run as small appliances/servers get their OS updated every year? No, they are only patched for security vulnerabilities with CVE of 07 and above, and that’s if you have them public facing, otherwise there is no need to be worrying about which version of Raspbian OS your open source software is running.

Your contributions here are not helping, but thank you for telling me how to suck eggs.

@SirPaul , LOL, this actually made me laugh…

Seriously though, what do you need help with, I’ll see if I can help you troubleshoot.