Can't open PureMessage Manage Quarantine

Hello,

This error would point to a possible connectivity or process error with accessing the PostgreSQL database.  The host in which you are accessing is that the same host that the database is running on?  If not, verify that the database is running and is allowing connections from the host/ip you are accessing the administrative interface.

Thanks in advance Jason for the respond,

Yes the database is on the same machine. I checked the database status, it is stopped with below error:

$ ./pmx-database status

/libexec/ld-elf.so.1: Shared object "libpq.so.5" not found, required by "pg_ctl"PostgreSQL database is not running.

Tried to search libpq.so.5, it looks there:

pmx# find /opt/pmx -name "libpq.so.5"

/opt/pmx/var/snapshot/Initial_Install/data/lib/libpq.so.5

/opt/pmx/var/snapshot/Initial_Install/data/postgres-8.3.3/lib/libpq.so.5

/opt/pmx/lib/libpq.so.5/opt/pmx/postgres-8.3.3/lib/libpq.so.5

Hi,

That error is usually when you execute the command without loading the PMX user enviornment.  Make sure that you "su - pmx" before running "pmx-database start".

-Jason

We have the same issue ...

Puremessage is working, but we can't access quarantine (we get the same error as stated in the first post)

ans the PostgreSQL service is 'stopped' in the dashboard (we can't make it 'running' although we sent 'start' signal to the service.

Any help ?

we get this error when puremessage is starting, or when we try to manually start the database ..

/opt/pmx/postgres/bin/pg_ctl: error while loading shared libraries: libpq.so.5: cannot open shared object file: No such file or directory
/opt/pmx/postgres/bin/pg_ctl: error while loading shared libraries: libpq.so.5: cannot open shared object file: No such file or directory

Can you tell me if any recent changes or system failures occured when you noticed that error.  When you mentioned you started manually, what exact command did you try?

There are some things you can try to be sure that perhaps the system is still utilizing resources. As the root user try this command.

# ipcs

Your output shoud look like the following if PostgreSQL is successfully running.  The format may look slightly different depending on your OS.

------ Shared Memory Segments --------
key        shmid      owner      perms      bytes      nattch     status
0x00000000 327680     root      600        393216     2          dest
0x0052e2c1 1015809   pmx       600        117211136  4
0x00000000 360450     root      600        393216     2          dest
0x00000000 393219     root      600        393216     2          dest
0x00000000 425988     root      600        393216     2          dest
0x00000000 458757     root      600        393216     2          dest
0x00000000 491526     root      600        393216     2          dest
0x00000000 524295     root      600        393216     2          dest
0x00000000 557064     root      600        393216     2          dest
0x00000000 589833     root      600        393216     2          dest

------ Semaphore Arrays --------
key        semid      owner      perms      nsems
0x0052e2c1 6488064    pmx       600        17
0x0052e2c2 6520833    pmx       600        17
0x0052e2c3 6553602    pmx       600        17
0x0052e2c4 6586371    pmx       600        17
0x0052e2c5 6619140    pmx       600        17
0x0052e2c6 6651909    pmx       600        17
0x0052e2c7 6684678    pmx       600        17

------ Message Queues --------
key        msqid      owner      perms      used-bytes   messages

If no postmaster process or postgres user is running, then you have left over processes in memory.  You will need to clear those before attempting to start up the DB.  To clear the above you will need to use the command "ipcrm", there are 2 parameter options "-m"  for shared memory, and "-s" for shared semaphores.  ie.

# ipcrm -m 1015809   

# ipcrm -s 6684678   

Only clear the ones that are for the user PMX. Once no more processes are shown, you can attempt to start the db with pmx-database as the pmx user, or you can manually attempt to start an instance as a test using the following syntax.

pmx@ $ /opt/pmx/postgres/bin/pg_ctl start -D /opt/pmx/postgres/var/data

-Jason

we noticed the error a couple of days ago .

We run

pmx-database start

as pmx user

the same error was shown when we restarted Puremessage.

we get this with icps

------ Shared Memory Segments --------
key        shmid      owner      perms      bytes      nattch     status
0x74010176 1572864    root      600        4          0
0x7401014c 2293761    root      600        4          0
0x00000000 2654210    root      644        80         2
0x7401014b 2260995    root      600        4          0
0x740101af 688132     root      600        4          0
0x00000000 2686981    root      644        16384      2
0x00000000 2719750    root      644        280        2
0x00000000 2752519    gdm       600        393216     2          dest

------ Semaphore Arrays --------
key        semid      owner      perms      nsems
0x000000a7 0          root      600        1
0x00000000 32769      nobody    600        1
0x00000000 262146     pmx       600        1
0x00000000 327683     pmx       600        1
0x00000000 360452     pmx       600        1
0x00000000 393221     apache    600        1
0x00000000 425990     apache    600        1

------ Message Queues --------
key        msqid      owner      perms      used-bytes   messages

PostgreSQL is not running - at least this is what we see on the web interface dashboard ..

Your output looks fine,  Can you provide the output of these two commands.

$ env

and

$ ldd /opt/pmx/postgres/bin/psql

I suspect that the LD_LIBRARY_PATH is not defined or is missing the LD_LIBRARY_PATH entry for /opt/pmx/lib.  I was able to reproduce the error after unsetting the LD_LIBRARY_PATH variable under the PMX user.

-Jason

$ env

results to :

HOSTNAME=mail.xxxxx.xx
TERM=xterm
SHELL=/bin/bash
HISTSIZE=1000
TMPDIR=/var/tmp
NLS_LANG=AMERICAN_AMERICA.EL8ISO8859P7
SSH_CLIENT=1.0.0.97 52224 22
SSH_TTY=/dev/pts/3
USER=root
LS_COLORS=no=00:fi=00:di=00;34:ln=00;36:pi=40;33:so=00;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=00;32:*.cmd=00;32:*.exe=00;32:*.com=00;32:*.btm=00;32:*.bat=00;32:*.sh=00;32:*.csh=00;32:*.tar=00;31:*.tgz=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.zip=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.bz=00;31:*.tz=00;31:*.rpm=00;31:*.cpio=00;31:*.jpg=00;35:*.gif=00;35:*.bmp=00;35:*.xbm=00;35:*.xpm=00;35:*.png=00;35:*.tif=00;35:
LD_LIBRARY_PATH=/opt/oracle/oraclehome/lib
ORACLE_SID=
ORACLE_BASE=/opt/oracle
TNS_ADMIN=/opt/oracle/oraclehome/network/admin
MAIL=/var/spool/mail/root
PATH=/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/opt/oracle/oraclehome/bin:/opt/oracle/oraclehome/lib:/root/bin
INPUTRC=/etc/inputrc
PWD=/root
LANG=en_US.UTF-8
ORACLE_TERM=xterm
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
SHLVL=1
HOME=/root
LOGNAME=root
CVS_RSH=ssh
CLASSPATH=/opt/oracle/oraclehome/JRE:/opt/oracle/oraclehome/jlib:/opt/oracle/oraclehome/rdbms/jlib
SSH_CONNECTION=1.0.0.97 52224 1.0.0.250 22
LESSOPEN=|/usr/bin/lesspipe.sh %s
ORACLE_HOME=/opt/oracle/oraclehome
G_BROKEN_FILENAMES=1
_=/bin/env

$ ldd /opt/pmx/postgres/bin/psql

results to

        linux-gate.so.1 =>  (0xffffe000)
        libpq.so.5 => not found
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x006a4000)
        libdl.so.2 => /lib/libdl.so.2 (0xf7eee000)
        libm.so.6 => /lib/libm.so.6 (0xf7ec5000)
        libc.so.6 => /lib/libc.so.6 (0x00549000)
        /lib/ld-linux.so.2 (0x0052a000)

Hi dcstech,

I think we might need the same output, but as the pmx user.

The error you're getting indicates libpq.so.5 isn't in the library path.  It won't be for root, because postgres should be started as pmx.

So as pmx user, you should see an environment variable like this:

LD_LIBRARY_PATH=/opt/pmx/lib/

Note, if you've recently upgraded to pmx6, then you would need to do this as the pmx6 user, and the libary path would be /opt/pmx6/lib/.

Thanks,

Tom.