similar to: rpc.statd: gethostbyname error for ...

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

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

Hello I'm trying to mount a nfs system. But i receive this message: mount -t nfs <IP>:/backup /backupnfs mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified After a fews searchs on google i tried to execute the files: sbin/rpc.statd

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

Hi, Few days a go one of my rsync server stop respond. When I tried to figure out way, I discover that rpc.statd is listen to port 873. Killing the rpc.statd process bypass the problem. I'm using an update version CentOS 4.* rsync start via xinetd. Do you have any idea how it happen? Regards, Milutin Voinivich NasBackup -------------- next part -------------- A non-text attachment

greetings, is there any reason i would want any of these daemons active in memory on a simple DNS server if i do not use NFS and... of course, the unit is not being used as a workstation. 1712 ? Ss 0:00 rpc.statd 1745 ? Ss 0:00 rpc.idmapd 1813 ? Ss 0:00 /usr/sbin/acpid tia - rh

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 ________________________________

Hi Soumya, what I can say so far: it is working on a standalone system but not on the clustered system from reading the ganesha wiki I have the impression that it is possible to change the log level without restarting ganesha. I was playing with dbus-send but so far was unsuccessful. if you can help me with that, this would be great. here some details about the tested machines. the nfs client

Hello, First and foremost, thanks *very* much for ctdb. It's a joy to use after banging around with other HA solutions. We're planning to use it to export Samba and NFS shares throughout campus. I'm having one problem with the NFS part though. When ctdbd first starts statd (we're using CTDB_MANAGES_NFS=yes), it does so without appending the stuff in the STATD_HOSTNAME variable

Hi I'm trying to access an SD-card using the built-in reader on a Lenovo T61 Laptop running CentOS 5.7. The unit is recognised by lspci: # lspci [ ... ] 15:00.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 21) 15:00.3 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 11) 15:00.4 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host

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 have changed /etc/sysconfig/nfs to specify port numbers for NFS daemons. Somehow statd is still starting up at random port number. Other damons are starting at properly at specified port numbers Any clues on what might be wrong? Any other location/setting that takes precedence over sysconfig/nfs ? It's CentOS 5.5 64bit with nfs-utils 1.0.9-44.el5. -- Thanks, CS

Hello, after upgrade from CentOS 5 to 5.1 I see the following error in /var/log/messages: 'rpc.idmapd[2330]: main: open(/var/lib/nfs/rpc_pipefs/nfs): No such file or directory' The directory exists with the permissions dr-xr-xr-x 2 root root 0 Dec 7 10:21 nfs So is this an owner/permisson problem? Should /var/lib/nfs/rpc_pipefs/nfs be owned by rpcuser? # ls -al /var/lib/nfs/ total

Hi, I have a problem with nfs-ganesha serving gluster volumes I can read and write files but then one of the DBAs tried to dump an Oracle DB onto the NFS share and got the following errors: Export: Release 11.2.0.4.0 - Production on Wed Sep 27 23:27:48 2017 Copyright (c) 1982, 2011, Oracle and/or its affiliates.??All rights reserved. Connected to: Oracle Database 11g Enterprise Edition

> Ok, I've just checked doing the same thing under windows. > > The test(ripdaveno is the name of the Computer I tested on): > > { > ... > hostent* h = gethostbyname("ripdaveno"); > char* str = inet_ntoa(*((in_addr*)h->h_addr_list[0])); > ... > } > > The string in str was "192.168.2.75" which is my Network IP-Adress. With >

So just a quick note: Dovecot in general doesn't do DNS lookups, except the ones in configuration files and such. So I don't think there are any Dovecot setups which do DNS lookups for untrusted hostnames. Also, gethostbyname() is used only if IPv6 support isn't compiled into Dovecot. And IPv6 support is enabled by default if the libc is detected to support it, so pretty much all

----- Original Message ----- > From: "Simon Banton" <centos at web.org.uk> > To: "CentOS mailing list" <centos at centos.org> > Sent: Wednesday, January 28, 2015 6:10:34 AM > Subject: Re: [CentOS] CVE-2015-0235 - glibc gethostbyname > > Hi, > > For reasons which are too tiresome to bore you all with, I have an > obligation to look after

On Tue, January 27, 2015 2:35 pm, Thomas Eriksson wrote: > On 01/27/2015 12:22 PM, Valeri Galtsev wrote: >> >> On Tue, January 27, 2015 1:58 pm, Peter Lawler wrote: >>> On 28/01/15 04:47, Always Learning wrote: >>>> >>>> Saw this on the Exim List:- >>>> >>> <SNIP> >>>> >>>> I use Exim on C5 and C6 -

I know this has been discussed; but I can't seems to find the answer on the digest server. Can/How do I provide WINS name resolution for unix machine names ? We are using WINS on the PC side and /etc/hosts on the unix side. I would like to have a unix machine respond to WINS queries when it finds the requested name in it's host file. I have experimented with 'wins proxy',

I have an issue, although it's a result of sketchy code in the sip implementation in Asterisk that's been around forever, I am sure I am going to have to fix it some other way as many people have waited with no fix yet from Digium. If a name resolution fails for a remote sip peer, the entire stack tanks and local sip phones don't work either. We have several sip trunks and an analog