Closed si458 closed 6 years ago
Do you still have the wired connection plugged in? Rpisurv start the moment there at least one network device which is up
its wireless only, no lan cable plugged in :(
Can you try:
systemctl enable systemd-networkd-wait-online.service
Sorry for delay
pi@raspberrypi:~ $ systemctl enable systemd-networkd-wait-online.service Failed to enable unit: The name org.freedesktop.PolicyKit1 was not provided by any .service files pi@raspberrypi:~ $
Sorry ignore that forgot to use sudo
That enabled the service but after reboot it still loads before the network and says all streams are not available
Pi@raspberrypi:~ $ sudo systemctl enable systemd-networkd-wait-online.service Created symlink /etc/systemd/system/network-online.target.wants/systemd-networkd-wait-online.service → /lib/systemd/system/systemd-networkd-wait-online.service. pi@raspberrypi:~ $
I had a similar issue with rpisurv loading before the network was ready, wired only in my situation. Enabling systemd-networkd-wait-online.service did not resolve the issue.
Editing the /usr/bin/rpisurv file and adding /bin/sleep 10 resolved the issue in my case. This provided enough of a delay for the network to be active. Resulting rpisurv file:
I can not reproduce the issue. Could you try to
Wants=network-online.target
to the systemd file and reboot
` cat /etc/systemd/system/rpisurv.service [Unit] Description=Rpisurv Raspberry Pi Surveillance After=network-online.target Wants=network-online.target
[Service] Type=simple ExecStart=/usr/bin/rpisurv KillMode=control-group Restart=on-failure
[Install] WantedBy=multi-user.target `
My current systemd file already has these lines in place.
Edit: Perhaps it's due to my network configuration? Normally this RPi is on a separate network without DHCP, but for troubleshooting/updates/etc it is then physically moved to a different network which does have DHCP enabled. Ergo my /etc/dhcpcd.conf file is as follows:
I run rpisurv (rpi 2) on dhcp but wired. I do not see any issues with dhcp configured.
Might be something unique with my setup. Thank you for looking into this issue. :)
I can not reproduce the issue. Could you try to
Wants=network-online.target
to the systemd file and reboot
` cat /etc/systemd/system/rpisurv.service [Unit] Description=Rpisurv Raspberry Pi Surveillance After=network-online.target Wants=network-online.target
[Service] Type=simple ExecStart=/usr/bin/rpisurv KillMode=control-group Restart=on-failure
[Install] WantedBy=multi-user.target `
Hi,
so after not doing anything on surveillance tasks for awhile, im back to surveillance tasks again
and i started having this issue again, however adding the line 'Wants=network-online.target' fixed my issue!
can you update the service file to include this line as it might help others :)
when using the latest raspbian on RPI 3 AND using WiFi,
it appears the rpisurv is starting before the pi has actually connected to the network by wifi
i have used raspi-config to say WAIT UNTIL NETWORK CONNECTED
but its having no affect?