[CentOS] Restarting docker daemon fixes network problem inside containers

2018-01-30 Thread Andrew Holway
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

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

2018-01-30 Thread Tom Grace
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

Re: [CentOS] New messages in journalctl

2018-01-30 Thread Jonathan Billings
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 > places-m...@gnome-shell-extensio

[CentOS] logging in

2018-01-30 Thread m . roth
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 securi

Re: [CentOS] logging in

2018-01-30 Thread Jon Pruente
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 is where > it gets

Re: [CentOS] logging in

2018-01-30 Thread Stephen John Smoogen
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 issues. Trying to figure > > that, after processe

Re: [CentOS] logging in

2018-01-30 Thread Marcelo Roccasalva
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? -- Marcelo "¿No será

Re: [CentOS] logging in

2018-01-30 Thread m . roth
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 to the port 22 with

Re: [CentOS] Intel Skylake

2018-01-30 Thread Mark (Netbook)
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 Kingdom

Re: [CentOS] logging in

2018-01-30 Thread m . roth
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

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

2018-01-30 Thread John Naggets
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 reboot

Re: [CentOS] logging in

2018-01-30 Thread Valeri Galtsev
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 check

[CentOS] Redhat acquires CoreOS

2018-01-30 Thread Matty
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] Xen hypervisor on CentOS 7.4 with modern UEFI server not booting from grub

2018-01-30 Thread Mikhail Utin
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 I

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

2018-01-30 Thread Nick . Jacques
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 disk)