vpetersson
Posts: 395
Joined: Wed Jul 25, 2012 9:23 am
Contact: Website

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Tue Sep 18, 2012 3:04 pm

b0b_z wrote:I loaded apache and it's working fine

The problem is now the splash screen is looking for 127.0.0.1/splash_screen and it throws an error then the content begins serving fine from local

Just wondering how to address the splash screen error without breaking anything

Thanks!
Hmm, that's odd. Unless you configured Apache to listen on port 8080, it shouldn't interfere.

Screenly looks for the splash page at:

Code: Select all

http://127.0.0.1:8080/splash_page
and not:

Code: Select all

http://127.0.0.1/splash_page
Creator of Screenly (Screenly.io), the leading digital signage solution for the Raspberry Pi. Now hacking on WoTT (github.com/WoTTsecurity/agent),
Twitter: @vpetersson | vpetersson.com

b0b_z
Posts: 21
Joined: Sat Sep 15, 2012 1:56 pm

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Tue Sep 18, 2012 8:32 pm

We're still getting the splash_pager error and I think we've figured it out

It would appear there is a check for connectivity to the web and if there isn't the error appears

We were using a wireless connection and got the error even though we were able to shell into the RPi

Once I established a wired connection via eth0 the splash page appeared

Where in the logic is there a check for connectivity?

Thanks!

vpetersson
Posts: 395
Joined: Wed Jul 25, 2012 9:23 am
Contact: Website

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Tue Sep 18, 2012 8:42 pm

b0b_z wrote: We're still getting the splash_pager error and I think we've figured it out

It would appear there is a check for connectivity to the web and if there isn't the error appears

We were using a wireless connection and got the error even though we were able to shell into the RPi

Once I established a wired connection via eth0 the splash page appeared

Where in the logic is there a check for connectivity?

Thanks!
Ah! Yeah, the server-module assumes that eth0 is the network interface used. I suppose I could make it an option in the config file. Please open a github issue for that and I look into it later on. For the time being, you could just change 'eth0' in server.py to whatever your network interface is called.
Creator of Screenly (Screenly.io), the leading digital signage solution for the Raspberry Pi. Now hacking on WoTT (github.com/WoTTsecurity/agent),
Twitter: @vpetersson | vpetersson.com

b0b_z
Posts: 21
Joined: Sat Sep 15, 2012 1:56 pm

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Tue Sep 18, 2012 8:56 pm

Thank you for your patience...

I'm really not a n00b ;)

This was a little screwy...

Thanks!

vpetersson
Posts: 395
Joined: Wed Jul 25, 2012 9:23 am
Contact: Website

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Tue Sep 18, 2012 9:07 pm

b0b_z wrote:Thank you for your patience...

I'm really not a n00b ;)

This was a little screwy...

Thanks!
No worries.

By the way, I'd advise against using a wireless connection. I've played around with that on the digital signage solution I wrote before Screenly (that was also Linux-based), but the wireless connection was never as stable as I needed it to be. It usually gave up after a week or two and then you had to manually either restart the computer or manually bring the link up again. Maybe it was a driver-issue, but that's my experience.
Creator of Screenly (Screenly.io), the leading digital signage solution for the Raspberry Pi. Now hacking on WoTT (github.com/WoTTsecurity/agent),
Twitter: @vpetersson | vpetersson.com

b0b_z
Posts: 21
Joined: Sat Sep 15, 2012 1:56 pm

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Tue Sep 18, 2012 9:15 pm

The wireless was for test purposes in a controlled environment

WiFi in the real world is dodgy at best

Thanks again!

charly130.mk2
Posts: 10
Joined: Tue Sep 06, 2011 7:05 am

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Wed Sep 19, 2012 8:14 am

Hi there

I am also interested in this solution. However, in our case, the units would be placed out in the field, with a USB 3G dongle for data connectivity.

This however raises two questions

a) You mention that screenly only has limited caching in the browser. Any ideas of when the local caching for the full set of media might be implemented? I noticed you did say in a previous post that this is in the to-do list. As you can appreciate, this would have a significant impact on the data traffic, which is important for 3G solutions.

b) I noticed that screenly uses an HTTP connection, and doesn't ask for a username/password (at least as far as I can see, since I haven't got my pi yet to play). Are there any plans to harden this with a username/password and HTTPS connection, to allow units to be 'out in the wild'?

TIA

bababooey
Posts: 4
Joined: Wed Sep 19, 2012 4:05 pm

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Wed Sep 19, 2012 4:15 pm

Thanks for the work on Screenly, got it up and running in no time. As others mentioned, I need to cache the content locally as I do not always have a connection to the PI. I've loaded apache onto the PI and can pull content locally now, this seems to work ok.

Next hurdle would be to update the content. I want to 'push' new content onto the PI and have it update / overwrite the old content. For example I have the files "LatestNews.mov", "LatestWeather.jpg", "LatestTraffic.jpg". I add them as assets and put the JPG's resouce type as webpages pointed to my local apache server running on PI. I can overwrite the JPG's now and they are updated but don't know how to do this for the .mov. It won't play if i define the resource type as webpage, and if I put it as video, I overwrite the file but it doesn't pick it up.

OUT.

b0b_z
Posts: 21
Joined: Sat Sep 15, 2012 1:56 pm

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Fri Sep 21, 2012 12:02 am

Question:

When it comes to connectivity, is that handled by the line

my_ip = netifaces.ifaddresses('eth0')[2][0]['addr']

in server.py?

What's the easiest way to have it not throw an error if a network connection is not in place?

Thanks!

Clifor
Posts: 12
Joined: Thu Jul 26, 2012 10:58 am

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Fri Sep 21, 2012 10:33 am

vpetersson wrote:
Clifor wrote: Exactly: Adding

Code: Select all

display_rotate=3
to your config.txt will do the trick and then changing resolution on viewer.py

Not sure if omxplayer will work though as I have only tested web sites and still pictures...
Thanks Clifor. I've pushed an update to Screenly that enables you to set the resolution in Screenly's config-file instead. I also added an FAQ-entry with your instructions. I wasn't able to get it to work at my test-screen at the office, but I still added it.
The config.txt parameter should work with the latest Raspbian release. I have also tested your change in the config file and it works just fine.
ScreenlyVertical.JPG
ScreenlyVertical.JPG (21.39 KiB) Viewed 8131 times

vpetersson
Posts: 395
Joined: Wed Jul 25, 2012 9:23 am
Contact: Website

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Fri Sep 21, 2012 11:25 am

Clifor wrote:[
The config.txt parameter should work with the latest Raspbian release. I have also tested your change in the config file and it works just fine.
That's awesome! Great job.

By 'latest' you mean Raspbian 2012-09-18, right? I tried it on 2012-08-16 and it didn't work.
Creator of Screenly (Screenly.io), the leading digital signage solution for the Raspberry Pi. Now hacking on WoTT (github.com/WoTTsecurity/agent),
Twitter: @vpetersson | vpetersson.com

Clifor
Posts: 12
Joined: Thu Jul 26, 2012 10:58 am

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Fri Sep 21, 2012 12:03 pm

vpetersson wrote:
That's awesome! Great job.

By 'latest' you mean Raspbian 2012-09-18, right? I tried it on 2012-08-16 and it didn't work.
No, I actually meant 2012-08-16 and I hadn't seen the later.

I am about to test it with 2012-09-18...

... and yes, the display_rotate tweak works ok.

I am now installing screenly to test everything together, I expect to confirm later today.

themidithief
Posts: 3
Joined: Sat Sep 22, 2012 7:37 am

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Sat Sep 22, 2012 7:51 am

Hi!
Whatever I do, I can't get Screenly to work on the latest Wheezy version (2012-09-18-wheezy-raspbian). It worked just fine on the first install on the Previous Wheezy version. I'm using a 8GB SanDisk SD card. I've done three installs from scratch. The first one remotely over Wifi. The second remotely over Ethernet and the third straight from the RPi with Ethernet. I've followed all Wheezy setup requirements and Screenly seems to install fine. I get the splash screen on the RPi and I can reach the admin interface from another computer. In all three attempts I get an error when I try save assets to the database:
"Error 500: Internal Server Error
Sorry, the requested URL 'http://10.0.1.68:8080/process_asset' caused an error:
Internal Server Error"

This is what my logfile says. I'm pretty much a n00b so I can't make much of it unfortunately:
"10.0.1.5 - - [22/Sep/2012 07:51:24] "GET / HTTP/1.1" 200 679
10.0.1.5 - - [22/Sep/2012 07:51:24] "GET /favicon.ico HTTP/1.1" 404 32
10.0.1.5 - - [22/Sep/2012 07:51:25] "GET /add_asset HTTP/1.1" 200 1157
10.0.1.5 - - [22/Sep/2012 07:51:26] "GET /favicon.ico HTTP/1.1" 404 32
10.0.1.5 - - [22/Sep/2012 07:51:34] "POST /process_asset HTTP/1.1" 200 235
10.0.1.5 - - [22/Sep/2012 07:51:35] "GET /favicon.ico HTTP/1.1" 404 32
10.0.1.5 - - [22/Sep/2012 07:51:36] "GET / HTTP/1.1" 200 679
10.0.1.5 - - [22/Sep/2012 07:51:37] "GET /static/css/style.css HTTP/1.1" 304 0
10.0.1.5 - - [22/Sep/2012 07:51:37] "GET /favicon.ico HTTP/1.1" 404 32
10.0.1.5 - - [22/Sep/2012 07:51:38] "GET /add_asset HTTP/1.1" 200 1157
10.0.1.5 - - [22/Sep/2012 07:51:38] "GET /favicon.ico HTTP/1.1" 404 32
10.0.1.5 - - [22/Sep/2012 07:51:50] "GET /favicon.ico HTTP/1.1" 404 32
10.0.1.5 - - [22/Sep/2012 07:51:52] "GET /favicon.ico HTTP/1.1" 404 32
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/bottle.py", line 744, in _handle
return route.call(**args)
File "/usr/local/lib/python2.7/dist-packages/bottle.py", line 1479, in wrapper
rv = callback(*a, **ka)
File "/home/pi/screenly/server.py", line 170, in process_asset
if file.status_code == 200:
AttributeError: 'function' object has no attribute 'status_code'
10.0.1.5 - - [22/Sep/2012 07:51:55] "POST /process_asset HTTP/1.1" 500 754
10.0.1.5 - - [22/Sep/2012 07:51:55] "GET /favicon.ico HTTP/1.1" 404 32
Bottle server starting up (using WSGIRefServer())...
Listening on http://0.0.0.0:8080/
Hit Ctrl-C to quit.

localhost - - [22/Sep/2012 07:57:45] "GET /splash_page HTTP/1.1" 200 459
localhost - - [22/Sep/2012 07:57:46] "GET /static/css/style.css HTTP/1.1" 200 2261
localhost - - [22/Sep/2012 07:57:46] "GET /static/img/low_contrast_linen.png HTTP/1.1" 200 22749
localhost - - [22/Sep/2012 07:57:47] "GET /favicon.ico HTTP/1.1" 404 32"

I've also tried deleting the db file but it din't help. I have rebooted numerous times without any good results. Any ideas what's going on here?

themidithief
Posts: 3
Joined: Sat Sep 22, 2012 7:37 am

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Mon Sep 24, 2012 11:30 pm

Any news on this? I tried installing screenly on two SD Cards (8gb and 16gb) and it didn't work I also tried installing the old Wheezy but I kept getting the same "Error 500: Internal Server Error" when saving assets to the database. Since it worked for me before I start questioning if the install is broken? Has anyone gotten Screenly to work well lately?

Sebasp
Posts: 1
Joined: Mon Sep 24, 2012 9:18 pm

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Tue Sep 25, 2012 11:56 am

Hello, I have the same problem. Error 500. I tried everything said in the forum.

emmebi
Posts: 10
Joined: Wed Aug 08, 2012 7:47 pm

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Tue Sep 25, 2012 1:53 pm

Signs wrote:I have been looking over post for digital signage using the Raspberry Pi. I have even offered a bounty to someone that can build one.
The best one that I have found is located at: http://www.binaryemotions.com/instant-w ... pberry-pi/

It still needs some work, so I am hoping that you may want to put your head together with the owner of the website that host the website of the kiosk. You will see that he is very close, if not there.
There are a few problems still, however. One is with the flash content and the time it loads the video.
The biggest problem is that it does not launch the browser in full screen (F11)
Instant WebKiosk for Raspberry Pi 2.0 is out!
Now fully dedicated to digital signage (overclocked to 900Mhz).

Home page: http://www.binaryemotions.com/instant-webkiosk
Direct download http://sourceforge.net/projects/iwk-rpi/

cyanarnofsky
Posts: 70
Joined: Tue Jul 31, 2012 11:33 pm

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Wed Sep 26, 2012 9:08 pm

The free webkiosk fails for me as Apache fails at startup everytime. Resulting in it failing to connect to local server :/ ?

themidithief
Posts: 3
Joined: Sat Sep 22, 2012 7:37 am

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Wed Sep 26, 2012 9:11 pm

Same for me with the webkiosk.

cyanarnofsky
Posts: 70
Joined: Tue Jul 31, 2012 11:33 pm

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Thu Sep 27, 2012 4:57 pm

I was informed that for some an ethernet connection begin present is needed or apache fails to load. Unfortunately that did not help me wired or wireless. Still getting failed start due to invalid ELF header. :\

Darron.Michael
Posts: 13
Joined: Thu Sep 27, 2012 7:39 pm

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Thu Sep 27, 2012 7:46 pm

I've downloaded 2012-08-16-wheezy-raspian.img and 2012-09-18-wheezy-raspbian.img.

I'll burn them both to SD's, and try the install for screenly-OSE again.

If they both work, then I'll make my required mods (VNC, etc) one at a time on each card and try to determine which is causing the problems with the server portion not allowing me to add content.

I'm kind of a n00b at this but but maybe I can help nail down whatever is causing the problem.

DM

Darron.Michael
Posts: 13
Joined: Thu Sep 27, 2012 7:39 pm

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Fri Sep 28, 2012 12:49 pm

I installed the 2012-09-18-wheezy-raspbian.img thusly...
fdisk to remove existing partitions on SD card
dd bs=4M if=~/2012-09-18-wheezy-raspbian.img of=/dev/sdX
sync
fdisk make partition bootable
sync
raspi-config menu
expand fs
reboot
<ctrl><alt><backspace> exits xserver = YES, locale=en_us.utf-8
reboot
Screenly OSE install
cd ~
sudo apt-get -y install git-core
sudo git clone git://github.com/wireload/screenly-ose.git ~/screenly
sudo ~/screenly/misc/install.sh
reboot

ERROR MESSAGE concerning loading the 127.0.0.1:8080/splash_page

Changes in overscan or memsplit value had no effect on preventing the apache error.

It seems that the 9/18 build isn't liking apache so far, and we need apache to work to support screenly-OSE.

8^(

Now for a similar attempt using the 2012-08-16-wheezy-raspbian.img. Unless someone can suggest how to get apache on its feet?

cyanarnofsky
Posts: 70
Joined: Tue Jul 31, 2012 11:33 pm

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Fri Sep 28, 2012 9:42 pm

I am alot of issues with Apache as well but using webkiosk image. I get the following error on boot:

“Starting web server: apache2/usr/sbin/apache2: error while loading shared libraries: /usr/lib/libapr~1.so.0: invalid ELF header”

“Action ‘start’ failed.”

Once booted I get error 127.0.0.1 cannot establish connection, obviously cause Apache never started. Tried both the free and "donation" version, had a bit of help from the creator but we both are coming to a end with no real solutions, just odd to me for a basic platform that something this basic would work on some and not others with exact same image... just seems like there couldnt be really any big different variables with such a basic system to me but obviously there is :p

trazer
Posts: 22
Joined: Fri Sep 28, 2012 2:32 pm

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Sat Sep 29, 2012 1:59 am

New here, but screenly sounds like exactly what I need/want out of the pi I have on its way right now. I need photos to go by on a screen. That's it. This will be a secondary screen in a kiosk just displaying images. The other one I ordered will likely be connected to a large HDTV at some point for the same thing. Adding via an IP on the network would be perfect. I'll be following this.

I have really simple needs, my other thought was to just use a photo screensaver and VNC in to add photos as needed. The pi will have no kb or mouse so maybe this is a viable solution for just static images? Regardless, my first pi shipped earlier today so I'll be playing with this soon I'm sure.

I'll try to just read and not ask super stupid questions, but wanted to say thanks for everyone's hard work on here!

emmebi
Posts: 10
Joined: Wed Aug 08, 2012 7:47 pm

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Sat Sep 29, 2012 9:58 pm

On some machines Apache 2 fails to start (mine works).
I'm building an image which makes use of Lighttpd instead of Apache.
Stay tuned...

axel-b
Posts: 1
Joined: Sun Sep 30, 2012 8:40 pm

Re: Screenly OSE -- Digital Signage for the Raspberry Pi

Sun Sep 30, 2012 9:03 pm

themidithief wrote:Any news on this? I tried installing screenly on two SD Cards (8gb and 16gb) and it didn't work I also tried installing the old Wheezy but I kept getting the same "Error 500: Internal Server Error" when saving assets to the database. Since it worked for me before I start questioning if the install is broken? Has anyone gotten Screenly to work well lately?
I installed Screenly without problems last week (thursday, friday).

I have been working on adding username/password authentication to Screenly,
where a username and a password can be configured in the screenly config file.
My work-in-progress is at my fork of screenly at github, in the auth branch.
( https://github.com/axel-b/screenly-ose/tree/auth )

Return to “Other projects”