* autofs does not resolve names ?
@ 2011-07-16 1:01 JA Magallón
2011-07-16 2:30 ` [autofs] " Ian Kent
2011-07-16 13:01 ` Frank Thommen
0 siblings, 2 replies; 6+ messages in thread
From: JA Magallón @ 2011-07-16 1:01 UTC (permalink / raw)
To: autofs, Linux Kernel
Hi all...
Since the update to autofs-5.0.6, I have a curious problem. Probably it is not autofs
to blame, but I ask here to see if someone can give me some light...
Setup:
/etc/autofs/auto.master:
/home ldap://danae-nfs.cps.unizar.es/automountMapName=auto_home,o=diis --timeout=60,tcp,nobrowse
(user homes map from LDAP, shared homes at a server)
The name is resolved:
annwn:/etc/autofs# host danae-nfs
danae-nfs.cps.unizar.es has address 155.210.152.202
annwn:/etc/autofs# ping danae-nfs
PING danae-nfs.cps.unizar.es (155.210.152.202) 56(84) bytes of data.
64 bytes from danae-nfs.cps.unizar.es (155.210.152.202): icmp_req=1 ttl=255 time=0.339 ms
...
But when I access home (ssh the box):
Jul 15 01:39:31 annwn automount[7774]: Starting automounter version 5.0.6, master map auto.master
Jul 15 01:39:31 annwn automount[7774]: using kernel protocol version 5.02
Jul 15 01:39:31 annwn automount[7774]: lookup_nss_read_master: reading master files auto.master
...
Jul 15 01:39:31 annwn automount[7774]: mount_mount: mount(nfs): root=/home name=magallon what=danae-nfs:/export/home/usuarios/giga/magallon, fstype=nfs, options=tcp,quota
Jul 15 01:39:31 annwn automount[7774]: mount_mount: mount(nfs): nfs options="tcp,quota", nobind=0, nosymlink=0, ro=0
Jul 15 01:39:31 annwn automount[7774]: get_nfs_info: called with host danae-nfs(69.65.19.116) proto udp version 0x30
Jul 15 01:39:37 annwn automount[7774]: get_nfs_info: called with host danae-nfs(69.65.19.116) proto tcp version 0x30
Where the hell does it get that IP address for my server ????
Diggin a bit more:
annwn:/var/log# host 69.65.19.116
116.19.65.69.in-addr.arpa domain name pointer nx-deleted-host-1.no-ip.com
because I have at /etc/resolv.conf:
search cps.unizar.es unizar.es no-ip.org
Why did it not resolved first with the first domain ?
If I delete the no-ip.org domain, I get:
Jul 15 01:47:18 annwn automount[8068]: mount_mount: mount(nfs): root=/home name=magallon what=danae-nfs:/export/home/usuarios/giga/magallon, fstype=nfs, options=tcp,quota
Jul 15 01:47:18 annwn automount[8068]: mount_mount: mount(nfs): nfs options="tcp,quota", nobind=0, nosymlink=0, ro=0
Jul 15 01:47:20 annwn automount[8068]: add_host_addrs: hostname lookup failed: Name or service not known
Jul 15 01:47:20 annwn automount[8068]: mount(nfs): no hosts available
Jul 15 01:47:20 annwn automount[8068]: dev_ioctl_send_fail: token = 28
Jul 15 01:47:20 annwn automount[8068]: failed to mount /home/magallon
automount does not add the search domains and resolve ? what am I doing wrong ?
is it a bug ? uuhhh ?
TIA
--
J.A. Magallon <jamagallon()ono!com> \ Winter is coming...
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [autofs] autofs does not resolve names ?
2011-07-16 1:01 autofs does not resolve names ? JA Magallón
@ 2011-07-16 2:30 ` Ian Kent
2011-07-16 23:17 ` JA Magallón
2011-07-16 23:37 ` [autofs] " JA Magallón
2011-07-16 13:01 ` Frank Thommen
1 sibling, 2 replies; 6+ messages in thread
From: Ian Kent @ 2011-07-16 2:30 UTC (permalink / raw)
To: JA Magallón; +Cc: autofs, Linux Kernel
On Sat, 2011-07-16 at 03:01 +0200, JA Magallón wrote:
> Hi all...
>
> Since the update to autofs-5.0.6, I have a curious problem. Probably it is not autofs
> to blame, but I ask here to see if someone can give me some light...
Have you applied autofs-5.0.6-fix-ipv6-name-for-lookup-fix.patch?
Which fixes a stupid mistake on my part.
>
> Setup:
> /etc/autofs/auto.master:
>
> /home ldap://danae-nfs.cps.unizar.es/automountMapName=auto_home,o=diis --timeout=60,tcp,nobrowse
>
> (user homes map from LDAP, shared homes at a server)
>
> The name is resolved:
>
> annwn:/etc/autofs# host danae-nfs
> danae-nfs.cps.unizar.es has address 155.210.152.202
> annwn:/etc/autofs# ping danae-nfs
> PING danae-nfs.cps.unizar.es (155.210.152.202) 56(84) bytes of data.
> 64 bytes from danae-nfs.cps.unizar.es (155.210.152.202): icmp_req=1 ttl=255 time=0.339 ms
> ...
>
> But when I access home (ssh the box):
>
> Jul 15 01:39:31 annwn automount[7774]: Starting automounter version 5.0.6, master map auto.master
> Jul 15 01:39:31 annwn automount[7774]: using kernel protocol version 5.02
> Jul 15 01:39:31 annwn automount[7774]: lookup_nss_read_master: reading master files auto.master
> ...
> Jul 15 01:39:31 annwn automount[7774]: mount_mount: mount(nfs): root=/home name=magallon what=danae-nfs:/export/home/usuarios/giga/magallon, fstype=nfs, options=tcp,quota
> Jul 15 01:39:31 annwn automount[7774]: mount_mount: mount(nfs): nfs options="tcp,quota", nobind=0, nosymlink=0, ro=0
> Jul 15 01:39:31 annwn automount[7774]: get_nfs_info: called with host danae-nfs(69.65.19.116) proto udp version 0x30
> Jul 15 01:39:37 annwn automount[7774]: get_nfs_info: called with host danae-nfs(69.65.19.116) proto tcp version 0x30
>
> Where the hell does it get that IP address for my server ????
>
> Diggin a bit more:
>
> annwn:/var/log# host 69.65.19.116
> 116.19.65.69.in-addr.arpa domain name pointer nx-deleted-host-1.no-ip.com
>
> because I have at /etc/resolv.conf:
>
> search cps.unizar.es unizar.es no-ip.org
>
> Why did it not resolved first with the first domain ?
>
> If I delete the no-ip.org domain, I get:
>
> Jul 15 01:47:18 annwn automount[8068]: mount_mount: mount(nfs): root=/home name=magallon what=danae-nfs:/export/home/usuarios/giga/magallon, fstype=nfs, options=tcp,quota
> Jul 15 01:47:18 annwn automount[8068]: mount_mount: mount(nfs): nfs options="tcp,quota", nobind=0, nosymlink=0, ro=0
> Jul 15 01:47:20 annwn automount[8068]: add_host_addrs: hostname lookup failed: Name or service not known
> Jul 15 01:47:20 annwn automount[8068]: mount(nfs): no hosts available
> Jul 15 01:47:20 annwn automount[8068]: dev_ioctl_send_fail: token = 28
> Jul 15 01:47:20 annwn automount[8068]: failed to mount /home/magallon
>
> automount does not add the search domains and resolve ? what am I doing wrong ?
> is it a bug ? uuhhh ?
>
> TIA
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [autofs] autofs does not resolve names ?
2011-07-16 1:01 autofs does not resolve names ? JA Magallón
2011-07-16 2:30 ` [autofs] " Ian Kent
@ 2011-07-16 13:01 ` Frank Thommen
1 sibling, 0 replies; 6+ messages in thread
From: Frank Thommen @ 2011-07-16 13:01 UTC (permalink / raw)
To: JA Magallón; +Cc: autofs, Linux Kernel
JA Magallón wrote:
> [...]
>
> The name is resolved:
>
> annwn:/etc/autofs# host danae-nfs
> danae-nfs.cps.unizar.es has address 155.210.152.202
> annwn:/etc/autofs# ping danae-nfs
> PING danae-nfs.cps.unizar.es (155.210.152.202) 56(84) bytes of data.
> 64 bytes from danae-nfs.cps.unizar.es (155.210.152.202): icmp_req=1 ttl=255 time=0.339 ms
> ...
>
> But when I access home (ssh the box):
>
> Jul 15 01:39:31 annwn automount[7774]: Starting automounter version 5.0.6, master map auto.master
> Jul 15 01:39:31 annwn automount[7774]: using kernel protocol version 5.02
> Jul 15 01:39:31 annwn automount[7774]: lookup_nss_read_master: reading master files auto.master
> ...
> Jul 15 01:39:31 annwn automount[7774]: mount_mount: mount(nfs): root=/home name=magallon what=danae-nfs:/export/home/usuarios/giga/magallon, fstype=nfs, options=tcp,quota
> Jul 15 01:39:31 annwn automount[7774]: mount_mount: mount(nfs): nfs options="tcp,quota", nobind=0, nosymlink=0, ro=0
> Jul 15 01:39:31 annwn automount[7774]: get_nfs_info: called with host danae-nfs(69.65.19.116) proto udp version 0x30
> Jul 15 01:39:37 annwn automount[7774]: get_nfs_info: called with host danae-nfs(69.65.19.116) proto tcp version 0x30
>
> Where the hell does it get that IP address for my server ????
Did you check your /etc/hosts file?
>
> [...]
>
frank
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: autofs does not resolve names ?
2011-07-16 2:30 ` [autofs] " Ian Kent
@ 2011-07-16 23:17 ` JA Magallón
2011-07-16 23:37 ` [autofs] " JA Magallón
1 sibling, 0 replies; 6+ messages in thread
From: JA Magallón @ 2011-07-16 23:17 UTC (permalink / raw)
To: autofs
On Sat, 16 Jul 2011 10:30:58 +0800, Ian Kent <raven@themaw.net> wrote:
> On Sat, 2011-07-16 at 03:01 +0200, JA Magallón wrote:
> > Hi all...
> >
> > Since the update to autofs-5.0.6, I have a curious problem. Probably it is not autofs
> > to blame, but I ask here to see if someone can give me some light...
>
> Have you applied autofs-5.0.6-fix-ipv6-name-for-lookup-fix.patch?
> Which fixes a stupid mistake on my part.
>
Don't know, will check my distro src.rpm. Thanks for the pointer.
> >
> > Setup:
> > /etc/autofs/auto.master:
> >
> > /home ldap://danae-nfs.cps.unizar.es/automountMapName=auto_home,o=diis --timeout=60,tcp,nobrowse
> >
> > (user homes map from LDAP, shared homes at a server)
> >
> > The name is resolved:
> >
> > annwn:/etc/autofs# host danae-nfs
> > danae-nfs.cps.unizar.es has address 155.210.152.202
> > annwn:/etc/autofs# ping danae-nfs
> > PING danae-nfs.cps.unizar.es (155.210.152.202) 56(84) bytes of data.
> > 64 bytes from danae-nfs.cps.unizar.es (155.210.152.202): icmp_req=1 ttl=255 time=0.339 ms
> > ...
> >
> > But when I access home (ssh the box):
> >
> > Jul 15 01:39:31 annwn automount[7774]: Starting automounter version 5.0.6, master map auto.master
> > Jul 15 01:39:31 annwn automount[7774]: using kernel protocol version 5.02
> > Jul 15 01:39:31 annwn automount[7774]: lookup_nss_read_master: reading master files auto.master
> > ...
> > Jul 15 01:39:31 annwn automount[7774]: mount_mount: mount(nfs): root=/home name=magallon what=danae-nfs:/export/home/usuarios/giga/magallon, fstype=nfs, options=tcp,quota
> > Jul 15 01:39:31 annwn automount[7774]: mount_mount: mount(nfs): nfs options="tcp,quota", nobind=0, nosymlink=0, ro=0
> > Jul 15 01:39:31 annwn automount[7774]: get_nfs_info: called with host danae-nfs(69.65.19.116) proto udp version 0x30
> > Jul 15 01:39:37 annwn automount[7774]: get_nfs_info: called with host danae-nfs(69.65.19.116) proto tcp version 0x30
> >
> > Where the hell does it get that IP address for my server ????
> >
> > Diggin a bit more:
> >
> > annwn:/var/log# host 69.65.19.116
> > 116.19.65.69.in-addr.arpa domain name pointer nx-deleted-host-1.no-ip.com
> >
> > because I have at /etc/resolv.conf:
> >
> > search cps.unizar.es unizar.es no-ip.org
> >
> > Why did it not resolved first with the first domain ?
> >
> > If I delete the no-ip.org domain, I get:
> >
> > Jul 15 01:47:18 annwn automount[8068]: mount_mount: mount(nfs): root=/home name=magallon what=danae-nfs:/export/home/usuarios/giga/magallon, fstype=nfs, options=tcp,quota
> > Jul 15 01:47:18 annwn automount[8068]: mount_mount: mount(nfs): nfs options="tcp,quota", nobind=0, nosymlink=0, ro=0
> > Jul 15 01:47:20 annwn automount[8068]: add_host_addrs: hostname lookup failed: Name or service not known
> > Jul 15 01:47:20 annwn automount[8068]: mount(nfs): no hosts available
> > Jul 15 01:47:20 annwn automount[8068]: dev_ioctl_send_fail: token = 28
> > Jul 15 01:47:20 annwn automount[8068]: failed to mount /home/magallon
> >
> > automount does not add the search domains and resolve ? what am I doing wrong ?
> > is it a bug ? uuhhh ?
> >
> > TIA
> >
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
J.A. Magallon <jamagallon()ono!com> \ Winter is coming...
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [autofs] autofs does not resolve names ?
2011-07-16 2:30 ` [autofs] " Ian Kent
2011-07-16 23:17 ` JA Magallón
@ 2011-07-16 23:37 ` JA Magallón
2011-07-18 1:57 ` Ian Kent
1 sibling, 1 reply; 6+ messages in thread
From: JA Magallón @ 2011-07-16 23:37 UTC (permalink / raw)
To: Linux Kernel; +Cc: autofs
On Sat, 16 Jul 2011 10:30:58 +0800, Ian Kent <raven@themaw.net> wrote:
(CC LKML for info and completeness...)
> On Sat, 2011-07-16 at 03:01 +0200, JA Magallón wrote:
> > Hi all...
> >
> > Since the update to autofs-5.0.6, I have a curious problem. Probably it is not autofs
> > to blame, but I ask here to see if someone can give me some light...
>
> Have you applied autofs-5.0.6-fix-ipv6-name-for-lookup-fix.patch?
> Which fixes a stupid mistake on my part.
>
Love you ! That did the trick, everything works again.
Are you planning to release a 5.0.7 with the fix ?
> >
> > Setup:
> > /etc/autofs/auto.master:
> >
> > /home ldap://danae-nfs.cps.unizar.es/automountMapName=auto_home,o=diis --timeout=60,tcp,nobrowse
> >
> > (user homes map from LDAP, shared homes at a server)
> >
> > The name is resolved:
> >
> > annwn:/etc/autofs# host danae-nfs
> > danae-nfs.cps.unizar.es has address 155.210.152.202
> > annwn:/etc/autofs# ping danae-nfs
> > PING danae-nfs.cps.unizar.es (155.210.152.202) 56(84) bytes of data.
> > 64 bytes from danae-nfs.cps.unizar.es (155.210.152.202): icmp_req=1 ttl=255 time=0.339 ms
> > ...
> >
> > But when I access home (ssh the box):
> >
> > Jul 15 01:39:31 annwn automount[7774]: Starting automounter version 5.0.6, master map auto.master
> > Jul 15 01:39:31 annwn automount[7774]: using kernel protocol version 5.02
> > Jul 15 01:39:31 annwn automount[7774]: lookup_nss_read_master: reading master files auto.master
> > ...
> > Jul 15 01:39:31 annwn automount[7774]: mount_mount: mount(nfs): root=/home name=magallon what=danae-nfs:/export/home/usuarios/giga/magallon, fstype=nfs, options=tcp,quota
> > Jul 15 01:39:31 annwn automount[7774]: mount_mount: mount(nfs): nfs options="tcp,quota", nobind=0, nosymlink=0, ro=0
> > Jul 15 01:39:31 annwn automount[7774]: get_nfs_info: called with host danae-nfs(69.65.19.116) proto udp version 0x30
> > Jul 15 01:39:37 annwn automount[7774]: get_nfs_info: called with host danae-nfs(69.65.19.116) proto tcp version 0x30
> >
> > Where the hell does it get that IP address for my server ????
> >
> > Diggin a bit more:
> >
> > annwn:/var/log# host 69.65.19.116
> > 116.19.65.69.in-addr.arpa domain name pointer nx-deleted-host-1.no-ip.com
> >
> > because I have at /etc/resolv.conf:
> >
> > search cps.unizar.es unizar.es no-ip.org
> >
> > Why did it not resolved first with the first domain ?
> >
> > If I delete the no-ip.org domain, I get:
> >
> > Jul 15 01:47:18 annwn automount[8068]: mount_mount: mount(nfs): root=/home name=magallon what=danae-nfs:/export/home/usuarios/giga/magallon, fstype=nfs, options=tcp,quota
> > Jul 15 01:47:18 annwn automount[8068]: mount_mount: mount(nfs): nfs options="tcp,quota", nobind=0, nosymlink=0, ro=0
> > Jul 15 01:47:20 annwn automount[8068]: add_host_addrs: hostname lookup failed: Name or service not known
> > Jul 15 01:47:20 annwn automount[8068]: mount(nfs): no hosts available
> > Jul 15 01:47:20 annwn automount[8068]: dev_ioctl_send_fail: token = 28
> > Jul 15 01:47:20 annwn automount[8068]: failed to mount /home/magallon
> >
> > automount does not add the search domains and resolve ? what am I doing wrong ?
> > is it a bug ? uuhhh ?
> >
> > TIA
> >
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
J.A. Magallon <jamagallon()ono!com> \ Winter is coming...
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [autofs] autofs does not resolve names ?
2011-07-16 23:37 ` [autofs] " JA Magallón
@ 2011-07-18 1:57 ` Ian Kent
0 siblings, 0 replies; 6+ messages in thread
From: Ian Kent @ 2011-07-18 1:57 UTC (permalink / raw)
To: JA Magallón; +Cc: Linux Kernel, autofs
On Sun, 2011-07-17 at 01:37 +0200, JA Magallón wrote:
> On Sat, 16 Jul 2011 10:30:58 +0800, Ian Kent <raven@themaw.net> wrote:
>
> (CC LKML for info and completeness...)
>
> > On Sat, 2011-07-16 at 03:01 +0200, JA Magallón wrote:
> > > Hi all...
> > >
> > > Since the update to autofs-5.0.6, I have a curious problem. Probably it is not autofs
> > > to blame, but I ask here to see if someone can give me some light...
> >
> > Have you applied autofs-5.0.6-fix-ipv6-name-for-lookup-fix.patch?
> > Which fixes a stupid mistake on my part.
> >
>
> Love you ! That did the trick, everything works again.
>
> Are you planning to release a 5.0.7 with the fix ?
That will go into 5.0.7 but it probably won't be released for a while.
Patches, such as this, are available on
http://www.kernel.org/pub/linux/daemons/autofs/v5 as soon as they are
committed to the autofs repository.
>
> > >
> > > Setup:
> > > /etc/autofs/auto.master:
> > >
> > > /home ldap://danae-nfs.cps.unizar.es/automountMapName=auto_home,o=diis --timeout=60,tcp,nobrowse
> > >
> > > (user homes map from LDAP, shared homes at a server)
> > >
> > > The name is resolved:
> > >
> > > annwn:/etc/autofs# host danae-nfs
> > > danae-nfs.cps.unizar.es has address 155.210.152.202
> > > annwn:/etc/autofs# ping danae-nfs
> > > PING danae-nfs.cps.unizar.es (155.210.152.202) 56(84) bytes of data.
> > > 64 bytes from danae-nfs.cps.unizar.es (155.210.152.202): icmp_req=1 ttl=255 time=0.339 ms
> > > ...
> > >
> > > But when I access home (ssh the box):
> > >
> > > Jul 15 01:39:31 annwn automount[7774]: Starting automounter version 5.0.6, master map auto.master
> > > Jul 15 01:39:31 annwn automount[7774]: using kernel protocol version 5.02
> > > Jul 15 01:39:31 annwn automount[7774]: lookup_nss_read_master: reading master files auto.master
> > > ...
> > > Jul 15 01:39:31 annwn automount[7774]: mount_mount: mount(nfs): root=/home name=magallon what=danae-nfs:/export/home/usuarios/giga/magallon, fstype=nfs, options=tcp,quota
> > > Jul 15 01:39:31 annwn automount[7774]: mount_mount: mount(nfs): nfs options="tcp,quota", nobind=0, nosymlink=0, ro=0
> > > Jul 15 01:39:31 annwn automount[7774]: get_nfs_info: called with host danae-nfs(69.65.19.116) proto udp version 0x30
> > > Jul 15 01:39:37 annwn automount[7774]: get_nfs_info: called with host danae-nfs(69.65.19.116) proto tcp version 0x30
> > >
> > > Where the hell does it get that IP address for my server ????
> > >
> > > Diggin a bit more:
> > >
> > > annwn:/var/log# host 69.65.19.116
> > > 116.19.65.69.in-addr.arpa domain name pointer nx-deleted-host-1.no-ip.com
> > >
> > > because I have at /etc/resolv.conf:
> > >
> > > search cps.unizar.es unizar.es no-ip.org
> > >
> > > Why did it not resolved first with the first domain ?
> > >
> > > If I delete the no-ip.org domain, I get:
> > >
> > > Jul 15 01:47:18 annwn automount[8068]: mount_mount: mount(nfs): root=/home name=magallon what=danae-nfs:/export/home/usuarios/giga/magallon, fstype=nfs, options=tcp,quota
> > > Jul 15 01:47:18 annwn automount[8068]: mount_mount: mount(nfs): nfs options="tcp,quota", nobind=0, nosymlink=0, ro=0
> > > Jul 15 01:47:20 annwn automount[8068]: add_host_addrs: hostname lookup failed: Name or service not known
> > > Jul 15 01:47:20 annwn automount[8068]: mount(nfs): no hosts available
> > > Jul 15 01:47:20 annwn automount[8068]: dev_ioctl_send_fail: token = 28
> > > Jul 15 01:47:20 annwn automount[8068]: failed to mount /home/magallon
> > >
> > > automount does not add the search domains and resolve ? what am I doing wrong ?
> > > is it a bug ? uuhhh ?
> > >
> > > TIA
> > >
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2011-07-18 1:57 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-07-16 1:01 autofs does not resolve names ? JA Magallón
2011-07-16 2:30 ` [autofs] " Ian Kent
2011-07-16 23:17 ` JA Magallón
2011-07-16 23:37 ` [autofs] " JA Magallón
2011-07-18 1:57 ` Ian Kent
2011-07-16 13:01 ` Frank Thommen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).