If you try to run a fresh ACS install in a machine with, let's say, 2 GB of RAM, you might see some errors like:
| Code Block |
|---|
|
Detected the process has disappeared without ever emitting the expected string! |
| Code Block |
|---|
|
Will continue waiting any ways...
Detected the process has disappeared without ever emitting the expected string!
Will continue waiting any ways...
Detected the process has disappeared without ever emitting the expected string!
Will continue waiting any ways...
Detected the process has disappeared without ever emitting the expected string!
Will continue waiting any ways...
Detected the process has disappeared without ever emitting the expected string! |
This means some ACS service was not able to start within the timeout limit. First of all you might want to increase the timeout limit to give your machine more time to complete the services initialization:
| Code Block |
|---|
|
> acsStop
> export ACS_STARTUP_TIMEOUT_MULTIPLIER=10
> acsStart |
If ACS still won't start after this change, is possible that the Notification Channel service is not able to start. In this case you will need to modify the /alma/<RELEASE>/ACSSW/config/svc.conf/defaultNotify.svc.conf configuration file:
| Code Block |
|---|
|
# replace
static Notify_Default_Event_Manager_Objects_Factory "-AllocateTaskPerProxy -SourceThreads 1 -DispatchingThreads 1 -ValidateClient -ValidateClientInterval 60"
# by
static Notify_Default_Event_Manager_Objects_Factory "-ValidateClient -ValidateClientInterval 60" |
This will reduce the memory need for the Notification Service and allow it to start normally.
