Discuss

discuss@lists.centos.org

8 participants
34745 discussions

Weird localectl behavior under CentOS 7
by Nicolas Kovacs 15 May '21

15 May '21

Hi, On a fresh CentOS 7 installation using Français/France as regional parameters in the installer, here's what localectl looks like: [microlinux@linuxbox ~]$ localectl System Locale: LANG=fr_FR.UTF-8 VC Keymap: ch-fr X11 Layout: ch X11 Variant: fr Now I'd like to have my system messages in english. So I set the system language accordingly: $ sudo localectl set-locale LANG=en_US.utf8 Things seem to look OK now: [microlinux@linuxbox ~]$ localectl System Locale: LANG=en_US.utf8 VC Keymap: ch-fr X11 Layout: ch X11 Variant: fr Except when I display my LANG variable, it's still fr_FR.UTF-8 for normal users... but en_US.utf8 for root. This looks like inconsistent or buggy behavior to me. Any suggestions on how to change the default system locale LANG so that it's en_US.utf8 for everybody *without* having to jump through burning loops and putting it in everybody's ~/.bashrc ? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32 Mob. : 06 51 80 12 12

3 4

getssl was working stopped
by Jerry Geis 14 May '21

14 May '21

Hi All - I am using getssl on CentOS 7. It have been working fine since Feb 17th and just stopped. My script: getssl -u -a -q getssl: for some reason could not reach http://MY_NAME/.well-known/acme-challenge/lL_ublhWh3fnmbXhhh3BR3bdnjHoMFAgT… - please check it manually So I did check it manually from another machine - it works fine: curl http://MY_NAME/.well-known/acme-challenge/lL_ublhWh3fnmbXhhh3BR3bdnjHoMFAgT… lL_ublhWh3fnmbXhhh3BR3bdnjHoMFAgTimTvZUTLQM.tIS27xF0xtz7YHES31MATofXyCeyfqttq7B_YBYZetI So it works fine. I then thought perhaps a firewall issue. So I "systemctl stop firewalld", redid the getssl -u -a -q command above - and I get the same error. How do I see/tell what its not liking ? Thanks, Jerry

3 5

systemd and 'Stale file handle' errors?
by James Pearson 14 May '21

14 May '21

I have a CentOS 7 system where I needed to restart chronyd - but the systemctl restart failed with the error: systemd[1]: Starting NTP client/server... systemd[43578]: Failed at step NAMESPACE spawning /usr/sbin/chronyd: Stale file handle systemd[1]: chronyd.service: control process exited, code=exited status=226 Turns out there are a couple of Stale NFS file handles from fuse mounts (related to gvfsd) of sub directories under an NFS mounted home directory server - but the home directory for the user in this case, no longer exist (user has left) However, I have no idea why these 'Stale file handles' prevent a service being started by systemd ? In this case, chronyd has nothing to do with NFS mounted user home directories - so shouldn't really care ? I have tried everything I can think of to clear these stale mounts, but with no luck Does anyone know why systemd complains about unconnected 'Stale file handles' - and is there any way I can tell systemctl to start a service regardless of these 'errors' ? Rebooting the host will be a last resort (the system is used by many users) - but in the meantime, I've manually started the /usr/sbin/chronyd binary directly, which runs fine Thanks James Pearson

3 3

cups, stalling the transfer of printed files from the local machines to the cups print server
by Gregory P. Ennis 12 May '21

12 May '21

Everyone, I have been having some problems with our cups printing service for the last 4 months. I have a gateway machine that holds the printer information and is the print server. The other machines on the network use cups and cups-browsed that are set up to spool the print jobs to the gateway and then the gateway sends the data stream to the respective printers. The problem I have is that on any of the local machines the print jobs stall. I can run lpstat lpt6 for instance which gives me the listing of the stalled print jobs, but I am not seeing error messages in the logs either on the local machine or on the gateway print server. In doing some google searching I found that there was a problem with gh ghostscript-9.07-31.el7_6.10.x86_64 and ghostscript-cups-9.07- 31.el7_6.10.x86_64 that was apparently fixed. I am running Centos 7.9 that is fully updated with gs 9.25 on both the local machines and the gateway. The problem is intermittent and appears with various file types pdf, ps, pcl, and txt. I have not been able to identify any specific or consistent association. If any of you have had this problem I would sure appreciate your help. Thanks in advance !!!! -- Greg Ennis

1 1

ipforwarding -- routing
by R C 11 May '21

11 May '21

Hello, I have an accesspoint, that I connected to one ethernetport, the ap has ip 192.168.67.6, the port 192.168.67.1 I want to forward/route traffic for anything in 192.168.66.0 to go to that access point, and from the ap to the other port. What is the best way to do that? I tried: sudo sysctl -w net.ipv4.ip_forward=1 sudo firewall-cmd --direct --add-rule ipv4 filter FORWARD 0 -o eno1 -i enp0s20u4u1 -j ACCEPT sudo firewall-cmd --direct --add-rule ipv4 filter FORWARD 0 -o enp0s20u4u1 -i eno1 -j ACCEPT but that doesn't seem to work. thanks, Ron

2 1

will there be centos 8.4?
by d tbsky 11 May '21

11 May '21

Hi: RHEL 8.3 doesn't offer extended update support, so it seems be EOL this month. but centos8 will be supported until December. so will there be centos 8.4, or centos 8.3 will do the extend update support itself?

5 8

Reminder: CentOS Dojo this week
by Rich Bowen 10 May '21

10 May '21

Reminder: The CentOSDojo is this week, Thursday and Friday. The schedule and (Free!) registration is available at https://wiki.centos.org/Events/Dojo/May2021

1 0

yumex for CentOS 8.3
by Robert G. (Doc) Savage 09 May '21

09 May '21

If yumex is no longer available, please advise. A few minutes ago when 'dnfdragora' failed for CentOS 8.3, I tried: # yumex --root bash: yumex: command not found... Install package 'yumex' to provide command 'yumex'? [N/y] y * Waiting in queue... * Loading list of packages.... Failed to install packages: Could not depsolve transaction; 1 problem detected: Problem: conflicting requests - nothing provides python-iniparse needed by yumex-3.0.15-1.el7.nux.noarch - nothing provides pycairo needed by yumex-3.0.15-1.el7.nux.noarch - nothing provides dbus-python needed by yumex-3.0.15-1.el7.nux.noarch - nothing provides /usr/bin/python needed by yumex-3.0.15-1.el7.nux.noarch - nothing provides pexpect needed by yumex-3.0.15-1.el7.nux.noarch - nothing provides python-kitchen needed by yumex-3.0.15-1.el7.nux.noarch - nothing provides urlgrabber needed by yumex-3.0.15-1.el7.nux.noarch Is this a long-winded way of telling me to forget it? V/R --Doc Savage Fairview Heights, IL

5 7

Re: [CentOS] vlc: - nothing provides libfluidsynth.so.1
by Richard 07 May '21

07 May '21

> Date: Friday, May 07, 2021 15:46:14 -0600 > From: R C <cjvijf(a)gmail.com> > > I am trying to install vlc and get: > > > Problem: conflicting requests > - nothing provides libfluidsynth.so.1()(64bit) needed by vlc > What release of centos and version of vlc? EPEL appears to have libfluidsynth.so.1 for centos-7 fluidsynth-libs-1.1.6-7.el7.x86_64 Repo : epel Matched from: Filename : /usr/lib64/libfluidsynth.so.1 Filename : /usr/lib64/libfluidsynth.so.1.5.2 Did you cut something out from the message? I wouldn't expect (only) a "nothing provides" message under "Problem: conflicting requests:"

2 1

vlc: - nothing provides libfluidsynth.so.1
by R C 07 May '21

07 May '21

Hello, I am trying to install vlc and get: Problem: conflicting requests - nothing provides libfluidsynth.so.1()(64bit) needed by vlc any ideas? thanks, Ron

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss