similar to: systemd not restarting daemon

> On Aug 25, 2016, at 1:43 PM, Chris Adams <linux at cmadams.net> wrote: > > named-sdb (pulling domain > records from MySQL), which is segfaulting randomly named-sdb used to be(~7+ years ago) single threaded only and would crash if threads were enabled. Did you change named to NOT thread? Does named-sdb still do single threaded only?

I've looked high and low and I cannot a package that has the mariadb driver to go with bind-sdb-9.9.4-14.el7_0.1.x86_64. Everything I'm finding is how to build from source, which for this project will not be maintainable. Is there a yum repo with this driver anywhere? Thanks much, Jim

This seems to be just a stub with 3 READMEs? # locate bind-sdb /usr/share/doc/bind-sdb-9.9.4 /usr/share/doc/bind-sdb-9.9.4/INSTALL.ldap /usr/share/doc/bind-sdb-9.9.4/README.ldap /usr/share/doc/bind-sdb-9.9.4/README.sdb_pgsql Unless it is putting files elsewhere. These readmes are dated long ago. What is really needed and where is any good documentation for using this? thanks

I'm looking into 'porting' some custom init.d scripts that are in use on CentOS 6 boxes for use on CentOS 7 using systemd One particular init.d script needs to run after autofs has been started, but before X11 is started I'm guessing I could use something like: After=autofs.service Before=graphical.target Is this correct? However, I would like to use the same systemd

Hi all, With SystemD, how can I make certain service dependent on certain network interfaces being up? For example, I have an 802.1ad bond interface I need to wait on for being up (this interface has no ip address assigned, it is used to capture networks packets with a tcpdump?s script). Every time this service fails because bond interface is not up. I have configured the service as:

from both DC: dig google.com dig @8.8.8.8 google.com First dig will use resolvers declared into /etc/resolv.conf. Second dig forces usage of 8.8.8.8. Both commands should reply the same things, on all DC. 2016-06-30 15:58 GMT+02:00 lingpanda101 at gmail.com <lingpanda101 at gmail.com>: > On 6/30/2016 9:57 AM, Garland McAlexander wrote: > >> nslookup google.com

My ThinkStation runs CentOS 7 which I installed on a BIOS RAID 0 setup with two identical 256 Gb SSDs after removing Windows. It runs fine but I just discovered in gparted something that does not seem right: - Launching gparted it complains "invalid argument during seek for red on /dev/md126" and when I click on Ignore I get another error "The backup GPT table is corrupt, but the

On 9/23/20 7:07 AM, Stephen John Smoogen wrote: > On Wed, 23 Sep 2020 at 04:33, Carlos Lopez <clopmz at outlook.com> wrote: > >> Hi all, >> >> >> With SystemD, how can I make certain service dependent on certain network >> interfaces being up? >> >> For example, I have an 802.1ad bond interface I need to wait on for being >> up (this

Once upon a time, Chris Murphy <lists at colorremedies.com> said: > On Tue, Apr 26, 2016, 2:09 PM Chris Adams <linux at cmadams.net> wrote: > > I have several recently-installed CentOS 7 servers that keep having > > systemd-journald corruption > > Determined with 'journalctl --verify' or another way? I get messages like this in dmesg: [4756650.489117]

Once upon a time, Chris Murphy <lists at colorremedies.com> said: > Also I wonder if merely restarting the journal daemon solves it: > > systemctl restart systemd-journald > > What should happen is it realizes its own logs are corrupt and ignores > them, and starts working on new copies. And journalctl should still > try to read the old ones but skips the corrupt

Once upon a time, Chris Murphy <lists at colorremedies.com> said: > On Tue, Apr 26, 2016 at 3:01 PM, Chris Adams <linux at cmadams.net> wrote: > > Once upon a time, Chris Murphy <lists at colorremedies.com> said: > >> On Tue, Apr 26, 2016, 2:09 PM Chris Adams <linux at cmadams.net> wrote: > >> > I have several recently-installed CentOS 7

On Wed, Mar 01, 2017 at 07:28:46PM +0100, Viktor Mihajlovski wrote: > On 01.03.2017 16:58, Daniel P. Berrange wrote: > > given a basic Fedora 25 guest, with a virtio-mmio disk added as per the > > guide above... > > > > looking at device '/devices/platform/a003e00.virtio_mmio/virtio3/block/vda': > > KERNEL=="vda" > >

On Wed, Mar 01, 2017 at 07:28:46PM +0100, Viktor Mihajlovski wrote: > On 01.03.2017 16:58, Daniel P. Berrange wrote: > > given a basic Fedora 25 guest, with a virtio-mmio disk added as per the > > guide above... > > > > looking at device '/devices/platform/a003e00.virtio_mmio/virtio3/block/vda': > > KERNEL=="vda" > >

> My ThinkStation runs CentOS 7 which I installed on a BIOS RAID 0 setup > with two identical 256 Gb SSDs after removing Windows. It runs fine but I > just discovered in gparted something that does not seem right: > > - Launching gparted it complains "invalid argument during seek for red on > /dev/md126" and when I click on Ignore I get another error "The backup

I have several recently-installed CentOS 7 servers that keep having systemd-journald corruption (which stops ALL logging, including syslog). Interestingly, they are all spam-scanning servers running amavisd-new (so could be some particular pattern is triggering it). Is there a "supported" way to just cut systemd-journald out of the picture and have log entries go straight to rsyslogd?

Hi, I noticed that some, but not all, of my CentOS 7 machines have these kernel parameters for turning on systemd debug level logging added to the grub.cfg file. systemd.log_level=debug systemd.log_target=kmsg The parameters are *not* in the /etc/default/grub file, so if I rebuild grub.cfg with grub2-mkconfig, they disappear. I am a bit puzzled over how they got introduced. Has anyone else

Last time I saw it, I had just upgraded my CentOS 7 box with the 3.10.0-514 kernel and it rebooted already configured into debug mode. Not sure if this is a ?feature? of the newer kernels or not but glad to see that i?m not the only one who had noticed this. # awk -F\' '$1=="menuentry " {print i++ " : " $2}' /etc/grub2.cfg 0 : CentOS Linux

I recently installed mariadb-server 10.1 by adding the following repository: baseurl = http://yum.mariadb.org/10.1/centos7-amd64 ...all was well until we had a power failure and upon rebooting unixodbc was segfaulting. Once I did a yum undo, the mysql odbc driver was functional. I traced it to the following: [root at ec-ast yum.repos.d]# ldd /usr/lib64/libmyodbc5w.so | grep -iE

I just updated a server that's running CentOS 7. I do have elrepo enabled, because this Rave computer has four early Tesla cards. It won't boot. Nor can I get it to boot with either of the other two kernels, and I'll be the one that worked was erased. *Once* it complained that it couldn't fsck the large filesystem (IIRC, it's XFS). The other four-five times, I get pNFS

Thanks for each of your inputs. It was not a configuration issue as odbcinst.ini does not reference the mysql subdirectory. Rather than use Alexander's url, I ran: yum -y install centos-release-openstack-ocata yum -y install mariadb-server ...the cloud repository provides the properly pathed file. # repoquery -l mariadb-server mariadb-libs | grep lib64 | grep libmysqlclient