[CentOS] systemd-udevd not applying ATTR to block device at boot

Hi everyone, I have a udev rule file that contains a singular rule: SUBSYSTEM=="block", ACTION=="add|change", ENV{ID_VENDOR}=="*Google*", ENV{DEVTYPE}=="disk", ATTR{queue/scheduler}:="noop" When I use a Google Cloud instance and boot it, things work as expected and /dev/sda (a persistent

Re: [CentOS-virt] kernel-ml-4.15.0-1.el7.elrepo.x86_64 doesn't boot as Xen PV domU

Replicated on another Xen node, CentOS 6.9 running Xen-4.6.6-8.el6. xl dmesg: (XEN) d38v0: unhandled page fault (ec=) (XEN) Pagetable walk from 0028: (XEN) L4[0x000] = (XEN) domain_crash_sync called from entry.S: fault at 82d080230983

Re: [CentOS] Xen hypervisor on CentOS 7.4 with modern UEFI server not booting from grub

Why do you need UEFI? It does not add to security "a lot" but was designed to block booting software like a "hypervisor". I used my Dell notebooks to test our hypervisor identification software (HyperCatcher if you are interested) which is bootable image. However, I was unable to boot it until

[CentOS-virt] kernel-ml-4.15.0-1.el7.elrepo.x86_64 doesn't boot as Xen PV domU

Hi, has anyone managed to boot 4.15.0 as Xen PV domU? I've been loading 4.14.12 to 4.14.15 ELRepo builds no problem, but 4.15 crashes. Replicates on 2 CentOS 7.4 hypervisors running xen-4.6.6-9.el7.x86_64 on: - Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz - AMD Phenom(tm) II X6 1090T Processor xl

[CentOS] Redhat acquires CoreOS

This should make CentOS even better!: https://www.geekwire.com/2018/red-hat-snaps-coreos-250m-adding-big-piece-container-strategy/ - Ryan https://prefetch.net ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] logging in

On 01/30/18 16:21, m.r...@5-cent.us wrote: Interesting. lastlog was always my go-to. However, at least in C6, last gets it, while lastlog does not. How odd. Did you check /var/log/secure ? last command not mentioning logged i9n users will raise very big red flag for me. I also would

[CentOS] Xen hypervisor on CentOS 7.4 with modern UEFI server not booting from grub

Hi, I installed CentOS 7.4 on a modern Lenovo ThinkSystem SR630 server which uses UEFI. So far so good CentOS 7.4 works fine so then I went on to install the Xen hypervisor by following the instructions from the wiki (https://wiki.centos.org/HowTos/Xen/Xen4QuickStart). Unfortunately when I

Re: [CentOS] logging in

Interesting. lastlog was always my go-to. However, at least in C6, last gets it, while lastlog does not. How odd. mark ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Intel Skylake

Hello, There was a support issue with the Intel Skylake and CentOS 6.* where the graphics hardware was not supported. Intel have now come up with a software solution to support the AST2500 graphics hardware on the Skylake. Regards, Mark Woolfson MW Consultancy Ltd Leeds LS18 4LY United

Re: [CentOS] logging in

Marcelo Roccasalva wrote: > On Tue, Jan 30, 2018 at 3:26 PM, wrote: >> >> This is odd. >> >> We're seeing a *lot* of >> sshd[8400]: Timeout, client not responding. > > Is it possible you are testing ssh availability from nagios, monit, or > some other software that connects

Re: [CentOS] logging in

On Tue, Jan 30, 2018 at 3:26 PM, wrote: > > This is odd. > > We're seeing a *lot* of > sshd[8400]: Timeout, client not responding. Is it possible you are testing ssh availability from nagios, monit, or some other software that connects to the port 22 without logging in? --

Re: [CentOS] logging in

On 30 January 2018 at 13:40, Jon Pruente wrote: > On Tue, Jan 30, 2018 at 12:26 PM, wrote: > > > This is odd. > > > > We're seeing a *lot* of > > sshd[8400]: Timeout, client not responding. > > So I'm trying to find out whose client is having

Re: [CentOS] logging in

On Tue, Jan 30, 2018 at 12:26 PM, wrote: > This is odd. > > We're seeing a *lot* of > sshd[8400]: Timeout, client not responding. > So I'm trying to find out whose client is having issues. Trying to figure > that, after processes are gone, I tried looking in lastlog, which

[CentOS] logging in

This is odd. We're seeing a *lot* of sshd[8400]: Timeout, client not responding. So I'm trying to find out whose client is having issues. Trying to figure that, after processes are gone, I tried looking in lastlog, which is where it gets odd. lastlog shows root coming in, and it shows a

Re: [CentOS] New messages in journalctl

On Mon, Jan 29, 2018 at 10:04:39PM +0100, Martin Wagner wrote: > > The following messages have started to appear in the system log after > the most recent update of my Centos7 machine > > gnome-software-service.desktop[3389]: 20:54:22:0879 Gs no app for changed >

Re: [CentOS] Restarting docker daemon fixes network problem inside containers

On 30/01/2018 09:54, Andrew Holway wrote: > Does anyone have a clue what the root cause of this might be? I've had trouble before when settings in /etc/sysctl.d were disabling ip_forwarding, which will break Docker's networking in some configurations. You may also want to check firewall rules if

[CentOS] Restarting docker daemon fixes network problem inside containers

Hi, We are building docker containers on Centos 7 based machines. Sometimes the docker being built cannot install packages because of some kind of network failure. I just found that restarting the docker container fixes the problems and the builds are successful. Does anyone have a clue what the