Discuss

discuss@lists.centos.org

7 participants
34743 discussions

clamd / amavisd missing socket
by Jon LaBadie 12 Sep '19

12 Sep '19

I think something along these lines appeared before but I was unable to find them. I'm on a 7.6 system, been running clamav and amavisd-new since 6 days with little problem. On a recent reboot, clamd@amavisd does not start up and fails manual start. The problem seems to be the missing socket that connects the pair, "/var/run/clamd.amavisd/clamd.socket". I believe this should be created by systemd files but I see no indication of them on my system. Anyone know which files might be missing and where to get copies? Or a work around to run clamd@amavisd and get rid of the "*** UNCHECKED ***' additions to my my Subject lines? BTW manual creation of the socket with netcat had no effect on the startup. Jon -- Jon H. LaBadie jon(a)jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)

2 2

Increase logging verbosity of saslauthd?
by Jobst Schmalenbach 12 Sep '19

12 Sep '19

Hi CentOS 7.X, sendmail.x86_64 8.14.7-5.el7, cyrus-sasl.x86_64 2.1.26-23.el7 There are conflicting message on how to increase the logging of saslauthd. I know I can do this: /usr/sbin/saslauthd -d -n0 -m /var/run/saslauthd -a pam but that requires a terminal as saslauthd logs the output to STDOUT, this is not what I want. I would like to have it started as a daemon and verbosity of logging increased into a log file. How can I increase the verbosity of logging for saslauthd? thanks -- Jobst Schmalenbach If you think knowledge is expensive, try ignorance.

3 5

Need to update gcc to version >=6 on CentOS 7 ?
by John Chludzinski 11 Sep '19

11 Sep '19

I need to build u-boot on my CentOS 7 machine but encounter this: > *** Your GCC is older than 6.0 and is not supported I've updated the installation on my machine but the current version is: > gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36) How do I go about updating gcc to version 6 or greater on my CentOS 7 machine? And do so safely?

3 7

NFS Server on Centos 7.6.1810 dying without reason
by Erick Perez - Quadrian Enterprises 07 Sep '19

07 Sep '19

Good morning, in order to post proper documentation, what logs (or log level) do I need to troubleshoot a Centos 7.6.1810 3.10.0-957.27.2.el7.x86_64 tha tis running a NFS server on top LVM on top of XFS on top of VDO on top of MDAM on a 6 SSD disk RAID6 ? This physical NFS server is servign 2 NFS v4.2 shares to 2 physical KVM virtualization hosts. When remote NFS clients start doing intensive stuff (massive writes) , the NFS server crashes and sometimes make the Linux server reboot. form KVM side this is all I get: hvm002 kernel: nfs: server 10.10.10.2 not responding, timed out thanks --------------------- Erick ---------------------

2 2

CUPS job handling
by hw 06 Sep '19

06 Sep '19

Hi, is it somehow possible to make CUPS automatically redirect jobs, and following jobs, away from printers which can not print them to other printers that can print them until the printers that couldn't print them are again able to print them? Like I have a bunch of label printers which are all the same, and all of which are prone to run out of labels or out of ribbon every now and then. It can take hours or even days before someone can refill a printer. Hence it would be very useful if CUPS could be told something like "if printer A doesn't print, move its current job to printer B and divert all new jobs sent to A to printer B instead until A prints again". What exactly happens when a printer that is member of a class can not print a job that was sent to the class? Will the unprintable job be automatically moved to another member of the same class, or will it only be aborted and never printed? With a class of two printers and one of them running out of labels, /var/log/cups/error_log only holds: ... [Job 174733] Stopping unresponsive job. What does this mean? Has the job been printed or not? Has it been printed after I refilled the printer?

5 6

oval support for centos
by Sep0lkit 06 Sep '19

06 Sep '19

We use oval to check the system vulnerability. Redhat offer official oval(https://www.redhat.com/security/data/oval/), and it works well on redhat. There is no official centos oval, and using redhat oval on centos got false results. centos is based redhat, so I wrote a script fetch redhat oval files and convert it to useful for centos. And I push the oval to my github: https://github.com/Sep0lkit/oval-for-el Everyone interested in this can try to use it and tell me it works correctly or not.

2 2

CentOS 8 will be released soon?
by Turritopsis Dohrnii Teo En Ming 05 Sep '19

05 Sep '19

Good afternoon from Singapore, According to the CentOS 8 build timeline, everything has been completed except release work. Does this mean CentOS 8 will be released soon? https://wiki.centos.org/About/Building_8 -----BEGIN EMAIL SIGNATURE----- The Gospel for all Targeted Individuals (TIs): [The New York Times] Microwave Weapons Are Prime Suspect in Ills of U.S. Embassy Workers Link: https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html ******************************************************************************************** Singaporean Mr. Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 14 Feb 2019 [1] https://tdtemcerts.wordpress.com/ [2] https://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming -----END EMAIL SIGNATURE-----

7 7

nextcloud-client currently not installable from EPEL in CentOS7
by Kay Diederichs 02 Sep '19

02 Sep '19

Dear all, after enabling the EPEL repository, [root@localhost ~]# yum install nextcloud-client in a freshly installed and updated CentOS 7.6 machine gives Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: centos.bio.lmu.de * epel: ftp.uni-stuttgart.de * extras: centos.schlundtech.de * updates: mirror1.hs-esslingen.de Resolving Dependencies --> Running transaction check ---> Package nextcloud-client.x86_64 0:2.3.3-1.el7 will be installed --> Processing Dependency: nextcloud-client-libs(x86-64) = 2.3.3-1.el7 for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Processing Dependency: libQt5WebKitWidgets.so.5(Qt_5)(64bit) for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Processing Dependency: libQt5Solutions_LockedFile-2.4.so.1()(64bit) for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Processing Dependency: libQt5Solutions_SingleApplication-2.6.so.1()(64bit) for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Processing Dependency: libQt5WebKit.so.5()(64bit) for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Processing Dependency: libQt5WebKitWidgets.so.5()(64bit) for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Processing Dependency: libnextcloudsync.so.0()(64bit) for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Processing Dependency: libocsync.so.0()(64bit) for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Processing Dependency: libqt5keychain.so.1()(64bit) for package: nextcloud-client-2.3.3-1.el7.x86_64 --> Running transaction check ---> Package nextcloud-client-libs.x86_64 0:2.3.3-1.el7 will be installed ---> Package qt5-qtwebkit.x86_64 0:5.9.1-2.el7 will be installed --> Processing Dependency: qt5-qtbase(x86-64) = 5.9.7 for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: qt5-qtdeclarative(x86-64) = 5.9.7 for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Positioning.so.5(Qt_5)(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Qml.so.5(Qt_5)(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Quick.so.5(Qt_5)(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Quick.so.5(Qt_5_PRIVATE_API)(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Sensors.so.5(Qt_5)(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5WebChannel.so.5(Qt_5)(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Positioning.so.5()(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Qml.so.5()(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Quick.so.5()(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5Sensors.so.5()(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: libQt5WebChannel.so.5()(64bit) for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 ---> Package qtkeychain-qt5.x86_64 0:0.7.0-1.el7 will be installed --> Processing Dependency: qtkeychain(x86-64) = 0.7.0-1.el7 for package: qtkeychain-qt5-0.7.0-1.el7.x86_64 ---> Package qtlockedfile-qt5.x86_64 0:2.4-20.20150629git5a07df5.el7 will be installed ---> Package qtsingleapplication-qt5.x86_64 0:2.6.1-28.el7 will be installed --> Running transaction check ---> Package qt5-qtdeclarative.x86_64 0:5.9.2-1.el7 will be installed --> Processing Dependency: libQt5XmlPatterns.so.5(Qt_5)(64bit) for package: qt5-qtdeclarative-5.9.2-1.el7.x86_64 --> Processing Dependency: libQt5XmlPatterns.so.5()(64bit) for package: qt5-qtdeclarative-5.9.2-1.el7.x86_64 ---> Package qt5-qtlocation.x86_64 0:5.9.2-1.el7 will be installed ---> Package qt5-qtsensors.x86_64 0:5.9.2-1.el7 will be installed ---> Package qt5-qtwebchannel.x86_64 0:5.9.2-1.el7 will be installed ---> Package qt5-qtwebkit.x86_64 0:5.9.1-2.el7 will be installed --> Processing Dependency: qt5-qtbase(x86-64) = 5.9.7 for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: qt5-qtdeclarative(x86-64) = 5.9.7 for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 ---> Package qtkeychain.x86_64 0:0.7.0-1.el7 will be installed --> Processing Dependency: libQtCore.so.4()(64bit) for package: qtkeychain-0.7.0-1.el7.x86_64 --> Processing Dependency: libQtDBus.so.4()(64bit) for package: qtkeychain-0.7.0-1.el7.x86_64 --> Running transaction check ---> Package qt.x86_64 1:4.8.7-3.el7_6 will be installed --> Processing Dependency: qt-settings for package: 1:qt-4.8.7-3.el7_6.x86_64 ---> Package qt5-qtwebkit.x86_64 0:5.9.1-2.el7 will be installed --> Processing Dependency: qt5-qtbase(x86-64) = 5.9.7 for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: qt5-qtdeclarative(x86-64) = 5.9.7 for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 ---> Package qt5-qtxmlpatterns.x86_64 0:5.9.2-1.el7 will be installed --> Running transaction check ---> Package qt-settings.noarch 0:19-23.8.el7.centos will be installed ---> Package qt5-qtwebkit.x86_64 0:5.9.1-2.el7 will be installed --> Processing Dependency: qt5-qtbase(x86-64) = 5.9.7 for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Processing Dependency: qt5-qtdeclarative(x86-64) = 5.9.7 for package: qt5-qtwebkit-5.9.1-2.el7.x86_64 --> Finished Dependency Resolution Error: Package: qt5-qtwebkit-5.9.1-2.el7.x86_64 (epel) Requires: qt5-qtbase(x86-64) = 5.9.7 Installed: qt5-qtbase-5.9.2-3.el7.x86_64 (@anaconda) qt5-qtbase(x86-64) = 5.9.2-3.el7 Error: Package: qt5-qtwebkit-5.9.1-2.el7.x86_64 (epel) Requires: qt5-qtdeclarative(x86-64) = 5.9.7 Available: qt5-qtdeclarative-5.9.2-1.el7.x86_64 (base) qt5-qtdeclarative(x86-64) = 5.9.2-1.el7 Error: Package: qt5-qtwebkit-5.9.1-2.el7.x86_64 (epel) Requires: qt5-qtdeclarative(x86-64) = 5.9.7 Installing: qt5-qtdeclarative-5.9.2-1.el7.x86_64 (base) qt5-qtdeclarative(x86-64) = 5.9.2-1.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest [root@localhost ~]# The culprit appears to be the current qt5-qtwebkit-5.9.1-2 from EPEL. A workaround is: downloading and installing qt5-qtwebkit-5.9.1-1 (from https://archive.fedoraproject.org/pub/archive/epel/7/x86_64/Packages/ ) lets the installation succeed. However, /etc/yum.conf then needs exclude=qt5-qtwebkit I think this is is due to the fact that EPEL is synchronized with RedHat (which has version 7.7), but CentOS is still at 7.6 This type of problem has bitten us a couple of times (mostly with ElRepo and the NVidia kmod and driver) - whenever a CentOS update was not yet ready, but the corresponding RedHat point release was out. ElRepo seems to have an elegant solution for this solution - yum-plugin-elrepo . Is there anything like that available for EPEL ? thanks, Kay

1 0

Mailbox for Sysadmin
by Administrator 01 Sep '19

01 Sep '19

Good day Administrator, Every self-respecting Admin should have a mailbox in worthy domain. Do you have it already? If no - go to https://nox11.com choose one and start new life If you aren't interested accept apology for spam. --- Cheers admin(a)nox11.com

3 2

I broke "yum update" - C7
by Gary Stainburn 30 Aug '19

30 Aug '19

This evening I decided to do some work on my development C7 system. As I have not touched it for a while, and wanted to install new services I thought I'd better yum update first. I saw that it only did updates from Google and PHP, and none from the system repo's so I had a closer look. It showed certificate errors on a number of repo's. [root@stan2 ~]# yum update Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=x86_64 error was 14: curl#60 - "Peer's Certificate issuer is not recognized." * base: mirrors.clouvider.net * epel: mirrors.coreix.net * extras: mirrors.clouvider.net * remi-php72: mirror.netweaver.uk * remi-safe: mirror.netweaver.uk * updates: mirrors.vooservers.com https://rpm.nodesource.com/pub_6.x/el/7/x86_64/repodata/repomd.xml: [Errno 14] curl#60 - "Peer's Certificate issuer is not recognized." Trying other mirror. It was impossible to connect to the CentOS servers. This could mean a connectivity issue in your environment, such as the requirement to configure a proxy, or a transparent proxy that tampers with TLS security, or an incorrect system clock. You can try to solve this issue by using the instructions on https://wiki.centos.org/yum-errors If above article doesn't help to resolve this issue please use https://bugs.centos.org/. https://download.postgresql.org/pub/repos/yum/10/redhat/rhel-7-x86_64/repod…: [Errno 14] curl#60 - "Peer's Certificate issuer is not recognized." Trying other mirror. https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/repo…: [Errno 14] curl#60 - "Peer's Certificate issuer is not recognized." Trying other mirror. No packages marked for update [root@stan2 ~]# I wrongly followed the instructions in https://wiki.centos.org/yum-errors hoping that it would resolve the problems but it's only made it worse. Now all I get is: [root@stan2 ~]# yum clean all Loaded plugins: fastestmirror, langpacks Cleaning repos: base epel extras google-chrome nodesource pgdg10 pgdg96 remi-php72 remi-safe updates Cleaning up list of fastest mirrors [root@stan2 ~]# rm -rf /var/cache/yum/* [root@stan2 ~]# yum update Loaded plugins: fastestmirror, langpacks Determining fastest mirrors One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this: 1. Contact the upstream for the repository and get them to fix the problem. 2. Reconfigure the baseurl/etc. for the repository, to point to a working upstream. This is most often useful if you are using a newer distribution release than is supported by the repository (and the packages for the previous distribution release still work). 3. Run the command with the repository temporarily disabled yum --disablerepo=<repoid> ... 4. Disable the repository permanently, so yum won't use it by default. Yum will then just ignore the repository until you permanently enable it again or use --enablerepo for temporary usage: yum-config-manager --disable <repoid> or subscription-manager repos --disable=<repoid> 5. Configure the failing repository to be skipped, if it is unavailable. Note that yum will try to contact the repo. when it runs most commands, so will have to try and fail each time (and thus. yum will be be much slower). If it is a very temporary problem though, this is often a nice compromise: yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again [root@stan2 ~]# I removed and re-installed the epel-release RPM which made no difference. I've also tried disabling each repo in turn, pgdg10, remi-php72, nodesource-el, pgdg96, google-chrome but still have no success. Anyone got any suggestions?

7 28

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