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).

[RobertFulton]

Every case can be different. And without looking at an individual circumstance it is difficult to say what the best course of action is. That being said, regardless of the course of action taken, data preservation is always the highest priority.

[Anonymous]

Hello All,

I am facing an issue after upgrading the RSA ESA and VLC. After upgrading the 10.3 ESA and VLC to 10.4, I am unable to make these appliances up successfully. After upgrading these appliances, they are not getting started now.

Please refer to the the below mentioned screenshot for your reference.

This appliance is not coming up from more than 4 days. I have restarted the same so many times, but facing the same challenge to get it up back.

Is some one facing the same challenge after upgradation?

Kindly suggest.

[Anonymous]

@maarten_claes

Have you tried just starting the services?  I would suggest puppet first, then tokumx then rabbitmq and last mcollective.  I did have issues initially with mcollective and rabbitmq but started them manually to get the initial config done and rebooted.  After the reboot everything came up correctly. 

[MaartenClaes]

Hey Sean,

Yes, i've tried to manually start the services and now again in the order you specified.. There is a warning however when I start the tokumx service.

[root@sa-as ~]# /etc/init.d/tokumx start

Error disabling transparent_hugepages, are you running in a linux container?

If the server fails to start, check that transparent hugepages are disabled.

Starting tokumx:                                           [  OK  ]

Services seem to come up but the mco ping test still fails and i don't think

[root@sa-as ~]# mco ping

^C

The ping application failed to run, use -v for full error backtrace details: Could not connect to ActiveMQ Server:

[Anonymous]

Give it a reboot.  My ping also failed until a reboot. 

[Anonymous]

Hi sean,

These service:-

1. rabbitmq

2. Mcollective

3.tokumx

4. puppetmaster

should be running on all appliances or only SA server, i got all the service running on SA server but on Concentrator tokumx and puppetmaster not running. even MCO ping is also fails.

kindly suggest.

Thanks

[Anonymous]

while puppet service is running on concentrator or decoder. but mco ping failed

[Anonymous]

Did you make sure to "Enable" each appliance?

[Anonymous]

hey i am geeting attached error, when i run puupet agent -t

[RobertFulton]

that log is coming from your sa head unit? Or your decoder/concentrator?