in reply to Re^2: Net::OpenSSH killing script
in thread Net::OpenSSH killing script

Have you googled for "unable to establish master SSH Connection: Unknown error"? Didn't think so.

As a matter of fact I did, and although these perlmonks nodes are mentioned, the first link I got back from Google was a node where it was pointed out it is usually a filesystem permissions error which spits out that message.

I didn't include the quotations in the search string. That explains the difference in our search results.

You show why you remain anonymous, since your programming troubleshooting techniques are so poor.

Bad wu wei man. You come here asking for free answers, then complain when you are not spoon fed an answer.

I'm not really a human, but I play one on earth.
Old Perl Programmer Haiku ................... flash japh

Replies are listed 'Best First'.
Re^4: Net::OpenSSH killing script
by Anonymous Monk on Feb 04, 2011 at 15:19 UTC
    Try again, dude.

    These PM nodes are not only mentioned first, they are the only ones mentioned. (HINT: when searching for a specific error message, you need to quote the search string.)

    I did not come here asking for answers, free or otherwise. Don't blame someone else for my node. Bad wu wei, indeed.

[reply]
      Look you loser, google for

      unable to establish master SSH Connection: Unknown error

      without any quote marks around it. Then search for the ones which mention ssh.

      The answer is in the first page of numerous links.

      You shouldn't be a programmer, you always check for string quoting errors in failed searches.... the class is called "Try_Harder_101"

      I'm not really a human, but I play one on earth.
      Old Perl Programmer Haiku ................... flash japh
[reply]
        Look you loser,
        Yipes! Major, major bad wei wu for that!

        Let me explain carefully what I did. First I searched with quotes around the error string. I maintain that when one wants to find information about a specific error message that one must include the quotes so as to immediately filter out the extraneous hits that would otherwise match things like ssh. (Cluebat: In this context all those links out there that mention ssh in some random context are noise.) This search yielded two (2) hits (as mentioned above), both of which were for the OPs original node (one directly to the node, the other via SoPW).

        Next I did it your way (sans quotes), which turned up 15k+ hits. The top hit there is to an html-ized rendering of the Net::OpenSSH sources. Of course this error message is there, but we already knew that, as the OP was kind enough to tell us that this error message was provided by the module in question. The next two hits are for the root node of this thread; the next is the one where you start calling me names, and the rest go off into that nether world of random links about ssh. As the question posed by the OP is about an error message from Net::OpenSSH, hoping to find something useful in those links seems like a waste of time.

        The answer is in the first page of numerous links.

        Well, then, if you're willing to be truly helpful and demonstrate some of your superior intelligence, please point to the specific google result that has you throwing fits like

        You shouldn't be a programmer, you always check for string quoting errors in failed searches.... the class is called "Try_Harder_101"
        I'm willing to learn the error(s) of my ways. Are you willing to teach? Or are you going to continue with the bovine birthing rituals?
[reply]

In Section Seekers of Perl Wisdom