What Syslog Facility And Priority Does the Dispatcher Process Use During Startup Failures? (Doc ID 2095494.1)

Last updated on JANUARY 15, 2016

Applies to:

Oracle Communications Messaging Server - Version 7.0.0 to 7.0.5 [Release 7.0.0]
Information in this document applies to any platform.

Symptoms

New install of MS 7u5, unable to start Dispatcher due to:

1. No imta_tailor file on the new systems (which running "imsimta cnbuild" doesn't seem to complain about or error out)
2. New install does not do a "imsimta cnbuild", so was running an uncompiled version and didn't realize it
3. Dispatcher, when running uncompiled, doesn't like not having an imta_tailor file
4. Product is running under SMF, so it took forever to hunt this problem down, requiring root access in order to truss the 'startd' process so we could see why Dispatcher was not starting up

We do not have syslog configured for anything in Messaging Server.
In fact, on this system, we don't have any logfile.* settings in configutil.

Sample truss:

3531/1: 4.5394 0.0001 putmsg(4, 0xFFFF80FFBFFFCCF0, 0xFFFF80FFBFFFCD00, 0) = 0
3531/1: ctl: maxlen=24 len=24 buf=0xFFFF80FFBFFFC3A0: "\0\0\0\0\0\010\0"..
3531/1: \0\0\0\0\0\010\0\0\0\0\0\0\0\0\0\0\0\0\0\r\0\0\0
3531/1: dat: maxlen=1280 len=154 buf=0xFFFF80FFBFFFC3C0: " J a n 6 1"..
3531/1: J a n 6 1 4 : 3 3 : 3 4 d i s p a t c h e r [ 3 5 3 1 ]
3531/1: : [ I D 9 2 4 1 0 0 F A C I L I T Y _ A N D _ P R I O R I
3531/1: T Y ] % I M T A - W - U n a b l e t o o p e n t h e t
3531/1: a i l o r f i l e / o p t / s u n / c o m m s / m e s s a g
3531/1: i n g 6 4 / c o n f i g / i m t a _ t a i l o r\n\0

The above info should have gone to /var/adm/messages, but it didn't.

SMF log shows:

[ Jan 6 14:24:53 Executing start method ("/opt/sun/comms/messaging64/bin/start-msg mta"). ]
Connecting to watcher ...
Starting dispatcher server ............................................................... timeout
Starting job_controller server ............................................................... timeout
[ Jan 6 14:26:53 Method "start" exited with status 70. ]

 

Changes

Brand new install of MS version 7u5

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