aserver.sh script references the same CT_ROOT location, thereby using the same .pid file

Resolution

When the second AServer was created and the ctrust5 directory copied, the aserver.sh script was not modified to reflect the new CT_ROOT.

To correct this issue, edit the aserver.sh script and verify that the CT_ROOT variable corresponds to the correct location of this particular Authorization Server. Now the second instance will use the aserver.pid file in its own CT_ROOT location.