Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 5244

Raspberry Pi Connect • Re: disagreement about a pi's connect status, over Connect or SSH

$
0
0
But if I do the same things on pi0w, the status looks the same whether I inquire over Connect (first) or SSH (second). (You can see that the CPU times are slightly different):
pi@pi0w:~ $ rpi-connect status
Signed in: yes
Screen sharing: unavailable
Remote shell: allowed (1 session active)
pi@pi0w:~ $ systemctl --user status rpi-connect
● rpi-connect.service - Raspberry Pi Connect
Loaded: loaded (/usr/lib/systemd/user/rpi-connect.service; enabled; preset: enabled)
Active: active (running) since Wed 2024-08-14 13:32:33 CDT; 2h 36min ago
Main PID: 601 (rpi-connectd)
Tasks: 14 (limit: 375)
CPU: 4min 43.342s
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/rpi-connect.service
├─ 601 /usr/bin/rpi-connectd -socket /run/user/1000/rpi-connect-wayvnc.sock
├─2742 /bin/bash -l
├─2762 systemctl --user status rpi-connect
└─2763 pager

Aug 14 13:32:35 pi0w rpi-connect[601]: 2024/08/14 13:32:35 systray error: failed to register: The name org.kde.StatusNotifie>
Aug 14 13:32:36 pi0w rpi-connect[601]: 2024/08/14 13:32:36 WARN API call unsuccessful error="Get \"https://api.connect.raspb>
Aug 14 13:32:41 pi0w rpi-connect[601]: 2024/08/14 13:32:41 WARN API call unsuccessful error="Get \"https://api.connect.raspb>
Aug 14 13:32:59 pi0w rpi-connect[601]: 2024/08/14 13:32:59 WARN API call unsuccessful error="Get \"https://api.connect.raspb>
Aug 14 15:04:39 pi0w rpi-connect[601]: 2024/08/14 15:04:39 INFO [e31bc891-17cc-4cb5-94cf-d498c4bb6d89] [shell]: Proxy sessio>
Aug 14 15:31:51 pi0w rpi-connect[601]: 2024/08/14 15:31:51 INFO [e31bc891-17cc-4cb5-94cf-d498c4bb6d89] [shell]: Proxy sessio>
Aug 14 15:46:48 pi0w rpi-connect[601]: 2024/08/14 15:46:48 INFO [e0408274-79f8-43fa-90d7-c4dbea1494d5] [shell]: Proxy sessio>
Aug 14 16:05:53 pi0w rpi-connect[601]: 2024/08/14 16:05:53 INFO [e0408274-79f8-43fa-90d7-c4dbea1494d5] [shell]: Proxy sessio>
Aug 14 16:05:53 pi0w rpi-connect[601]: mux ERROR: 2024/08/14 16:05:53 mux: ending readLoop packetio.Buffer error the agent i>
Aug 14 16:07:41 pi0w rpi-connect[601]: 2024/08/14 16:07:41 INFO [37c627e7-9343-44e6-bca0-837e3b820a15] [shell]: Proxy sessio>
pi@pi0w:~ $ ps -fade | grep connect
pi 601 517 4 14:17 ? 00:04:46 /usr/bin/rpi-connectd -socket /run/user/1000/rpi-connect-wayvnc.sock
pi 2788 2742 16 16:10 pts/1 00:00:00 grep --color=auto connect
pi@pi0w:~ $
pi@pi0w:~ $ rpi-connect status
Signed in: yes
Screen sharing: unavailable
Remote shell: allowed (1 session active)
pi@pi0w:~ $ systemctl --user status rpi-connect
● rpi-connect.service - Raspberry Pi Connect
Loaded: loaded (/usr/lib/systemd/user/rpi-connect.service; enabled; preset: enabled)
Active: active (running) since Wed 2024-08-14 13:32:33 CDT; 2h 36min ago
Main PID: 601 (rpi-connectd)
Tasks: 12 (limit: 375)
CPU: 4min 44.608s
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/rpi-connect.service
├─ 601 /usr/bin/rpi-connectd -socket /run/user/1000/rpi-connect-wayvnc.sock
└─2742 /bin/bash -l

Aug 14 13:32:35 pi0w rpi-connect[601]: 2024/08/14 13:32:35 systray error: failed to register: The name org.kde.StatusNotifierWatcher was not provided by an>
Aug 14 13:32:36 pi0w rpi-connect[601]: 2024/08/14 13:32:36 WARN API call unsuccessful error="Get \"https://api.connect.raspberrypi.com/key ... r=com.rasp>
Aug 14 13:32:41 pi0w rpi-connect[601]: 2024/08/14 13:32:41 WARN API call unsuccessful error="Get \"https://api.connect.raspberrypi.com/key ... r=com.rasp>
Aug 14 13:32:59 pi0w rpi-connect[601]: 2024/08/14 13:32:59 WARN API call unsuccessful error="Get \"https://api.connect.raspberrypi.com/key ... r=com.rasp>
Aug 14 15:04:39 pi0w rpi-connect[601]: 2024/08/14 15:04:39 INFO [e31bc891-17cc-4cb5-94cf-d498c4bb6d89] [shell]: Proxy session started
Aug 14 15:31:51 pi0w rpi-connect[601]: 2024/08/14 15:31:51 INFO [e31bc891-17cc-4cb5-94cf-d498c4bb6d89] [shell]: Proxy session ended reason="Client->Server >
Aug 14 15:46:48 pi0w rpi-connect[601]: 2024/08/14 15:46:48 INFO [e0408274-79f8-43fa-90d7-c4dbea1494d5] [shell]: Proxy session started
Aug 14 16:05:53 pi0w rpi-connect[601]: 2024/08/14 16:05:53 INFO [e0408274-79f8-43fa-90d7-c4dbea1494d5] [shell]: Proxy session ended reason="Client->Server >
Aug 14 16:05:53 pi0w rpi-connect[601]: mux ERROR: 2024/08/14 16:05:53 mux: ending readLoop packetio.Buffer error the agent is closed
Aug 14 16:07:41 pi0w rpi-connect[601]: 2024/08/14 16:07:41 INFO [37c627e7-9343-44e6-bca0-837e3b820a15] [shell]: Proxy session started
pi@pi0w:~ $ ps -fade | grep connect
pi 601 517 4 14:17 ? 00:04:46 /usr/bin/rpi-connectd -socket /run/user/1000/rpi-connect-wayvnc.sock
pi 2786 1760 16 16:10 pts/0 00:00:00 grep --color=auto connect
pi@pi0w:~ $

Statistics: Posted by tinker2much — Wed Aug 14, 2024 9:14 pm



Viewing all articles
Browse latest Browse all 5244

Trending Articles