Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

inetd error message

Status
Not open for further replies.

stevenriz

IS-IT--Management
May 21, 2001
1,069
I get this when I try to run inetd after making system changes....

server1 inetd[983]: ISTATE not in environment

What's this mean? I can find info on it anywhere.
 
Also when I restart the server, the console displays this...

server1: RPC: Program not registered

Thanks all!
 
I did some Googling (!) & found a (garbled) link which included the line "inetd: couldn't find ISTATE environment variable. Try -s flag."

So, [tt]
# strings /usr/sbin/inetd | grep ISTATE
inetd: couldn't find ISTATE environment variable. Try -s flag.
ISTATE not in environment
[/tt]

Therefore, [tt]
# man inetd
<snip>
-s Allows you to run inetd ``stand-alone,'' outside
the Service Access Facility (SAF). If the -s
option is omitted, inetd will attempt to contact
the service access controller (SAC) and will exit
if SAC is not already running. See sac(1M).
[/tt]

OK, can you try inetd -s & see what happens?
One by one, the penguins steal my sanity.
 
And, re: RPC: Program not registered ...

[tt]When I restarted the box, which acts both as an NFS server and an NFS client, the boot process was paused with the following message:

Mounting NFS file systemsNFS Portmap: RPC: Program not registered

I also found the following messages in /var/log/messages on the NFS server:

portmap[83487]: connect from 192.168.0.18 to getport(mountd): request from unauthorized host
portmap[83517]: connect from 192.168.0.18 to getport(nfs): request from unauthorized host

I mentioned this on IRC, and Unfurl suggested it was an /etc/hosts.allow (i.e. tcpwrappers) issue. He suggested I change allow all for portmap. I did. Rebooted the client box (as that's the situation under which the problem occurred). This time, the box rebooted properly and the NFS partitions were properly mounted.

Here's what I had in /etc/hosts.allow:

# Portmapper is used for all RPC services; protect your NFS!
# (IP addresses rather than hostnames *MUST* be used here)
portmap : 192.0.2.32/255.255.255.224 : allow
portmap : 192.0.2.96/255.255.255.224 : allow
portmap : ALL : deny

Here's what I changed it to:

# Portmapper is used for all RPC services; protect your NFS!
# (IP addresses rather than hostnames *MUST* be used here)
portmap : 192.0.2.32/255.255.255.224 : allow
portmap : 192.0.2.96/255.255.255.224 : allow
portmap : 192.168.0.0/255.255.255.0 : allow
portmap : ALL : deny
[/tt]

Any use ?
One by one, the penguins steal my sanity.
 
Thank you. I will go through all of this info and let you know. Appreciate it greatly!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top