similar to: C7, nfs issue on restart

On Thu, 18 Feb 2016, m.roth at 5-cent.us wrote: > This is happening on anything other than plain vanilla Dell servers. One > R730, with dual Tesla cards, one R420, with a fibre card for a RAID > device, it never switches root. All these systems have Xeons, not AMD > CPUs. > > We've had this with every one of the 327 kernels. In addition, it seems to > happen also with the

This is happening on anything other than plain vanilla Dell servers. One R730, with dual Tesla cards, one R420, with a fibre card for a RAID device, it never switches root. All these systems have Xeons, not AMD CPUs. We've had this with every one of the 327 kernels. In addition, it seems to happen also with the 229.20.1; the 229.14.1 has no such problem. >From the rdsosreport: starting

Paul Heinlein wrote: > On Thu, 18 Feb 2016, m.roth at 5-cent.us wrote: > >> This is happening on anything other than plain vanilla Dell servers. One >> R730, with dual Tesla cards, one R420, with a fibre card for a RAID >> device, it never switches root. All these systems have Xeons, not AMD >> CPUs. >> >> We've had this with every one of the 327

Ok, folks, I don't get this one at all. I've got a server that I just rebuilt last week, from C5 to C7. It used to export filesystems. Those were moved to another server, and NFS wasn't turned up when I built it. I just turned it down again. And yet, I see Mar 14 10:26:33 <servername> systemd: Job dev-disk-by\x2dlabel-export1.device/start timed out. Mar 14 10:26:33

I am trying to get a remote screen on C7. I did the following on C7 server: yum install tigervnc-server cp /lib/systemd/system/vncserver at .service /etc/systemd/system/vncserver@:1.service systemctl daemon-reload edit /etc/systemd/system/vncserver@:1.service and replace <USER> with myuser su - myuser run

On Thu, Jun 2, 2016 at 7:56 AM, Jerry Geis <geisj at pagestation.com> wrote: > I am trying to get a remote screen on C7. > I did the following on C7 server: > yum install tigervnc-server > cp /lib/systemd/system/vncserver at .service > /etc/systemd/system/vncserver@:1.service > systemctl daemon-reload > edit

On Tue, 14 Mar 2017, m.roth at 5-cent.us wrote: > Ok, folks, I don't get this one at all. > > I've got a server that I just rebuilt last week, from C5 to C7. It used to > export filesystems. Those were moved to another server, and NFS wasn't > turned up when I built it. I just turned it down again. And yet, I see > Mar 14 10:26:33 <servername> systemd: Job >

------------ Original Message ------------ > Date: Sunday, May 10, 2015 01:20:34 PM -0700 > From: John R Pierce <pierce at hogranch.com> > > On 5/10/2015 1:04 PM, Earl A Ramirez wrote: >> Did a little Googling [0] and I saw that they recommend starting >> it as follows: >> >> /etc/init.d/mysql start > > which is old school sysVinit style. >

That is the thing - rpc.statd does have rpcbind a pre-req. It looks like systemd is not handling this correctly. Just wondering if anyone knows a good way to fix. root at ls2 /usr/lib/systemd/system 110# grep Requires rpc-statd.service Requires=nss-lookup.target rpcbind.target On 8/30/15 7:45 PM, Rob Kampen wrote: > On 08/31/2015 01:39 PM, Mark Selby wrote: >> I have seen some talk

On 08/31/2015 01:39 PM, Mark Selby wrote: > I have seen some talk about this but have not seen any answers. I know > this is a problem on CentOS 7.1 and I also think it is a problem on > CentOS 7.0. > > Basically if I have an NFS client only config - meaning that the > nfs-server.service is not enabled then I have to wait 60 seconds after > boot for the 1st NFSV3 mount to

On 11/23/2014 12:02 PM, Edward M wrote: > > On 11/23/2014 10:58 AM, Gregory P. Ennis wrote: >> Everyone, >> >> I have installed Centos 7.0 on my homework machine in order to take a >> test drive with it, and am low on the learning curve with it at this >> point. I have a small Gateway SX2855-UB12P. >> >> I have a critical hurdle in that when I try

Thats wierd. I've never had any problem with systemctl or systemd like that. Do you have your service file in the right place with the right permissions. here is the httpd service file as a reference. [centos at ipa ~]$ ls /usr/lib/systemd/system/httpd.service -l -rw-r--r--. 1 root root 694 Mar 12 14:57 /usr/lib/systemd/system/httpd.service [centos at ipa ~]$ cat

Devuan.. a thing im going to have a look into. I do get why debian is swithching to systemd.. really much better control of the startup process, but yeah, lots harder to configure... Besides that... This is a samba using internal DNS? Can you also post the output of systemctl list-dependencies samba-ad-dc or systemctl list-dependencies and post systemctl show samba-ad-dc.service |

I have seen some talk about this but have not seen any answers. I know this is a problem on CentOS 7.1 and I also think it is a problem on CentOS 7.0. Basically if I have an NFS client only config - meaning that the nfs-server.service is not enabled then I have to wait 60 seconds after boot for the 1st NFSV3 mount to succeed. What I can surmise is the following. I attempt to perform a NFS

On Sun, Sep 30, 2018 at 08:56:52PM +0200, Alessandro Baggi wrote: > Hi James, > I tried as suggested installing cuda but the problem persist. > In a previous c7.5 installation all works as expected but the driver was > less then 390.77. I'm puzzled... I'm running up to date C7 with Nvidia card and the elrepo nvidia bits at 390.87 without problems. Have you tried using the

----- Original Message ----- From: "hvjunk" <hvjunk at gmail.com> To: "Adam Ru" <ad.ruckel at gmail.com> Cc: gluster-users at gluster.org Sent: Monday, June 5, 2017 9:29:03 PM Subject: Re: [Gluster-users] Gluster and NFS-Ganesha - cluster is down after reboot Sorry, got sidetracked with invoicing etc.

Sorry, got sidetracked with invoicing etc. https://bitbucket.org/dismyne/gluster-ansibles/src/6df23803df43/ansible/files/?at=master <https://bitbucket.org/dismyne/gluster-ansibles/src/6df23803df43/ansible/files/?at=master> The .service files are the stuff going into SystemD, and they call the test-mounts.sh scripts. The playbook installing higher up in the directory > On 05 Jun 2017,

On 19.01.24 09:00, Jim Klimov via Nut-upsuser wrote: >Well, from your logs it seems that at 05:17:03 your nut-server (upsd) >restarted, so an upsmon reconnection attempt at 05:17:09 had an issue with >that (config not all applied? strange a bit) but since 05:17:14 it is okay. > >Maybe a few too many banners shown from upsmon, while its same uptime seems >to continue. Maybe

Jan 19 05:50:13 mars nut-monitor[849]: Signal 15: exiting Jan 19 05:50:13 mars nut-monitor[849]: Network UPS Tools upsmon 2.8.0 Jan 19 05:50:13 mars systemd[1]: Stopping nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller... Jan 19 05:50:13 mars systemd[1]: nut-monitor.service: Deactivated successfully. Jan 19 05:50:13 mars systemd[1]: Stopped nut-monitor.service

On 15/12/15 18:31, gimili wrote: > On 12/15/2015 12:13 PM, L.P.H. van Belle wrote: >> Hai, >> >> If not, well, very stange, i have about 7 Jessie's here with samba and >> i dont have any problems. >> I think systemd is blocking your startup of samba due to multple >> errors on startups previously. >> >> Few questions? >> >> Do you