Re: [X2Go-Dev] X2go crash on Fedora 37, port already in use?
On 1/4/23 10:43, Ulrich Sibiller wrote: I agree that the error messages should be more helpful. On the other hand all this would not have occurred if the installer had checked for the group to exist before creating another one. Plus: Your systems should always return the same GID for a given groupname. From your description it looks like this is not ensured. So maybe check if you NIS setup (or rather your nscd, sssd, nsswitch.conf) is clean. Uli The Fedora package does check before creating the group or user: %pre common getent group x2gouser >/dev/null || groupadd -r x2gouser getent passwd x2gouser >/dev/null || \ useradd -r -g x2gouser -d /var/lib/x2go -s /sbin/nologin \ -c "x2go" x2gouser exit 0 Of course this assumes the NIS is setup and running at the time of package install, which may not be the case. On Wed, Jan 4, 2023 at 5:08 PM Robert Kudyba wrote: The chmod commands allowed X2Go to open. So perhaps not a bug per se but a suggestion to improve on some error checking. We still use NIS/yp (yes it's ok to groan). The NIS server included the x2gouser GID in /etc/group. This led to creation of the user when x2go was installed adopting that GID (461) in /etc/passwd instead of the one that the installation created (973) in /etc/group. (Thus /etc/passwd had x2gouser:x:977:461 while /etc/group had x2gouser:x:973.) The GID of the setgid program /usr/lib64/x2go/libx2go-server-db-sqlite3-wrapper was the one in /etc/group, namely 973, while the GID of /var/lib/x2go and /var/lib/x2go/x2go_sessions was the one in /etc/passwd, namely 461. Hence when the process adopted the GID 973 of the wrapper, it was not granted access to files with GID 461. This caused any of the x2go library scripts that access the database to fail when run as a normal user, In practice, the first one that is run as a session is starting is x2gogetports, which returned a "cannot open file" error message instead of a list of port numbers. This error message (or more precisely the first "word" of it) was fed to x2gocheckports at line 131, which tried to interpret it as a port number, and got a syntax error as a result. In fact, there are many ways that the x2go server process could fail to open the database file. All of them will generate the exact same error message. If I may suggest a change, it would be to catch these errors earlier (e.g. by a success code from x2gogetports and its kin) and report the file open failure with a message based on the errno, (e.g. no such file or access denied). This would narrow down the possible causes of the failure. Thanks for all of your suggestions in getting this to work. On Mon, Jan 2, 2023 at 3:52 AM wrote: It could be a bug: the version distributed with Fedora 37 is 4.1.0.3-19.fc37.x86_64.rpm whereas the one in CentOS 8 is x2goserver-4.1.0.3-17.el8.1.x86_64.rpm , with this showing in the change log: 2022-07-23 - Fedora Release Engineering - 4.1.0.3-19 - Rebuilt for https://urldefense.proofpoint.com/v2/url?u=https-3A__fedoraproject.org_wiki_Fedora-5F37-5FMass-5FRebuild&d=DwIDaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=c4doz1suIijY2NueNOG6O9qnEmjwZUxxuWDG4ja3upV5tc8ZxcyS12WTuJJIWT3F&s=L9tIePHQQsnuZYnxUL9fh-gQnR4Rx0oKIVntrG7c-LE&e= 2022-05-30 - Jitka Plesnikova - 4.1.0.3-18 - Perl 5.36 rebuild Those are the permissions I have on my side (on Debian 11 but it should be the same): root@dev:~# ls -lah /var/lib/ drwxrwx---+ 2 x2gouser x2gouser 4.0K Dec 29 01:37 x2go root@dev:~# ls -lah /var/lib/x2go/ -rw-rw+ 1 root x2gouser 40K Dec 29 01:37 x2go_sessions So try this: sudo chmod 0770 /var/lib/x2go && sudo chown x2gouser:x2gouser /var/lib/x2go && sudo chmod 0660 /var/lib/x2go/x2go_sessions && sudo chown root:x2gouser /var/lib/x2go/x2go_sessions && echo "PERMISSIONS FIXED" If it still doesn't work: maybe you can revert to version x2goserver-4.1.0.3-17 ? I tried to find the package for Fedora 37 but could only find the el8 ones... Maybe this command would work: sudo dnf install x2goserver-4.1.0.3-17.fc37 Otherwise, the only last option to test out would be to use the EPEL8 repo and install the x2goserver-4.1.0.3-17.el8 package... Regards, Chris, Quantum Hosting®. On 2023-01-02 02:26, Robert Kudyba wrote: Well a hypothesis was tested with simply changing permissions as follows X2Go launched: sudo chmod 777 /var/lib/x2go pascal:~/$ sudo chmod 666 /var/lib/x2go/x2go_sessions Is x2go_sessions is needed after a session is up and running? This proves that it is a problem of permission to read and write the db. Permission should be gotten via the sgid wrapper, but for some reason it is not. Uninstalling and reinstalling did not work. Is there a script to fix permissions correctly? Should we remove the x2go user and group and re-add? On Sun, Jan 1, 2023, 2:33 PM wrote: Hi again Robert, I have tried (and succeeded) on a server using AlmaLinux 8 (I don't have access to Fedora 3
Re: [X2Go-Dev] X2go crash on Fedora 37, port already in use?
I agree that the error messages should be more helpful. On the other hand all this would not have occurred if the installer had checked for the group to exist before creating another one. Plus: Your systems should always return the same GID for a given groupname. From your description it looks like this is not ensured. So maybe check if you NIS setup (or rather your nscd, sssd, nsswitch.conf) is clean. Uli On Wed, Jan 4, 2023 at 5:08 PM Robert Kudyba wrote: > > The chmod commands allowed X2Go to open. So perhaps not a bug per se but a > suggestion to improve on some error checking. > > We still use NIS/yp (yes it's ok to groan). The NIS server included the > x2gouser GID in /etc/group. This led to creation of the user when x2go was > installed adopting that GID (461) in /etc/passwd instead of the one that the > installation created (973) in /etc/group. (Thus /etc/passwd had > x2gouser:x:977:461 while /etc/group had x2gouser:x:973.) The GID of the > setgid program /usr/lib64/x2go/libx2go-server-db-sqlite3-wrapper was the one > in /etc/group, namely 973, while the GID of /var/lib/x2go and > /var/lib/x2go/x2go_sessions was the one in /etc/passwd, namely 461. Hence > when the process adopted the GID 973 of the wrapper, it was not granted > access to files with GID 461. > > This caused any of the x2go library scripts that access the database to fail > when run as a normal user, In practice, the first one that is run as a > session is starting is x2gogetports, which returned a "cannot open file" > error message instead of a list of port numbers. This error message (or more > precisely the first "word" of it) was fed to x2gocheckports at line 131, > which tried to interpret it as a port number, and got a syntax error as a > result. > > In fact, there are many ways that the x2go server process could fail to open > the database file. All of them will generate the exact same error message. > If I may suggest a change, it would be to catch these errors earlier (e.g. by > a success code from x2gogetports and its kin) and report the file open > failure with a message based on the errno, (e.g. no such file or access > denied). This would narrow down the possible causes of the failure. > > Thanks for all of your suggestions in getting this to work. > > On Mon, Jan 2, 2023 at 3:52 AM wrote: >> >> It could be a bug: the version distributed with Fedora 37 is >> 4.1.0.3-19.fc37.x86_64.rpm whereas the one in CentOS 8 is >> x2goserver-4.1.0.3-17.el8.1.x86_64.rpm , with this showing in the change >> log: >> >> 2022-07-23 - Fedora Release Engineering - >> 4.1.0.3-19 >> - Rebuilt for >> https://urldefense.proofpoint.com/v2/url?u=https-3A__fedoraproject.org_wiki_Fedora-5F37-5FMass-5FRebuild&d=DwIDaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=c4doz1suIijY2NueNOG6O9qnEmjwZUxxuWDG4ja3upV5tc8ZxcyS12WTuJJIWT3F&s=L9tIePHQQsnuZYnxUL9fh-gQnR4Rx0oKIVntrG7c-LE&e= >> 2022-05-30 - Jitka Plesnikova - 4.1.0.3-18 >> - Perl 5.36 rebuild >> >> Those are the permissions I have on my side (on Debian 11 but it should >> be the same): >> root@dev:~# ls -lah /var/lib/ >> drwxrwx---+ 2 x2gouser x2gouser 4.0K Dec 29 01:37 x2go >> >> root@dev:~# ls -lah /var/lib/x2go/ >> -rw-rw+ 1 root x2gouser 40K Dec 29 01:37 x2go_sessions >> >> So try this: >> sudo chmod 0770 /var/lib/x2go && sudo chown x2gouser:x2gouser >> /var/lib/x2go && sudo chmod 0660 /var/lib/x2go/x2go_sessions && sudo >> chown root:x2gouser /var/lib/x2go/x2go_sessions && echo "PERMISSIONS >> FIXED" >> >> If it still doesn't work: maybe you can revert to version >> x2goserver-4.1.0.3-17 ? I tried to find the package for Fedora 37 but >> could only find the el8 ones... Maybe this command would work: >> sudo dnf install x2goserver-4.1.0.3-17.fc37 >> Otherwise, the only last option to test out would be to use the EPEL8 >> repo and install the x2goserver-4.1.0.3-17.el8 package... >> >> >> Regards, >> Chris, >> Quantum Hosting®. >> >> On 2023-01-02 02:26, Robert Kudyba wrote: >> > Well a hypothesis was tested with simply changing permissions as >> > follows X2Go launched: >> > >> > sudo chmod 777 /var/lib/x2go >> > pascal:~/$ sudo chmod 666 /var/lib/x2go/x2go_sessions >> > >> > Is x2go_sessions is needed after a session is up and running? >> > >> > This proves that it is a problem of permission to read and write the >> > db. Permission should be gotten via the sgid wrapper, but for some >> > reason it is not. >> > >> > Uninstalling and reinstalling did not work. >> > Is there a script to fix permissions correctly? Should we remove the >> > x2go user and group and re-add? >> > >> > On Sun, Jan 1, 2023, 2:33 PM wrote: >> > >> >> Hi again Robert, >> >> >> >> I have tried (and succeeded) on a server using AlmaLinux 8 (I don't >> >> have >> >> access to Fedora 37, sorry) and this is the command I used (you >> >> might >> >> skip the 2x "epel" commands?): >> >> >> >> dnf upgrade -y && dnf install >> >> >>
Re: [X2Go-Dev] X2go crash on Fedora 37, port already in use?
The chmod commands allowed X2Go to open. So perhaps not a bug per se but a suggestion to improve on some error checking. We still use NIS/yp (yes it's ok to groan). The NIS server included the x2gouser GID in /etc/group. This led to creation of the user when x2go was installed adopting that GID (461) in /etc/passwd instead of the one that the installation created (973) in /etc/group. (Thus /etc/passwd had x2gouser:x:977:461 while /etc/group had x2gouser:x:973.) The GID of the setgid program /usr/lib64/x2go/libx2go-server-db-sqlite3-wrapper was the one in /etc/group, namely 973, while the GID of /var/lib/x2go and /var/lib/x2go/x2go_sessions was the one in /etc/passwd, namely 461. Hence when the process adopted the GID 973 of the wrapper, it was not granted access to files with GID 461. This caused any of the x2go library scripts that access the database to fail when run as a normal user, In practice, the first one that is run as a session is starting is x2gogetports, which returned a "cannot open file" error message instead of a list of port numbers. This error message (or more precisely the first "word" of it) was fed to x2gocheckports at line 131, which tried to interpret it as a port number, and got a syntax error as a result. In fact, there are many ways that the x2go server process could fail to open the database file. All of them will generate the exact same error message. If I may suggest a change, it would be to catch these errors earlier (e.g. by a success code from x2gogetports and its kin) and report the file open failure with a message based on the errno, (e.g. no such file or access denied). This would narrow down the possible causes of the failure. Thanks for all of your suggestions in getting this to work. On Mon, Jan 2, 2023 at 3:52 AM wrote: > It could be a bug: the version distributed with Fedora 37 is > 4.1.0.3-19.fc37.x86_64.rpm whereas the one in CentOS 8 is > x2goserver-4.1.0.3-17.el8.1.x86_64.rpm , with this showing in the change > log: > > 2022-07-23 - Fedora Release Engineering - > 4.1.0.3-19 > - Rebuilt for > https://urldefense.proofpoint.com/v2/url?u=https-3A__fedoraproject.org_wiki_Fedora-5F37-5FMass-5FRebuild&d=DwIDaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=c4doz1suIijY2NueNOG6O9qnEmjwZUxxuWDG4ja3upV5tc8ZxcyS12WTuJJIWT3F&s=L9tIePHQQsnuZYnxUL9fh-gQnR4Rx0oKIVntrG7c-LE&e= > 2022-05-30 - Jitka Plesnikova - 4.1.0.3-18 > - Perl 5.36 rebuild > > Those are the permissions I have on my side (on Debian 11 but it should > be the same): > root@dev:~# ls -lah /var/lib/ > drwxrwx---+ 2 x2gouser x2gouser 4.0K Dec 29 01:37 x2go > > root@dev:~# ls -lah /var/lib/x2go/ > -rw-rw+ 1 root x2gouser 40K Dec 29 01:37 x2go_sessions > > So try this: > sudo chmod 0770 /var/lib/x2go && sudo chown x2gouser:x2gouser > /var/lib/x2go && sudo chmod 0660 /var/lib/x2go/x2go_sessions && sudo > chown root:x2gouser /var/lib/x2go/x2go_sessions && echo "PERMISSIONS > FIXED" > > If it still doesn't work: maybe you can revert to version > x2goserver-4.1.0.3-17 ? I tried to find the package for Fedora 37 but > could only find the el8 ones... Maybe this command would work: > sudo dnf install x2goserver-4.1.0.3-17.fc37 > Otherwise, the only last option to test out would be to use the EPEL8 > repo and install the x2goserver-4.1.0.3-17.el8 package... > > > Regards, > Chris, > Quantum Hosting®. > > On 2023-01-02 02:26, Robert Kudyba wrote: > > Well a hypothesis was tested with simply changing permissions as > > follows X2Go launched: > > > > sudo chmod 777 /var/lib/x2go > > pascal:~/$ sudo chmod 666 /var/lib/x2go/x2go_sessions > > > > Is x2go_sessions is needed after a session is up and running? > > > > This proves that it is a problem of permission to read and write the > > db. Permission should be gotten via the sgid wrapper, but for some > > reason it is not. > > > > Uninstalling and reinstalling did not work. > > Is there a script to fix permissions correctly? Should we remove the > > x2go user and group and re-add? > > > > On Sun, Jan 1, 2023, 2:33 PM wrote: > > > >> Hi again Robert, > >> > >> I have tried (and succeeded) on a server using AlmaLinux 8 (I don't > >> have > >> access to Fedora 37, sorry) and this is the command I used (you > >> might > >> skip the 2x "epel" commands?): > >> > >> dnf upgrade -y && dnf install > >> > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__dl.fedoraproject.org_pub_epel_epel-2Drelease-2Dlatest-2D8.noarch.rpm&d=DwIDaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=7p_4VYLAUDElk8vMZgdq0Z9McN077vuO0VabguwetT409bSXJvY1JoGQ0Pc6wHog&s=zksEEUIvkzgtDnM8715wOsqYfM21ArqKZhRQdldhWWA&e= > >> > >> -y && dnf config-manager --enable epel && dnf config-manager > >> --set-enabled powertools && dnf install -y xfdesktop gtk-doc xfce* > >> --exclude=xfce4-sensors-plugin-devel lightdm firefox x2goserver > >> x2goserver-xsession && systemctl isolate graphical.target &
Re: [X2Go-Dev] X2go crash on Fedora 37, port already in use?
It could be a bug: the version distributed with Fedora 37 is 4.1.0.3-19.fc37.x86_64.rpm whereas the one in CentOS 8 is x2goserver-4.1.0.3-17.el8.1.x86_64.rpm , with this showing in the change log: 2022-07-23 - Fedora Release Engineering - 4.1.0.3-19 - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild 2022-05-30 - Jitka Plesnikova - 4.1.0.3-18 - Perl 5.36 rebuild Those are the permissions I have on my side (on Debian 11 but it should be the same): root@dev:~# ls -lah /var/lib/ drwxrwx---+ 2 x2gouser x2gouser 4.0K Dec 29 01:37 x2go root@dev:~# ls -lah /var/lib/x2go/ -rw-rw+ 1 root x2gouser 40K Dec 29 01:37 x2go_sessions So try this: sudo chmod 0770 /var/lib/x2go && sudo chown x2gouser:x2gouser /var/lib/x2go && sudo chmod 0660 /var/lib/x2go/x2go_sessions && sudo chown root:x2gouser /var/lib/x2go/x2go_sessions && echo "PERMISSIONS FIXED" If it still doesn't work: maybe you can revert to version x2goserver-4.1.0.3-17 ? I tried to find the package for Fedora 37 but could only find the el8 ones... Maybe this command would work: sudo dnf install x2goserver-4.1.0.3-17.fc37 Otherwise, the only last option to test out would be to use the EPEL8 repo and install the x2goserver-4.1.0.3-17.el8 package... Regards, Chris, Quantum Hosting®. On 2023-01-02 02:26, Robert Kudyba wrote: Well a hypothesis was tested with simply changing permissions as follows X2Go launched: sudo chmod 777 /var/lib/x2go pascal:~/$ sudo chmod 666 /var/lib/x2go/x2go_sessions Is x2go_sessions is needed after a session is up and running? This proves that it is a problem of permission to read and write the db. Permission should be gotten via the sgid wrapper, but for some reason it is not. Uninstalling and reinstalling did not work. Is there a script to fix permissions correctly? Should we remove the x2go user and group and re-add? On Sun, Jan 1, 2023, 2:33 PM wrote: Hi again Robert, I have tried (and succeeded) on a server using AlmaLinux 8 (I don't have access to Fedora 37, sorry) and this is the command I used (you might skip the 2x "epel" commands?): dnf upgrade -y && dnf install https://urldefense.proofpoint.com/v2/url?u=https-3A__dl.fedoraproject.org_pub_epel_epel-2Drelease-2Dlatest-2D8.noarch.rpm&d=DwIDaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=7p_4VYLAUDElk8vMZgdq0Z9McN077vuO0VabguwetT409bSXJvY1JoGQ0Pc6wHog&s=zksEEUIvkzgtDnM8715wOsqYfM21ArqKZhRQdldhWWA&e= -y && dnf config-manager --enable epel && dnf config-manager --set-enabled powertools && dnf install -y xfdesktop gtk-doc xfce* --exclude=xfce4-sensors-plugin-devel lightdm firefox x2goserver x2goserver-xsession && systemctl isolate graphical.target && systemctl set-default graphical.target && echo "PLEASE REBOOT NOW" Pausing and resuming the session didn't work though (probably bec my 1x CPU and 768 MB RAM are too small!). Again: I really prefer the LXQt or LXDE on Ubuntu/Debian as it is a lot faster than XFDE...(I can't imagine how slow MATE could be!). Regards, Chris, Quantum Hosting®. ___ x2go-dev mailing list [email protected] https://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] X2go crash on Fedora 37, port already in use?
Well a hypothesis was tested with simply changing permissions as follows X2Go launched: sudo chmod 777 /var/lib/x2go pascal:~/$ sudo chmod 666 /var/lib/x2go/x2go_sessions Is x2go_sessions is needed after a session is up and running? This proves that it is a problem of permission to read and write the db. Permission should be gotten via the sgid wrapper, but for some reason it is not. Uninstalling and reinstalling did not work. Is there a script to fix permissions correctly? Should we remove the x2go user and group and re-add? On Sun, Jan 1, 2023, 2:33 PM wrote: > Hi again Robert, > > > I have tried (and succeeded) on a server using AlmaLinux 8 (I don't have > access to Fedora 37, sorry) and this is the command I used (you might > skip the 2x "epel" commands?): > > dnf upgrade -y && dnf install > > https://urldefense.proofpoint.com/v2/url?u=https-3A__dl.fedoraproject.org_pub_epel_epel-2Drelease-2Dlatest-2D8.noarch.rpm&d=DwIDaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=7p_4VYLAUDElk8vMZgdq0Z9McN077vuO0VabguwetT409bSXJvY1JoGQ0Pc6wHog&s=zksEEUIvkzgtDnM8715wOsqYfM21ArqKZhRQdldhWWA&e= > > -y && dnf config-manager --enable epel && dnf config-manager > --set-enabled powertools && dnf install -y xfdesktop gtk-doc xfce* > --exclude=xfce4-sensors-plugin-devel lightdm firefox x2goserver > x2goserver-xsession && systemctl isolate graphical.target && systemctl > set-default graphical.target && echo "PLEASE REBOOT NOW" > > Pausing and resuming the session didn't work though (probably bec my 1x > CPU and 768 MB RAM are too small!). > > Again: I really prefer the LXQt or LXDE on Ubuntu/Debian as it is a lot > faster than XFDE...(I can't imagine how slow MATE could be!). > > > Regards, > Chris, > Quantum Hosting®. > ___ x2go-dev mailing list [email protected] https://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] X2go crash on Fedora 37, port already in use?
Hi again Robert, I have tried (and succeeded) on a server using AlmaLinux 8 (I don't have access to Fedora 37, sorry) and this is the command I used (you might skip the 2x "epel" commands?): dnf upgrade -y && dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -y && dnf config-manager --enable epel && dnf config-manager --set-enabled powertools && dnf install -y xfdesktop gtk-doc xfce* --exclude=xfce4-sensors-plugin-devel lightdm firefox x2goserver x2goserver-xsession && systemctl isolate graphical.target && systemctl set-default graphical.target && echo "PLEASE REBOOT NOW" Pausing and resuming the session didn't work though (probably bec my 1x CPU and 768 MB RAM are too small!). Again: I really prefer the LXQt or LXDE on Ubuntu/Debian as it is a lot faster than XFDE...(I can't imagine how slow MATE could be!). Regards, Chris, Quantum Hosting®. ___ x2go-dev mailing list [email protected] https://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] X2go crash on Fedora 37, port already in use?
Thanks, but none of those suggestions fixes the problem. The db exists, and the wrapper has sgid set. The hard drive is far from full. I didn't see anything in /etc/aliases that looked off. I do think it is sgid being inhibited for some reason. But the fs is mounted without the nosuid attribute, the file permissions are not insecure (e.g. world writable would be a problem). On Sun, Jan 1, 2023, 11:32 AM wrote: > I found this, tell me if it helps: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__unix.stackexchange.com_questions_467507_x2go-2Dunable-2Dto-2Dfind-2Dfree-2Ddisplay-2Dport-2Dor-2Dinsert-2Dnew-2Dsession-2Dinto-2Ddatabase&d=DwIDaQ&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=jnjCMuD7uhXKlYmHmk53nEGqoH4xm9JIRwvZw4zKXa2YW72rWmg8WowBbPtrnyNf&s=VqEHzMjrGAm1ZVBamX4jpLbcbYBDre5B-ooXBJsCY2s&e= > > Regards, > Chris, > Quantum Hosting®. > ___ x2go-dev mailing list [email protected] https://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] X2go crash on Fedora 37, port already in use?
I found this, tell me if it helps: https://unix.stackexchange.com/questions/467507/x2go-unable-to-find-free-display-port-or-insert-new-session-into-database Regards, Chris, Quantum Hosting®. ___ x2go-dev mailing list [email protected] https://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] X2go crash on Fedora 37, port already in use?
Xfce and MATE are installed. Stopping firewalld did not help. Here is the screenshot https://snipboard.io/UvWQTg.jpg So the session starts but is unusable. Could there be something inhibiting setuid on the server? Perl no longer permits suid scripts, so the procedure is either to use sudo or to use a suid wrapper written securely in C, which calls the perl script. /usr/lib64/x2go/libx2go-server-db-sqlite3-wrapper is a C program with the set-gid bit set to run as group x2gouser. I take it this is what enables an ordinary user to run x2togogetports and not hit a permission error when reading the database file /var/lib/x2go/x2go_sessions. On the (not working) server it fails with "unable to open database" unless run as root. On other servers we have, the perm bits are rwxr-sr-x with ownership root:x2gouser. On Sat, Dec 31, 2022, 2:48 PM wrote: > Hi again Robert, > > > On 2022-12-31 19:25, Robert Kudyba wrote: > > It's the client side. I'll have my colleague who is having this issue > > take the screenshot and upload. We just just dnf install on the server > > side, and no compilation on client side just the installer. > > Did you install any desktop manager too?... This might be your problem > as it's probably missing. Because X2GO only installs the remote access > to the desktop, but doesn't install any desktop manager. > > Last time I tried on CentOS 8 it wasn't working though (I had a library > problem or config problem). Here is the command I used back then: > dnf install -y xfdesktop gtk-doc xfce* lightdm firefox > > I might try again on a server if you face difficulties. The best would > be to use a Debian/Ubuntu distro (and use their task-sel packages). I > know: Linux distro is some kind of a religion, and you feel that you > betray yourself if you switch... meanwhile: the new year 2023 is coming > fast! > > > > Could firewalld or something like that be blocking these requested > > ports? > > Absolutely~ you might disable this (temporarily) to check! > > > Regards, > Chris N. > Quantum Hosting® > ___ x2go-dev mailing list [email protected] https://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] X2go crash on Fedora 37, port already in use?
On Sat, Dec 31, 2022 at 11:48 AM wrote: [...] > Last time I tried on CentOS 8 it wasn't working though (I had a library > problem or config problem). Here is the command I used back then: > dnf install -y xfdesktop gtk-doc xfce* lightdm firefox "There exists a bug in either XFCE or X2Go causing rendering issues with the compositor when using X2Go. Workaround is to disable compositing: /usr/bin/xfconf-query -c xfwm4 -p /general/use_compositing -s false https://wiki.x2go.org/doku.php/doc:de-compat I encountered the above issue in AlmaLinux 8; CentOS 8 would likely be using the same software versions. ___ x2go-dev mailing list [email protected] https://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] X2go crash on Fedora 37, port already in use?
Hi again Robert, On 2022-12-31 19:25, Robert Kudyba wrote: It's the client side. I'll have my colleague who is having this issue take the screenshot and upload. We just just dnf install on the server side, and no compilation on client side just the installer. Did you install any desktop manager too?... This might be your problem as it's probably missing. Because X2GO only installs the remote access to the desktop, but doesn't install any desktop manager. Last time I tried on CentOS 8 it wasn't working though (I had a library problem or config problem). Here is the command I used back then: dnf install -y xfdesktop gtk-doc xfce* lightdm firefox I might try again on a server if you face difficulties. The best would be to use a Debian/Ubuntu distro (and use their task-sel packages). I know: Linux distro is some kind of a religion, and you feel that you betray yourself if you switch... meanwhile: the new year 2023 is coming fast! Could firewalld or something like that be blocking these requested ports? Absolutely~ you might disable this (temporarily) to check! Regards, Chris N. Quantum Hosting® ___ x2go-dev mailing list [email protected] https://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] X2go crash on Fedora 37, port already in use?
It's the client side. I'll have my colleague who is having this issue take the screenshot and upload. We just just dnf install on the server side, and no compilation on client side just the installer. Could firewalld or something like that be blocking these requested ports? On Sat, Dec 31, 2022, 2:20 PM wrote: > Meh, I don't see the port 6000 opened in your list... > > Is your error on the server side or client side? If it's the client > side: can you show me a screenshot? (You can upload on > https://urldefense.proofpoint.com/v2/url?u=https-3A__snag.gy&d=DwICAg&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=gUp9gElVn2Qw3BM2bDqjgtsXQArlBOeLNk87KCCKsSgEJAcmpENe8B8pNL75m_Kj&s=xXffNMxVycEbxjVFghBzQhwNR2CPhj4cVNLkKB55syQ&e= > > ). > > Did you compile X2GO? How did you install it?.. > > > Regards, > Chris N. > ___ x2go-dev mailing list [email protected] https://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] X2go crash on Fedora 37, port already in use?
Meh, I don't see the port 6000 opened in your list... Is your error on the server side or client side? If it's the client side: can you show me a screenshot? (You can upload on https://snag.gy ). Did you compile X2GO? How did you install it?.. Regards, Chris N. ___ x2go-dev mailing list [email protected] https://lists.x2go.org/listinfo/x2go-dev
Re: [X2Go-Dev] X2go crash on Fedora 37, port already in use?
Thanks for the quick response. If it's not a bug then perhaps the error messages could be more clear rather than syntax error? # netstat -tulpn | grep LISTEN tcp0 0 127.0.0.53:53 0.0.0.0:* LISTEN 851/systemd-resolve tcp0 0 0.0.0.0:50201 0.0.0.0:* LISTEN 1518/rpc.statd tcp0 0 0.0.0.0:944 0.0.0.0:* LISTEN 1192/ypbind tcp0 0 0.0.0.0:631 0.0.0.0:* LISTEN 1538/cupsd tcp0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1/systemd tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1326/sshd: /usr/sbi tcp0 0 0.0.0.0:25 0.0.0.0:* LISTEN 2979/sendmail: acce tcp0 0 192.168.122.1:10002 0.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 192.168.122.1:10003 0.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 192.168.122.1:10001 0.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 192.168.122.1:10004 0.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 192.168.122.1:10005 0.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 127.0.0.54:53 0.0.0.0:* LISTEN 851/systemd-resolve tcp0 0 192.168.122.1:530.0.0.0:* LISTEN 2581/dnsmasq tcp0 0 150.108.64.67:10001 0.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 150.108.64.67:10003 0.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 150.108.64.67:10002 0.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 150.108.64.67:10005 0.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 150.108.64.67:10004 0.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 0.0.0.0:53550.0.0.0:* LISTEN 851/systemd-resolve tcp0 0 172.17.0.1:100030.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 172.17.0.1:100020.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 172.17.0.1:100010.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 172.17.0.1:100050.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 172.17.0.1:100040.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 127.0.0.1:10002 0.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 127.0.0.1:10003 0.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 127.0.0.1:10001 0.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 127.0.0.1:10004 0.0.0.0:* LISTEN 4575/agentid-servic tcp0 0 127.0.0.1:10005 0.0.0.0:* LISTEN 4575/agentid-servic tcp6 0 0 fe80::e1f0:711b:b:10001 :::*LISTEN 4575/agentid-servic tcp6 0 0 fe80::e1f0:711b:b:10002 :::*LISTEN 4575/agentid-servic tcp6 0 0 fe80::e1f0:711b:b:10003 :::*LISTEN 4575/agentid-servic tcp6 0 0 fe80::e1f0:711b:b:10004 :::*LISTEN 4575/agentid-servic tcp6 0 0 fe80::e1f0:711b:b:10005 :::*LISTEN 4575/agentid-servic tcp6 0 0 :::944 :::*LISTEN 1192/ypbind tcp6 0 0 :::631 :::*LISTEN 1538/cupsd tcp6 0 0 :::111 :::*LISTEN 1/systemd tcp6 0 0 :::22 :::*LISTEN 1326/sshd: /usr/sbi tcp6 0 0 ::1:10001 :::*LISTEN 4575/agentid-servic tcp6 0 0 ::1:10002 :::*LISTEN 4575/agentid-servic tcp6 0 0 ::1:10003 :::*LISTEN 4575/agentid-servic tcp6 0 0 ::1:10004 :::*LISTEN 4575/agentid-servic tcp6 0 0 ::1:10005 :::*LISTEN 4575/agentid-servic tcp6 0 0 :::5355 :::*LISTEN 851/systemd-resolve tcp6 0 0 :::56035:::*LISTEN 1518/rpc.statd On Sat, Dec 31, 2022, 1:59 PM wrote: > Hi Robert, > > > Surely this isn't a bug. Have you checked your opened ports? The command > is: > netstat -tulpn | grep LISTEN > > If you get a "command not found" error, please install it: > yum install -y net-tools > OR this command: > apt install -y net-tools > > > Regards, > Chris N. > __
Re: [X2Go-Dev] X2go crash on Fedora 37, port already in use?
Hi Robert, Surely this isn't a bug. Have you checked your opened ports? The command is: netstat -tulpn | grep LISTEN If you get a "command not found" error, please install it: yum install -y net-tools OR this command: apt install -y net-tools Regards, Chris N. ___ x2go-dev mailing list [email protected] https://lists.x2go.org/listinfo/x2go-dev
