Issues re-installing Pyramid on Linux

If a Pyramid installation fails, you may encounter an error when attempting to reinstall Pyramid, even after running the uninstaller.

One possible error is:

Error reading INI File /home/admin/Pyramid/config.ini

This can occur when configuration files or service registrations from a previous installation remain on the Linux server.

The installation path shown in the error message is an example. The actual path will depend on the directory used during installation.

Example of the installer error. The screenshot is illustrative; the displayed installer version is not a verified build number.

1. Check for Remaining Pyramid Configuration Files

If the installation failed and Pyramid has already been uninstalled, check whether the following configuration file remains:

/etc/pareg.ini

You can check whether the file exists by running:

sudo ls -l /etc/pareg.ini

This file may contain configuration information pointing to a previous Pyramid installation directory.

If it belongs to the failed installation and is no longer required, back it up before removing it.

sudo cp -p /etc/pareg.ini /etc/pareg.ini.bak

Then remove the obsolete file:

sudo rm /etc/pareg.ini

Important: Only remove this file after verifying that it belongs to the installation being cleaned up. Do not remove configuration files belonging to an active Pyramid deployment.

2. Check for Remaining Pyramid Services

Pyramid creates Linux services to manage its application components.

Older Pyramid installations used service scripts under /etc/init.d.

More recent Linux installations can use systemd to manage these services.

Before reinstalling Pyramid, check for obsolete service registrations left behind by the previous installation.

Current Pyramid Service Names

Depending on the Pyramid version, installed components, and deployment configuration, the following services may be present:

• pyramidAgent - Pyramid Agent
• pyramidFs - File System service
• pyramidRTE - Runtime Engine
• pyramidRTR - Router
• pyramidTE - Task Engine
• pyramidWeb - Web Server
• pyramidIMDB - In-Memory Database
• pyramidNLP - Natural Language Processing
• pyramidSOLVE - Solve Engine
• pyramidAI - AI service
• pyramidDNC - .NET Connector, where installed
• pyramidPG - Older bundled PostgreSQL service, where applicable

Note: Not every service will be installed in every environment.

The pyramidPG service is associated with installations using Pyramid's older bundled PostgreSQL repository. Environments using separately installed PostgreSQL will have their own PostgreSQL service, managed independently of Pyramid.

For more information, see: The Pyramid Services in Linux .

3. Check for Older Init.d Service Scripts

On installations using the older Linux service scripts, check the following directory:

/etc/init.d

To list any Pyramid-related service scripts, run:

ls -l /etc/init.d/pyramid*

You may find some of the service names listed above, depending on the version previously installed.

If Pyramid was completely uninstalled and these scripts are confirmed to be remnants of the failed installation, back them up before removing them.

For example, to back up an obsolete Task Engine service script:

sudo cp -p /etc/init.d/pyramidTE /etc/init.d/pyramidTE.bak

Once confirmed to be obsolete, the original script can be removed:

sudo rm /etc/init.d/pyramidTE

Repeat this procedure only for obsolete scripts associated with the failed installation.

Warning: Do not remove the entire /etc/init.d directory or automatically delete every Pyramid service script. Some scripts may still be required by an existing installation.

4. Check for Systemd Services

On Linux systems using systemd, Pyramid services may be registered as systemd units rather than traditional init.d scripts.

To list installed Pyramid service units, run:

systemctl list-unit-files 'pyramid*'

To list currently loaded Pyramid service units, including inactive services, run:

systemctl list-units --all 'pyramid*'

To inspect a particular service, for example the Task Engine, run:

sudo systemctl status pyramidTE

You can also inspect its unit definition:

systemctl cat pyramidTE

If service registrations remain from a failed installation, check whether they reference an installation directory that no longer exists.

Before removing any systemd unit, confirm its location, ownership, and whether it is still required.

If obsolete service registrations need to be removed, follow the appropriate systemd cleanup procedure for the Linux distribution.

After removing obsolete systemd unit files, reload the systemd manager configuration:

sudo systemctl daemon-reload

Important: Do not remove active Pyramid service units or disable services belonging to another working Pyramid installation.

5. Check the Previous Installation Directory

If the installer reports that it cannot read config.ini, verify the installation directory referenced by the error.

For example:

/home/admin/Pyramid/config.ini

Or, for an installation under the commonly used Linux installation directory:

/opt/pyramid/config.ini

Check whether the directory and configuration file exist and whether the installation account has the required permissions.

If the path points to an installation that has already been removed, the remaining registration or configuration may need to be cleaned up.

Warning: Do not delete the entire Pyramid installation or repository data directory without confirming that all required data, configuration, and database backups have been taken.

6. Run the Installation Again

After removing any confirmed obsolete configuration files and service registrations:

1. Verify that the previous Pyramid installation has been completely uninstalled.
2. Confirm that any required repository and data backups have been saved.
3. Ensure that obsolete service registrations no longer reference the previous installation.
4. Verify that the installation directories and permissions are correct.
5. Run the Pyramid installer again using the appropriate permissions.

If the installation fails again, collect the installer logs and review the reported error.

On Linux, installer logs may be located in the temporary directory:

/tmp

Include the installer logs and the exact error message when opening a ticket with Pyramid Support.

For additional installation troubleshooting recommendations, see: Pyramid Installation Tips .

Additional Notes

This article describes troubleshooting steps for installations that failed or were incompletely removed.

Service names and registration methods may differ depending on the Pyramid version, Linux distribution, and deployment configuration.

If the server is part of a distributed Pyramid deployment, verify the affected node and services before making any changes.