Can't open PureMessage Manage Quarantine

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

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