08-26-2014 05:38 AM
I recently posted about dealing with issues involving visualrf performance and was waiting for the new upgrade to be released to see if this fixed the issues was experiencing. Since Friday, whenver visualrf is clicked on, the message above claiming "VisualRF Configuration Service started. Please wait, the engine may take a few minutes to start up." has been all that shows up when trying to use visualrf. After performing the upgrade, the same message has not gone away. Any one have any ideas why this could be happening? Aside from upgrading AMP, I have done nothing to change the settings of AMP or visualrf.
Solved! Go to Solution.
08-26-2014 07:03 AM
Sent from my Verizon Wireless 4G LTE smartphone
08-27-2014 10:35 AM
It's been over a day and a half since we upgraded to 184.108.40.206 and VisualRF still hasn't started.
We want to roll back to 8.0.1 (We did a backup before upgrading ), but TAC keeps asking for more time for their developer to fix the issue.
08-27-2014 10:45 AM
TAC should already have this in their knowlegebase.
Ask them if the following fix will work for you before trying this:
1) Click on the VisualRF to get the message
2) Edit the URL to replace /vrf with /site_list and hit enter. Don't expect to see anything happen
3) Login to the Airwave root shell account and remove the file /var/airwave/cache/visualrf_bootstrap
4) At the same root prompt, enter the command "psk airwave.visualrf"
I would suggest you remain with 220.127.116.11, it does work better for us, once we got it started.
08-27-2014 11:40 AM
Well, don't know what to say then, that worked for us almost instantaneously when we did it.
Our visualRF process log was complaining about waiting for an authentication service to start at the time. Maybe yours is complaining about something different?
09-04-2014 01:56 AM
We have the same issue, since we upgraded Airwave to 18.104.22.168.
The workaround above didn´t solve the problem, so we are going to open a TAC case for this.
Any updates in the meantime?