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.
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 TigerVNC installed RealVNC, changed port from 5901 to 5900 but still can't connect...

If I don't get this working I have to roll back unfortunately. :cry:
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 »

If possible it would be helpful if we could try to work on the issue instead of rollback. ;)

can you share following once Tiger VNC is installed

Code: Select all

journalctl -u vncserver.service
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 »

Code: Select all

root@DietPi:~# journalctl -u vncserver.service
Journal file /var/log/journal/f0811f1ea22f48198b75b9d8062578c3/system.journal is truncated, ignoring file.
-- Journal begins at Sun 2021-08-29 19:29:07 WEST, ends at Sun 2021-08-29 22:17:09 WEST. --
Aug 29 19:29:29 DietPi systemd[1]: Started Manage VNC Server (DietPi).
Aug 29 19:29:29 DietPi systemd[718]: pam_unix(login:session): session opened for user root(uid=0) by (uid=0)
Aug 29 19:41:10 DietPi systemd[1]: Stopping Manage VNC Server (DietPi)...
Aug 29 19:41:10 DietPi systemd[5536]: pam_unix(login:session): session opened for user root(uid=0) by (uid=0)
Aug 29 19:41:10 DietPi vncserver[5536]: [FAILED] No supported VNC server installed
Aug 29 19:41:10 DietPi systemd[1]: vncserver.service: Control process exited, code=exited, status=1/FAILURE
Aug 29 19:41:10 DietPi systemd[1]: vncserver.service: Failed with result 'exit-code'.
Aug 29 19:41:10 DietPi systemd[1]: Stopped Manage VNC Server (DietPi).
Aug 29 19:45:10 DietPi systemd[1]: Started Manage VNC Server (DietPi).
Aug 29 19:45:10 DietPi systemd[8721]: pam_unix(login:session): session opened for user root(uid=0) by (uid=0)
Aug 29 19:45:11 DietPi systemd[1]: vncserver.service: Main process exited, code=exited, status=1/FAILURE
Aug 29 19:45:11 DietPi systemd[1]: vncserver.service: Failed with result 'exit-code'.
Aug 29 22:12:50 DietPi systemd[1]: Started Manage VNC Server (DietPi).
Aug 29 22:12:50 DietPi systemd[5373]: pam_unix(login:session): session opened for user root(uid=0) by (uid=0)
Aug 29 22:12:50 DietPi systemd[1]: vncserver.service: Main process exited, code=exited, status=1/FAILURE
Aug 29 22:12:50 DietPi systemd[1]: vncserver.service: Failed with result 'exit-code'.
Aug 29 22:13:09 DietPi systemd[1]: Started Manage VNC Server (DietPi).
Aug 29 22:13:09 DietPi systemd[5490]: pam_unix(login:session): session opened for user root(uid=0) by (uid=0)
Aug 29 22:13:09 DietPi systemd[1]: vncserver.service: Main process exited, code=exited, status=1/FAILURE
Aug 29 22:13:09 DietPi systemd[1]: vncserver.service: Failed with result 'exit-code'.

Code: Select all

ss -tulpn | grep LISTEN
tcp   LISTEN 0      4096             0.0.0.0:10000      0.0.0.0:*    users:(("miniserv.pl",pid=8703,fd=5))
tcp   LISTEN 0      1024             0.0.0.0:80         0.0.0.0:*    users:(("lighttpd",pid=8157,fd=4))
tcp   LISTEN 0      128              0.0.0.0:22         0.0.0.0:*    users:(("sshd",pid=720,fd=3))
tcp   LISTEN 0      4096           127.0.0.1:8125       0.0.0.0:*    users:(("netdata",pid=8167,fd=29))
tcp   LISTEN 0      4096        192.168.2.40:19999      0.0.0.0:*    users:(("netdata",pid=8167,fd=4))
tcp   LISTEN 0      1024   192.168.2.40%eth0:59584      0.0.0.0:*    users:(("zerotier-one",pid=594,fd=20))
tcp   LISTEN 0      1024        10.6.0.1%wg0:59584      0.0.0.0:*    users:(("zerotier-one",pid=594,fd=18))
tcp   LISTEN 0      1024   192.168.2.40%eth0:59585      0.0.0.0:*    users:(("zerotier-one",pid=594,fd=24))
tcp   LISTEN 0      1024        10.6.0.1%wg0:59585      0.0.0.0:*    users:(("zerotier-one",pid=594,fd=22))
tcp   LISTEN 0      1024   192.168.2.40%eth0:9993       0.0.0.0:*    users:(("zerotier-one",pid=594,fd=16))
tcp   LISTEN 0      1024        10.6.0.1%wg0:9993       0.0.0.0:*    users:(("zerotier-one",pid=594,fd=14))
tcp   LISTEN 0      1024           127.0.0.1:9993       0.0.0.0:*    users:(("zerotier-one",pid=594,fd=6))
tcp   LISTEN 0      5              127.0.0.1:5901       0.0.0.0:*    users:(("Xtigervnc",pid=777,fd=7))
tcp   LISTEN 0      1024                [::]:80            [::]:*    users:(("lighttpd",pid=8157,fd=5))
tcp   LISTEN 0      128                 [::]:22            [::]:*    users:(("sshd",pid=720,fd=4))
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 »

And this on the other one:

Code: Select all

root@Unify:~# journalctl -u vncserver.service
Journal file /var/log/journal/9290cc6d05c648b1ad37b19873f26fd1/system.journal is truncated, ignoring file.
-- Journal begins at Sun 2021-08-29 19:07:13 WEST, ends at Sun 2021-08-29 22:17:05 WEST. --
Aug 29 19:07:41 Unify systemd[1]: Started Manage VNC Server (DietPi).
Aug 29 19:07:41 Unify systemd[724]: pam_unix(login:session): session opened for user root(uid=0) by (uid=0)
Aug 29 19:36:42 Unify systemd[1]: Stopping Manage VNC Server (DietPi)...
Aug 29 19:36:42 Unify systemd[10041]: pam_unix(login:session): session opened for user root(uid=0) by (uid=0)
Aug 29 19:36:42 Unify vncserver[10041]: [FAILED] No supported VNC server installed
Aug 29 19:36:42 Unify systemd[1]: vncserver.service: Control process exited, code=exited, status=1/FAILURE
Aug 29 19:36:42 Unify systemd[1]: vncserver.service: Failed with result 'exit-code'.
Aug 29 19:36:42 Unify systemd[1]: Stopped Manage VNC Server (DietPi).
Aug 29 19:40:24 Unify systemd[1]: Started Manage VNC Server (DietPi).
Aug 29 19:40:24 Unify systemd[13183]: pam_unix(login:session): session opened for user root(uid=0) by (uid=0)
Aug 29 19:40:24 Unify systemd[1]: vncserver.service: Main process exited, code=exited, status=1/FAILURE
Aug 29 19:40:24 Unify systemd[1]: vncserver.service: Failed with result 'exit-code'.
Aug 29 19:56:07 Unify systemd[1]: Started Manage VNC Server (DietPi).
Aug 29 19:56:07 Unify systemd[17809]: pam_unix(login:session): session opened for user root(uid=0) by (uid=0)
Aug 29 19:56:07 Unify systemd[1]: vncserver.service: Main process exited, code=exited, status=1/FAILURE
Aug 29 19:56:07 Unify systemd[1]: vncserver.service: Failed with result 'exit-code'.
Aug 29 19:59:19 Unify systemd[1]: Started Manage VNC Server (DietPi).
Aug 29 19:59:19 Unify systemd[20082]: pam_unix(login:session): session opened for user root(uid=0) by (uid=0)
Aug 29 19:59:20 Unify systemd[1]: vncserver.service: Main process exited, code=exited, status=1/FAILURE
Aug 29 19:59:20 Unify systemd[1]: vncserver.service: Failed with result 'exit-code'.

Code: Select all

ss -tulpn | grep LISTEN
tcp   LISTEN 0      4096                  0.0.0.0:10000      0.0.0.0:*    users:(("miniserv.pl",pid=20063,fd=5))
tcp   LISTEN 0      1024        192.168.1.51%eth0:25552      0.0.0.0:*    users:(("zerotier-one",pid=553,fd=17))
tcp   LISTEN 0      1024        192.168.1.51%eth0:25553      0.0.0.0:*    users:(("zerotier-one",pid=553,fd=19))
tcp   LISTEN 0      128                 127.0.0.1:28017      0.0.0.0:*    users:(("mongod",pid=340,fd=10))
tcp   LISTEN 0      128                   0.0.0.0:22         0.0.0.0:*    users:(("sshd",pid=725,fd=3))
tcp   LISTEN 0      4096                127.0.0.1:8125       0.0.0.0:*    users:(("netdata",pid=19528,fd=31))
tcp   LISTEN 0      4096             192.168.1.51:19999      0.0.0.0:*    users:(("netdata",pid=19528,fd=4))
tcp   LISTEN 0      1024        192.168.1.51%eth0:9993       0.0.0.0:*    users:(("zerotier-one",pid=553,fd=15))
tcp   LISTEN 0      1024                127.0.0.1:9993       0.0.0.0:*    users:(("zerotier-one",pid=553,fd=6))
tcp   LISTEN 0      128                 127.0.0.1:27017      0.0.0.0:*    users:(("mongod",pid=340,fd=9))
tcp   LISTEN 0      128                 127.0.0.1:27117      0.0.0.0:*    users:(("mongod",pid=1822,fd=7))
tcp   LISTEN 0      5                   127.0.0.1:5901       0.0.0.0:*    users:(("Xtigervnc",pid=764,fd=7))
tcp   LISTEN 0      100                         *:8880             *:*    users:(("java",pid=1354,fd=167))
tcp   LISTEN 0      100                         *:8080             *:*    users:(("java",pid=1354,fd=163))
tcp   LISTEN 0      128                      [::]:22            [::]:*    users:(("sshd",pid=725,fd=4))
tcp   LISTEN 0      100                         *:8443             *:*    users:(("java",pid=1354,fd=206))
tcp   LISTEN 0      4096                    [::1]:8125          [::]:*    users:(("netdata",pid=19528,fd=30))
tcp   LISTEN 0      50                          *:6789             *:*    users:(("java",pid=1354,fd=197))
tcp   LISTEN 0      1024                    [::1]:9993          [::]:*    users:(("zerotier-one",pid=553,fd=7))
tcp   LISTEN 0      100                         *:8843             *:*    users:(("java",pid=1354,fd=219))
tcp   LISTEN 0      5                       [::1]:5901          [::]:*    users:(("Xtigervnc",pid=764,fd=8))
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 »

vnc server is bound to localhost only, hence not accepting request from local network

Code: Select all

tcp   LISTEN 0      5              127.0.0.1:5901       0.0.0.0:*    users:(("Xtigervnc",pid=777,fd=7))
something to be checked
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: Sun Aug 29, 2021 11:20 pm vnc server is bound to localhost only, hence not accepting request from local network

Code: Select all

tcp   LISTEN 0      5              127.0.0.1:5901       0.0.0.0:*    users:(("Xtigervnc",pid=777,fd=7))
something to be checked
Haven't changed anything... Just upgraded.
What to do to fix this?
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 »

ok @MichaIng already did some enhancement on VNC https://github.com/MichaIng/DietPi/pull/4679
They will become available on release 7.6.

If you like you could test the new VNC implementation on our dev branch or you try to add it manually.

On my test 7.6 fixed it and I was able to connect to TigerVNC. Our install script adds a new option into Tiger VNC configuration file

Code: Select all

[  OK  ] DietPi-Software | Added setting $localhost = "no"; to end of file /etc/tigervnc/vncserver-config-defaults
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 »

OK tried:

nano /etc/tigervnc/vncserver-config-defaults

added: $localhost = "no" to the end of the file. Rebooted.

Worked!

Should leave it like this and this will be updated by dietpi 7.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 »

the update themselves will not change anything on existing configuration as long as you don't do a reinstall.
If it is working fine, nothing to do I guess.
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 »

OK. I’ll leave it at that then.

BTW I also tried RealVNC and had the same issue. Already mentioned that I see ;)


Thx!
Post Reply