Administrator's and User's Guide for SFM HP-UX 11i v3 March 2012

Table 25 Troubleshooting EVWEB (continued)
SolutionCauseProblem
IPProviderModule OK
SFMProviderModule Degraded
If the status of SFMProviderModule is Degraded as displayed in
the given output, SFMProviderModule is not running.
To enable SFMProviderModule, complete the following steps:
1. Enter the following command at the HP-UX prompt to disable
SFMProviderModule:
# cimprovider –d –m SFMProviderModule
2. Enter the following command at the HP-UX prompt to enable
SFMProviderModule:
# cimprovider –e –m SFMProviderModule
Alternatively, you can run the following script at the HP-UX
prompt to start SFMProviderModule:
# sh /opt/sfm/bin/restart_sfm.sh
NOTE: The script restarts SFM only if SFMProviderModule
is in Degraded state.
3. Enter the following command at the HP-UX prompt to check
if the SFMProviderModule is running:
# cimprovider -ls
If the status of SFMProviderModule is OK, SFMProviderModule
is running properly. Otherwise, repeat steps 1 to 3.
If you still encounter the same issue, check for error logs in the
/var/opt/sfm/log/sfm.log file. For further assistance,
contact the HP support center.
To improve performance of the Event Viewer, set the locale to
English.
The locale on your
system is set to a
The response time for a
command used to view
language other than
English.
indications from the Event
Archive is long.
You can safely ignore this message.When the startup script,
/sbin/rc2.d/S550psbdb
What is "su: + tty??
root-sfmdb" only once
logged in syslog.log?
(IA) or
/sbin/rc2.d/S550sfmdb
(PA), runs at the system
start-up, the su command
is issued in the script to
launch a postmaster
process as the sfmdb
user. "+" in the message
indicates the su attempt
is successful (if "-" is
present instead of "+", it
indicates the attempt
fails).
This message is
harmless, it does not
indicate a problem with
the installation
To disable EMS logging events to syslog, complete the following
steps:
The syslog functionality
is available from SFM
Both EMS and SFM log
the same symptom in the
syslog.
Troubleshooting EVWEB 91