[cisco-voip] CUCM 7.0.1 DB error

[Ryan Ratliff]

Looks like DRF is trying to register itself to get notification of  
hostname changes.   Not sure what to make of the incorrect password  
though, that's a new one to me.

-Ryan

On Feb 8, 2009, at 10:51 AM, Wes Sisk wrote:

This sounds similar to something Ryan worked on recdently where DRS  
is not updated properly if server hostname is changed.  Was the  
servername changed?  I believe the workaround was to toggle backup on  
the affected server.

Otherwise verify forward and reverse DNS resolution from that  
server.  I could also see some reference to CSCsw88022.

/Wes

On Sunday, February 08, 2009 10:35:46 AM, Philip Walenta  
<pwalenta at wi.rr.com> wrote:
> Anyone ever seen this from RTMT?  I can't find any reference to it  
> on CCO.
>
>  At Sun Feb 08 08:53:36 CST 2009 on node cucm72; the following  
> SyslogSeverityMatchFound events generated:  SeverityMatch -  
> Critical Cisco Database Layer Monitor: Failed to connect to  
> datasource: [Informix][Informix ODBC Driver][Informix] 
> INFORMIXSERVER does not match either DBSERVERNAME or  
> DBSERVERALIASES.    SeverityMatch - Alert sudo:      drf : 1  
> incorrect password attempt ; TTY=console ; PWD=/ ; USER=root ;  
> COMMAND=/usr/local/platform/bin/comp_notification/registration.sh - 
> u drf -r register /usr/local/platform/bin/ 
> drf_notify_hostname_change.py
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090209/c2336d82/attachment.html>