Skip to content

MXQI: Unable to enter UTF-8 characters like … #459

Closed
pmenzel opened this issue Apr 24, 2025 · 3 comments · Fixed by #460
Closed

MXQI: Unable to enter UTF-8 characters like … #459

pmenzel opened this issue Apr 24, 2025 · 3 comments · Fixed by #460

Comments

@pmenzel
Copy link
Contributor

pmenzel commented Apr 24, 2025

$ env | grep LANG
GDM_LANG=de_DE.UTF-8
LANG=de_DE.UTF-8
$ # …
$ ssh -t pmenzel@geniux.molgen.mpg.de mxqi -j 64 -m 200G --whitelist hotelcalifornia

Requested Resources:

    processors:    64
    max memory:    204800 MB
    max runtime:   600 min
    whitelist:     hotelcalifornia

Note, that your job is killed without warning, if you exceed the reserved memory or runtime.

Waiting for callback from job 54849681 (group 568440)
Last login: Wed Apr 23 16:23:15 2025 from geniux.molgen.mpg.de
[…]
$ env
SHELL=/usr/bin/bash
MXQ_SERVERID=main
MXQ_JOBID=54849681
MXQI_SUBMIT_WD=/home/pmenzel
PWD=/home/pmenzel
LOGNAME=pmenzel
HOME=/home/pmenzel
TMPDIR=/dev/shm/mxqd/mnt/job/54849681
PERL5LIB=/home/pmenzel/perl5/lib/perl5
MXQ_THREADS=64
MXQ_TIME=600
SSH_CONNECTION=141.14.21.78 39526 141.14.16.151 33927
MXQ_MEMORY=204800
TERM=xterm-256color
PERL_MB_OPT=--install_base "/home/pmenzel/perl5"
USER=pmenzel
MXQ_HOSTNAME=hotelcalifornia.molgen.mpg.de
MXQ_HOSTID=12c86da0-a55a-4b72-b587-6b40f466b0b6-436a9-a22
PERL_MM_OPT=INSTALL_BASE=/home/pmenzel/perl5
SHLVL=1
PS1=\u@\h:\w\$ 
SSH_CLIENT=141.14.21.78 39526 33927
PERL_LOCAL_LIB_ROOT=/home/pmenzel/perl5
PATH=/home/pmenzel/perl5/bin:/usr/local/package/bin:/usr/local/bin:/usr/sbin:/usr/bin:/home/pmenzel/bin:/home/pmenzel/.cargo/bin
MXQ_SLOTS=64
JOB_ID=54849681
MAIL=/var/mail/pmenzel
SSH_TTY=/dev/pts/1
_=/usr/bin/env

Entering … or pasting it into the terminal is not possible.

@donald
Copy link
Collaborator

donald commented Apr 29, 2025

Hmmm, the ssh server doesn't have PAM enable. And it can't be enabled. sshd_config(5): "If UsePAM is enabled, you will not be able to run sshd(8) as a non-root user. The default is no."

For normal ssh connections, we set LC_CTYPE DEFAULT=en_US.UTF-8 via /etc/security/pam_env.conf via pam_env via /etc/pam.d/sshd.

We can just hardcode that into mxqi. Or would it be cleaner to forward it from the client?

@pmenzel pmenzel changed the title Unable to enter UTF-8 characters like … MXQI: Unable to enter UTF-8 characters like … Apr 30, 2025
@pmenzel
Copy link
Contributor Author

pmenzel commented Apr 30, 2025

We can just hardcode that into mxqi. Or would it be cleaner to forward it from the client?

I guess forwarding it is cleaner, but until now nobody but me asked for it. So hardcoding it, if much easier, should be enough.

@pmenzel
Copy link
Contributor Author

pmenzel commented Apr 30, 2025

Merci! Works for me.

(My test was incorrect, and mxqi would have needed to be updated on stairwaytoheaven.)

Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants