Problem after update to 10.4

[Anonymous]

Hello,

After update from 10.3.4 to 10.4 I receive some problem. My Log Collector not work. In first time I receive many like:

Sep 23 09:36:00 SA-LogDecoder nw[2196]: [AMQPClientBase] [failure] An error occurred creating an AMQP channel: a socket error occurred

Sep 23 09:36:00 SA-LogDecoder nw[2196]: [LogdecoderProcessor] [failure] [queue.odbc] [idle] Failed during getWork: a socket error occurred

I can see only logs collect via log decoder (protocol Syslog). Then I try find solution at forum and find action rekey (). I'm also reinstall nwlogcollector, rabbit-mq server. Now I can access to Log Collector (Service x.x.x.x host LogCollector is unreachable).

[Anonymous]

From decoder and concentrator and VLC

[RobertFulton]

It looks like puppet may be having trouble communicating with the SA Head Unit in some way. Has the SA Head Unit been upgraded to 10.4?

[Anonymous]

Also, does your /etc/hosts file have the proper information in it?  It should have *.*.*.* puppetmaster.local

[Anonymous]

Hi Sean,

we have 3 SA server one primary and two secondary 1 for logs and 1 for packet.

i have manually updated all the server using primary SA server and yes i enable all the device form here but that primary server is for both logs as well as packets. so we used secondary server to  manage all the log appliances and in secondary server i am not getting any enable option.

for all the log appliance i made secondary server as puppet-master and log appliances are puppet agent.

[Anonymous]

Hi Robertfulton,

Yes, this SA server is manually upgraded from a primary SA server.

[Anonymous]

@Sean, yes it have secondary SA IP as puppetmaster.local

[RobertFulton]

On the SA Head Unit, under administration -> services click on a few of your appliances and click edit. Take a look at the port numebrs. Are they 5000x or 5600x ?

[Anonymous]

@Robertfulton

yes, all the service using 5000x port

[RobertFulton]

On your services list in the SA GUI, take a few of them (as a test) click edit and check the SSL box. Let's see if that resolves your problem.

[RobertFulton]

@rajveer

Did that resolve your issue?