In my /var/adm/messages, it contains the following error.

clinet_hostname statd[203]: [ID 859811 daemon.warning] statd: host
old_netapps_server_hostname  is not responding

I used old_netapps_server_hosntame before, but I have changed the
netapps server and
with new hostname. why is the mouning still trying to pull the
old_netapps_server_hostname.

I have cleaned up /var/yp/aliases on client system and I use the new
domain name
at /var/yp/binding/new_domain_name

Please shed a light.

Thanks in advance

[ Post a follow-up to this message ]

On 8 Nov 2005 04:52:29 -0800, blackdog <cljlk@hotmail.com> wrote:
> In my /var/adm/messages, it contains the following error.

On, presumably, some system other than the netapp?  Does it mount it, or
what's the relationship?

> clinet_hostname statd[203]: [ID 859811 daemon.warning] statd: host
> old_netapps_server_hostname  is not responding

Does old_netapps_server_hostname resolve?

> I used old_netapps_server_hosntame before, but I have changed the
> netapps server and
> with new hostname.

That sentence may be key to identifying the problem and is unclearly
worded.  Can you try again?

> why is the mouning still trying to pull the
> old_netapps_server_hostname.

What's the fstab, vfstab, or whatever, look like?  What OS are you on?

> I have cleaned up /var/yp/aliases on client system and I use the new
> domain name

> at /var/yp/binding/new_domain_name

Hang on, you're getting off in the weeds.  Can you resolve the hostname?
Can you ping it?  Let's not worry about YP until you can actually see
the netapp.  I suspect name resolution problems and nothing more at this
point.

[ Post a follow-up to this message ]

Dave Hinz wrote:
> On 8 Nov 2005 04:52:29 -0800, blackdog <cljlk@hotmail.com> wrote: 
>
> On, presumably, some system other than the netapp?  Does it mount it, or
> what's the relationship?

I have NIS server, mount the file form NetApps. NetApps is my filer.

> 
>
> Does old_netapps_server_hostname resolve?

We have moved the old_netapps_server to other area, I should not use
the old_netapps_server.
since I have the new server with the new hostname.
Right now, the client is trying to talk to old_netapps_server.
Obviously, client cannot
get respond.

> 
>
> That sentence may be key to identifying the problem and is unclearly
> worded.  Can you try again?
> 
>
> What's the fstab, vfstab, or whatever, look like?  What OS are you on?
> 
> 
>
> Hang on, you're getting off in the weeds.  Can you resolve the hostname?
> Can you ping it?  Let's not worry about YP until you can actually see
> the netapp.  I suspect name resolution problems and nothing more at this
> point.

[ Post a follow-up to this message ]

Dave Hinz wrote:
> On 8 Nov 2005 04:52:29 -0800, blackdog <cljlk@hotmail.com> wrote: 
>
> On, presumably, some system other than the netapp?  Does it mount it, or
> what's the relationship?
> 
>
> Does old_netapps_server_hostname resolve?
> 
>
> That sentence may be key to identifying the problem and is unclearly
> worded.  Can you try again?
> 
>
> What's the fstab, vfstab, or whatever, look like?  What OS are you on?


I use Solaris 2.8 for client, the vfstab as below:

fd      -       /dev/fd fd      -       no      -
/proc   -       /proc   proc    -       no      -
/dev/dsk/c0t0d0s1       -       -       swap    -       no      -
/dev/dsk/c0t0d0s0       /dev/rdsk/c0t0d0s0      /       ufs     1
no
-
/dev/dsk/c0t0d0s5       /dev/rdsk/c0t0d0s5      /usr    ufs     1
no
-
/dev/dsk/c0t0d0s7       /dev/rdsk/c0t0d0s7      /var    ufs     1
no
-
/dev/dsk/c0t0d0s4       /dev/rdsk/c0t0d0s4      /apps1    ufs     2
yes
-
/dev/dsk/c0t0d0s3       /dev/rdsk/c0t0d0s3      /apps2  ufs     2
yes
-
/dev/dsk/c0t0d0s6       /dev/rdsk/c0t0d0s6      /tmp    ufs     2
yes


> 
> 
>
> Hang on, you're getting off in the weeds.  Can you resolve the hostname?
> Can you ping it?  Let's not worry about YP until you can actually see
> the netapp.  I suspect name resolution problems and nothing more at this
> point.

[ Post a follow-up to this message ]

On 8 Nov 2005 08:06:13 -0800, blackdog <cljlk@hotmail.com> wrote:
>
> Dave Hinz wrote: 
>
> I have NIS server, mount the file form NetApps. NetApps is my filer.

So you have a unix system of some sort, which uses nfs to mount a share
exported by the filer.
 
>
> We have moved the old_netapps_server to other area, I should not use
> the old_netapps_server.

There is your problem.

> since I have the new server with the new hostname.
> Right now, the client is trying to talk to old_netapps_server.
> Obviously, client cannot
> get respond.

You need to change your vfstab to point to:
newserver:/share
instead of
oldserver:/share
[vbcol=seagreen] 

[ Post a follow-up to this message ]

On 8 Nov 2005 08:09:43 -0800, blackdog <cljlk@hotmail.com> wrote:
>
> Dave Hinz wrote: 
[vbcol=seagreen]
> I use Solaris 2.8 for client, the vfstab as below:

(snip vfstab)

There is nothing talking about your filer in that vfstab.  Perhaps you
are mounting it by automount?  What do /etc/auto?master and
/etc/auto?home look like, for instance?

Until you know what mechanism is supposed to be mounting that device,
you don't know where to fix the problem.

[ Post a follow-up to this message ]

Dave Hinz wrote:
> On 8 Nov 2005 08:09:43 -0800, blackdog <cljlk@hotmail.com> wrote: 
> 
>
> (snip vfstab)
>
> There is nothing talking about your filer in that vfstab.  Perhaps you
> are mounting it by automount?  What do /etc/auto?master and
> /etc/auto?home look like, for instance?
>
> Until you know what mechanism is supposed to be mounting that device,
> you don't know where to fix the problem.


Yes, I use automount.
the auto_home contains:
+auto_home

and auto_master contains:
+auto_master
/net            -hosts          -nosuid,nobrowse
/home           auto_home       -nobrowse
/xfn            -xfn

[ Post a follow-up to this message ]

On 8 Nov 2005 08:53:04 -0800, blackdog <cljlk@hotmail.com> wrote:
>
> Dave Hinz wrote:
 
[vbcol=seagreen] 
[vbcol=seagreen]
> Yes, I use automount.
> the auto_home contains:
> +auto_home

And what's in the auto_home map?  The question we're painfully getting
towards, slowly, maybe, is, where is the old netapp's hostname coming
from.  Find that, fix that.  All will be better.

Can you mount it manually?  That'll verify that you're on the right
track.

> and auto_master contains:
> +auto_master
> /net            -hosts          -nosuid,nobrowse
> /home           auto_home       -nobrowse
> /xfn            -xfn

Likewise, what does the auto_master map look like?

[ Post a follow-up to this message ]

Dave Hinz wrote:
> On 8 Nov 2005 08:53:04 -0800, blackdog <cljlk@hotmail.com> wrote: 
> 
> 
> 
>
> And what's in the auto_home map?  The question we're painfully getting
> towards, slowly, maybe, is, where is the old netapp's hostname coming
> from.  Find that, fix that.  All will be better.
>
> Can you mount it manually?  That'll verify that you're on the right
> track.
> 
>
> Likewise, what does the auto_master map look like?

I can mount from new filer system. But, every time I reboot the client,
the log /var/adm/messages comes up an error as below on client:

Oct 10 22:40:38 client_system statd[203]: [ID 859811 daemon.warning]
statd: host old_netapps_server is not responding

auto_master file contains as below:
+auto_master
/net            -hosts          -nosuid,nobrowse
/home           auto_home       -nobrowse
/xfn            -xfn

and the auto_home file contains as below:
+auto_home

[ Post a follow-up to this message ]

On 8 Nov 2005 09:16:59 -0800, blackdog <cljlk@hotmail.com> wrote:
>
> Dave Hinz wrote:
 
[vbcol=seagreen] 

You need to look at the automount maps on your YP master.
[vbcol=seagreen] 
[vbcol=seagreen]
> I can mount from new filer system. But, every time I reboot the client,
> the log /var/adm/messages comes up an error as below on client:

> Oct 10 22:40:38 client_system statd[203]: [ID 859811 daemon.warnin
g]
> statd: host old_netapps_server is not responding

> auto_master file contains as below:
> +auto_master

That's the map.

> and the auto_home file contains as below:
>  +auto_home

That's also a map.

[ Post a follow-up to this message ]