TCPcentral reporting on Solaris - more info

["Steve Williams" <S.Williams@ukerna.ac.uk>]

Hi All

Further to the last mail about Solaris TCP Central reporting.

It seems that the reason the central server closes the tcp reporting
connection from its clients is that it is not seeing the first data line
sent from the client beacons send_tcp_report - i.e the authentication
line. The only beacon that reports as being OK, i.e. the central beacon
received the correct first authentication line is the one from itself:

$check (auth line) 	= chilton.beacon.ja.net|233.3.18.2|10002|1.1
first tcp line		= chilton.beacon.ja.net|233.3.18.2|10002|1.1

all other remote beacon clients come in as (anonymaised data for
privacy)

Bad:

$check (auth line) 	= chilton.beacon.ja.net|233.3.18.2|10002|1.1
first tcp line 		=
1617360507|beacon.xxx.net.uk|xxx|xxxx.70|solaris|5.008005|XXXXX|xxxxx|AB
34 3QY|-1|11189444.984|120|-1|-1|-1|-1

So the central server receive_tcp_reports() sub seems to be dropping the
first incoming line from the TCP report from remote beacons. Snooping
the link confirms that the clients are sending the report correctly -
and watching the push process within receive_tcp_reports() confirms that
the rest of the data is available to the script - but the first line is
just missing.

Any thoughts always appreciated...

Cheers

Steve