Wireless Access

Reply
Highlighted

Re: No WEB Access after upgrade to AirWave 8.2.4

What did you use?

 

I´ve tried an OpenSSH server on Ubunto 17.04. Not working.

All other problems are like yours with Child object code 1.

Got a case with TAC, but their server gave me the same error (lol).

 

This is the worse release ever. And I also lost GUI access when trying the reset password function. That removes the original password but doesn´t set it to admin.

 

Best Airwave week ever!

Highlighted
MVP Expert

Re: No WEB Access after upgrade to AirWave 8.2.4

pnobels, your AirWave server is running with 8G of RAM? How many devices?


Jerrod Howard
Distinguished Technologist, TME
Highlighted
Frequent Contributor II

Re: No WEB Access after upgrade to AirWave 8.2.4

So i upgraded to 8.2.3.1.  And what do you know...  noticed also httpd complaining about shortage of memory.  So after verifying i noticed i had 4 GByte of RAM and 4 GByte of swap defined.  Clearly the 4 GByte of RAM did not suffice anymore...  Upgraded to 8 GByte and did no longer notice httpd errors.  Unfortunately 8.2.3.1 demonstrated failing visualrf behaviour.  So this morning upgraded back to 8.2.4.  Seems to work fine now.  Also visualrf functions back correctly.

Bottomline : upgrading from 4 to 8 Gbyte of RAM is the solution. Running with approx. 160 devices configured in Airwave.

Highlighted
MVP Expert

Re: No WEB Access after upgrade to AirWave 8.2.4

4GB would have absolutely been too little. 8GB could actually still be too little depending on how you use the AMP(if you have lots of users per AP, heavy usage of VisualRF, etc). But 8GB is the bare minimum. You can also modify how much memory VisualRF uses in the VRF settings. If you are a heavy VRF user, upping the available RAM and assigning more to VRF will help.


Jerrod Howard
Distinguished Technologist, TME
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: