dojabergen
ADSM.ORG Member
- Joined
- Nov 4, 2013
- Messages
- 35
- Reaction score
- 2
- Points
- 0
Hi,
We are running Admin Assistant to monitor our R3 backups. The version is 6.2.1.1 Build 4.5.9 (24.08.10). The application is running on an AIX server. We run the default Derby Apache DB that is included in the application.
The filesystem for the HISTORY logging went full.
Originally, it was in the /usr file system, but we created a separate filesystem for the logging, and updated the HISTORY PATH in the assist.cfg file. Now we are not able to start the Darby DB,:
nohup ./sdb.ksh start &
says:
>>> start
Security manager installed using the Basic server security policy:
Could not listen on port 1528 on host 0.0.0.0:
java.net.BindException: The socket name is already in use.
>>> stop
However, we can connect and login to the DB and run sect statements:
Select * from adminAssistant.SYSTEM;
and we get ouput.
But the sdb prosess is not running.
What to do to recover.
Thank you in advance.
We are running Admin Assistant to monitor our R3 backups. The version is 6.2.1.1 Build 4.5.9 (24.08.10). The application is running on an AIX server. We run the default Derby Apache DB that is included in the application.
The filesystem for the HISTORY logging went full.
Originally, it was in the /usr file system, but we created a separate filesystem for the logging, and updated the HISTORY PATH in the assist.cfg file. Now we are not able to start the Darby DB,:
nohup ./sdb.ksh start &
says:
>>> start
Security manager installed using the Basic server security policy:
Could not listen on port 1528 on host 0.0.0.0:
java.net.BindException: The socket name is already in use.
>>> stop
However, we can connect and login to the DB and run sect statements:
Select * from adminAssistant.SYSTEM;
and we get ouput.
But the sdb prosess is not running.
What to do to recover.
Thank you in advance.
