Fujitsu Logo
ENQUIRE

    Knowledge articles -Installation/Setup

    icon-kb-article-instsetup-color-simple

    I received the error message FATAL: Could not access directory for core file "/var/tmp/xxxxx/yyyyy/core": No such file or directory when starting FUJITSU Enterprise Postgres via WebAdmin.KB8001

    This error occurs when the core files cannot be found in the /var/tmp directory (the default location for FUJITSU Enterprise Postgres core files set up by WebAdmin).

    This can happen because, by default, Linux deletes from /var/tmp any content that has not been accessed for 30 days or more.

    The directory to output core files is specified by the core_directory parameter in postgresql.conf. When you create an instance in WebAdmin, /var/tmp/xxxxx/yyyyy/core is set by default.

    Resolution

    Do one of the following:

    • Specify a directory other than /var/tmp to output core files, then restart FUJITSU Enterprise Postgres.
    • Modify the Linux OS environment so that contents of /var/tmp are not automatically deleted after 30 days.

    Modifying the Linux default behavior

    You can either remove the tmpwatch package (which is responsible for deleting content from /tmp and /var/tmp) or you disable the cron entry.

    Please note that in some cases, you may not be able to remove the tmpwatch package, because of its dependencies, so you may want to disable the cron entry instead.

    Removing the tmpwatch package

    Execute one of the commands below:

    # rpm -e tmpwatch

    or

    # yum remove tmpwatch

    Disable the cron entry

    Execute one of the commands below:

    # mv /etc/cron.daily/tmpwatch /other/location/tmpwatch.bkp

    or

    # rm /etc/cron.daily/tmpwatch

    For details, refer to FUJITSU Enterprise Postgres 13 SP1 Installation and Setup Guide for Server > Chapter 4 - Setup > 4.2 - Preparations for Setup > 4.2.2 - Preparing Directories for Resource Placement.

    Applicable to

    Product: FUJITSU Enterprise Postgres Standard Edition, FUJITSU Enterprise Postgres Advanced Edition

    Architecture: X86, S390x

    Operating System: Windows, Linux

    Versions: from 9.4

    How do I configure an initialized database instance (using initdb) so that a client can connect from a different machine?KB8002

    ANSWER

    This answer is based on the following environment and configuration:

    • OS: RHEL 7
    • Instance port number: 27500
    • Client IP address: 192.168.93.10

    Follow the steps below:

    1. Add the entries below to postgresql.conf (* means listen on all adapters for a connection):
      listen_addresses = *
      port = 27500
    2. Register and reload the ports you want to connect to with firewall-cmd.
      1. Register the port.
        firewall-cmd-zone = public-add-port = 27500/tcp-permanent
      2. Reload the port.
        firewall-cmd-reload
    3. Create an entry in pg_hba.conf (host-based configuration file) that matches the client machine that you want to connect from.
      In the example below all machines on the 192.168.93.x subnet will match and use the md5 authentication method.
      host all all 192.168.93.0/24 md5
    4. Restart Postgres for the setting to take effect.
      $pg_ctl restart -D instance_destination_directory
    5. If the user's password is entered correctly, other hosts can connect.

    For details, refer to FUJITSU Enterprise Postgres 13 SP1 Installation and Setup Guide for Server > Chapter 4 - Setup > 4.4 - Configuring Remote Connections > 4.4.2 - When an Instance was Created with the initdb Command.

    Applicable to

    Product: FUJITSU Enterprise Postgres Standard Edition, FUJITSU Enterprise Postgres Advanced Edition

    Architecture: X86, S390x

    Operating System: Linux

    Versions: from 9.4

    How do I configure FUJITSU Enterprise Postgres to use the pg_stat_statements extension?KB8003

    The pg_stat_statements library is pre-installed (along with other modules) in the contrib folder of the installation folder, so no additional libraries are required to be installed.

    Follow the steps below to configure FUJITSU Enterprise Postgres to use pg_stat_statements:

    1. Open postgresql.conf, and edit the shared_preload_libraries setting so that pg_stat_statements is the first entry in the list (if other libraries are specified, separate them with commas)
      shared_preload_libraries = 'pg_stat_statements'
    2. Restart the instance.
      pg_ctl restart -D instance_destination_directory
    3. Connect to the database and execute the CREATE EXTENSION command, specifying pg_stat_statements as the parameter.
      This will capture metrics for that database which can be viewed by querying the pg_stat_statements view.
      psql -d postgres -c "CREATE EXTENSION pg_stat_statements"

    Applicable to

    Product: FUJITSU Enterprise Postgres Standard Edition, FUJITSU Enterprise Postgres Advanced Edition

    Architecture: X86, S390x

    Operating System: Linux

    Versions: from 9.4

    Read our latest blogs

    Read our most recent articles regarding all aspects of PostgreSQL and FUJITSU Enterprise Postgres.