similar to: Lockd: failed to reclaim lock for pid ...

-> Is there a way to get a date stamp for the dmesg? At least on CentOS7: dmesg -T ----- Original Message ----- From: "Dan Hyatt" <dhyatt at dsgmail.wustl.edu> To: "CentOS mailing list" <centos at centos.org> Sent: Tuesday, October 18, 2016 1:36:46 PM Subject: [CentOS] Lockd: failed to reclaim lock for pid ... My environment is "heterogeneous" my

Hello! I'm trying to install Centos 6.4 64 bit on this Xserve: http://www.everymac.com/systems/apple/xserve/specs/xserve-intel-xeon-2.8-eight-core-specs.html I got a bootloader from: http://blog.christophersmart.com/2009/07/23/linux-on-an-apple-xserve-efi-only-machine/ as none of the official Centos releases (full, minimal, network 64 bit) boot on this machine. They all crash when loading

Well, we're figure the board's got problems, but I installed OpenIPMI a couple weeks ago, and fired it up as a service, then added a cron job. That all ran well until last evening; we came in to find 5 zillion emails complaining Unable to open SDR for reading I worked my way through logs, and googling, and then trying to run ipmitool by hand, and it complains there's no such device as

Good morning! On a CentOS 6.4 / 64 bit server I have installed the watchdog 5.5 package. The rpm -qi watchdog states: The watchdog program can be used as a powerful software watchdog daemon or may be alternately used with a hardware watchdog device such as the IPMI hardware watchdog driver interface to a resident Baseboard Management Controller (BMC). ... This configuration file is also used to

here is my problem: Parsing config file vir2.cfg Daemon running with PID 11570 Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 3.0.0 (root@localhost.localdomain) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) ) #1 SMP Mon Oct 28 00:35:01 CST 2013 Command line: root=/dev/hda1 ro ACPI in unprivileged domain disabled released 0 pages

Hi, guys. I've read the information in the Wiki about making dovecot's UID's match Courier's UID's in the POP3 server, so that a UIDL command on either server will return the same UID's for the same group of messages. However, what I've read doesn't match what I'm seeing in Courier. Courier appears to keep the UID numbers for messages that it uses for the POP3

Hi all, I am trying to load kernel module ipmi_si, while failed with error "No such device", truth is I can find file in ../kernel/drivers/char/ipmi/ipmi_si.ko. So why I can't load it? Steps: # ls -l /lib/modules/2.6.32-573.el6.x86_64/kernel/drivers/char/ipmi/ipmi_si.ko -rwxr--r--. 1 root root 93080 Jul 23 2015

Hi all, New to the list and (mostly) new to CentOS. We have just moved from running RHEL to CentOS on our main production servers. Anyway, I am configuring a couple of new SunFire v20z servers here at the moment and trying to get the systems' management interfaces to work fully under CentOS. First issue was trying to install the openipmi RPM from the CD that came with the SunFires, this RPM

Control: tag -1 +moreinfo On Tue, 2014-05-13 at 08:55 -0700, Mike Egglestone wrote: > After booting into kernel 3.13 dom0, the keyboard no longer works. > All other aspects work, ssh is needed to login to the system to > start working with the domU's. > They keyboard works at the grub menu just fine, and > works normal when booting into the non xen kernel. I think at a minimum

Ian Campbell <ijc at hellion.org.uk> writes: #I think at a minimum to make any progress we would need to see some #logs. Probably the dom0 dmesg (perhaps compared to the native boot #dmesg) and the set of modules which are loaded would be a good start. #Probably xen's dmesg would be useful too. Lastly, it would be good to #mention what sort of keyboard this is (USB, PS2?) # #Also the

On Mon, Jan 22, 2018 at 10:38 PM, Nathan March <nathan at gt.net> wrote: > Just a heads up that I'm seeing major stability problems on these builds. > Didn't have console capture setup unfortunately, but have seen my test > hypervisor hard lock twice over the weekend. > > This is with xpti being used, rather than the shim. Thanks for the heads-up. It's been

Running the nightly from two days ago. The Dovecot log shows no errors, but I keep getting login errors for a few users. top shows: 71486 user1 1 96 0 4552K 2408K lockd 0 0:00 0.00% imap 11170 user2 1 96 0 4440K 2480K lockd 0 0:00 0.00% imap And a ps aux shows that these processes have been open for hours. If I move the mbox that contains their mail, the same

Hi folks, We experiencing some difficulties in getting IPMI to work on RHEL 6 running as Guest using KVM. We have verified that IPMI works on RHEL 6 if installed on bare metal. Is this a known issue? Can anyone please suggest a fix or work-around for this problem? *RHEL 6 as guest os with kvm on RHEL 6 as host os -- doesn't work* RHEL 6 (client) on bare metal (i.e., the above mentioned host

On Sun, Jun 04, 2017 at 08:57:44AM -0400, Michael Butler wrote: > It seems that {rpc.}lockd no longer runs after the ino64 changes on any > of my systems after a full rebuild of src and ports. No log entries > offer any insight as to why :-( > > imb I don't tend to use NFS on my systems that are running head, so I haven't had occasion to test this as stated. However, I

On Tue, Feb 17, 2009 at 11:33, Alan Bartlett <ajb.stxsl at googlemail.com> wrote: > The subject line for this "conversation / thread" reads: > "Re: [CentOS-docs] [CentOS] Is the NFS lockd bug fixed ?" > The contents, however, relates to XFS & the CentOSPlus kernel. > Filipe, please take care with what you do. :-) Very sorry about that. Fixed it now. In

I thnk I posted this last week, but to refresh your minds (for Americans, after all the turkey): two C7 boxes, updated. box 1 is exporting directories; box 2 is not running nfs. From box 1, every minute, I get <...> kernel: lockd: server fred.local not responding, timed out Now, on box 2, fred is eth0:fred, and is one of five secondaries on eth0. When I do an ip a, it shows as the last

Since moving from 4.4 to 4.6, I've been seeing an increasing number of stability issues on our hypervisors. I'm not clear if there's a singular root cause here, or if I'm dealing with multiple bugs. One of the more common ones I've seen, is a VM on shutdown will remain in the null state and a kernel bug is thrown: xen001 log # xl list Name

Ian Campbell <ijc at hellion.org.uk> writes: #Please boot with loglvl=all on the hypervisor command line for this too. No problem Ian, Here are some results with (now) the latest BIOS version 41. (was version 35) This is a fresh new install of Debian "Testing" non production server. Just wanted to run some test domU's. Changing USB ports, no effect. I even tried a different

I had a supermicro server SuperServer 1027R-WRF4+ and a old Dell PowerEdge 2950. In both machines I setup centos 6.5, which is running 3.10.34-11.el6.centos.alt.x86_64. I follow Xen4Cen wiki to setup Xen, I had other servers running Centos 5.x without issues. Now, once I build my vm's dom-u centos 6.5/centos 5.9 both x64, I receive different erros, let me show u the message I receive in my

I'm getting the (unintelligible to me) error message ipmi_si: Could not set up I/O space ERST: Failed to get Error Log Address Range when I try to boot any OS on the grub menu apart from the one I last installed. (Actually, Windows also boots properly.) I wonder if anyone has had this error message, and worked out where it comes from? I googled for it, and it has come up many times; but