Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-13503

Moodle Networking: cannot find openssl.cnf so networking fails.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • 1.9.6
    • 1.9
    • MNet
    • None
    • Confirmed on both Windows and Linux platforms including with fresh installs
    • MOODLE_19_STABLE
    • MOODLE_19_STABLE

      When going through the Site Administration tree in the latest CVS and with server Debug messages set to normal, most items of the Networking branch give several warnings of the form below that are within the function mnet_generate_keypair. We don't use this form of networking yet, so I am unable to fully understand the problem, but it appears that the keypair is not being generated. And the admin block should not be giving warnings under normal initial install situations. There have been several changes to these files in the past 5 days, so perhaps an issue got introduced.

      Here are the messages:

      Warning: openssl_csr_sign() [function.openssl-csr-sign]: cannot get CSR from parameter 1 in /var/www/moodle/mnet/lib.php on line 323

      Warning: openssl_x509_export() [function.openssl-x509-export]: cannot get cert from parameter 1 in /var/www/moodle/mnet/lib.php on line 327

      Warning: openssl_x509_free() expects parameter 1 to be resource, boolean given in /var/www/moodle/mnet/lib.php on line 328

      Warning: openssl_pkey_export() [function.openssl-pkey-export]: cannot get key from parameter 1 in /var/www/moodle/mnet/lib.php on line 332

      Warning: openssl_pkey_free() expects parameter 1 to be resource, boolean given in /var/www/moodle/mnet/lib.php on line 333

            danmarsden Dan Marsden
            ganderson Gary Anderson
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.