[systemd-devel] Need suggsetion on weird characters on RHEL7 !
Hello, I need suggestion on a case 01270671, where customer is getting weird characters as below : Can some one suggest what is wrong? Weird characters when displaying man pages on RHEL 7.0 e.g. man firewall-cmd ample 2 Enable port 443/tcp immediately and permanently in default zone. To make the change effective immediately and also after restart we need two commands. The first command makes the change in runtime configuration, i.e. makes it effective immediately, until restart. The second command makes the change in permanent configuration, i.e. makes it effective after restart. firewall-cmd --add-port=443/tcp firewall-cmd --permanent --add-port=443/tcp EXIT CODES On success 0 is returned. On failure the output is red colored and exit code is either 2 in case of wrong command-line option usage or one of the following error codes in other cases: ┌────────────────────┬──────┠│String │ Code │ ├────────────────────┼──────┤ │ALREADY_ENABLED │ 11 │ ├────────────────────┼──────┤ │NOT_ENABLED │ 12 │ ├────────────────────┼──────┤ │COMMAND_FAILED │ 13 │ ├────────────────────┼──────┤ │NO_IPV6_NAT │ 14 │ ├────────────────────┼──────┤ │PANIC_MODE │ 15 │ --- Also customer can see these characters in other commands too e.g. systemctl [root@eadmzu084p ~]# systemctl list-dependencies rpcbind.service rpcbind.service ├─rpcbind.socket ├─system.slice └─basic.target ├─firewalld.service ├─microcode.service ├─rhel-autorelabel-mark.service ├─rhel-autorelabel.service ├─rhel-configure.service ├─rhel-dmesg.service ├─rhel-loadmodules.service ├─paths.target ├─slices.target │ ├─-.slice │ └─system.slice ├─sockets.target │ ├─dbus.socket │ ├─dm-event.socket │ ├─iscsid.socket │ ├─iscsiuio.socket │ ├─lvm2-lvmetad.socket │ ├─systemd-initctl.socket │ ├─systemd-journald.socket │ ├─systemd-shutdownd.socket │ ├─systemd-udevd-control.socket │ └─systemd-udevd-kernel.socket ├─sysinit.target │ ├─dev-hugepages.mount │ ├─dev-mqueue.mount │ ├─dmraid-activation.service │ ├─iscsi.service │ ├─kmod-static-nodes.service │ ├─lvm2-monitor.service -- Here is the output of env and os-release from customer end : [root@~]# env XDG_SESSION_ID=877 HOSTNAME=eadmzu084p.ea.toyota-fs.com SHELL=/bin/bash TERM=vt100 HISTSIZE=1000 USER=root LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=01;05;37;41:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=01;36:*.au=01;36:*.flac=01;36:*.mid=01;36:*.midi=01;36:*.mka=01;36:*.mp3=01;36:*.mpc=01;36:*.ogg=01;36:*.ra=01;36:*.wav=01;36:*.axa=01;36:*.oga=01;36:*.spx=01;36:*.xspf=01;36: MAIL=/var/spool/mail/root PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin PWD=/root LANG=en_GB.UTF-8 HISTCONTROL=ignoredups SHLVL=1 HOME=/root LOGNAME=root LESSOPEN=||/usr/bin/lesspipe.sh %s _=/bin/env --- [root@eadmzu084p ~]# cat /etc/os-release NAME=Red Hat Enterprise Linux Server VERSION=7.0 (Maipo) ID=rhel ID_LIKE=fedora VERSION_ID=7.0 PRETTY_NAME=Red Hat Enterprise Linux ANSI_COLOR=0;31
Re: [systemd-devel] Need suggsetion on weird characters on RHEL7 !
From memory that's pretty standard with vt100 emulation, I always noticed it in man pages .. have they tried setting TERM to xterm? - Original Message - From: Manish Saxena msax...@redhat.com To: systemd-devel@lists.freedesktop.org, Red Hat Technical Discussion List tech-l...@redhat.com Sent: Tuesday, 28 October, 2014 11:28:54 PM Subject: Need suggsetion on weird characters on RHEL7 ! Hello, I need suggestion on a case 01270671, where customer is getting weird characters as below : Can some one suggest what is wrong? Weird characters when displaying man pages on RHEL 7.0 e.g. man firewall-cmd ample 2 Enable port 443/tcp immediately and permanently in default zone. To make the change effective immediately and also after restart we need two commands. The first command makes the change in runtime configuration, i.e. makes it effective immediately, until restart. The second command makes the change in permanent configuration, i.e. makes it effective after restart. firewall-cmd --add-port=443/tcp firewall-cmd --permanent --add-port=443/tcp EXIT CODES On success 0 is returned. On failure the output is red colored and exit code is either 2 in case of wrong command-line option usage or one of the following error codes in other cases: ┌────────────────────┬──────┠│String │ Code │ ├────────────────────┼──────┤ │ALREADY_ENABLED │ 11 │ ├────────────────────┼──────┤ │NOT_ENABLED │ 12 │ ├────────────────────┼──────┤ │COMMAND_FAILED │ 13 │ ├────────────────────┼──────┤ │NO_IPV6_NAT │ 14 │ ├────────────────────┼──────┤ │PANIC_MODE │ 15 │ --- Also customer can see these characters in other commands too e.g. systemctl [root@eadmzu084p ~]# systemctl list-dependencies rpcbind.service rpcbind.service ├─rpcbind.socket ├─system.slice └─basic.target ├─firewalld.service ├─microcode.service ├─rhel-autorelabel-mark.service ├─rhel-autorelabel.service ├─rhel-configure.service ├─rhel-dmesg.service ├─rhel-loadmodules.service ├─paths.target ├─slices.target │ ├─-.slice │ └─system.slice ├─sockets.target │ ├─dbus.socket │ ├─dm-event.socket │ ├─iscsid.socket │ ├─iscsiuio.socket │ ├─lvm2-lvmetad.socket │ ├─systemd-initctl.socket │ ├─systemd-journald.socket │ ├─systemd-shutdownd.socket │ ├─systemd-udevd-control.socket │ └─systemd-udevd-kernel.socket ├─sysinit.target │ ├─dev-hugepages.mount │ ├─dev-mqueue.mount │ ├─dmraid-activation.service │ ├─iscsi.service │ ├─kmod-static-nodes.service │ ├─lvm2-monitor.service -- Here is the output of env and os-release from customer end : [root@~]# env XDG_SESSION_ID=877 HOSTNAME=eadmzu084p.ea.toyota-fs.com SHELL=/bin/bash TERM=vt100 HISTSIZE=1000 USER=root LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=01;05;37;41:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01!
Re: [systemd-devel] Need suggsetion on weird characters on RHEL7 !
On Tue, Oct 28, 2014 at 2:28 PM, Manish Saxena msax...@redhat.com wrote: Hello, I need suggestion on a case 01270671, where customer is getting weird characters as below : Can some one suggest what is wrong? Weird characters when displaying man pages on RHEL 7.0 e.g. man firewall-cmd ample 2 Enable port 443/tcp immediately and permanently in default zone. To make the change effective immediately and also after restart we need two commands. The first command makes the change in runtime configuration, i.e. makes it effective immediately, until restart. The second command makes the change in permanent configuration, i.e. makes it effective after restart. firewall-cmd --add-port=443/tcp firewall-cmd --permanent --add-port=443/tcp EXIT CODES On success 0 is returned. On failure the output is red colored and exit code is either 2 in case of wrong command-line option usage or one of the following error codes in other cases: ┌────────────────────┬──────┠│String │ Code │ ├────────────────────┼──────┤ │ALREADY_ENABLED │ 11 │ ├────────────────────┼──────┤ │NOT_ENABLED │ 12 │ ├────────────────────┼──────┤ │COMMAND_FAILED │ 13 │ ├────────────────────┼──────┤ │NO_IPV6_NAT │ 14 │ ├────────────────────┼──────┤ │PANIC_MODE │ 15 │ What you're seeing here is a table or a tree drawn using the Unicode line-drawing characters, which `man` outputs encoded as UTF-8 (due to the correct $LANG), but your terminal emulator is trying to decode each byte as ISO-8859-1 instead (usually due to wrong, or lack of, $LANG in its own environment). You didn't mention /which/ terminal emulator is used: * For the Linux console, UTF-8 mode is enabled by systemd-vconsole-setup.service, but only when the system locale is a UTF-8 one (that is, when /etc/locale.conf has LANG=en_GB.UTF-8 or something such). [Note that some things might accidentally turn off the UTF-8 mode or prevent it from being enabled; there was another thread just last week about such problems.] Check src/vconsole-setup/vconsole-setup.c:enable_utf8 to see how it's done. * For X11 terminal emulators, having $LANG in environment should be enough. This problem usually occurs when $LANG is being set in the wrong place (e.g. ~/.bashrc), so the shell has it but the terminal emulator doesn't. You can verify this by checking /proc/pid/environ. * Various layers like tmux or screen can also have the same problem as X11 terminals above ($LANG correct inside but wrong outside). * Older versions of screen can't read locale settings and need UTF-8 mode enabled explicitly using `screen -U`. -- Mantas Mikulėnas graw...@gmail.com ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Need suggsetion on weird characters on RHEL7 !
Thanks everyone, actually customer was using some third party software to access the terminal which they confirmed now. and they are not facing any issue while using console or ssh. Thanks for help and sorry for noise. Regards, Manish - Original Message - From: Morgan Weetman mweet...@redhat.com To: Red Hat Technical Discussion List tech-l...@redhat.com Cc: systemd-devel@lists.freedesktop.org Sent: Tuesday, October 28, 2014 6:09:26 PM Subject: Re: Need suggsetion on weird characters on RHEL7 ! From memory that's pretty standard with vt100 emulation, I always noticed it in man pages .. have they tried setting TERM to xterm? - Original Message - From: Manish Saxena msax...@redhat.com To: systemd-devel@lists.freedesktop.org, Red Hat Technical Discussion List tech-l...@redhat.com Sent: Tuesday, 28 October, 2014 11:28:54 PM Subject: Need suggsetion on weird characters on RHEL7 ! Hello, I need suggestion on a case 01270671, where customer is getting weird characters as below : Can some one suggest what is wrong? Weird characters when displaying man pages on RHEL 7.0 e.g. man firewall-cmd ample 2 Enable port 443/tcp immediately and permanently in default zone. To make the change effective immediately and also after restart we need two commands. The first command makes the change in runtime configuration, i.e. makes it effective immediately, until restart. The second command makes the change in permanent configuration, i.e. makes it effective after restart. firewall-cmd --add-port=443/tcp firewall-cmd --permanent --add-port=443/tcp EXIT CODES On success 0 is returned. On failure the output is red colored and exit code is either 2 in case of wrong command-line option usage or one of the following error codes in other cases: ┌────────────────────┬──────┠│String │ Code │ ├────────────────────┼──────┤ │ALREADY_ENABLED │ 11 │ ├────────────────────┼──────┤ │NOT_ENABLED │ 12 │ ├────────────────────┼──────┤ │COMMAND_FAILED │ 13 │ ├────────────────────┼──────┤ │NO_IPV6_NAT │ 14 │ ├────────────────────┼──────┤ │PANIC_MODE │ 15 │ --- Also customer can see these characters in other commands too e.g. systemctl [root@eadmzu084p ~]# systemctl list-dependencies rpcbind.service rpcbind.service ├─rpcbind.socket ├─system.slice └─basic.target ├─firewalld.service ├─microcode.service ├─rhel-autorelabel-mark.service ├─rhel-autorelabel.service ├─rhel-configure.service ├─rhel-dmesg.service ├─rhel-loadmodules.service ├─paths.target ├─slices.target │ ├─-.slice │ └─system.slice ├─sockets.target │ ├─dbus.socket │ ├─dm-event.socket │ ├─iscsid.socket │ ├─iscsiuio.socket │ ├─lvm2-lvmetad.socket │ ├─systemd-initctl.socket │ ├─systemd-journald.socket │ ├─systemd-shutdownd.socket │ ├─systemd-udevd-control.socket │ └─systemd-udevd-kernel.socket ├─sysinit.target │ ├─dev-hugepages.mount │ ├─dev-mqueue.mount │ ├─dmraid-activation.service │ ├─iscsi.service │ ├─kmod-static-nodes.service │ ├─lvm2-monitor.service -- Here is the output of env and os-release from customer end : [root@~]# env XDG_SESSION_ID=877 HOSTNAME=eadmzu084p.ea.toyota-fs.com SHELL=/bin/bash TERM=vt100 HISTSIZE=1000 USER=root
