-
-
Notifications
You must be signed in to change notification settings - Fork 627
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
old asset is displayed until log in to config screen #207
Comments
alright, i can't get it to do this issue this morning. please mark this low priority until i can reliably get it to fail. |
ok, it seems to be, old asset is displayed on boot if new asset is not yet active. I think there was another issue similar to this, i'll look for it now |
@magnets99 Yes, I think you are referring to issue #209. That issue was fixed yesterday. Can you report back if that fixed your issue? |
Hi, On 04/07/14 14:28, Richard To wrote:
|
i've updated them, will report back if it happens again, but feel free to close this issue as duplicate. Thanks for your help! |
I've updated it using apt-get upgrade, but my error persists. How can i check to see what version i'm running, and what should i be runnning? |
@magnets99,
|
thank you! On 28/07/14 17:25, Viktor Petersson wrote:
|
yup, that seems to have fixed it! |
Great. |
so..... i'll try and get the log up now |
is this the right log? 192.168.0.12 - - [31/Jul/2014 09:27:22] "GET /api/assets HTTP/1.1" 200 627 Bottle v0.12.7 server starting up (using WSGIRefServer(fast=True))... Bottle v0.12.7 server starting up (using WSGIRefServer(fast=True))... 192.168.0.12 - - [04/Aug/2014 08:06:31] "GET / HTTP/1.1" 200 12418 |
from the screenly_viewer.log Fri, 01 Aug 2014 17:04:47 Showing asset fri (image) even though the playlist is empty, it's still showing Friday's asset. |
confirmed, if no new asset is loaded (not loaded but turned off). then the old asset is displayed even though it should not be. |
Hi @magnets99 Can you describe the steps to reproduce the bug? I'll try to see if I can reproduce it. EDIT: Looks like you described the steps in your initial message. Are the steps still the same? And is there a quicker way to reproduce the issue? |
not sure if there is a quicker way. basically the steps are: |
I didn't have time to run a longer test on my Raspberry Pi yet. But here is a test to try. Can you check if this shorter experiment works for you? I think this will help narrow down the possibilities a bit. I ran a quick test on laptop using the following settings:
The viewer displayed the asset within the time interval. Next I turned off the viewer and then turned it on again at 10:22AM. I got a black screen. Also here is the relevant part of my log:
|
@magnets99 / @richard-to - Actually, this might be related to the fact that the Pi doesn't have RTC. Hence if you power it off and then power it on later, the clock might be screwed up. Also, since the device doesn't have access to an NTP server (i presume), that might be the root cause and why you can't reproduce it. |
@magnets99 Are you able to reproduce this on the latest version? |
I've been running into this myself, and after the update I was still getting same behavior. |
@madcackler Interesting. Could you run the following and attach the file here?
Once done, could you attach the file here? That should help us troubleshoot the issue. |
Hi Viktor, just cathcing up on the other comments. The pi does access a NTP server on our internal lan. |
@magnets99 Got it. Yeah I would recommend running the device 24/7 regardless. Closing out issue. |
Dear sir, |
hi Dennis, |
bit of a weird one this:
When i turn on the pi's in the morning yesterdays asset is displayed until you log in into the config, then it immediately starts working again and the viewer log under system info gives the impression it was working all along.
But the actual image from yesterday is displayed. I think it may be something to do with the fact i turn the pi's off at night.
To reproduce:
make 2 images, we'll call them A and B
load them up into screenly with A showing until 11pm this evening. and B showing from 3am tomorrow. Switch them both on, A should move to the active section
turn your pi off via the cron command
01 17 * * * sudo /sbin/shutdown -h now
in the morning of the next day (AFTER 3am) turn on your pi and let it load without going into the management screen
Observed behavior (bug)
Sceernly will load up and show asset A. once you log into the management screen it will start showing b before you change anything
Expected Behavior
that a stops showing and b becomes active once ntp sync is complete.
notes:
tried on two different pi's, all pi's have access to local ntp server. Problem remains after at least 3 hours. all assets are images.
The text was updated successfully, but these errors were encountered: