Healthcheck error for clean v2.0.0-rc2 install

I’m attempting to install v2.0.0-rc2 according to instructions available here (clean install on Ubuntu 16.04):

With the following configuration file:

return [

/**
 * DEFAULT APP CONFIGURATION
 *
 * All the information in this section must be provided in order for passbolt to work
 * This configuration overrides the CakePHP defaults locating in app.php
 * Do not edit app.php as it may break your upgrade process
 */
'App' => [
    // A base URL to use for absolute links.
    // The url where the passbolt instance will be reachable to your end users.
    // This information is need to render images in emails for example
    'fullBaseUrl' => 'https://passbolt.test.local',
],

// Database configuration.
'Datasources' => [
    'default' => [
        'host' => 'localhost',
        'username' => 'passbolt',
        'password' => 'xxxxx',
        'database' => 'passbolt',
    ],
],

// Email configuration.
'EmailTransport' => [
    'default' => [
        'host' => 'email.test.local',
        'port' => 25,
        'username' => null,
        'password' => null,
        // Is this a secure connection? true if yes, null if no.
        'tls' => null,
        //'timeout' => 30,
        //'client' => null,
        'url' => 'https://passbolt.test.local',
    ],
],
'Email' => [
    'default' => [
        // Defines the default name and email of the sender of the emails.
        'from' => ['infra@test.local' => 'Test Passbolt'],
        //'charset' => 'utf-8',
        //'headerCharset' => 'utf-8',
    ],
],

/**
 * DEFAULT PASSBOLT CONFIGURATION
 *
 * This is the default configuration.
 * It enforces the use of ssl, and does not provide a default OpenPGP key.
 * If your objective is to try passbolt quickly for evaluation purpose, and security is not important
 * you can use the demo config example provided in the next section below.
 */
'passbolt' => [
    // GPG Configuration.
    // The keyring must to be owned and accessible by the webserver user.
    // Example: www-data user on Debian
    'gpg' => [
        // Tell GPG where to find the keyring.
        // If putenv is set to false, gnupg will use the default path ~/.gnupg.
        // For example :
        // - Apache on Centos it would be in '/usr/share/httpd/.gnupg'
        // - Apache on Debian it would be in '/var/www/.gnupg'
        // - Nginx on Centos it would be in '/var/lib/nginx/.gnupg'
        // - etc.
        'keyring' => '/var/www/.gnupg',
        //
        // Replace GNUPGHOME with above value even if it is set.
        'putenv' => true,

        // Main server key.
        'serverKey' => [
            // Server private key fingerprint.
            'fingerprint' => 'A7BB9CF7470F4518A6FE3815ECABD0AD803A509D',
            'public' => '/var/www/gpg/private.key',
            'private' => '/var/www/gpg/public.key',
        ],
    ],
],

];

When trying to perform a healthcheck a segmentation fault is raised:

ansible@cri-global-pb-01:/var/www/passbolt$ sudo -u www-data ./bin/cake passbolt healthcheck
Warning Error: array_keys() expects parameter 1 to be array, null given in [/var/www/passbolt/plugins/PassboltTestData/src/Shell/Task/DataTask.php, line 41]

 ____                  __          ____
/ __ \____  _____ ____/ /_  ____  / / /_

/ // / __ `/ / / __ / __ / / _/
/ / // ( |
) /
/ / /
/ / / /
/
/ _
,
/
//.__/__//_/

Open source password manager for teams

Healthcheck shell…Notice Error: Undefined variable: plaintext in [/var/www/passbolt/src/Utility/Healthchecks.php, line 424]

2018-04-04 17:54:30 Notice: Notice (8): Undefined variable: plaintext in [/var/www/passbolt/src/Utility/Healthchecks.php, line 424]

Segmentation fault

I have been unable to find a previous report or workaround

Checklist
[x] I have read intro post: About the Installation Issues category
[x] I have read the tutorials, help and searched for similar issues
[x] I provide relevant information about my server (component names and versions, etc.)
[x] I provide a copy of my logs and healthcheck
[x] I describe the steps I have taken to trouble shoot the problem
[x] I describe the steps on how to reproduce the issue

Hi @teddyphreak,

Thanks for the report.

We are able to reproduce the issue on unbuntu 16.04. The issue comes from the php extension gnupg provided by the official repo. We just tried to install the extension via pecl, and it solve the issue.

We proceed as following :
sudo apt-get remove php-gnupg
sudo apt-get install php-dev pear libpgpme11-dev
sudo pecl install gnupg

Ensure the extension is enabled for your cli and for your php-fpm (or whatever flavor you are using).

Let us know how it goes on your side.

Thank you, the provided workaround works as intended.

Cheers,
Ted

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.