similar to: C7.4 and sshd restart problem

Hi list, I solved the problem. Anyone had answered but I report the solution for similar problem. The problem was caused by an sshd.service under /etc/systemd/system/. This file was placed because upgrading from 7.2 to 7.3 I got problem with ssh startup and someone suggested to add pidfile directive in sshd.service to solve the problem. Updating from 7.3 to 7.4 I think that 2 files for sshd

On 27/09/17 07:56, Sorin Srbu wrote: >> -----Original Message----- >> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Phil Perry >> Sent: den 26 september 2017 21:46 >> To: centos at centos.org >> Subject: Re: [CentOS] Semi-OT: hardware: NVidia proprietary driver, C7.4 >> >> On 26/09/17 18:40, m.roth at 5-cent.us wrote: >>> This is

> -----Original Message----- > From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Phil Perry > Sent: den 26 september 2017 21:46 > To: centos at centos.org > Subject: Re: [CentOS] Semi-OT: hardware: NVidia proprietary driver, C7.4 > > On 26/09/17 18:40, m.roth at 5-cent.us wrote: > > This is really frustrating. I've got a server with two K20c Tesla

Kernel parameters aside (console=ttyUSB0 console=tty0), I am trying to get a login console working on a USB-to-serial adapter. systemctl enable serial-getty at ttyUSB0.service systemctl start serial-getty at ttyUSB0.service This works without issue on Debian 8. However when running the same on CentOS 7, my logs are filled with: May 16 12:44:58 localhost.localdomain systemd[1]: Starting Serial

Hello listmates, Somehow or other my DNS services that are part of the ndjbdns-1.06-1.el7.x86_64 package would not start properly at startup. When I then start them up using systemctl: systemctl start dnscache systemctl start tinydns they start just fine. >From the log I got the following for tinydns: Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: version 1.06: starting: Oct-24 2014 15:01:43

Le 26/09/2017 ? 19:59, Scott Robbins a ?crit?: > Why not use the elrepo repo? They've worked flawlessly for me, both with > legacy and new cards. I know this is weird, but I've had cases where the downloaded NVidia driver worked and the ELRepo driver didn't, and the other way around. Details here: https://blog.microlinux.fr/nvidia-centos/ Niki -- Microlinux - Solutions

On Tue, Sep 26, 2017 at 01:40:54PM -0400, m.roth at 5-cent.us wrote: > This is really frustrating. I've got a server with two K20c Tesla cards. I > need to use the proprietary drivers to use the CUDA toolkit. Btw, I had no > trouble at all with building for CentOS 7.3 > > I have what NVidia claims is the correct driver package, a 340 series. It > appears to build, but then

On Tue, Sep 26, 2017 at 1:59 PM, Scott Robbins <scottro11 at gmail.com> wrote: > On Tue, Sep 26, 2017 at 01:40:54PM -0400, m.roth at 5-cent.us wrote: > > This is really frustrating. I've got a server with two K20c Tesla cards. > I > > need to use the proprietary drivers to use the CUDA toolkit. Btw, I had > no > > trouble at all with building for CentOS 7.3

On Tue, 2017-09-26 at 13:40 -0400, m.roth at 5-cent.us wrote: > This is really frustrating. I've got a server with two K20c Tesla cards. I > need to use the proprietary drivers to use the CUDA toolkit. Btw, I had no > trouble at all with building for CentOS 7.3 > > I have what NVidia claims is the correct driver package, a 340 series. It > appears to build, but then fails to

On 26/09/17 18:40, m.roth at 5-cent.us wrote: > This is really frustrating. I've got a server with two K20c Tesla cards. I > need to use the proprietary drivers to use the CUDA toolkit. Btw, I had no > trouble at all with building for CentOS 7.3 > > I have what NVidia claims is the correct driver package, a 340 series. It > appears to build, but then fails to load. The only

On 11/20/2017 05:23 AM, Kretschmer, Jens wrote: > Hi Mark, > > did you manage to sort out messages from Dracut and /sbin/weak-modules you received while installing kmod-nvidia? We get the same messages while installing kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 on RHEL 7.4 with the kernel 3.10.0-693.5.2.el7.x86_64. > weak modules allow modules built on one kernel version to apply to

Thank you! I messaged the ELREPO Mailing List. We are currently investigating the cause of the messages. Br, Jens

Hi all, I have a strange situation. I have a machine connected to an AT&T VPN. Sometimes the VPN gets disconnected, so I create a cronjob to restart the VPN client when it happens: Problem is: sshd seem doesn't want to bind to tun0. I restart ssh, network, no good. Anyone has any clue? So strange. Thank you.

On 27/09/17 16:49, m.roth at 5-cent.us wrote: > Hi, folks, > > Well, still more fun (for values of fun approaching zero): > > 1. Went to install CUDA 9.0... well, gee, there is *no* CUDA 9.0. > Even though I installed the 9 repo, all that I get is 8. I've > used their webform, and an waiting on a reply. > 2. I remove all nvidia packages.

Hi Mark, did you manage to sort out messages from Dracut and /sbin/weak-modules you received while installing kmod-nvidia? We get the same messages while installing kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 on RHEL 7.4 with the kernel 3.10.0-693.5.2.el7.x86_64. Kr, Jens

On Wed, Feb 17, 2016 at 2:48 PM, Adrian Sevcenco <Adrian.Sevcenco at cern.ch> wrote: > Hi! I want to change the sshd port at install for centos7 but i am not sure > if i am on the good track (and it is time expensive to make many > try-outs).. > So, i would be grateful if someone with experience can spot if i have > problems > with my planning.. (the actual purpose is that

Hi list, I have a dedicated server managed through ssh and this morning I have upgraded my system from 7.2 to 7.3. After yum finished his work, and rebooted my server. After reboot I tried to log in with ssh and got "Connection refused". I've noticed that all public services were online. So I've contacted my provider to get access to the server and I've noticed that ssh

This is really frustrating. I've got a server with two K20c Tesla cards. I need to use the proprietary drivers to use the CUDA toolkit. Btw, I had no trouble at all with building for CentOS 7.3 I have what NVidia claims is the correct driver package, a 340 series. It appears to build, but then fails to load. The only error I see is "no such device", which makes no sense to me, esp.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am having a problem getting sshd to run after changing it's default port. I edit sshd_config and set the desired port, open it with firewall-cmd and then issue a systemctl start sshd. No error gets reported on the console but the following is logged in /var/messages sshd.service: main process exited, code=exited, status=255/n/a Not a very

Phil Perry wrote: > On 27/09/17 16:49, m.roth at 5-cent.us wrote: >> Hi, folks, >> >> Well, still more fun (for values of fun approaching zero): >> >> 1. Went to install CUDA 9.0... well, gee, there is *no* CUDA 9.0. >> Even though I installed the 9 repo, all that I get is 8. I've >> used their webform, and an waiting on a