Controllerless Networks

Reply
Occasional Contributor II
Posts: 19
Registered: ‎05-14-2015

Airwave Amp Upgrade Failed error creating chain 'acct~i':File exists

So I been trying to for 2 days to upgrade Airwave Amp. Yesterday I was going from 8.2.2 to 8.2.3.1 but had to resolve some centos update issues, but that update borked the upgrade which turned into a fiasico. Long story short I reimaged the server with our initial Airwave setup using clonezilla this morning. That took me back to ver 8.0.7.

 

But then I had upgrade issues with 8.0.10:

/usr/bin/make -C src install
make[2]: Entering directory `/root/svn/mercury/src'
/usr/bin/make -f Makefile.perllib remove_old_rpms
make[3]: Entering directory `/root/svn/mercury/src'
error: Failed dependencies:
fontconfig-devel is needed by (installed) gd-devel-2.0.35-11.el6.x86_64
freetype-devel is needed by (installed) gd-devel-2.0.35-11.el6.x86_64
error: Failed dependencies:
krb5-devel is needed by (installed) openssl-devel-1.0.1e-30.el6.8.x86_64
error: Failed dependencies:
libpng-devel is needed by (installed) gd-devel-2.0.35-11.el6.x86_64
make[3]: Leaving directory `/root/svn/mercury/src'
/usr/bin/make -C /root/svn/mercury/src/x86_64/rpms/CentOS-6 install
make[3]: Entering directory `/root/svn/mercury/src/x86_64/rpms/CentOS-6'
error: open of ../node_js/npm/openssl-devel-1.0.1e-30.el6.11.x86_64.rpm failed: No such file or directory
make[3]: *** [security_patches] Error 1
make[3]: Leaving directory `/root/svn/mercury/src/x86_64/rpms/CentOS-6'
make[2]: *** [perllib] Error 2
make[2]: Leaving directory `/root/svn/mercury/src'
make[1]: *** [src_install] Error 2
make[1]: Leaving directory `/root/svn/mercury'
make: *** [upgrade] Error 2
make: Leaving directory `/root/svn/mercury'
Stopping Pound: [ OK ]
Stopping httpd: [ OK ]
tsdb-server: unrecognized servic

 

So then I read there was an rpm package version issue and that 8.0.11.1 should have resolved it. so I tried it and got this:

/bin/cp -f lib/conf/ld.so.conf /etc/ld.so.conf.d/airwave.conf
/sbin/ldconfig
/usr/bin/make -C src install
make[2]: Entering directory `/root/svn/mercury/src'
/usr/bin/make -f Makefile.perllib remove_old_rpms
make[3]: Entering directory `/root/svn/mercury/src'
error: Failed dependencies:
fontconfig-devel is needed by (installed) gd-devel-2.0.35-11.el6.x86_64
freetype-devel is needed by (installed) gd-devel-2.0.35-11.el6.x86_64
error: Failed dependencies:
krb5-devel is needed by (installed) openssl-devel-1.0.1e-30.el6.8.x86_64
error: Failed dependencies:
libpng-devel is needed by (installed) gd-devel-2.0.35-11.el6.x86_64
make[3]: Leaving directory `/root/svn/mercury/src'
/usr/bin/make -C /root/svn/mercury/src/x86_64/rpms/CentOS-6 install
make[3]: Entering directory `/root/svn/mercury/src/x86_64/rpms/CentOS-6'
error: open of ../node_js/npm/openssl-devel-1.0.1e-30.el6.11.x86_64.rpm failed: No such file or directory
make[3]: *** [security_patches] Error 1
make[3]: Leaving directory `/root/svn/mercury/src/x86_64/rpms/CentOS-6'
make[2]: *** [perllib] Error 2
make[2]: Leaving directory `/root/svn/mercury/src'
make[1]: *** [src_install] Error 2
make[1]: Leaving directory `/root/svn/mercury'
make: *** [upgrade] Error 2
make: Leaving directory `/root/svn/mercury'
Stopping httpd: [ OK ]
tsdb-server: unrecognized service

 

So I decided to run OS updates. 

First I did "yum upgrade yum rpm"

afterwards, I did: "yum update"

 

I rebooted at least 3 times today as yesterday one did not seem to be enough which start the whole fiasco with moving to 8.2.3.1.

 

So now I tried to go to 8.0.11.1 again. and got the following error:

/opt/airwave/bin/perl -MMercury::Scripts::ConfigureRedis -e 'Mercury::Scripts::ConfigureRedis->go'
/sbin/service redis condrestart
/opt/airwave/bin/perl -MMercury::Scripts::ConfigureFreeRadius -e 'Mercury::Scripts::ConfigureFreeRadius->go'
bin/conf_common_post_install
Shutting down system logger: [ OK ]
Starting system logger: [ OK ]
iptables: Setting chains to policy ACCEPT: filter nat [ OK ]
iptables: Flushing firewall rules: [ OK ]
iptables: Unloading modules: [ OK ]
iptables: Applying firewall rules: iptables-restore v1.4.7: error creating chain 'acct~i':File exists

Error occurred at line: 76
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
[FAILED]
iptables: Setting chains to policy ACCEPT: filter nat [ OK ]
iptables: Flushing firewall rules: [ OK ]
iptables: Unloading modules: [ OK ]
iptables: Applying firewall rules: iptables-restore v1.4.7: error creating chain 'acct~i':File exists

Error occurred at line: 76
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
[FAILED]
iptables: Setting chains to policy ACCEPT: filter nat [ OK ]
iptables: Flushing firewall rules: [ OK ]
iptables: Unloading modules: [ OK ]
iptables: Applying firewall rules: iptables-restore v1.4.7: error creating chain 'acct~i':File exists

Error occurred at line: 76
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
[FAILED]
Failed to restart iptables cleanly after 3 retries! at bin/conf_common_post_install line 31.
make[1]: *** [conf_common_post_install] Error 1
make[1]: Leaving directory `/root/svn/mercury'
make: *** [upgrade] Error 2
make: Leaving directory `/root/svn/mercury'
Stopping Pound: [ OK ]
Stopping httpd: [ OK ]
tsdb-server: unrecognized service
beam.erl: no process killed

 

So I was like ok lets try 8.2.0.2 since I know it was workign for me before I had to reimage. But had the same issue is before plus some new ones:  

/sbin/service redis-vrf condrestart
redis-vrf: unrecognized service
make[1]: [redis_conf] Error 1 (ignored)
/opt/airwave/bin/perl -MMercury::Scripts::ConfigureFreeRadius -e 'Mercury::Scripts::ConfigureFreeRadius->go'
/bin/cp -f lib/conf/tmux.conf /etc/tmux.conf
bin/conf_common_post_install
Shutting down system logger: [ OK ]
Starting system logger: [ OK ]
iptables: Setting chains to policy ACCEPT: filter nat [ OK ]
iptables: Flushing firewall rules: [ OK ]
iptables: Unloading modules: [ OK ]
iptables: Applying firewall rules: iptables-restore v1.4.7: error creating chain 'acct~i':File exists

Error occurred at line: 76
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
[FAILED]
iptables: Setting chains to policy ACCEPT: filter nat [ OK ]
iptables: Flushing firewall rules: [ OK ]
iptables: Unloading modules: [ OK ]
iptables: Applying firewall rules: iptables-restore v1.4.7: error creating chain 'acct~i':File exists

Error occurred at line: 76
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
[FAILED]
iptables: Setting chains to policy ACCEPT: filter nat [ OK ]
iptables: Flushing firewall rules: [ OK ]
iptables: Unloading modules: [ OK ]
iptables: Applying firewall rules: iptables-restore v1.4.7: error creating chain 'acct~i':File exists

Error occurred at line: 76
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
[FAILED]
Failed to restart iptables cleanly after 3 retries! at bin/conf_common_post_install line 35.
make[1]: *** [conf_common_post_install] Error 1
make[1]: Leaving directory `/root/svn/mercury'
make: *** [upgrade] Error 2
make: Leaving directory `/root/svn/mercury'
Stopping Pound: [ OK ]
Stopping httpd: [ OK ]
rabbitmq-server: unrecognized service
Wed Mar 22 14:41:32 2017: Last PID not available VisualRF Engine..

 

I am at loss for what to do. I am either going to have to reimage again or start from scratch using the ISO which I don't want to do as are server had issues with the network adapter when we installed set this server up with v8.0.7. I really don't want to go down that road again. As it was not simply finding the correct nic drivers there was an issue with the amp install as well because of the nic issue. 

 

So can someone point me in the right direction as to why this is all borked?  I never had an upgrade issue before. I original had Aruba TAC do the 8.0.7 to 8.0.10,  I did all of the others just fine on my own after that. I have my last good backup from 8.2.2  If I can get there I will be all good again. 

 

 

 

 

 

 

 

 

Contributor I
Posts: 38
Registered: ‎10-11-2012

Re: Airwave Amp Upgrade Failed error creating chain 'acct~i':File exists

We had weird stuff with IP table too when we upgraded recently to 8.2.3. We got help from the TAC engineer specialized with AirWave and he was able to cleanup stuff in our database prior the upgrade.

 

I suggest you to call the TAC to get support!

Aruba Employee
Posts: 459
Registered: ‎02-19-2015

Re: Airwave Amp Upgrade Failed error creating chain 'acct~i':File exists

Hi Joe,

 

  • To fix uprade failed due to iptables issue, follow below steps
    #amp_enable -now
  • Flush and reset the iptables with the following commands
    #service iptables stop
    #iptables --flush
    #service iptables save
    #service iptables restart
  • Recompile the code with the make script
    #root; make | tee  /tmp/make.txt

Regards,

Pavan

If my post address your query, give kudos:)

Search Airheads
Showing results for 
Search instead for 
Did you mean: