Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.sys.mac.system > #70062 > unrolled thread

AFP hell - How to stop Mac from insisting on connecting to non-existing remote volume?

Back to article view | Back to comp.sys.mac.system

Contents

  AFP hell - How to stop Mac from insisting on connecting to non-existing remote volume? rijk <rijk@blah.invalid> - 2015-02-21 19:04 +0100
    Re: AFP hell - How to stop Mac from insisting on connecting to non-existing remote volume? Jolly Roger <jollyroger@pobox.com> - 2015-02-21 20:12 +0000
    Re: AFP hell - How to stop Mac from insisting on connecting to non-existing remote volume? rijk <rijk@blah.invalid> - 2015-02-21 21:41 +0100
      Re: AFP hell - How to stop Mac from insisting on connecting to non-existing remote volume? Jolly Roger <jollyroger@pobox.com> - 2015-02-21 20:43 +0000
        Re: AFP hell - How to stop Mac from insisting on connecting to non-existing remote volume? rijk <rijk@blah.invalid> - 2015-02-22 02:51 +0100
          Re: AFP hell - How to stop Mac from insisting on connecting to non-existing remote volume? Jolly Roger <jollyroger@pobox.com> - 2015-02-22 15:39 +0000
            Re: AFP hell - How to stop Mac from insisting on connecting to non-existing remote volume? rijk <rijk@blah.invalid> - 2015-02-22 21:13 +0100
    Re: AFP hell - How to stop Mac from insisting on connecting to non-existing remote volume? JF Mezei <jfmezei.spamnot@vaxination.ca> - 2015-02-21 15:55 -0500

#70062 — AFP hell - How to stop Mac from insisting on connecting to non-existing remote volume?

To copy some files from one Mac to another, I enabled filesharing on the 
source afp server (OS X 10.8.5) and mounted the volume on the client (OS 
X Server 10.7.5). When I was done, I unmounted the volume on the client 
Mac[1], and disabled filesharing on the server.

Since then, the cliet Mac keeps on insisting on mounting that remote 
volume. It continually brings up a modal[2] dialog[3] that it can't find 
the server. After OK-ing that, it just reappears exactly 30 seconds 
later. Also, just opening a Finder window takes easily 5 minutes or more 
for it to even appear, and at least another 5 for it to list the 
contents of my home directory. (All the while continuously having to 
click away the dialogs about it not being able to find the server.)

I've tried multiple reboots of both machines, inclusidng Safe Boots 
(Shift key). I've tried looking with sudo lsof | grep [server/volume], 
which doesn't seem to list anything relevant. I've tried adding the 
remote volume to the client's Login Items (and then reboot, confirming 
it worked), and then removing it again, but even then, after yet another 
reboot, the problem persists.

How do I stop this insanity?


[1] Well, after days of troubleshooting this, I may remember 
incorrectly. It's possible that originally the source made itself 
unavailable. It's a disk in a Sharkoon SATA Quickport "Dock", which 
appears to be unreliable garbage. It's possible that the client lost the 
connection before I got the chance to explicitly unmount the remote 
volume. Possibly that's where the reconnection attempts stem from 
originally. But after that, I have succesfully reconnected, and 
unmounted it properly. And yet it keeps on insisting on connecting to 
the server.

[2] Impossible to ignore, as it shows atop whatever frontmost app.

[3] "There was a problem connecting to the server 'blah'. The server may 
not exist or it is unavailable at this time. Check the server name or IP 
address, check your network connection, and then try again." {OK}

-- 
"-- \n"

[toc] | [next] | [standalone]

#70066

On 2015-02-21, rijk <rijk@blah.invalid> wrote:
> To copy some files from one Mac to another, I enabled filesharing on the 
> source afp server (OS X 10.8.5) and mounted the volume on the client (OS 
> X Server 10.7.5). When I was done, I unmounted the volume on the client 
> Mac[1], and disabled filesharing on the server.
>
> Since then, the cliet Mac keeps on insisting on mounting that remote 
> volume. It continually brings up a modal[2] dialog[3] that it can't find 
> the server. After OK-ing that, it just reappears exactly 30 seconds 
> later. Also, just opening a Finder window takes easily 5 minutes or more 
> for it to even appear, and at least another 5 for it to list the 
> contents of my home directory. (All the while continuously having to 
> click away the dialogs about it not being able to find the server.)
>
> I've tried multiple reboots of both machines, inclusidng Safe Boots 
> (Shift key). I've tried looking with sudo lsof | grep [server/volume], 
> which doesn't seem to list anything relevant. I've tried adding the 
> remote volume to the client's Login Items (and then reboot, confirming 
> it worked), and then removing it again, but even then, after yet another 
> reboot, the problem persists.
>
> How do I stop this insanity?

[snip]

Hmm... That's peculiar. Login Items would have been my first guess. Is
it possible that you have enabled the "Reopen windows when logging back
in" setting in the window that appears when you log out of this user
account? If so, I wonder if Finder is trying to display a window showing
contents from this remote volume when you log in. You might try logging
out and disabling that feature temporarily to see if it makes a
difference. 

If not, then if you know the name of the server & volume to which the
computer is trying to connect, you could try searching through
/Library/Preferences and your own ~/Library/Preferences files for one or
both of those strings to see which preference files mention them. I'd
probably do that search with grep on the command line.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#70068

In article <rijk-B54E8B.19042621022015@news.xs4all.nl>,
 rijk <rijk@blah.invalid> wrote:

[…]

> Since then, the cliet Mac keeps on insisting on mounting that remote 
> volume.

{sigh} Too smart for my own good. I had forgotten about an alias 
pointing to the remote machine.

-- 
"-- \n"

[toc] | [prev] | [next] | [standalone]

#70069

On 2015-02-21, rijk <rijk@blah.invalid> wrote:
> In article <rijk-B54E8B.19042621022015@news.xs4all.nl>,
>  rijk <rijk@blah.invalid> wrote:
>
> […]
>
>> Since then, the cliet Mac keeps on insisting on mounting that remote 
>> volume.
>
> {sigh} Too smart for my own good. I had forgotten about an alias 
> pointing to the remote machine.

Aha! But where was this alias, that the system would want to resolve it
so often?

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#70079

In article <cks8uoFq318U6@mid.individual.net>,
 Jolly Roger <jollyroger@pobox.com> wrote:

> On 2015-02-21, rijk <rijk@blah.invalid> wrote:
> > In article <rijk-B54E8B.19042621022015@news.xs4all.nl>,
> >  rijk <rijk@blah.invalid> wrote:
> >
> > […]
> >
> >> Since then, the cliet Mac keeps on insisting on mounting that remote 
> >> volume.
> >
> > {sigh} Too smart for my own good. I had forgotten about an alias 
> > pointing to the remote machine.
> 
> Aha! But where was this alias, that the system would want to resolve it
> so often?

In my home folder. But the problem was that it had slipped my mind that 
it was used by Air Video Server. That turned out to be the app that 
triggered the mount attempts.

I had already tried quitting 'all' apps, thinking that something like 
this might be the cause. But AVS had completely slipped my mind. (I only 
use it to watch movies on my iPad while taking a bath, which I do maybe 
5 times a year.)

Longer background story, 'cause it might all still sound vague: the 
original story's afp client is a Mac mini, hooked up to a TV, posing as 
a media center. It has an external disk containing media, with an alias 
pointing media players (iTunes, XBMC, Air Video Server) to it.

That external disk died (loads of bad blocks - so much for "G-Drives are 
indestructible"…). While awaiting a replacement disk, I put a back-up in 
that Sharkoon Dock I mentioned and made it available over afp, and made 
the aforementioned alias point to it.

But that Sharkoon Dock seems unreliable. The disk kept on becoming 
unresponsive. So I decided to give up on that approach. Read some books 
until I get a replacement drive.

And then I ran into the "can't find remote server" issue that triggered 
my OP.

So there :)

-- 
"-- \n"

[toc] | [prev] | [next] | [standalone]

#70098

On 2015-02-22, rijk <rijk@blah.invalid> wrote:
> In article <cks8uoFq318U6@mid.individual.net>,
>  Jolly Roger <jollyroger@pobox.com> wrote:
>
>> On 2015-02-21, rijk <rijk@blah.invalid> wrote:
>> > In article <rijk-B54E8B.19042621022015@news.xs4all.nl>,
>> >  rijk <rijk@blah.invalid> wrote:
>> >
>> > […]
>> >
>> >> Since then, the cliet Mac keeps on insisting on mounting that remote 
>> >> volume.
>> >
>> > {sigh} Too smart for my own good. I had forgotten about an alias 
>> > pointing to the remote machine.
>> 
>> Aha! But where was this alias, that the system would want to resolve it
>> so often?
>
> In my home folder. But the problem was that it had slipped my mind that 
> it was used by Air Video Server. That turned out to be the app that 
> triggered the mount attempts.
>
> I had already tried quitting 'all' apps, thinking that something like 
> this might be the cause. But AVS had completely slipped my mind. (I only 
> use it to watch movies on my iPad while taking a bath, which I do maybe 
> 5 times a year.)

It's a little strange that lsof wouldn't have shown that AVS had that
file open. Perhaps you just missed it in the listing?

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

[toc] | [prev] | [next] | [standalone]

#70108

In article <ckubgtFc28uU4@mid.individual.net>,
 Jolly Roger <jollyroger@pobox.com> wrote:

[…]

> It's a little strange that lsof wouldn't have shown that AVS had that
> file open. Perhaps you just missed it in the listing?

Could be. Because I had forgotten not just about AVS but also about the 
alias file, I didn't think to look for its name with lsof. Just for the 
names of the remote volume and server (which are different).

-- 
"-- \n"

[toc] | [prev] | [next] | [standalone]

#70072

On 15-02-21 13:04, rijk wrote:

> How do I stop this insanity?

I would restart the server's AFP, let the client mount it when it wants.
And once done, do a proper dismount of the disk (eject it), and then
stop the server.


I have an alias on Snow Leopard that points to a directory on a remote
server. It exists on the dock. And if I click on it when connection is
not done, it just either doesn't do anthing or puts an error, it does
not ask to mount the remote thing.

My guess though is that once you have mounted it, if improperly
dismounted, the client will try to reconnect. Consider a laptop, it
reconnects to the shares when you wake it up, and this is a good thing.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.sys.mac.system

csiph-web