NetBSD 9.3 tmux on console problem - Solved

jmcunx

I have a fresh install of NetBSD 9.3 on a PII PC. I installed tmux from pkgsrc via pkgin. Its version is 'tmux 3.1c'.

When I execute tmux from the NetBSD Console, I get these errors:

ERROR: server exited unexpectedly client started (461): version 3.1c, socket /tmp/tmux-1001/default, protocol 8 on NetBSD 9.3 NetBSD 9.3 (GENERIC) #0: Thu Aug 4 15:30:37 UTC 2022 mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/i386/compile/GENERIC; libevent 2.1.8-stable (kqueue) socket is /tmp/tmux-1001/default trying connect connect failed: No such file or directory lock file is /tmp/tmux-1001/default.lock flock succeeded got lock (5) trying connect connect failed: No such file or directory

When I ssh into the system, tmux works fine, no issues

Any ideas on how to get it working from the console (virtual terminal 2 or 3 or 4) ?

JuvenalUrbino

jmcunx maybe something cleared /tmp taking the tmux socket with it? Do you have some special script to handle /tmp in your ~/.profile and ~/.login?

Anyway, from tmux(1):

   -L socket-name
                   tmux stores the server socket in a directory under
                   TMUX_TMPDIR or /tmp if it is unset.  The default socket is
                   named default.  This option allows a different socket name
                   to be specified, allowing several independent tmux servers
                   to be run.  Unlike -S a full path is not necessary: the
                   sockets are all created in a directory tmux-UID under the
                   directory given by TMUX_TMPDIR or in /tmp.  The tmux-UID
                   directory is created by tmux and must not be world read-
                   able, writable or executable.

               If the socket is accidentally removed, the SIGUSR1 signal
               may be sent to the tmux server process to recreate it (note
               that this will fail if any parent directories are missing).

So, I'd try to recreate the socket first:

$ for i in $(pgrep tmux)
    > do kill -USR1 $i
    > done

JuvenalUrbino

jmcunx maybe something cleared /tmp taking the tmux socket with it? Do you have some special script to handle /tmp in your ~/.profile and ~/.login?

Anyway, from tmux(1):

   -L socket-name
                   tmux stores the server socket in a directory under
                   TMUX_TMPDIR or /tmp if it is unset.  The default socket is
                   named default.  This option allows a different socket name
                   to be specified, allowing several independent tmux servers
                   to be run.  Unlike -S a full path is not necessary: the
                   sockets are all created in a directory tmux-UID under the
                   directory given by TMUX_TMPDIR or in /tmp.  The tmux-UID
                   directory is created by tmux and must not be world read-
                   able, writable or executable.

               If the socket is accidentally removed, the SIGUSR1 signal
               may be sent to the tmux server process to recreate it (note
               that this will fail if any parent directories are missing).

So, I'd try to recreate the socket first:

$ for i in $(pgrep tmux)
    > do kill -USR1 $i
    > done

rvp

jmcunx I have a fresh install of NetBSD 9.3 on a PII PC. I installed tmux from pkgsrc via pkgin.

a) Doesn't 9.3 already have tmux in base? Does that work? (I can't reproduce this with the base tmux in 9.3_STABLE.)
b) Do you have this line in /etc/fstab?

ptyfs           /dev/pts        ptyfs   rw

c) can you tmux -vv, then post the ~/tmux-*-NNNN.log files somewhere?

jmcunx

JuvenalUrbino

Thanks for the idea, sadly it did not fix the error. I did additional searches and saw this (my) issue is considered a bug with v3.1 of tmux

For now I am using screen, and I downloaded the latest version of tmux (v3.3a) and will try and compile that to see if that version solves the issue.

jmcunx For now I am using screen, and I downloaded the latest version of tmux (v3.3a) and will try and compile that

You should get 3.3 once the Q2 binaries are available, https://pkgsrc.se/misc/tmux

3.3a is already available in pkgsrc-current, so no need to build from upstream tarball

JuvenalUrbino

jmcunx I did additional searches and saw this (my) issue is considered a bug with v3.1 of tmux

If that's the case, could you report it on netbsd-users and maybe open a PR on GNATS? Just to prevent it fom passing unnoticed and landing in NetBSD-10

jmcunx

2023Q2 that is what I am waiting for 🙂

But this is embarrassing for me, based upon someone else's post I found out tmux is in 9.3 base. When I execute /usr/pkg/bin/tmux all works fine on 9.3.

That explains some weird things I noticed with tmux on this system.

JuvenalUrbino Do you have an instance with 10_BETA?
I don't see how this could end in 10_RELEASE?!

rvp Hmm.... looking at the first post on the thread, I see

NetBSD 9.3 (GENERIC) #0: Thu Aug 4 15:30:37 UTC 2022

What version of tmuxwould that be?

On the other hand I don't see where the OP got v3.1c from ...

Version history: (Expand)

(2022-07-23) Updated to version: tmux-3.3a

(2022-06-02) Updated to version: tmux-3.3

(2021-12-29) Updated to version: tmux-3.2a

(2021-04-17) Updated to version: tmux-3.2

(2020-11-01) Updated to version: tmux-3.1c

(2020-06-14) Updated to version: tmux-3.1b

cat /usr/pkg/etc/pkgin/repositories.conf, please

jmcunx

rvp
Based upon your post, I found out tmux is in base as version 3.1c, but in pkgsrc as 3.3a.

I never knew tmux was in base 🙂

Thanks, I will check 10.0 BETA on my other PC to see what is there.

jmcunx

Yes, on my "real" PC I am using 10-BETA amd64. No issues with tmux on 10.0 BETA

The PC with an issue is a PII with 512M memory, no USB. I wanted 9.3 because I did not want to mess with updated 10.0 BETA images 🙂

jmcunx

pin
I just checked 10.0 BETA tmux, all works fine on 10.0 BETA.

I would say this is solved. For the PII with version 9.3, this is a summary:

Base has 3.1c
pkgsrc has 3.3a (2023Q1)
I did not know tmux was in Base
The pkgsrc version works fine on 9.3

So I can say this issue can be closed, will see if it can be marked as as such

Thanks all

jmcunx

This is what I have in the file:

jmcnet1 % grep http /usr/pkg/etc/pkgin/repositories.conf
# Remote http repository
# http://mirror-master.dragonflybsd.org/packages/$arch/DragonFly-$osrelease/stable/All
#OLD#https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/$arch/9.0/All
https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/$arch/9.0_2023Q1/All/

JuvenalUrbino

My fault, thought OP was running 10_BETA 😉

JuvenalUrbino No worries 😉
Still, I would like to know what pkgin repository OP is using, 3.1c is old by now and shouldn't be available.
My guess, is that OP has an old 9.0 repository enabled by default, which is bad.

JuvenalUrbino

pin My guess, is that OP has an old 9.0 repository enabled by default, which is bad.

3.1c is the built-in version currently available on -9 (since 9.2_RELEASE).

JuvenalUrbino But, OP said it was installed with pkgin. Of course, launching tmux without using ${PATH} will start the built-in binary.

EDIT: I have no clue as to what is built-in anymore. Over two years now only running current. Thanks!

jmcunx Looks ok. Apparently, 2023Q2 is not available yet, http://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/amd64/