http://qs321.pair.com?node_id=1232425


in reply to Problem connecting with SSL to mySQL database

Hello ibm1620,

I'm taking a stab in the dark here, just trying to be helpful.

Stating the obvious, the 5.16 version doesn't mind that you've got some self-signed certs. 5.22 doesn't like the self-signed certs.

Perhaps 5.16 is configured to disregard SSL errors?

Lastly, I don't know anything about invoking with /usr/bin/env perl, but perhaps it's adjusting the environment (variables) such that the two Perls behave differently? (Running the programs under two different user accounts could have a similar effect.)

Good luck.

EDIT: What happens when you use an absolute path to the 5.22 installation in the shebang instead of using env?

Cheers,

Brent

-- Yeah, I'm a Delt.

Replies are listed 'Best First'.
Re^2: Problem connecting with SSL to mySQL database
by ibm1620 (Hermit) on Apr 10, 2019 at 23:29 UTC
    Brent,

    Thanks for your feedback. I didn't get any different results using absolute paths in the shebang line. And I'm running under the same account in all cases (the same account whose credentials I'm providing to mysql).

    I don't know what a "self-signed SSL certification" is so I don't know if that's what we have, or whether that's a misleading error message. I think we've established that the only thing different is the version (or location?) of Perl and its library of modules.

    I'm going to try to figure out if this is a matter of missing modules, or of the way the 5.16 version was configured when it was built.

[reply]
      hmm... I'm really out of decent ideas.

      I haven't used DBI in quite some time. Perhaps you can try enabling some debugging information by using DBI->trace() ?

      Something like:

      DBI->trace($trace_setting);

      [download]
      where $trace_setting is number from 1 and 15. Start with 1 and work your way up until you see something useful.

      Cheers,

      Brent

      -- Yeah, I'm a Delt.
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom