On Wed, 12 Aug 2020 17:36:09 +0200 Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
16:56:12 /usr/bin/x2gostartagent: unable to insert port into database. Retrying (run 5).
Hmm, could this be a disk full / read-only mount issue, or maybe a hung/stuck NFS mount somewhere? Or an issue with "private tmp"?
No NFS, I purged everything and the db file is created:
ls -al /var/lib/x2go/ total 52 drwxrwx--- 2 x2gouser x2gouser 4096 Aug 12 16:22 . drwxr-xr-x 41 root root 4096 Feb 20 10:37 .. -rw-rw---- 1 root x2gouser 40960 Aug 12 16:22 x2go_sessions
Compared to the working server this is correct.
The sessions database is at /var/lib/x2go/x2go_sessions if you're using SQLite (the default). So you might want to check if that file exists, how large it is, what its ownership/permissions are, and how much disk space is available at its mountpoint.
$ df / Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda3 32765712 13929784 17141824 45% /
$ df -i / Filesystem Inodes IUsed IFree IUse% Mounted on /dev/sda3 2097152 286285 1810867 14% /
The database is created at install, has the right permissions but is empty:
# sqlite3 /var/lib/x2go/x2go_sessions SQLite version 3.32.3 2020-06-18 14:00:33 Enter ".help" for usage hints. sqlite> .tables messages mounts sessions used_ports user_messages sqlite> SELECT * FROM used_ports; sqlite> SELECT * FROM user_messages; sqlite> SELECT * FROM sessions; sqlite> SELECT * FROM mounts; sqlite> SELECT * FROM messages; sqlite> INSERT INTO messages ('mess_id', 'message') VALUES ('1','test'); sqlite> SELECT * FROM messages; 1|test sqlite> DELETE FROM messages WHERE mess_id = '1'; sqlite> SELECT * FROM messages; sqlite> .q
So, nothing wrong with the database IMHO
# grep x2gouser /etc/group x2gouser:x:117: (same as on working server)
I'm a bit confused now...
Is there a way to output debug info to syslog on Debian packages?
R.
-- richard lucassen http://contact.xaq.nl/