Screenly Forum

Little startup error

hi there…

i was eager to run a small info screen for some pictures and scedules. screenly looks perfect for this.
i had already a Pi Zero WH Rev 1.1 and used this one.

i tried some weeks ago, but running on splash-screen error during boot up:

Problem occurred while loading the URL http://127.0.0.1:8080/splash_page could not connect: connection refused

this stays for half a minute and then starts normally to switch through the configured assets as nothing happend.

reflashing the sd doesnt help, tried dozen time. i did only minimal steps:

  • flash with balena Etcher 2019-09-25-Screenly-OSE-lite.img (checked with md5)
  • set wifi connection
  • run raspi-config and changed timezone, keyboard layout and wifi country. activate ssh
  • removed all assets and uploaded a small png image
  • restart

journalctl:

Oct 17 11:44:23 raspberrypi systemd[1]: Started Screenly Viewer.
Oct 17 11:44:23 raspberrypi systemd[1]: Starting Hold until boot process finishes up...
Oct 17 11:44:24 raspberrypi systemd[1]: Starting Terminate Plymouth Boot Screen...
Oct 17 11:44:25 raspberrypi systemd[1]: Received SIGRTMIN+20 from PID 130 (plymouthd).
Oct 17 11:44:27 raspberrypi systemd[1]: Reloading OpenBSD Secure Shell server.
Oct 17 11:44:28 raspberrypi sshd[341]: Received SIGHUP; restarting.
Oct 17 11:44:28 raspberrypi systemd[1]: Reloaded OpenBSD Secure Shell server.
Oct 17 11:44:29 raspberrypi sshd[341]: Server listening on 0.0.0.0 port 22.
Oct 17 11:44:29 raspberrypi sshd[341]: Server listening on :: port 22.
Oct 17 11:44:44 raspberrypi systemd[1]: plymouth-quit.service: Start operation timed out. Terminating.
Oct 17 11:44:44 raspberrypi systemd[1]: Failed to start Terminate Plymouth Boot Screen.
Oct 17 11:44:44 raspberrypi systemd[1]: plymouth-quit.service: Unit entered failed state.
Oct 17 11:44:44 raspberrypi systemd[1]: plymouth-quit.service: Failed with result 'timeout'.
Oct 17 11:44:51 raspberrypi rabbitmq[319]: Waiting for rabbit@raspberrypi ...
Oct 17 11:44:51 raspberrypi rabbitmq[319]: pid is 331 ...
Oct 17 11:44:58 raspberrypi systemd[1]: Received SIGRTMIN+21 from PID 130 (plymouthd).
Oct 17 11:44:58 raspberrypi systemd[1]: Started Hold until boot process finishes up.
Oct 17 11:44:58 raspberrypi systemd[1]: Started Getty on tty1.
Oct 17 11:44:58 raspberrypi systemd[1]: Reached target Login Prompts.
Oct 17 11:45:01 raspberrypi systemd[1]: Reloading OpenBSD Secure Shell server.
Oct 17 11:45:02 raspberrypi sshd[341]: Received SIGHUP; restarting.
Oct 17 11:45:02 raspberrypi systemd[1]: Reloaded OpenBSD Secure Shell server.
Oct 17 11:45:02 raspberrypi sshd[341]: Server listening on 0.0.0.0 port 22.
Oct 17 11:45:02 raspberrypi sshd[341]: Server listening on :: port 22.
Oct 17 11:45:27 raspberrypi systemd[1]: rabbitmq-server.service: Start-post operation timed out. Stopping.
Oct 17 11:45:28 raspberrypi systemd[1]: Failed to start RabbitMQ Messaging Server.
Oct 17 11:45:28 raspberrypi systemd[1]: rabbitmq-server.service: Unit entered failed state.
Oct 17 11:45:28 raspberrypi systemd[1]: rabbitmq-server.service: Failed with result 'timeout'.
Oct 17 11:45:28 raspberrypi systemd[1]: Started Screenly celery worker.
Oct 17 11:45:38 raspberrypi python[786]: /usr/local/lib/python2.7/dist-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.1) or chardet (3.0.4) doesn't match a supported version!
Oct 17 11:45:38 raspberrypi python[786]:   RequestsDependencyWarning)
Oct 17 11:45:42 raspberrypi python[627]: /usr/local/lib/python2.7/dist-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.1) or chardet (3.0.4) doesn't match a supported version!
Oct 17 11:45:42 raspberrypi python[627]:   RequestsDependencyWarning)
Oct 17 11:45:57 raspberrypi systemd[1]: Started Wifi Connect.
Oct 17 11:45:57 raspberrypi systemd[1]: Reached target Multi-User System.
Oct 17 11:45:57 raspberrypi systemd[1]: Reached target Graphical Interface.
Oct 17 11:45:57 raspberrypi systemd[1]: Starting Update UTMP about System Runlevel Changes...
Oct 17 11:45:58 raspberrypi systemd[1]: Started Update UTMP about System Runlevel Changes.
Oct 17 11:45:58 raspberrypi systemd[1]: Startup finished in 1.743s (kernel) + 2min 19.807s (userspace) = 2min 21.550s.
Oct 17 11:46:03 raspberrypi python[786]: Generating asset-list...
Oct 17 11:46:05 raspberrypi python[786]: browser found dead, restarting
Oct 17 11:46:05 raspberrypi python[786]: Loading browser...
Oct 17 11:46:05 raspberrypi python[786]: Browser loading http://127.0.0.1:8080/splash-page. Running as PID 1007.
Oct 17 11:46:13 raspberrypi python[786]: current url is http://127.0.0.1:8080/splash-page
Oct 17 11:46:14 raspberrypi python[764]: /usr/local/lib/python2.7/dist-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.1) or chardet (3.0.4) doesn't match a supported version!
Oct 17 11:46:14 raspberrypi python[764]:   RequestsDependencyWarning)
Oct 17 11:46:25 raspberrypi python[764]: [2019-10-17 11:46:25 +0000] [764] [INFO] Starting gunicorn 19.8.1
Oct 17 11:46:25 raspberrypi python[764]: [2019-10-17 11:46:25 +0000] [764] [INFO] Listening at: http://127.0.0.1:8080 (764)
Oct 17 11:46:25 raspberrypi python[764]: [2019-10-17 11:46:25 +0000] [764] [INFO] Using worker: threads
Oct 17 11:46:25 raspberrypi python[764]: [2019-10-17 11:46:25 +0000] [1023] [INFO] Booting worker with pid: 1023
Oct 17 11:46:35 raspberrypi celery[981]: /usr/local/lib/python2.7/dist-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.1) or chardet (3.0.4) doesn't match a supported version!
Oct 17 11:46:35 raspberrypi celery[981]:   RequestsDependencyWarning)
Oct 17 11:46:43 raspberrypi celery[981]: [2019-10-17 11:46:43,367: INFO/Beat] beat: Starting...
Oct 17 11:46:44 raspberrypi celery[981]: [2019-10-17 11:46:44,433: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:46:44 raspberrypi celery[981]: Trying again in 2.00 seconds...
Oct 17 11:46:46 raspberrypi celery[981]: [2019-10-17 11:46:46,731: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:46:46 raspberrypi celery[981]: Trying again in 4.00 seconds...
Oct 17 11:46:51 raspberrypi celery[981]: [2019-10-17 11:46:51,003: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:46:51 raspberrypi celery[981]: Trying again in 6.00 seconds...
Oct 17 11:46:57 raspberrypi celery[981]: [2019-10-17 11:46:57,308: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:46:57 raspberrypi celery[981]: Trying again in 8.00 seconds...
Oct 17 11:47:05 raspberrypi celery[981]: [2019-10-17 11:47:05,600: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:47:05 raspberrypi celery[981]: Trying again in 10.00 seconds...
Oct 17 11:47:14 raspberrypi python[786]: current url is file:///tmp/screenly_html/black_page.html
Oct 17 11:47:14 raspberrypi python[786]: Showing asset test.png (image)
Oct 17 11:47:15 raspberrypi python[786]: Sleeping for 300
Oct 17 11:47:16 raspberrypi celery[981]: [2019-10-17 11:47:16,199: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:47:16 raspberrypi celery[981]: Trying again in 12.00 seconds...
Oct 17 11:47:28 raspberrypi celery[981]: [2019-10-17 11:47:28,491: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:47:28 raspberrypi celery[981]: Trying again in 14.00 seconds...
Oct 17 11:47:42 raspberrypi celery[981]: [2019-10-17 11:47:42,756: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:47:42 raspberrypi celery[981]: Trying again in 16.00 seconds...
Oct 17 11:47:59 raspberrypi celery[981]: [2019-10-17 11:47:59,023: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:47:59 raspberrypi celery[981]: Trying again in 18.00 seconds...
Oct 17 11:48:17 raspberrypi celery[981]: [2019-10-17 11:48:17,325: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:48:17 raspberrypi celery[981]: Trying again in 20.00 seconds...
Oct 17 11:48:37 raspberrypi celery[981]: [2019-10-17 11:48:37,821: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:48:37 raspberrypi celery[981]: Trying again in 22.00 seconds...
Oct 17 11:49:00 raspberrypi celery[981]: [2019-10-17 11:49:00,104: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:49:00 raspberrypi celery[981]: Trying again in 24.00 seconds...
Oct 17 11:49:24 raspberrypi celery[981]: [2019-10-17 11:49:24,429: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:49:24 raspberrypi celery[981]: Trying again in 26.00 seconds...
Oct 17 11:49:50 raspberrypi celery[981]: [2019-10-17 11:49:50,742: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:49:50 raspberrypi celery[981]: Trying again in 28.00 seconds...
Oct 17 11:50:19 raspberrypi celery[981]: [2019-10-17 11:50:19,069: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:50:19 raspberrypi celery[981]: Trying again in 30.00 seconds...
Oct 17 11:50:49 raspberrypi celery[981]: [2019-10-17 11:50:49,373: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:50:49 raspberrypi celery[981]: Trying again in 32.00 seconds...
Oct 17 11:51:21 raspberrypi celery[981]: [2019-10-17 11:51:21,691: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:51:21 raspberrypi celery[981]: Trying again in 32.00 seconds...
Oct 17 11:51:54 raspberrypi celery[981]: [2019-10-17 11:51:54,025: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:51:54 raspberrypi celery[981]: Trying again in 32.00 seconds...
Oct 17 11:52:15 raspberrypi python[786]: Showing asset test.png (image)
Oct 17 11:52:15 raspberrypi python[786]: Sleeping for 300
Oct 17 11:52:26 raspberrypi celery[981]: [2019-10-17 11:52:26,332: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 11:52:26 raspberrypi celery[981]: Trying again in 32.00 seconds...
...
...
...
Oct 17 12:12:12 raspberrypi celery[981]: [2019-10-17 12:12:12,461: ERROR/Beat] beat: Connection error: [Errno 111] Connection refused. Trying again in 2.0 seconds...
Oct 17 12:12:14 raspberrypi celery[981]: [2019-10-17 12:12:14,777: ERROR/Beat] beat: Connection error: [Errno 111] Connection refused. Trying again in 4.0 seconds...
Oct 17 12:12:16 raspberrypi python[786]: Showing asset test.png (image)
Oct 17 12:12:16 raspberrypi python[786]: Sleeping for 300
Oct 17 12:12:19 raspberrypi celery[981]: [2019-10-17 12:12:19,107: ERROR/Beat] beat: Connection error: [Errno 111] Connection refused. Trying again in 6.0 seconds...
Oct 17 12:12:22 raspberrypi celery[981]: [2019-10-17 12:12:22,014: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 12:12:22 raspberrypi celery[981]: Trying again in 32.00 seconds...
Oct 17 12:12:25 raspberrypi celery[981]: [2019-10-17 12:12:25,408: ERROR/Beat] beat: Connection error: [Errno 111] Connection refused. Trying again in 8.0 seconds...
Oct 17 12:12:33 raspberrypi celery[981]: [2019-10-17 12:12:33,709: ERROR/Beat] beat: Connection error: [Errno 111] Connection refused. Trying again in 10.0 seconds...
Oct 17 12:12:44 raspberrypi celery[981]: [2019-10-17 12:12:44,042: ERROR/Beat] beat: Connection error: [Errno 111] Connection refused. Trying again in 12.0 seconds...
Oct 17 12:12:54 raspberrypi celery[981]: [2019-10-17 12:12:54,328: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 12:12:54 raspberrypi celery[981]: Trying again in 32.00 seconds...
Oct 17 12:12:56 raspberrypi celery[981]: [2019-10-17 12:12:56,369: ERROR/Beat] beat: Connection error: [Errno 111] Connection refused. Trying again in 14.0 seconds...
Oct 17 12:13:10 raspberrypi celery[981]: [2019-10-17 12:13:10,695: ERROR/Beat] beat: Connection error: [Errno 111] Connection refused. Trying again in 16.0 seconds...
Oct 17 12:13:26 raspberrypi celery[981]: [2019-10-17 12:13:26,630: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 12:13:26 raspberrypi celery[981]: Trying again in 32.00 seconds...
Oct 17 12:13:26 raspberrypi celery[981]: [2019-10-17 12:13:26,989: ERROR/Beat] beat: Connection error: [Errno 111] Connection refused. Trying again in 18.0 seconds...
Oct 17 12:13:45 raspberrypi celery[981]: [2019-10-17 12:13:45,306: ERROR/Beat] beat: Connection error: [Errno 111] Connection refused. Trying again in 20.0 seconds...
Oct 17 12:13:58 raspberrypi celery[981]: [2019-10-17 12:13:58,966: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 12:13:58 raspberrypi celery[981]: Trying again in 32.00 seconds...
Oct 17 12:14:05 raspberrypi celery[981]: [2019-10-17 12:14:05,656: ERROR/Beat] beat: Connection error: [Errno 111] Connection refused. Trying again in 22.0 seconds...
Oct 17 12:14:27 raspberrypi celery[981]: [2019-10-17 12:14:27,986: ERROR/Beat] beat: Connection error: [Errno 111] Connection refused. Trying again in 24.0 seconds...
Oct 17 12:14:31 raspberrypi celery[981]: [2019-10-17 12:14:31,292: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 12:14:31 raspberrypi celery[981]: Trying again in 32.00 seconds...
Oct 17 12:14:52 raspberrypi celery[981]: [2019-10-17 12:14:52,315: ERROR/Beat] beat: Connection error: [Errno 111] Connection refused. Trying again in 26.0 seconds...
Oct 17 12:15:03 raspberrypi celery[981]: [2019-10-17 12:15:03,596: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 12:15:03 raspberrypi celery[981]: Trying again in 32.00 seconds...
...
...
...
Oct 17 12:36:36 raspberrypi celery[981]: Traceback (most recent call last):
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/celery/worker/worker.py", line 205, in start
Oct 17 12:36:36 raspberrypi celery[981]:     self.blueprint.start(self)
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/celery/bootsteps.py", line 119, in start
Oct 17 12:36:36 raspberrypi celery[981]:     step.start(parent)
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/celery/bootsteps.py", line 369, in start
Oct 17 12:36:36 raspberrypi celery[981]:     return self.obj.start()
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/celery/worker/consumer/consumer.py", line 317, in start
Oct 17 12:36:36 raspberrypi celery[981]:     blueprint.start(self)
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/celery/bootsteps.py", line 119, in start
Oct 17 12:36:36 raspberrypi celery[981]:     step.start(parent)
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/celery/worker/consumer/connection.py", line 23, in start
Oct 17 12:36:36 raspberrypi celery[981]:     c.connection = c.connect()
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/celery/worker/consumer/consumer.py", line 404, in connect
Oct 17 12:36:36 raspberrypi celery[981]:     conn = self.connection_for_read(heartbeat=self.amqheartbeat)
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/celery/worker/consumer/consumer.py", line 411, in connection_for_read
Oct 17 12:36:36 raspberrypi celery[981]:     self.app.connection_for_read(heartbeat=heartbeat))
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/celery/worker/consumer/consumer.py", line 435, in ensure_connected
Oct 17 12:36:36 raspberrypi celery[981]:     callback=maybe_shutdown,
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/kombu/connection.py", line 428, in ensure_connection
Oct 17 12:36:36 raspberrypi celery[981]:     callback, timeout=timeout)
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/lib/python2.7/contextlib.py", line 35, in __exit__
Oct 17 12:36:36 raspberrypi celery[981]:     self.gen.throw(type, value, traceback)
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/kombu/connection.py", line 442, in _reraise_as_library_errors
Oct 17 12:36:36 raspberrypi celery[981]:     sys.exc_info()[2])
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/kombu/connection.py", line 437, in _reraise_as_library_errors
Oct 17 12:36:36 raspberrypi celery[981]:     yield
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/kombu/connection.py", line 428, in ensure_connection
Oct 17 12:36:36 raspberrypi celery[981]:     callback, timeout=timeout)
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/kombu/utils/functional.py", line 343, in retry_over_time
Oct 17 12:36:36 raspberrypi celery[981]:     return fun(*args, **kwargs)
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/kombu/connection.py", line 281, in connect
Oct 17 12:36:36 raspberrypi celery[981]:     return self.connection
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/kombu/connection.py", line 829, in connection
Oct 17 12:36:36 raspberrypi celery[981]:     self._connection = self._establish_connection()
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/kombu/connection.py", line 784, in _establish_connection
Oct 17 12:36:36 raspberrypi celery[981]:     conn = self.transport.establish_connection()
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/kombu/transport/pyamqp.py", line 130, in establish_connection
Oct 17 12:36:36 raspberrypi celery[981]:     conn.connect()
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/amqp/connection.py", line 311, in connect
Oct 17 12:36:36 raspberrypi celery[981]:     self.transport.connect()
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/amqp/transport.py", line 77, in connect
Oct 17 12:36:36 raspberrypi celery[981]:     self._connect(self.host, self.port, self.connect_timeout)
Oct 17 12:36:36 raspberrypi celery[981]:   File "/usr/local/lib/python2.7/dist-packages/amqp/transport.py", line 148, in _connect
Oct 17 12:36:36 raspberrypi celery[981]:     "failed to resolve broker hostname"))
Oct 17 12:36:36 raspberrypi celery[981]: OperationalError: [Errno 111] Connection refused
Oct 17 12:36:37 raspberrypi celery[981]: [2019-10-17 12:36:37,416: INFO/MainProcess] beat: Shutting down...
Oct 17 12:36:37 raspberrypi celery[981]:
Oct 17 12:36:37 raspberrypi celery[981]:  -------------- worker@screenly v4.2.1 (windowlicker)
Oct 17 12:36:37 raspberrypi celery[981]: ---- **** -----
Oct 17 12:36:37 raspberrypi celery[981]: --- * ***  * -- Linux-4.19.66+-armv6l-with-debian-9.11 2019-10-17 11:46:42
Oct 17 12:36:37 raspberrypi celery[981]: -- * - **** ---
Oct 17 12:36:37 raspberrypi celery[981]: - ** ---------- [config]
Oct 17 12:36:37 raspberrypi celery[981]: - ** ---------- .> app:         server:0xb4c8df10
Oct 17 12:36:37 raspberrypi celery[981]: - ** ---------- .> transport:   amqp://guest:**@localhost:5672//
Oct 17 12:36:37 raspberrypi celery[981]: - ** ---------- .> results:     rpc://
Oct 17 12:36:37 raspberrypi celery[981]: - *** --- * --- .> concurrency: 1 (prefork)
Oct 17 12:36:37 raspberrypi celery[981]: -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
Oct 17 12:36:37 raspberrypi celery[981]: --- ***** -----
Oct 17 12:36:37 raspberrypi celery[981]:  -------------- [queues]
Oct 17 12:36:37 raspberrypi celery[981]:                 .> celery           exchange=celery(direct) key=celery
Oct 17 12:36:37 raspberrypi celery[981]:
Oct 17 12:36:37 raspberrypi celery[981]: [tasks]
Oct 17 12:36:37 raspberrypi celery[981]:   . server.append_usb_assets
Oct 17 12:36:37 raspberrypi celery[981]:   . server.cleanup
Oct 17 12:36:37 raspberrypi celery[981]:   . server.cleanup_usb_assets
Oct 17 12:36:37 raspberrypi celery[981]:   . server.reboot_screenly
Oct 17 12:36:37 raspberrypi celery[981]:   . server.remove_usb_assets
Oct 17 12:36:37 raspberrypi celery[981]:   . server.shutdown_screenly
Oct 17 12:36:37 raspberrypi celery[981]:   . server.upgrade_screenly
Oct 17 12:36:38 raspberrypi systemd[1]: screenly-celery.service: Main process exited, code=exited, status=1/FAILURE
Oct 17 12:36:38 raspberrypi systemd[1]: screenly-celery.service: Unit entered failed state.
Oct 17 12:36:38 raspberrypi systemd[1]: screenly-celery.service: Failed with result 'exit-code'.
Oct 17 12:36:43 raspberrypi systemd[1]: screenly-celery.service: Service hold-off time over, scheduling restart.
Oct 17 12:36:43 raspberrypi systemd[1]: Stopped Screenly celery worker.
Oct 17 12:36:43 raspberrypi systemd[1]: Started Screenly celery worker.
Oct 17 12:37:15 raspberrypi celery[1243]: /usr/local/lib/python2.7/dist-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.1) or chardet (3.0.4) doesn't match a supported version!
Oct 17 12:37:15 raspberrypi celery[1243]:   RequestsDependencyWarning)
Oct 17 12:37:18 raspberrypi python[786]: Showing asset test.png (image)
Oct 17 12:37:18 raspberrypi python[786]: Sleeping for 300
Oct 17 12:37:23 raspberrypi celery[1243]: [2019-10-17 12:37:23,304: INFO/Beat] beat: Starting...
Oct 17 12:37:24 raspberrypi celery[1243]: [2019-10-17 12:37:24,481: ERROR/Beat] beat: Connection error: [Errno 111] Connection refused. Trying again in 2.0 seconds...
Oct 17 12:37:24 raspberrypi celery[1243]: [2019-10-17 12:37:24,578: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 12:37:24 raspberrypi celery[1243]: Trying again in 2.00 seconds...
Oct 17 12:37:26 raspberrypi celery[1243]: [2019-10-17 12:37:26,924: ERROR/Beat] beat: Connection error: [Errno 111] Connection refused. Trying again in 4.0 seconds...
Oct 17 12:37:27 raspberrypi celery[1243]: [2019-10-17 12:37:27,057: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Oct 17 12:37:27 raspberrypi celery[1243]: Trying again in 4.00 seconds...

i have placed the splash-page (http://127.0.0.1:8080/splash-page) in the assets and it show up without problem.
does anyone know, how to fix this?

thnx for any help.

hmm… those timeouts are weird… i’ll try to replicate by using the exact image you used…

can you tell me exactly where you got the 9-25 image with the “lite” option from? i cant see it on the sprint assets:

thnx for the answer.

the lite image is inside the 2019-09-25-Screenly-OSE.zip
i have extracted it, after got a not booting system after first flashing.

ok… i did: sudo apt-get update, sudo apt-get upgrade
and gave all services and docker, cause of my slow pi zero, a bit more time to start up
by setting DefaultTimeoutStartSec=180s
so i got rid permanently of the error (rabbitmq-server.service) and sometimes of the error (plymouth-quit.service) in the log above and all follow ups, caused by rabbitmq not running.

but i get still the splash-screen error.

without looking into it too much i would think the splash error is simply because the web server hasn’t loaded/started at the exact moment when the viewer tries to connect to that default splash page…

yeah… it wouldnt be a problem, if it does show the error page and later goes on to the schedule. but sometimes it just stays at the error page and does nothing (maybe waiting that someone is press the “retry”).

(took me some days to test arround)

to speed things up, i switched to static ip with NetworkManagers mncli

here some systemd-analyze:
blame (plymouth takes really long… and still wifi with static ip too)

2min 57.106s wifi-connect.service
1min 41.998s rabbitmq-server.service
     32.692s plymouth-quit-wait.service
     23.687s networking.service
     22.645s raspi-config.service
     20.153s plymouth-quit.service
      8.858s screenly-web.service
      8.574s NetworkManager-wait-online.service
      8.137s dev-mmcblk0p2.device
      6.353s hciuart.service
      5.010s ModemManager.service
      4.260s screenly-viewer.service
      4.057s NetworkManager.service
      3.918s systemd-logind.service
      3.701s keyboard-setup.service
      3.147s ssh.service
      3.016s nginx.service
      2.697s alsa-restore.service
      2.461s wifi-country.service
      2.438s pppd-dns.service
      2.253s wpa_supplicant.service
      1.993s rc-local.service
      1.804s triggerhappy.service
      1.800s polkit.service
      1.798s user@1000.service
      1.707s systemd-udev-trigger.service
      1.605s systemd-rfkill.service
      1.597s systemd-user-sessions.service
      1.497s systemd-udevd.service
      1.355s systemd-timesyncd.service
      1.309s systemd-journald.service
      1.236s avahi-daemon.service
      1.035s systemd-fsck-root.service
       913ms systemd-tmpfiles-setup.service
       776ms systemd-fsck@dev-disk-by\x2dpartuuid-b26b9e73\x2d01.service
       760ms fake-hwclock.service
       718ms kmod-static-nodes.service
       696ms systemd-remount-fs.service
       647ms rsyslog.service
       646ms sys-kernel-debug.mount
       599ms systemd-update-utmp.service
       571ms bluetooth.service
       557ms dev-mqueue.mount
       548ms systemd-tmpfiles-setup-dev.service
       459ms systemd-journal-flush.service
       430ms console-setup.service
       411ms sys-kernel-config.mount
       407ms nfs-config.service
       384ms run-rpc_pipefs.mount
       356ms systemd-sysctl.service
       341ms plymouth-read-write.service
       335ms systemd-modules-load.service
       320ms systemd-random-seed.service
       317ms systemd-update-utmp-runlevel.service
       253ms boot.mount
       230ms plymouth-start.service

critical-chain has nothing special…

but dmesg showed me some problems

...
[   13.367704 <    1.339146>] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[   13.420802 <    0.053098>] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   13.421298 <    0.000496>] usbcore: registered new interface driver brcmfmac
[   13.859483 <    0.438185>] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   13.859710 <    0.000227>] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[   13.861134 <    0.001424>] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f
[   15.895944 <    2.034810>] uart-pl011 20201000.serial: no DMA platform data
[   20.790403 <    4.894459>] Bluetooth: Core ver 2.22
[   20.790591 <    0.000188>] NET: Registered protocol family 31
[   20.790606 <    0.000015>] Bluetooth: HCI device and connection manager initialized
[   20.790643 <    0.000037>] Bluetooth: HCI socket layer initialized
[   20.790666 <    0.000023>] Bluetooth: L2CAP socket layer initialized
[   20.790757 <    0.000091>] Bluetooth: SCO socket layer initialized
[   20.898183 <    0.107426>] Bluetooth: HCI UART driver ver 2.3
[   20.898206 <    0.000023>] Bluetooth: HCI UART protocol H4 registered
[   20.912120 <    0.013914>] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   20.924462 <    0.012342>] Bluetooth: HCI UART protocol Broadcom registered
[   25.717886 <    4.793424>] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   25.717909 <    0.000023>] Bluetooth: BNEP filters: protocol multicast
[   25.717947 <    0.000038>] Bluetooth: BNEP socket layer initialized
[   29.298684 <    3.580737>] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   29.353023 <    0.054339>] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   29.353054 <    0.000031>] brcmfmac: power management disabled
[   29.915899 <    0.562845>] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   29.915956 <    0.000057>] brcmfmac: power management disabled
[   30.741453 <    0.825497>] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   32.732073 <    1.990620>] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   32.732131 <    0.000058>] brcmfmac: power management disabled
[   35.845900 <    3.113769>] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   36.939294 <    1.093394>] brcmfmac: power management disabled
[  203.893184 <  166.953890>] random: crng init done

for the last one i got this solution from here

i m not using ip6 on the local network, so i did:
add in /boot/cmdline.txt

ipv6.disable=1

add in /etc/modprobe.d/ipv6.conf

# uncommented
alias ipv6 off
# added
options ipv6 disable_ipv6=1
# this is needed for not loading ipv6 driver 
blacklist ipv6

this made a little error with the neighbor discovery, but can be removed in nmcli by changing ipv6.method to ignore

both changes took effect to speed up drastically boot time


now dmesg and systemd-analyse look like

[   14.329668 <    1.105036>] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[   14.363047 <    0.033379>] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   14.365238 <    0.002191>] usbcore: registered new interface driver brcmfmac
[   14.741526 <    0.376288>] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   14.741754 <    0.000228>] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[   14.743044 <    0.001290>] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f
[   18.057946 <    3.314902>] uart-pl011 20201000.serial: no DMA platform data
[   22.726007 <    4.668061>] Bluetooth: Core ver 2.22
[   22.726142 <    0.000135>] NET: Registered protocol family 31
[   22.726152 <    0.000010>] Bluetooth: HCI device and connection manager initialized
[   22.726181 <    0.000029>] Bluetooth: HCI socket layer initialized
[   22.726195 <    0.000014>] Bluetooth: L2CAP socket layer initialized
[   22.726252 <    0.000057>] Bluetooth: SCO socket layer initialized
[   22.778687 <    0.052435>] Bluetooth: HCI UART driver ver 2.3
[   22.778708 <    0.000021>] Bluetooth: HCI UART protocol H4 registered
[   22.803433 <    0.024725>] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   22.808474 <    0.005041>] Bluetooth: HCI UART protocol Broadcom registered
[   29.768528 <    6.960054>] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   29.768541 <    0.000013>] Bluetooth: BNEP filters: protocol multicast
[   29.768566 <    0.000025>] Bluetooth: BNEP socket layer initialized
[   34.177990 <    4.409424>] brcmfmac: power management disabled
[   34.735458 <    0.557468>] brcmfmac: power management disabled
[   34.800809 <    0.065351>] brcmfmac: power management disabled
[   38.380467 <    3.579658>] brcmfmac: power management disabled
[   53.402240 <   15.021773>] random: crng init done
[   53.402261 <    0.000021>] random: 1 urandom warning(s) missed due to ratelimiting

1min 49.919s rabbitmq-server.service
1min 42.750s wifi-connect.service
     10.280s NetworkManager-wait-online.service
     10.042s screenly-web.service
      8.559s dev-mmcblk0p2.device
      8.266s ModemManager.service
      8.009s networking.service
      6.075s hciuart.service
      4.826s systemd-logind.service
      4.174s NetworkManager.service
      3.348s rsyslog.service
      3.102s wpa_supplicant.service
      2.953s avahi-daemon.service
      2.916s ssh.service
      2.712s polkit.service
      2.686s keyboard-setup.service
      2.648s raspi-config.service
      2.574s nginx.service
      2.206s systemd-rfkill.service
      1.692s pppd-dns.service
      1.613s screenly-viewer.service
      1.536s systemd-timesyncd.service
      1.520s systemd-udev-trigger.service
      1.518s systemd-udevd.service
      1.515s systemd-fsck-root.service
      1.347s user@1000.service
      1.326s triggerhappy.service
      1.304s rc-local.service
      1.237s systemd-journald.service
      1.188s systemd-user-sessions.service
      1.022s alsa-restore.service
       946ms systemd-tmpfiles-setup.service
       931ms systemd-tmpfiles-setup-dev.service
       812ms kmod-static-nodes.service
       783ms systemd-fsck@dev-disk-by\x2dpartuuid-b26b9e73\x2d01.service
       773ms systemd-update-utmp.service
       749ms wifi-country.service
       663ms bluetooth.service
       661ms systemd-modules-load.service
       641ms systemd-remount-fs.service
       638ms fake-hwclock.service
       554ms run-rpc_pipefs.mount
       476ms sys-kernel-config.mount
       465ms systemd-journal-flush.service
       449ms plymouth-quit-wait.service
       419ms systemd-update-utmp-runlevel.service
       380ms plymouth-read-write.service
       362ms console-setup.service
       355ms dev-mqueue.mount
       349ms nfs-config.service
       332ms systemd-random-seed.service
       312ms systemd-sysctl.service
       256ms sys-kernel-debug.mount
       246ms plymouth-quit.service
       239ms plymouth-start.service
       225ms boot.mount
       208ms systemd-tmpfiles-clean.service

anyway… dont know what to do with the brcmfmac error and as well how to get away the error screen. here are the two relevant parts in the log:

Oct 25 18:49:53 raspberrypi kernel: brcmfmac: F1 signature read @0x18000000=0x1541a9a6
Oct 25 18:49:53 raspberrypi kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
Oct 25 18:49:53 raspberrypi kernel: usbcore: registered new interface driver brcmfmac
Oct 25 18:49:54 raspberrypi kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
Oct 25 18:49:54 raspberrypi kernel: brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
Oct 25 18:49:54 raspberrypi kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f

Oct 25 18:52:27 raspberrypi systemd[1]: Startup finished in 1.601s (kernel) + 2min 34.388s (userspace) = 2min 35.990s.
Oct 25 18:52:28 raspberrypi python[767]: Generating asset-list…
Oct 25 18:52:30 raspberrypi python[767]: browser found dead, restarting
Oct 25 18:52:30 raspberrypi python[767]: Loading browser…
Oct 25 18:52:30 raspberrypi python[767]: Browser loading http://127.0.0.1:8080/splash-page. Running as PID 979.
Oct 25 18:52:39 raspberrypi python[767]: current url is http://127.0.0.1:8080/splash-page
Oct 25 18:52:40 raspberrypi python[748]: /usr/local/lib/python2.7/dist-packages/requests/init.py:91: RequestsDependencyWarning: urllib3 (1.25.1) or chardet (3.0.4) doesn’t match a supported version!

have a nice weekend :wink: and thnx for the help

In order to not get too crazy troubleshooting this I’ll just mention few things:

  1. rabbitmq-server has been replaced with redis, you should run ./screenly/bin/install.sh to reinstall with latest changes by selecting the development branch/version.

  2. disabling ipv6 should have simply been done in /etc/sysctl.conf and it would have disabled it without the need for those extra steps.

  3. the brcmf errors are broadcom drivers and there is nothing you need to do about it, unless you want to go and find the linux kernels for the firmware and replace it with one that doesnt give that error, which as far as i know it doesnt affect the booting process at all…

hope that helps, took long to reply because been super busy.

hi there,
thanks for the answer.

for the moment this project has been put on hold from my friend as a result of the delay in progress.
someone tried to convince him to use yodeck.
as soon as i get time, i ll come back. still want to get it running… i prefer a local solution instead of a cloud one.

you can close this thread.

Gotcha.
I think threads just stay for record keeping so no need to delete/close, unless an admin wants to do it…

ok, got the opportunity to give ./screenly/bin/install.sh a try.

tried two times… but i hangs at “building wheels for cffi (setup.py)” more than a hour till its not reacting anymore.

so i did a fresh flash install and only this steps:

  • first run set wifi -reboot
  • changed pass
  • sudo apt-get update
  • sudo apt-get upgrade
  • ./screenly/bin/install.sh no experimental. yes dev, no wott, yes network management, no upgrade

this time it passes cffi setup
but stop with a error “cant not allocate memory”
at sudo -u ansible localhost -m git -a …

did the flashing and steps again, same error.

looks like pi zero isnt working any longer for screenly.
can you confirm this.

so… back to the first problem. i would be fine with the production branch if the connection error disappears.

Nov 27 09:35:01 screenly python[491]: browser found dead, restarting
Nov 27 09:35:01 screenly python[491]: Loading browser...
Nov 27 09:35:01 screenly python[491]: Browser loading http://127.0.0.1:8080/splash-page. Running as PID 609.
Nov 27 09:35:10 screenly python[491]: current url is http://127.0.0.1:8080/splash-page
Nov 27 09:35:16 screenly python[461]: [2019-11-27 09:35:16 +0000] [461] [INFO] Starting gunicorn 19.8.1

can you tell me, where i can find the start up script.
and maybe how to put a delay (>16sec would be enough, as you can see) before the browser is loading the splash-screen.

thanks

ps:
btw. i got the update to development branch to finish successful
by killing serveral times X to have enough mem.
it stopped finally at sudo -E ansible-playbook site.yml --skip-tags enable-ssl,system-upgrade
somewhere by pip dependecies … no progress over night
i just restarted and run this and the follow up commands in install.sh manually
but i am getting here the same problem as in the production branch.

sorry was busy for a while…

regarding the delay for the viewer, this might need some service tuning, which means you would go into /etc/systemd/system/screenly-viewer.service and tweak it only if you know what you’re doing with services…

can you tell me again how the browser found dead, restarting error is affecting you? this usually goes away on it’s own when all the required services are fully started…

hmm… that wifi connect service is taking so long, but then this is on a pi zero w right? because i am testing on one now and its almost the exact time you have there from the systemd-analyze blame…

so… as you can see, this could simply be that screenly-web.service is started after the screenly-viewer.service, even though on the service file it is saying that it should start after the web one (but Requires is more strict than After), but if the viewer starts first, thats pretty much as far as i know why you would get an error because the viewer is starting and trying to access that URL which is serviced from the screenly-web.service thus until that service starts fully you will always see that…

I tested by changing that file i mentioned above (screenly-viewer.service), within the contents of the file, moving the screenly-web.service from the same line as matchbox.service and making its own line with Requires=screenly-web.service, as seen on this screenshot:

I am still seeing the analyzed time though show that viewer starts up within 1-2 seconds and web service takes about 6-7 seconds so it is still starting before the web service which i explicitly said required the web service… its late so i’ll mess with this more another time.