similar to: C 7, lockd issue

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

Hello, booting starts /etc/init.d/nfslock. today, rpc.statd used port 873. later starting xinetd finds port used and disabled rsync daemon. So its more or less a lucky break, to boot CentOS and have rsync running? In /etc/rc3.d is S14nfslock S56xinetd so by design xinetd starts always after nfslock!!!! Best regards -- Viele Gr??e i.V. Helmut Drodofsky ________________________________

I have two RHEL4 email servers running postfix/MailScanner which use dovecot. They work great. But during bootup the nfslock script in my init.d loads rpc.statd and calls portmap to get a port number. Portmap keeps giving rpc.statd the imaps port number (993). I then have to stop my mail server services, manually start dovecot, then restart the mail server services and everything goes merrily on

Hello, I am attempting to get flock/file locking working between my -stable (updated ~19 may) nfs file server and -current desktop; the server is running lockd/statd, and both my mail client (mutt) and a simple perl program complain that files on the nfs server cannot be locked. I am aware that there has been work on the nfs locking code in current, and have a vague recollection of a workaround

Hi all, I have setup a CentOS6.3 x86_64 host to act as a nfs server. According to RHEL6 docs, portmap is not needed when you use NFSv4, but in my host I need to start rpcbind service to make NFSv4 works. My /etc/sysconfig/nfs # # Define which protocol versions mountd # will advertise. The values are "no" or "yes" # with yes being the default MOUNTD_NFS_V2="no"

After getting a reasonably configured NFS4 setup working on my Scientific Linux server, I spent a majority of my evening trying to do the same with my Centos 5 box, with fruitless results. Most attempts to mount that server returns the following message: [root at sl01 log]# mount -t nfs4 192.168.15.200:/opt/company_data /mnt mount.nfs4: Operation not permitted As nearest as I can tell, I was

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

i want to tag categories to its menuname. i have a csv containing menu item name and in other csv i have a column containing some strings, i want to pick that strings from categories and look into menu items if any menu item containing that string i want to create a new column next to menu item name flagged as 1 otherwise 0 and the only condition is once a menu item flagged as 1 i don't need

My environment is "heterogeneous" my authentication and home server are currently stuck on a 1G shared network, the production servers and storage servers are on a bonded 40G network, all are in the same VLAN. I have about 100 servers on the 40GB bonded network each with 12cores and 128GB of memory. They are running centos 6.6 Except for my storage servers they are all just running

So I'm running nfs to get content to my web servers. Now I've had this problem 2 times (about 2 weeks since the last occurrence). I use drbd on the nfs server for redundancy. Now to my problem: All my web sites stopped responding so I started by checking dmesg and there I found a bunch of this errors || Aug 11 16:00:39 web03 kernel: lockd: server 192.168.20.22 not responding, timed out

This was previously posed to the sun-managers mailing list but the only reply I received recommended I post here at well. We have a production Solaris 10u5 / ZFS X4500 file server which is reporting NLM_DENIED_NOLOCKS immediately for any nfs locking request. The lockd does not appear to be busy so is it possible we have hit some sort of limit on the number of files that can be locked? Are there

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

Hi, I am configuring firewall for NFS. I see that statd and mountd start at random port. Is there any way to force it to start at specific port each time. The '-p ' option would work, but how do I configure it to start at specific port number each time. I mean where do statd and mountd look for default configuration options? Any clues? - CS.

I just updated one of our servers to 5.8, and rebooted. In the logs, I saw a bunch of Mar 21 16:29:02 <server> rpc.statd[9783]: recv_rply: can't decode RPC message! Mar 21 16:29:33 <server> last message repeated 442 times Mar 21 16:30:34 <server> last message repeated 835 times Mar 21 16:31:36 <server> last message repeated 884 times Mar 21 16:32:38 <server> last

Greetings, CentOS. After up2dating one of the corporate mail servers to CentOS 4.4 (was CentOS 4.2) and upgrading kernel to kernel-smp-2.6.9-42.0.3.EL, the following kernel messages started to appear in syslog: [root at gamma ~]# dmesg ........... ...CUT..... ........... lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected

-> 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, is dotlock supposed to work with NFS? I noticed that the default-locking method causes problems even with nfslockd started. Regards Marten

Hi Friends, At present, I am using VoIPJET.COM provider for make calls to USA. I have two doubts. 1) I am unable to make call to UK Mobile phone. Why? 2) I want to make calls to "Turkey" country from "India". With VoIPJET, I am unable to make call to "Turkey" and unable to find VoIP provider for Turkey. Please tell me VoIP Provider for Turkey from India.

On Fri, Nov 20, 2020 at 12:18 PM Frank Cox <theatre at sasktel.net> wrote: > > On Fri, 20 Nov 2020 12:07:40 -0500 > Michael B Allen wrote: > > > So TCP src 760 to 41285. What's that? > > Apparently "that" is what you need to allow in order for your desktop to work. > > What it is actually doing, I'm not sure. Google tells me that port 760 has

This removes the appliance configuration bits from the installer and associated files since it has been deprecated --- installer/modules/ovirt/files/cobbler-import | 6 - .../modules/ovirt/files/ovirt-appliance-setup | 4 - installer/modules/ovirt/files/ovirt-storage | 73 ---------- installer/modules/ovirt/manifests/appliance.pp | 152 -------------------- 4 files