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]

@rajveer  Did you delete the nw-erlang file?  If not delete that file on your SA repo then run a #yum clean all then a yum check-update, then a yum update

@robertfulton @chandlerhall Hey Robert and Chandler.  I just wanted to let you guys know that I did the full upgrade to SA this weekend.  After running the upgrade on the headunit and sending the enable command, it fixed all errors.   

[RobertFulton]

@rajveer if what Sean said doesn't work then I would suggest opening a ticket with support at your earliest convenience

@Sean.Koniarz I am glad to hear that worked for you

[Anonymous]

Hubaa900,

if you are facing any challenges then you can update the same via offline method or thru online method.

By uploading the upgradepack or by running two or three simple commands on your log collector.

I have done the same, and it's get upgrade to 10.4 successfully and also to 10.4.1 as well.

[Anonymous]

Hi Robertfulton/Sean.Koniarz,

Thanks for the response,

now i stuck on the same issue that was faced by Chandlerhal.

if you have any solution please suggest.

thanks in advance.

[RobertFulton]

@rajveer

I would suggest putting in a support ticket for your problem.

[MaartenClaes]

Hey all

First time user here trying to upgrade SA from 10.3.2 to 10.4 (to avoid licensing bugs etc etc 🙂 )

What's the impact of not removing the nw-erlang file as described in the upgrade file?

My upgrade succeeded though but none of the new services that we have to check start correctly. I'm trying to assess if it's smarter to try and re-image the box or continue & involve support. It's a green field setup so no need to 'save the config'

Must say it's challenging, administering SA 🙂

[RobertFulton]

@maarten_claes

Which services aren't starting correctly? And how do they fail?

[MaartenClaes]

Here's an extract from the SSH sessions' output when the upgrade was finalized. I honestly don't know why these services fail to start. I dont know what all these services actually do or how they work together.

If you start them from the cmd line, they seem to start succesfully but the 'mco ping' still fails.

Alternatively, is there way to 'reset to factory defaults' for an appliance?

ql2500-firmware.noarch 0:7.03.00-1.el6_5                                     

  re-server.noarch 0:10.4.0.0.4693-5                                           

  rpm.x86_64 0:4.8.0-37.el6                                                    

  rpm-libs.x86_64 0:4.8.0-37.el6                                               

  rpm-python.x86_64 0:4.8.0-37.el6                                             

  rsaCAS.x86_64 0:1.0-52.el6                                                   

  rsaMalwareDeviceCoLo.x86_64 0:10.4.0.0.8286-5                                

  rsyslog.x86_64 0:5.8.10-8.el6                                                

  samba.x86_64 0:3.6.9-169.el6_5                                               

  samba-common.x86_64 0:3.6.9-169.el6_5                                        

  samba-winbind.x86_64 0:3.6.9-169.el6_5                                       

  samba-winbind-clients.x86_64 0:3.6.9-169.el6_5                               

  security-analytics-web-server.noarch 0:10.4.0.1.11709-5                      

  selinux-policy.noarch 0:3.7.19-231.el6_5.3                                   

  selinux-policy-targeted.noarch 0:3.7.19-231.el6_5.3                          

  sudo.x86_64 0:1.8.6p3-12.el6                                                 

  sysstat.x86_64 0:9.0.4-22.el6_5.1                                            

  sysvinit-tools.x86_64 0:2.87-5.dsf.el6                                       

  tg3.x86_64 0:3.129d-431.5.1                                                  

  tzdata.noarch 0:2014h-1.el6                                                  

  tzdata-java.noarch 0:2014h-1.el6                                             

  udev.x86_64 0:147-2.51.el6                                                   

  upstart.x86_64 0:0.6.5-13.el6_5.3                                            

  util-linux-ng.x86_64 0:2.17.2-12.14.el6_5                                    

  vsftpd.x86_64 0:2.2.2-12.el6_5.1                                             

  wget.x86_64 0:1.12-1.11.el6_5                                                

  xfsprogs.x86_64 0:3.1.1-14.el6                                               

  xorg-x11-drv-ati-firmware.noarch 0:7.1.0-3.el6                               

  yum.noarch 0:3.2.29-43.el6.centos                                            

  yum-plugin-fastestmirror.noarch 0:1.1.30-17.el6_5                            

  yum-utils.noarch 0:1.1.30-17.el6_5                                           

Complete!

[root@sa-as ~]# reboot

Broadcast message from root@sa-as

(/dev/pts/0) at 13:32 ...

The system is going down for reboot NOW!

[root@sa-as ~]# Connection to sa-as closed by remote host.

onnection to sa-as closed.

maarten@******:~$ ssh root@sa-asl-conas

ssh: connect to host sa-as port 22: No route to host

maarten@******:~$ ssh root@sa-as

root@sa-as's password:

Last login: Sat Oct 11 12:18:16 2014 from 192.168.196.2

[root@sa-as ~]# service rabbitmq-server status

Status of node 'rabbit@sa-as' ...

Error: unable to connect to node 'rabbit@sa-as': nodedown

DIAGNOSTICS

===========

attempted to contact: ['rabbit@sa-as']

rabbit@sa-as:

  * connected to epmd (port 4369) on sa-as

  * epmd reports: node 'rabbit' not running at all

                  no other nodes on sa-as

  * suggestion: start the node

current node details:

- node name: 'rabbitmqctl4137@sa-as'

- home dir: /var/lib/rabbitmq

- cookie hash: BLNzg0oU246ohrZa8ral5g==

[root@sa-as ~]# service mcollective status

mcollectived is stopped

[root@sa-as ~]# service tokumx status

tokumx is stopped

[root@sa-as ~]# service puppetmaster status

puppet dead but subsys locked

[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:

[root@sa-as ~]#

[RobertFulton]

It seems like something happened during the upgrade process. This being the case I don't think resetting to defaults will fix anything.

You have two options:

1) You can call support and put in a ticket to troubleshoot this issue further

2) You can re-image your appliance.

Since you say this is a "green fields" set up and assuming that you have no data you want to save, I wonder if it would be more time effective for you to just to re-image your appliance rather then submit a ticket. The .iso files you need to do this are located on download central.

If you do not want to re-image your appliance please submit a support ticket.

[Anonymous]

Is there any solution of this issue without re-imaging the appliance?

Sent from my iPhone