multihop attempted

[RolandH]

Hey Forumers,

we have a strange error message.

We have a user who whants rlogin to a system.
If he tried he gets this message:

Unable to change directory to "/h/e5/ts1002/home"
Logging in with home = "/".
Please wait...checking for disk quotas
mkdir: cannot create /h/e5/xxx/home/.CATIA4: Multihop attempted
mkdir: cannot create /h/e5/xxx/home/.CATIA4: Multihop attempted
mkdir: cannot create /h/e5/xxx/home/.CATIA4: Multihop attempted
mkdir: cannot create /h/e5/xxx/home/.CATIA5: Multihop attempted
mkdir: cannot create /h/e5/xxx/home/.CATIA5: Multihop attempted
mkdir: cannot create /h/e5/xxx/home/.CATIA5: Multihop attempted
mkdir: cannot create /h/e5/xxx/home/.VPM1: Multihop attempted
mkdir: cannot create /h/e5/xxx/home/.VPM1: Multihop attempted
rm: cannot stat /h/e5/xxx/home/.CNextPrinters: Multihop attempted
ln: /h/e5/xxx/home/.CNextPrinters: Multihop attempted


What does that mean ? Any suggests

Roland

[Mark Grant]

Just a guess, automounted home directory where automount doesn't work correctly. Would use autofs myself.

[RolandH]

Mark thx for y reply we using autofs !!!
Any suggest what *** Multihop attempted ***
means?

Thx
Roland

[Mark Grant]

The only reference I have been able to find says "This error occurs when users try to access remote resources that are not directly accessible."

This looks very much like those days of old when automounter created a billion symbolic links when mounting users home directories. So, it looks like and NFS mount where there is no permission to do that.

I appreciate this isn't especially helpful though!

[Massimo Bianchi]

#define EMULTIHOP 72 /* Multihop attempted */

But ?????

[Massimo Bianchi]

from google:

EMULTIHOP Components of path require hopping to multiple remote machines
and the file system does not allow it.

[RolandH]

Have made a Call to HP. They do not know what it is in the moment, too. Waiting for response of them. =|;-}
.. wait
.. wait
.. wait
.. please, wait
..


Roland

[RolandH]

Thx Guys,

the problem is solved. The internal links that the automounter created were corrupted.
The result was that the automounter couldn't remove them after the umount of the autmount-point. If the user tries now to make a new connection to that system he tries to create it again but cannot because it is still there. Then comes that message what I mentioned above. Strange isn't it. Never tought that this is the error. I expected another message.

Have nice day and thx for help =:-}}}

Roland