| Asset ID: |
1-72-1939848.1 |
| Update Date: | 2016-11-04 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1939848.1
:
"View Provisioning DataBase Application (PDBA) Status" via the Graphical User Interface (GUI) is Showing "Database Daemon is not Running" for remote PDBA site
| Related Items |
- Oracle Communications EAGLE (Software)
|
| Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec OS EPAP ECAP
|
In this Document
Created from <SR 3-9797620811>
Applies to:
Oracle Communications EAGLE (Software) - Version EPAP 13.0 and later
Information in this document applies to any platform.
Symptoms
On Standby PDB site, the "View PDBA Status" database daemon via the GUI is reported as "Database daemon is not running" for Active PDB site.
Restarting GUI process does not fix the condition.
Changes
Hardware migration from T1000 to E5-APP-B card server type.
Cause
Remote site ssh host key was not updated after the migration and it is rejected.
[epapdev@mpsa-tek ~]$ /usr/bin/ssh -l epapdev mpsa-tek "mysqladmin -uroot -pXXXXXX -S /var/TKLC/epap/db/pdb/mysql.sock ping"
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for mpsa-tek has changed,
and the key for the according IP address N.N.N.N
is unchanged. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
Offending key for IP in /home/epapall/.ssh/known_hosts:13
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx.
Please contact your system administrator.
Add correct host key in /home/epapall/.ssh/known_hosts to get rid of this message.
Offending key in /home/epapall/.ssh/known_hosts:9
RSA host key for mpsa-nant-tek has changed and you have requested strict checking.
Host key verification failed.
Solution
1. Verify which server is reporting incorrect status when "viewing PDBA Status" on the EAGLE Provisioning Application (EPAP) GUI.
2. Exchange the ssh host keys on affected server:
- If Active EPAP A server: /usr/TKLC/plat/bin/keyexchange epapdev@"IP address of Standby PDB EPAP A server"
- If Standby EPAP A server: /usr/TKLC/plat/bin/keyexchange epapdev@"IP address of Active PDB EPAP A server"
3. View the PDBA status on the GUI to see the daemon status is correct: ''Database Daemon is running''.
Attachments
This solution has no attachment
