problem while trying to upgrade to Bullseye following your blog post Topic is solved

Having issues with your DietPi installation or found a bug? Post it here.
User avatar
Joulinar
Posts: 5619
Joined: Sat Nov 16, 2019 12:49 am

Re: problem while trying to upgrade to Bullseye following your blog post

Post by Joulinar »

remove both Tiger and Real. reboot. and check if there is no process running afterwards

Code: Select all

ps -ef | grep vnc
as well check no LISTEN vnc process

Code: Select all

ss -tulpn | grep LISTEN
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
manilx
Posts: 124
Joined: Mon Dec 07, 2020 11:02 am

Re: problem while trying to upgrade to Bullseye following your blog post

Post by manilx »

Uninstalled RealVNC. Rebooted.

Code: Select all

root@Unify:~# ps -ef | grep vnc
root      1991  1458  0 09:18 pts/0    00:00:00 grep vnc

Code: Select all

root@Unify:~# ss -tulpn | grep LISTEN
tcp   LISTEN 0      4096                  0.0.0.0:10000      0.0.0.0:*    users:(("miniserv.pl",pid=1616,fd=5))
tcp   LISTEN 0      1024        192.168.1.51%eth0:25552      0.0.0.0:*    users:(("zerotier-one",pid=547,fd=17))
tcp   LISTEN 0      1024        192.168.1.51%eth0:25553      0.0.0.0:*    users:(("zerotier-one",pid=547,fd=19))
tcp   LISTEN 0      128                 127.0.0.1:28017      0.0.0.0:*    users:(("mongod",pid=335,fd=10))
tcp   LISTEN 0      128                   0.0.0.0:22         0.0.0.0:*    users:(("sshd",pid=662,fd=3))
tcp   LISTEN 0      4096                127.0.0.1:8125       0.0.0.0:*    users:(("netdata",pid=705,fd=53))
tcp   LISTEN 0      4096             192.168.1.51:19999      0.0.0.0:*    users:(("netdata",pid=705,fd=4))
tcp   LISTEN 0      1024        192.168.1.51%eth0:9993       0.0.0.0:*    users:(("zerotier-one",pid=547,fd=15))
tcp   LISTEN 0      1024                127.0.0.1:9993       0.0.0.0:*    users:(("zerotier-one",pid=547,fd=6))
tcp   LISTEN 0      128                 127.0.0.1:27017      0.0.0.0:*    users:(("mongod",pid=335,fd=9))
tcp   LISTEN 0      128                 127.0.0.1:27117      0.0.0.0:*    users:(("mongod",pid=1736,fd=7))
tcp   LISTEN 0      100                         *:8880             *:*    users:(("java",pid=680,fd=167))
tcp   LISTEN 0      100                         *:8080             *:*    users:(("java",pid=680,fd=163))
tcp   LISTEN 0      128                      [::]:22            [::]:*    users:(("sshd",pid=662,fd=4))
tcp   LISTEN 0      100                         *:8443             *:*    users:(("java",pid=680,fd=205))
tcp   LISTEN 0      4096                    [::1]:8125          [::]:*    users:(("netdata",pid=705,fd=52))
tcp   LISTEN 0      50                          *:6789             *:*    users:(("java",pid=680,fd=196))
tcp   LISTEN 0      1024                    [::1]:9993          [::]:*    users:(("zerotier-one",pid=547,fd=7))
tcp   LISTEN 0      100                         *:8843             *:*    users:(("java",pid=680,fd=218))
User avatar
Joulinar
Posts: 5619
Joined: Sat Nov 16, 2019 12:49 am

Re: problem while trying to upgrade to Bullseye following your blog post

Post by Joulinar »

install Real now and perform both checks again afterwards
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
manilx
Posts: 124
Joined: Mon Dec 07, 2020 11:02 am

Re: problem while trying to upgrade to Bullseye following your blog post

Post by manilx »

Reinstalled Real. Can't connect to 5900.
Rebooted, still no go.

Code: Select all

root@Unify:~# ss -tulpn | grep LISTEN
tcp   LISTEN 0      4096             0.0.0.0:10000      0.0.0.0:*    users:(("miniserv.pl",pid=1804,fd=5))
tcp   LISTEN 0      1024   192.168.1.51%eth0:25552      0.0.0.0:*    users:(("zerotier-one",pid=552,fd=17))
tcp   LISTEN 0      128              0.0.0.0:6001       0.0.0.0:*    users:(("Xvnc-core",pid=707,fd=1))
tcp   LISTEN 0      1024   192.168.1.51%eth0:25553      0.0.0.0:*    users:(("zerotier-one",pid=552,fd=19))
tcp   LISTEN 0      128            127.0.0.1:28017      0.0.0.0:*    users:(("mongod",pid=337,fd=10))
tcp   LISTEN 0      128              0.0.0.0:22         0.0.0.0:*    users:(("sshd",pid=668,fd=3))
tcp   LISTEN 0      4096           127.0.0.1:8125       0.0.0.0:*    users:(("netdata",pid=861,fd=47))
tcp   LISTEN 0      4096        192.168.1.51:19999      0.0.0.0:*    users:(("netdata",pid=861,fd=4))
tcp   LISTEN 0      1024   192.168.1.51%eth0:9993       0.0.0.0:*    users:(("zerotier-one",pid=552,fd=15))
tcp   LISTEN 0      1024           127.0.0.1:9993       0.0.0.0:*    users:(("zerotier-one",pid=552,fd=6))
tcp   LISTEN 0      128            127.0.0.1:27017      0.0.0.0:*    users:(("mongod",pid=337,fd=9))
tcp   LISTEN 0      5                0.0.0.0:5901       0.0.0.0:*    users:(("Xvnc-core",pid=707,fd=7))
tcp   LISTEN 0      100                    *:8880             *:*    users:(("java",pid=1052,fd=167))
tcp   LISTEN 3      100                    *:8080             *:*    users:(("java",pid=1052,fd=163))
tcp   LISTEN 0      128                 [::]:6001          [::]:*    users:(("Xvnc-core",pid=707,fd=0))
tcp   LISTEN 0      128                 [::]:22            [::]:*    users:(("sshd",pid=668,fd=4))
tcp   LISTEN 0      4096               [::1]:8125          [::]:*    users:(("netdata",pid=861,fd=46))
tcp   LISTEN 0      1024               [::1]:9993          [::]:*    users:(("zerotier-one",pid=552,fd=7))
tcp   LISTEN 0      5                   [::]:5901          [::]:*    users:(("Xvnc-core",pid=707,fd=6))
User avatar
Joulinar
Posts: 5619
Joined: Sat Nov 16, 2019 12:49 am

Re: problem while trying to upgrade to Bullseye following your blog post

Post by Joulinar »

you are trying to connect to wrong port. RealVNC is running on 5901

Code: Select all

tcp   LISTEN 0      5                0.0.0.0:5901       0.0.0.0:*    users:(("Xvnc-core",pid=707,fd=7))
tcp   LISTEN 0      5                   [::]:5901          [::]:*    users:(("Xvnc-core",pid=707,fd=6))
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
manilx
Posts: 124
Joined: Mon Dec 07, 2020 11:02 am

Re: problem while trying to upgrade to Bullseye following your blog post

Post by manilx »

I can connect only via the RealVNC app.
The app I normally use "Royal TSX" can't connect. Tried port 5900 and 5901.
User avatar
Joulinar
Posts: 5619
Joined: Sat Nov 16, 2019 12:49 am

Re: problem while trying to upgrade to Bullseye following your blog post

Post by Joulinar »

Why not using RealVNC app? I checked it on my Windows box as well as Android Mobile. Both are working fine and can connect to RealVNC server.
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
manilx
Posts: 124
Joined: Mon Dec 07, 2020 11:02 am

Re: problem while trying to upgrade to Bullseye following your blog post

Post by manilx »

Joulinar wrote: Mon Aug 30, 2021 10:33 am Why not using RealVNC app? I checked it on my Windows box as well as Android Mobile. Both are working fine and can connect to RealVNC server.
Royal TSX can connect to a LOT of services and protocols. I have defined there connections to 40 servers (vnc, terminal, vmware, rdp etc). It has apps for macos and ios. Highly recommended.

Will change back to Tiger. I hope not to have bothered to much but helped a bit "debugging" Bullseye stuff.....

A reboot after uninstall of Tiger is pertinent and perhaps you could put it in the uninstall script.
User avatar
Joulinar
Posts: 5619
Joined: Sat Nov 16, 2019 12:49 am

Re: problem while trying to upgrade to Bullseye following your blog post

Post by Joulinar »

at least you could have tried RealVNC native app, just to check if it is working in general.
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
manilx
Posts: 124
Joined: Mon Dec 07, 2020 11:02 am

Re: problem while trying to upgrade to Bullseye following your blog post

Post by manilx »

Joulinar wrote: Mon Aug 30, 2021 10:51 am at least you could have tried RealVNC native app, just to check if it is working in general.
I did and mentioned it. "I can connect only via the RealVNC app." ;)
Post Reply