Error after updating to the 10c9a69 version of Screenly-OSE

Hi there all,

We are using Raspberry PI’s and Baleno to show the marketing presentation in our stores. After we updated to release 10c9a69 all the devices malfunctioned. Anybody familiar with this problem, and know how the solve it?

Following loop is repeated

05.12.18 16:07:32 (+0100)  main  Dec 05 15:07:32 3fb8e2e systemd[1]: screenly-viewer.service: main process exited, code=exited, status=1/FAILURE
05.12.18 16:07:32 (+0100)  main  Dec 05 15:07:32 3fb8e2e systemd[1]: Unit screenly-viewer.service entered failed state.
05.12.18 16:07:32 (+0100)  main  Dec 05 15:07:32 3fb8e2e systemd[1]: screenly-viewer.service holdoff time over, scheduling restart.
05.12.18 16:07:32 (+0100)  main  Dec 05 15:07:32 3fb8e2e systemd[1]: Stopping Screenly Viewer...
05.12.18 16:07:32 (+0100)  main  Dec 05 15:07:32 3fb8e2e systemd[1]: Starting Screenly Viewer...
05.12.18 16:07:32 (+0100)  main  Dec 05 15:07:32 3fb8e2e systemd[1]: Started Screenly Viewer.
05.12.18 16:07:33 (+0100)  main  Dec 05 15:07:33 3fb8e2e python[9182]: /usr/local/lib/python2.7/dist-packages/cryptography/hazmat/bindings/openssl/binding.py:163: CryptographyDeprecationWarning: OpenSSL version 1.0.1 is no longer supported by the OpenSSL project, please upgrade. A future version of cryptography will drop support for it.
05.12.18 16:07:33 (+0100)  main  Dec 05 15:07:33 3fb8e2e python[9182]: utils.CryptographyDeprecationWarning
05.12.18 16:07:34 (+0100)  main  Dec 05 15:07:34 3fb8e2e python[9182]: browser found dead, restarting
05.12.18 16:07:34 (+0100)  main  Dec 05 15:07:34 3fb8e2e python[9182]: Loading browser...
05.12.18 16:07:34 (+0100)  main  Dec 05 15:07:34 3fb8e2e python[9182]: Browser loading file:///tmp/screenly_html/black_page.html. Running as PID 9194.
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: current url is file:///tmp/screenly_html/black_page.html
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: Generating asset-list...
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: Viewer crashed.
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: Traceback (most recent call last):
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: File "/home/pi/screenly/viewer.py", line 482, in <module>
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: main()
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: File "/home/pi/screenly/viewer.py", line 466, in main
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: scheduler = Scheduler()
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: File "/home/pi/screenly/viewer.py", line 125, in __init__
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: self.update_playlist()
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: File "/home/pi/screenly/viewer.py", line 169, in update_playlist
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: (new_assets, new_deadline) = generate_asset_list()
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: File "/home/pi/screenly/viewer.py", line 201, in generate_asset_list
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: assets = assets_helper.read(db_conn)
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: File "/home/pi/screenly/lib/assets_helper.py", line 97, in read
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: c.execute(queries.read_all(keys))
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: OperationalError: no such column: skip_asset_check
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: Traceback (most recent call last):
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: File "/home/pi/screenly/viewer.py", line 482, in <module>
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: main()
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: File "/home/pi/screenly/viewer.py", line 466, in main
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: scheduler = Scheduler()
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: File "/home/pi/screenly/viewer.py", line 125, in __init__
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: self.update_playlist()
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: File "/home/pi/screenly/viewer.py", line 169, in update_playlist
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: (new_assets, new_deadline) = generate_asset_list()
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: File "/home/pi/screenly/viewer.py", line 201, in generate_asset_list
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: assets = assets_helper.read(db_conn)
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: File "/home/pi/screenly/lib/assets_helper.py", line 97, in read
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: c.execute(queries.read_all(keys))
05.12.18 16:07:35 (+0100)  main  Dec 05 15:07:35 3fb8e2e python[9182]: sqlite3.OperationalError: no such column: skip_asset_check

Hi @ALLSAFE_IT, can you tell us a bit more about your situation:

What do you mean by Baleno? What’s the release that you mention? Is it one of your application releases? You pushed a new application version and have this error? It seems like an application error, and would depend on the code you pushed to the device.

Checking it further, you mean you are deploying the 10c9a69 version of Screenly-OSE on your device?

What was the previous version that worked?

It looks like an application problem, though, would be good to know more. Maybe @vpetersson have any possible insights?

Hi thnx for the reply.
We released indeed the 10c9a69 version of Screenly-OSE on our devices
The previous version was ‘df2252d’

@ALLSAFE_IT This certainly looks like an error in the screenly OSE software. It might be worth pinning the device to an earlier known-working release until this is resolved?

You can find more information on device pinning here: https://github.com/balena-io-projects/staged-releases