I got warning setlocale LC_CTYPE when I ssh connect to vagrant centos 6

Question

I'm a beginner with vagrant. I try to create a virtual machine (cent os 6) on my computer with vagrant. When I run vagrant ssh, it prints this warning:

-bash: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8): No such file or directory

When I run locale, I get this:

locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LC_CTYPE=UTF-8
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

I searched for an hour but I still cannot fix that.

Possible duplicate of [Locale Error in centos](https://stackoverflow.com/questions/22430747/locale-error-in-centos) — kenorb, Apr 18 '18 at 15:51

Dominik · Answer 1 · 2016-12-02T12:57:13.250

76

For CentOS or Amazon AMI Linux, add these lines to /etc/environment (create it, if it doesn't exist):

LANG=en_US.UTF-8
LC_ALL=en_US.UTF-8

To edit this file via SSH console, try

sudo nano /etc/environment

Edit

For Debian-related distributions (Ubuntu, etc.), you should check that /etc/default/locale is empty. That's the outcome of choosing None in dpkg-reconfigure locales which is suggested if users access via SSH (see Debian Wiki).

/etc/environment is deprecated since Debian Lenny (5.0).

edited Dec 02 '16 at 12:57

answered Aug 19 '16 at 16:54

Dominik

2,283
1
25
37

`/etc/default/locale` seems to be a more reasonable place for such configuration. – Franklin Yu Dec 01 '16 at 22:52
@FranklinYu It seems that `/etc/environment` is deprecated only in Debian. Updated my answer. – Dominik Dec 02 '16 at 12:58
In Fedora I would add: `LC_CTYPE="en_US.UTF-8"` to `/etc/locale.conf` . – MichK Dec 19 '17 at 11:39

kenorb · Answer 2 · 2019-06-12T11:43:31.590

You can set LC_ALL to C, e.g.

export LC_ALL=C

or prefix before connecting to your VM:

LC_ALL=C ssh vagrant@localhost

^{Note: You can consider also setting SetEnv for your SSH config (man ssh_config) as explained below.}

To make it permanent, you can add the following rule in your ~/.ssh/config:

Host *
  SetEnv LC_ALL=C

Assuming your server got the following line in /etc/ssh/sshd_config:

AcceptEnv LANG LC_*

Check also: man ssh_config and man sshd_config.

score 6 · Answer 3 · edited Feb 25 '16 at 08:48

6

Under root in bashrc add following :

vi /root/.bashrc

export LC_ALL=en_US.UTF-8

export LANG=en_US.UTF-8

And reboot your system afterwards.

edited Feb 25 '16 at 08:48

Markus

3,225
6
35
47

answered Feb 25 '16 at 08:18

Slava

87
1

This only sets the environment variables for the root user, which probably is not the user you log in with when you see the warning message – drrossum Dec 08 '17 at 09:47
1

This works for me, in my local user as I didn't have root access, not need to restart, just log off, and log in. Thanks! – dhgouveia2 Jan 09 '20 at 09:02

score 5 · Answer 4 · answered May 27 '21 at 13:33

This might be caused by your terminal settings.

For iTerm2, uncheck this setting:

Profiles -> Terminal -> "Set locale variables automatically".

Context: In case you are working on a shared node where you can't modify locale settings, the warning might be caused by your terminal trying (and failing) to change locale.

score 3 · Answer 5 · answered Aug 07 '16 at 10:48

3

In my case, on Slackware64 14.1 I got the error:

-bash: warning: setlocale: LC_ALL: cannot change locale (en_DK.UTF-8)

It turned out to be missing glibc packages.

Installing the packages:

glibc-2.17-x86_64-11_slack14.1
glibc-i18n-2.17-x86_64-11_slack14.1

Solved the problem.

My /etc/profile.d/lang.sh contains:

export LANG=en_DK.UTF-8
export LANGUAGE=en_DK.UTF-8
export LC_ALL=en_DK.UTF-8

export LC_COLLATE=C

Enjoy.

answered Aug 07 '16 at 10:48

Mogens TrasherDK

661
1
10
19

I had the same problem but on Android/Termux. https://github.com/termux/termux-packages/issues/3009 – Vlastimil Ovčáčík Nov 02 '18 at 17:06

score 2 · Answer 6 · answered Mar 30 '22 at 11:50

2

I'm using macOS. I put the following contents into my ~/.ssh/config:

Host *
    SetEnv LC_CTYPE=

It seems to me the least intrusive way to alter ssh configuration.

answered Mar 30 '22 at 11:50

vbezhenar

11,148
9
49
63

score 1 · Answer 7 · answered Feb 25 '16 at 12:28

1

please try next:

localedef -i en_US -f UTF-8 en_US.UTF-8

answered Feb 25 '16 at 12:28

Slava

87
1

1

Put this as an Edit to your original answer earlier, or as a Comment on that. – aneroid Feb 27 '16 at 12:27

score 0 · Answer 8 · answered Feb 15 '22 at 10:23

For those getting this error in MacOS: Open /etc/ssh/ssh_config file (in any editor you prefer, I have used vi editor in the example)

sudo vi /etc/ssh/ssh_config
(enter sudo password)

in this file, comment out the line below:

SendEnv LANG LC_*

(use # for commenting: #SendEnv LANG LC_*)

close the file. Close and reopen the terminal and try the ssh command again.

For a detailed understanding of the issue you can check this tech blog: https://www.cyberciti.biz/faq/os-x-terminal-bash-warning-setlocale-lc_ctype-cannot-change-locale/

I got warning setlocale LC_CTYPE when I ssh connect to vagrant centos 6

8 Answers8