"CM Bad Login Attempt" Logged When Using F5 Load Balancer For Failover Testing (Doc ID 1316172.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 and later
Information in this document applies to any platform.
Checked for relevance on 12-Nov-2012.
Checked for relevance on 24-Jun-2014.

Symptoms

A user is testing failover scenario between two BRM servers. If the first server is down, the request is redirecting to the second server.

To achieve this, the F5 Load Balancer is continuously checking the health of the servers by telnet command. If it finds that the first server is down, it does the failover.

This causes the following error to be logged in the cm pinlog:

E Wed Jul 21 16:45:01 2010 hostname cm:18318 cm_login_pw001.c(21):146  1:hostname:cm:18187:-146143008:0:1279745074:0 bad 1st pcp_receive, err 50
E Wed Jul 21 16:45:01 2010 hostname cm:18318 cm_child.c(115):25641 1:hostname:cm:18187:-146143008:0:1279745074:0
   CM bad login attempt from ip_addr=138.xx.xxx.xx:61964, err=50(PIN_ERR_STREAM_EOF), field=0(0)

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