Hi, I was doing some housekeeping and on one of the raspberry pi instances that I have remote.it installed I get the following journal entry every 5 seconds!
I am not logged in via remote.it and remote.it was installed here the same as it was on another instance. Everything appears to work the entries are polluting the logs, what is there cause and how should I prevent them. A fresh reboot made no difference.
Looking closely at the configuration reported by the two instances I see that the one that is creating the entries has this
Today I have also noticed that Screenview works on the instance that has the version shown and is noisy (the instance is on the local LAN) but does not work on the remote connection that has no version.
Does the rpi that doesn’t work have the Raspberry Pi Desktop installed? If it is just the rpi lite version then ScreenView might not be able to load without a desktop manager.
Both RPi instances are RPi4 with full Desktop installs and no physical display. They both also run rpi-connect (full version with display) and tailscale. Remote.it ssh works on both instances.
Great, let’s try this then.
For the log flooding do this:
Edit the /etc/systemd/system/screenview.service
Add the following two lines into the [Service] section:
StandardOutput=null
StandardError=null
Save the file. Then run the following commands to reload the changes and restart the service: sudo systemctl daemon-reload sudo systemctl restart screenview
On the rpi that ScreenView isn’t working try restarting the service using: sudo systemctl restart screenview
If that fixes the ScreenView and the other changes fixes the log entries on the other rpi then you can do the same edits on this rpi.
There is no /etc/systemd/system/screenview.service file on the rpi that isn’t working.
I created one identical to the working pi and rebooted and then get this error
(reenview)[2718]: screenview.service: Failed at step EXEC spawning /usr/sbin/screenview: No such file or directory
I looked in /usr/sbin and these files exist on the noisy RPi but are missing on the other RPi
-rwxr-xr-x 1 root root 6579312 Nov 4 20:55 screenview
-rwxr-xr-x 1 root root 5595056 Nov 4 20:55 screenview-drivers-wayland-keyboard
-rwxr-xr-x 1 root root 5595056 Nov 4 20:55 screenview-drivers-wayland-mouse
-rwxr-xr-x 1 root root 6121936 Nov 4 20:56 screenview-drivers-wayland-screen
-rwxr-xr-x 1 root root 5792720 Nov 4 20:56 screenview-drivers-x11-screen
-rwxr-xr-x 1 root root 5793424 Nov 4 20:56 screenview-drivers-x11-keyboard
-rwxr-xr-x 1 root root 5792144 Nov 4 20:56 screenview-drivers-x11-mouse
I tried a fresh install of remote.it but nothing new was installed.
I would try to delete the ScreenView service on the rpi that isn’t working from the Desktop or Portal. Then re-add the ScreenView service. The ScreenView service is different than other services. When you add that service it will actually install the screenview agent. So it appears that the ScreenView service got added to the second rpi without actually installing the software. How was this service added to the second rpi? Was it manually added through the Desktop or Portal? Was it added using a registration code with that service already in it? Were you using a product code?
Glad to hear that you are up and running again. Thank you for the detailed feedback. I will add an issue for the logging to get that fixed in future releases. I will also doing some more testing on our end to see if I can reproduce the case where there is a screenview service but no installation on the rpi.
