Messaging Server 6.3 - Job_controller Will Not Start (Doc ID 1371353.1)

Last updated on MARCH 29, 2013

Applies to:

Oracle Communications Messaging Server - Version 6.3 and later
Information in this document applies to any platform.
Add ***Checked for relevance on 29-Mar-2013***

Symptoms

Messaging Server 6.3 was patched from version 6.3-11.01 to version 6.3-15.01 (installed patch 120230-44 for Linux ) .

After the patch was applied, the job_controller would not start.  The "stop-msg" and "start-msg" commands were performed with the following results:

Connecting to watcher ...
shutting down all servers...
Stopping snmp server 4539 ............................................................... timeout
ERROR: Cannot stop server snmp with SIGTERM, now retrying with SIGKILL
Stopping snmp server 4539 .... done
job_controller server is not running
Stopping dispatcher server 18719 ... done
Stopping sched server 18717 ... done
Stopping http server 18712 ... done
Stopping pop server 18708 ... done
Stopping imap server 18706 ... done
Stopping store server 18702 .... done
Stopping ens server 18701 ... done
stopping watcher process 4493 .... done
-bash-3.00# start-msg
Connecting to watcher ...
Launching watcher ... 19764
Starting ens server ... 19765
Starting store server .... 19766
Checking store server status ... ready
Starting imap server .... 19770
Starting pop server .... 19772
Starting http server .... 19776
Starting sched server ... 19781
Starting dispatcher server .... 19783
Starting job_controller server .... failed
Starting snmp server .... 19807



The watcher log shows:

Watched 'job_controller' process 19798 exited abnormally
[09/26/11 00:55:14] Failure occurred. Please restart the following servers: job_controller
[09/26/11 00:55:14] Autorestart is not enabled. To enable autorestart, set local.autorestart to yes.


As a temporary workaround, the reprocess queue was moved off to another area on disk and subsequently, after this was done, the job_controller started successfully.

Changes

Messaging Server 6.3 patch upgrade was performed, but this was not the trigger of the issue.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms