Discuss

discuss@lists.centos.org

34747 discussions

systemd not restarting daemon
by Chris Adams 26 Aug '16

26 Aug '16

On an up-to-date CentOS 7 system, I am running named-sdb (pulling domain records from MySQL), which is segfaulting randomly (after 3-8 hours or so it appears) in libmysqlclient (I've opened a bug). Since this is an internal service, until the segfault can be addressed, I wanted systemd to restart it for me. I created a file called /etc/systemd/system/named-sdb-chroot.service.d/service.conf with: [Service] Restart=always in it. I did "systemctl daemon-reload" and restarted the service, but systemd is not restarting it. It knows it died, because that's in the log (and it ran the chroot cleanup service): Aug 25 12:03:39 dnssql systemd: named-sdb-chroot.service: main process exited, code=killed, status=11/SEGV Aug 25 12:03:39 dnssql systemd: named-sdb-chroot.service: control process exited, code=exited status=1 Aug 25 12:03:39 dnssql systemd: Unit named-sdb-chroot.service entered failed state. Aug 25 12:03:39 dnssql systemd: named-sdb-chroot.service failed. Aug 25 12:03:39 dnssql systemd: Stopping Set-up/destroy chroot environment for named-sdb... Aug 25 12:03:39 dnssql systemd: Stopped Set-up/destroy chroot environment for named-sdb. I see the file listed in the output of systemd-delta, so I know it is being seen. Any idea why systemd isn't restarting it? -- Chris Adams <linux(a)cmadams.net>

2 3

Email pid issue
by Jay Hart 26 Aug '16

26 Aug '16

Hello gents, First time poster here! Current system running Centos 6.8. Buddy of mine posted a few days back about me wanting to move from Postfix 2.6.x to 2.8 to above, still under centos 6.8. I might move over to 7, but probably not for a while, don't have the resources presently to make this happen. Running Centos 6.8, postfix 2.6.6, clamav 0.99.1. Basic Centos 6.8 box fully patched using stable repos. ____ISSUE_____ Logwatch is reporting this error, which I'm going to assume has been occurring for a few years but doesn't affect sending/receiving emails, so I haven't chased it down, now I'm looking to fix that. 1 (06498-19) ClamAV-clamd: All attempts (1) failed connecting to /var/spool/amavisd/clamd.sock, retrying (1) Since this is reported by "ClamAV-clamd", I am assuming this is coming from amavisd.conf. My logic on this is that a grep search for that particular string only shows up in the /etc/amavisd.conf file, when its calling the scanner. Pasted code from file below: @av_scanners = ( ['ClamAV-clamd', \&ask_daemon, ["CONTSCAN {}\n", "/var/spool/amavisd/clamd.sock"], qr/\bOK$/m, qr/\bFOUND$/m, qr/^.*?: (?!Infected Archive)(.*) FOUND$/m ], Best I can determine /var/spool/amavisd/clamd.sock file exists. So, not sure what is causing this or why, or how to fix. Here is /var/spool/amavisd contents: [run]# ls -al /var/spool/amavisd/ total 64 drwxr-x--- 7 amavis amavis 4096 Aug 21 19:10 . drwxr-xr-x. 15 root root 4096 Mar 15 2012 .. srwxr-x--- 1 amavis amavis 0 Aug 21 19:10 amavisd.sock srw-rw-rw- 1 amavis amavis 0 Aug 21 19:10 clamd.sock drwxr-x--- 2 amavis amavis 4096 Aug 21 19:10 db drwxr-x--- 2 amavis amavis 36864 Aug 21 19:50 quarantine drwxr-x--- 2 amavis amavis 4096 Aug 21 09:23 .razor drwx------ 2 amavis amavis 4096 Aug 21 20:42 .spamassassin drwxr-x--- 4 amavis amavis 4096 Aug 21 20:42 tmp Seems to be owned by the right group, I rebooted at 19.10 today hence timestamp date/time. So, my question is, what do I need to do to eliminate this error? How can I chase it down? TIA, Jay

3 4

Fail on start x server
by Edwin Agudelo 26 Aug '16

26 Aug '16

Good Day. Recently buy an lenovo laptop (110 Ideapad 14IBR). Install (with problems) Centos 7, but when start the first time, get the fail screen. Then, I try to start the x server (startx) get the error: FBIOBLANK invalid argument. This laptop have an Intel HD graphics 400 and a Intel Celeron N3060; googling , I concluded that is a fail in the driver, but don’t know how resolve. Please help me. Sorry For my English. Best regards.

5 10

how to find recently installed font packages
by geo.inbox.ignored 26 Aug '16

26 Aug '16

greetings. in an attempt to display correct fonts in firefox instead of squares with binary values, i installed wrong fonts and made things worse. how do i find out what fonts are, as i did not think to make note of what i was adding? tia. -- peace out. CentOS GNU/Linux 6.8 tc,hago. g . =+= Tired of having your microsoft os hacked? Change to Linux os, used by microsoft hackers. =+= in a world with out fences, who needs gates. =+=

7 9

Centos 7 and php 5.5
by Richard B. Pyne 25 Aug '16

25 Aug '16

I am hoping that the wisdom of the group here can at least point me in the right direction. I have a Centos7 server that I need to upgrade php from 5.4 to 5.5. I've tried several tutorials to add the remi repository and enable php55, but I always end up at the same result: Error: Package: php-5.5.38-1.el6.remi.x86_64 (remi-php55) Requires: httpd-mmn = 20051115 Installed: httpd-2.4.6-40.el7.centos.4.x86_64 (@updates) httpd-mmn = 20120211 httpd-mmn = 20120211x8664 httpd-mmn = 20120211-x86-64 Available: httpd-2.4.6-40.el7.centos.x86_64 (base) httpd-mmn = 20120211x8664 httpd-mmn = 20120211-x86-64 httpd-mmn = 20120211 Available: httpd-2.4.6-40.el7.centos.1.x86_64 (updates) httpd-mmn = 20120211x8664 httpd-mmn = 20120211-x86-64 httpd-mmn = 20120211 Error: Package: php-pecl-jsonc-1.3.10-1.el7.remi.5.4.x86_64 (remi) Requires: php(api) = 20100412-64 Removing: php-common-5.4.45-11.el7.remi.x86_64 (@remi) php(api) = 20100412-64 Updated By: php-common-5.5.38-1.el6.remi.x86_64 (remi-php55) php(api) = 20121113-64 Available: php-common-5.4.16-36.el7_1.x86_64 (base) php(api) = 20100412-64 Available: php-common-5.4.16-36.1.el7_2.1.x86_64 (updates) php(api) = 20100412-64 Available: php-common-5.4.16-36.3.el7_2.x86_64 (updates) php(api) = 20100412-64 Available: php-common-5.4.45-10.el7.remi.x86_64 (remi) php(api) = 20100412-64 Available: php-common-5.5.37-1.el6.remi.x86_64 (remi-php55) php(api) = 20121113-64 Error: Package: php-pecl-jsonc-1.3.10-1.el7.remi.5.4.x86_64 (remi) Requires: php(zend-abi) = 20100525-64 Removing: php-common-5.4.45-11.el7.remi.x86_64 (@remi) php(zend-abi) = 20100525-64 Updated By: php-common-5.5.38-1.el6.remi.x86_64 (remi-php55) php(zend-abi) = 20121212-64 Available: php-common-5.4.16-36.el7_1.x86_64 (base) php(zend-abi) = 20100525-64 Available: php-common-5.4.16-36.1.el7_2.1.x86_64 (updates) php(zend-abi) = 20100525-64 Available: php-common-5.4.16-36.3.el7_2.x86_64 (updates) php(zend-abi) = 20100525-64 Available: php-common-5.4.45-10.el7.remi.x86_64 (remi) php(zend-abi) = 20100525-64 Available: php-common-5.5.37-1.el6.remi.x86_64 (remi-php55) php(zend-abi) = 20121212-64 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest If I try --skip-broken, I get: Packages skipped because of dependency problems: gd-last-2.2.3-1.el7.remi.x86_64 from remi libpng12-1.2.50-7.el7_2.x86_64 from updates libzip-last-1.1.3-1.el7.remi.x86_64 from remi php-5.5.38-1.el6.remi.x86_64 from remi-php55 php-cli-5.5.38-1.el6.remi.x86_64 from remi-php55 php-common-5.5.38-1.el6.remi.x86_64 from remi-php55 php-gd-5.5.38-1.el6.remi.x86_64 from remi-php55 php-mbstring-5.5.38-1.el6.remi.x86_64 from remi-php55 php-mcrypt-5.5.38-1.el6.remi.x86_64 from remi-php55 php-mysqlnd-5.5.38-1.el6.remi.x86_64 from remi-php55 php-pdo-5.5.38-1.el6.remi.x86_64 from remi-php55 php-pecl-jsonc-1.3.10-1.el7.remi.5.4.x86_64 from remi php-pecl-zip-1.13.4-1.el6.remi.5.5.x86_64 from remi-php55 php-process-5.5.38-1.el6.remi.x86_64 from remi-php55 php-xml-5.5.38-1.el6.remi.x86_64 from remi-php55 Error: Multilib version problems found. This often means that the root cause is something else and multilib version checking is just pointing out that there is a problem. Eg.: 1. You have an upgrade for php-common which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of php-common of the different architecture. If you exclude the bad architecture yum will tell you what the root cause is (which package requires what). You can try redoing the upgrade with --exclude php-common.otherarch ... this should give you an error message showing the root cause of the problem. 2. You have multiple architectures of php-common installed, but yum can only see an upgrade for one of those architectures. If you don't want/need both architectures anymore then you can remove the one with the missing update and everything will work. 3. You have duplicate versions of php-common installed already. You can use "yum check" to get yum show these errors. ...you can also use --setopt=protected_multilib=false to remove this checking, however this is almost never the correct thing to do as something else is very likely to go wrong (often causing much more problems). Protected multilib versions: php-common-5.5.37-1.el6.remi.x86_64 != php-common-5.4.45-11.el7.remi.x86_64

3 5

Stopping NetworkManager doesn't shut down network interfaces
by Joe Smithian 25 Aug '16

25 Aug '16

Hi All, When I stop NetworkManager using the "systemctl stop NetworkManager", it doesn't bring network interfaces down. This behaviour is different than network service in CentOS 5/6. Is this the expected behaviour or a bug or configurable? I expected all networking to be shut down down after stopping NetworkManager. Please comment.

1 1

Re: [CentOS] Gnome weather applet stranded
by adrian＠pa0rda.nl 25 Aug '16

25 Aug '16

Hi, NOAA moved the url on which you can get the data. I use clweather, a little command-line util, I just change the URL in the sourcecode and it worked again. The move happen a couple of weeks ago. The new URL to point the application to is: http://tgftp.nws.noaa.gov/data/observations/metar/decoded/ Good luck & 73, Adrian -- Adri P. van Bloois Antonlaan 104 email: adrian(a)pa0rda.nl 3701 VG Zeist voice: +31-(0)-30-6912741 The Netherlands fax: NONE 52 05'15.77"N 5 4'44.56"E QTH-locater JO 22 OC "Elegance is not a dispensable luxury but a factor that decides between success and failure." Edsger W. Dijkstra

1 0

CentOS 6 : TigerVNC auto disconnect in version 1.1.0-18
by K Shen 25 Aug '16

25 Aug '16

Hi, When TigerVNC was updated from version 1.1.0-16.el6 to 1.1.0-18.el6, our VNC client kept getting killed after connecting for about 180s. We had to downgrade back to -16 to avoid this issue. We have a setup which allows users to log into our system via a web browser, with TigerVNC as the VNC server, noVNC as the client, and connecting via Websockify. With the update of TigerVNC, the VNC client kept getting killed 180s after logging in -- the user is returned to the login page. We are using CentOS 6.8. We can't figure out what the problem might be -- the update seem to be mostly changes related to x11-server - could this be somehow related? The timing of the logout seems quite precise, as if it is triggered by some timer. Does anyone have any idea what the problem might be? Is this the best place to ask about this? The changes between -16 and -18 seem specific to CentOS (I can't find them on the source at TigerVNC's website), so I assume that is not the place to ask about this issue. Kish Shen

1 0

Transparent HugePages question
by Laurentiu Soica 25 Aug '16

25 Aug '16

Hello, I have a CentOS 7 installation on baremetal with 2 CPUs, 10 cores each and HT enabled, 128 GB RAM. The system has transparent hugetables enabled. cat /sys/kernel/mm/transparent_hugepage/enabled [always] madvise never The system reports anonymous hugepages pages usage and a size of hugepage of 2048Kb cat /proc/meminfo |grep -i hugepages|grep AnonHugePages AnonHugePages: 35491840 kB cat /proc/meminfo |grep -i hugepages|grep Hugepagesize Hugepagesize: 2048 kB Anyway, checking the /proc/<pid>/smaps for each and every process on the system, the KernelPageSize reports 4K pages only. for i in `ls /proc/|egrep '[0-9]+'` ; do grep 'KernelPageSize: ' /proc/$i/smaps; done|grep ' 4 kB'|wc -l 9758 for i in `ls /proc/|egrep '[0-9]+'` ; do grep 'KernelPageSize: ' /proc/$i/smaps; done|grep -v ' 4 kB'|wc -l 0 So it turns out that even is I have the THP enabled the pages still have a size of 4K . Is there any extra setup in order to get 2MB pages ? Thanks, Laurentiu -- Laurentiu Soica

3 4

Broadcom BCM4313 support broken with kernel 2.6.32-573.7.1.el6.centos.plus.x86_64?
by wwp 25 Aug '16

25 Aug '16

Hello, I noticed that with latest kernel (2.6.32-573.7.1.el6.centos.plus.x86_64), my laptop's Wifi doesn't work, whereas with previous kernel (2.6.32-504.30.3.el6.centos.plus.x86_64), it works fine. Is this a known issue or did I miss something new? BTW, `lspci` says: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01) Regards, -- wwp

2 2

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