Msprobe Does Not Check Mshttpd When Role.http.enable Is Set To 0 And Role.http.enablesslport Is Set To 1

(Doc ID 2281020.1)

Last updated on JUNE 28, 2017

Applies to:

Oracle Communications Messaging Server - Version 8.0.1 and later
Information in this document applies to any platform.


Noticing that msprobe is not testing mshttpd when role.http.enable is set to 0 and role.http.enablesslport is set to 1. Is this expected?

role.http.enable = 0
role.http.enablesslport = 1
role.http.smtpauthuser = admin
role.http.smtphost =
role.http.smtptls = 1
role.http.sslport = 8991
role.http.sslusessl = 1

Here is the log of what msprobe is doing:

But interactively and specifically specifying "http", msprobe does test and show that http is disabled:

/opt/sun/comms/messaging64/lib/msprobe -d -n http
server version: Oracle Communications Messaging Server 8.1 patch 2
autorestart: disabled

connecting to watcher...
enpd 27258 0
mshttpd 27259 0
imsched 27261 0
dispatcher 27269 0
job_controller 27275 0
msprobe 29486 0
http is disabled
/opt/sun/comms/messaging64: Total space = 898065744 KB, available = 896571344 KB (99%)

Msprobe should be testing mshttpd, because not monitoring services is a potentially serious issue that could allow prolonged service failures.


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