Background: I have four Zero2Ws running my own kiosk-like setup. They had all been running under x11, but I reconfigured my setup and software to run under labwc, just so I could also get Screen Sharing access. But Screen Sharing only works on two of the four..
I have been looking at journalctl output. The "rpi-connect-wayvnc-watcher.service" does things on the machines that succeed, but doesn't appear at all on the ones that fail.
Backround detail: on all four machines, there's some issue with the rpi-connect-wayvnc.service, which always fails the first time but shortly after succeeds on a restart:On the two machines where I don't get screen sharing, rpi-connect makes its decision before wayvnc has finally come up, concludes it can't offer screen sharing, and that's that: On the two machines where I DO get screen sharing, something called the "rpi-connect-wayvnc-watcher.service" gets started during the restart process for wayvnc. Its own log entry says its purpose is to "Reload rpi-connect when rpi-connect-wayvnc changes...". This sounds just like what I need to happen on the other two machines. After wayvnc has come up, it makes rpi-connect do a reload, and with that second try, rpi-connect is happy to offer screen sharing. Can anyone explain this difference and help me fix it?
I have been looking at journalctl output. The "rpi-connect-wayvnc-watcher.service" does things on the machines that succeed, but doesn't appear at all on the ones that fail.
Backround detail: on all four machines, there's some issue with the rpi-connect-wayvnc.service, which always fails the first time but shortly after succeeds on a restart:
Code:
Jan 25 09:58:24 pizb systemd[689]: rpi-connect-wayvnc.service: Control process exited, code=exited, status=1/FAILUREJan 25 09:58:24 pizb systemd[689]: rpi-connect-wayvnc.service: Failed with result 'exit-code'.Jan 25 09:58:24 pizb systemd[689]: Failed to start rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.Code:
Jan 25 09:58:29 pizb systemd[689]: rpi-connect-wayvnc.service: Scheduled restart job, restart counter is at 1.Jan 25 09:58:29 pizb systemd[689]: Stopped rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.Jan 25 09:58:29 pizb systemd[689]: Starting rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...Jan 25 09:58:29 pizb systemd[689]: Started rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.Code:
Jan 25 05:01:28 piza systemd[1]: Starting wayvnc.service - VNC Server...Jan 25 05:01:29 piza systemd[606]: Starting rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...Jan 25 05:01:29 piza systemd[606]: Started rpi-connect.service - Raspberry Pi Connect.Jan 25 05:01:29 piza systemd[606]: rpi-connect-wayvnc.service: Control process exited, code=exited, status=1/FAILUREJan 25 05:01:29 piza systemd[606]: rpi-connect-wayvnc.service: Failed with result 'exit-code'.Jan 25 05:01:29 piza systemd[606]: Failed to start rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.Jan 25 05:01:33 piza rpi-connect[767]: 2025/01/25 05:01:33 INFO No VNC server found, starting without screen sharing supportJan 25 05:01:35 piza systemd[606]: rpi-connect-wayvnc.service: Scheduled restart job, restart counter is at 1.Jan 25 05:01:35 piza systemd[606]: Stopped rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.Jan 25 05:01:35 piza systemd[606]: Starting rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...Jan 25 05:01:35 piza systemd[606]: Started rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.Jan 25 05:01:37 piza systemd[1]: Started wayvnc.service - VNC Server.Code:
Jan 25 09:58:23 pizb systemd[689]: Started rpi-connect-wayvnc-watcher.path.Jan 25 09:58:24 pizb systemd[689]: Starting rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...Jan 25 09:58:24 pizb systemd[689]: Started rpi-connect.service - Raspberry Pi Connect.Jan 25 09:58:24 pizb systemd[689]: rpi-connect-wayvnc.service: Control process exited, code=exited, status=1/FAILUREJan 25 09:58:24 pizb systemd[689]: rpi-connect-wayvnc.service: Failed with result 'exit-code'.Jan 25 09:58:24 pizb systemd[689]: Failed to start rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.Jan 25 09:58:28 pizb rpi-connect[745]: 2025/01/25 09:58:28 INFO No VNC server found, starting without screen sharing supportJan 25 09:58:29 pizb systemd[689]: rpi-connect-wayvnc.service: Scheduled restart job, restart counter is at 1.Jan 25 09:58:29 pizb systemd[689]: Stopped rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.Jan 25 09:58:29 pizb systemd[689]: Starting rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect...Jan 25 09:58:29 pizb systemd[689]: Started rpi-connect-wayvnc.service - WayVNC process used by Raspberry Pi Connect.Jan 25 09:58:37 pizb systemd[689]: Starting rpi-connect-wayvnc-watcher.service - Reload rpi-connect when rpi-connect-wayvnc changes...Jan 25 09:58:44 pizb systemd[689]: Reloading rpi-connect.service - Raspberry Pi Connect...Jan 25 09:58:45 pizb rpi-connect[745]: 2025/01/25 09:58:45 INFO VNC server found, reloading with screen sharing supportJan 25 09:58:46 pizb rpi-connect[1358]: ✓ ReloadedJan 25 09:58:46 pizb systemd[689]: Reloaded rpi-connect.service - Raspberry Pi Connect.Jan 25 09:58:46 pizb systemd[689]: Finished rpi-connect-wayvnc-watcher.service - Reload rpi-connect when rpi-connect-wayvnc changes.Statistics: Posted by tinker2much — Sat Jan 25, 2025 7:17 pm — Replies 0 — Views 32
