Reply
Highlighted
Ubiquiti Employee
Posts: 6,655
Registered: ‎05-13-2009
Kudos: 2098
Solutions: 206

AC2 Beta17 released!

Hi all,

releasing AC2 Beta17 with follow changes:

 

- New: Added airOS 8.x support

- New: Added airOS 6.x support

- New: Added Rocket M6 support

- New: Added "not equals" filter criteria in automation rule editor

 

- Fix: Statistics summary for AF2X shows invalid TX Power value

 

IMPORTANT NOTES: 

 - To prevent from any data migration issues please do upgrade from the latest AC2-BETA version. 

 - AC2 no longer supports JAVA 1.6. Before upgrade please update JAVA to the latest available version.

 

Other Notes: 

- to fix graphical issues on OS X Maverics edit client startup script and add --enableTextureCoordFix argument

- when installing over an existing version, please close airControl2 client application if it is running

- if you see inconsistencies in the automatically resolved topology and you have active PoE configurations in it, please do not perform mass-firmware updates with AC2 beta, this can cause permanent damage to some devices 

 

Download:

Windows Server/Client installer: aircontrol2-2.0-Beta17.1318.151020.2002-win.exe

Ubuntu Server/Client installer: aircontrol2-2.0-Beta17.1318.151020.2002-ubuntu.deb

Mac OS Client installer: aircontrol2-2.0-Beta17.1318.151020.2002-mac.jar

 

Enjoy in using it and please report new problems or usability change requests in separate threads. 

 

Thanks,
Edmundas

SuperUser
Posts: 16,788
Registered: ‎06-18-2010
Kudos: 5395
Solutions: 1791

Re: AC2 Beta17 released!

Quick note: Upgrade from AC2 Beta 16 went smoothly. I can verify it now correctly shows AF2X TX Power.
Set a Frequency! Don't leave it on Auto!
Disable Uplink Connectivity Monitor
Always set-inform a Second time after Adopting
Senior Member
Posts: 3,441
Registered: ‎07-28-2009
Kudos: 1048
Solutions: 44

Re: AC2 Beta17 released!

Awsome.  Now I can go about testing the new FW in my network.  Thanks for the quick patch.

Senior Member
Posts: 3,441
Registered: ‎07-28-2009
Kudos: 1048
Solutions: 44

Re: AC2 Beta17 released!

[ Edited ]

@UBNT-Edmundas Installation went fine however my graphs no longer show any data prior to 12 days ago and I cannot scroll or zoom out past one month of this year for every device.  The db files are still available in my Aircontrol install folder.  I used to be able to pull up all past history even to a year ago before the updated to b17 today.

Established Member
Posts: 1,609
Registered: ‎10-11-2009
Kudos: 337
Solutions: 6

Re: AC2 Beta17 released!

[ Edited ]

@UBNT-Edmundas AC AP in mixed mode still shows a signal strenght of -231dBm in AC2 B17.  I'm also having issues discovering 8.0b2 CPEs.

Veteran Member
Posts: 7,911
Registered: ‎04-21-2011
Kudos: 2750
Solutions: 173

Re: AC2 Beta17 released!

I had that problem with an earlier version, and had to manually install the unit.  Once I listed the device address, it found it, and then it would monitor it!  I don't know if this is the same problem. Mine was on PowerBeam 400's.

Established Member
Posts: 1,232
Registered: ‎11-05-2008
Kudos: 548
Solutions: 49

Re: AC2 Beta17 released!


@sbyrd wrote:

@UBNT-Edmundas Installation went fine however my graphs no longer show any data prior to 12 days ago and I cannot scroll or zoom out past one month of this year for every device.  The db files are still available in my Aircontrol install folder.  I used to be able to pull up all past history even to a year ago before the updated to b17 today.


I also lost chart data.  After upgrade to b17, I only have the last 7.5 days of charts.  Reboots, online/offline etc, do not seem to be trunkated at all.

 

WISP Since 2001 | UniFi Sites >300 | UniFi Video Sites >45 | Protect Sites >5
Established Member
Posts: 1,232
Registered: ‎11-05-2008
Kudos: 548
Solutions: 49

Re: AC2 Beta17 released!


@UBNT-Edmundas wrote:

 

- New: Added "not equals" filter criteria in automation rule editor

 


YES!!! Been waiting for this for years.

WISP Since 2001 | UniFi Sites >300 | UniFi Video Sites >45 | Protect Sites >5
Emerging Member
Posts: 64
Registered: ‎11-29-2007
Kudos: 4
Solutions: 3

Re: AC2 Beta17 released!

[ Edited ]

Upgraded from b12 -> 14 = no problem

                        b14 -> 15 = rebooted the server initial install failed w/ something like start_client.bat error

                        b15 -> 16 = no problem still had all history of radio stats

                        b16 -> 17 = all chart plot history except events older than 5 days is gone from display

 

Database size is still about the same as it was at beta 12.

Established Member
Posts: 1,092
Registered: ‎08-14-2014
Kudos: 225
Solutions: 12

Re: AC2 Beta17 released!

Elaborate more on the M6 !?!?

Established Member
Posts: 1,232
Registered: ‎11-05-2008
Kudos: 548
Solutions: 49

Re: AC2 Beta17 released!


@BotaDriver wrote:

Elaborate more on the M6 !?!?


Russian Products

WISP Since 2001 | UniFi Sites >300 | UniFi Video Sites >45 | Protect Sites >5
Established Member
Posts: 791
Registered: ‎01-02-2009
Kudos: 193

Re: AC2 Beta17 released!

after upgrade in linux (debian) from beta16 to beta17 all history, graphs deleted....

 

also I cant configure rocket AC devices:

 

29Oct2015_10-44-14.jpg
SuperUser
Posts: 4,020
Registered: ‎06-30-2010
Kudos: 1834
Solutions: 173
Contributions: 9

Re: AC2 Beta17 released!

Configuration of AC devices is not done yet.

/Paetur
Member
Posts: 296
Registered: ‎10-31-2010
Kudos: 76
Solutions: 1

Re: AC2 Beta17 released!

Any chance of releasing centos-compatible RPM's ?

Member
Posts: 284
Registered: ‎11-11-2013
Kudos: 117
Solutions: 4

Re: AC2 Beta17 released!

Or officlal Docker images?

 

 

---* Bill

Regular Member
Posts: 341
Registered: ‎08-06-2013
Kudos: 233
Solutions: 5

Re: AC2 Beta17 released!

[ Edited ]

You could try this (convert from deb to rpm):
http://www.thegeekstuff.com/2010/11/alien-command-examples/

SuperUser
Posts: 4,020
Registered: ‎06-30-2010
Kudos: 1834
Solutions: 173
Contributions: 9

Re: AC2 Beta17 released!


@guipoletto wrote:

Any chance of releasing centos-compatible RPM's ?


I made a KB about non-debian based install some time ago, have you looked at it :

 

https://help.ubnt.com/hc/en-us/articles/204949804-airControl2-Server-installation-guide-for-non-Debi...

 

/Paetur

Member
Posts: 296
Registered: ‎10-31-2010
Kudos: 76
Solutions: 1

Re: AC2 Beta17 released!

tried that on centos7, got back a "service aircontrol2 does not support chkconfig"

 

Any ideas on that?

SuperUser
Posts: 4,020
Registered: ‎06-30-2010
Kudos: 1834
Solutions: 173
Contributions: 9

Re: AC2 Beta17 released!


@guipoletto wrote:

tried that on centos7, got back a "service aircontrol2 does not support chkconfig"

 

Any ideas on that?


Sounds like you skipped the step, where you edit the /etc/init.d/aircontrol2 file. and add the chkconfig tags.

 

It must begin first line with :

#!/bin/bash
# chkconfig: 2345 20 80
# description: Enable Ubiquiti AirControl2 service provided by daemon.

# Source function library.
. /etc/init.d/functions 

 

And you delete the debian based tags:

#!/bin/sh

### BEGIN INIT INFO
# Provides:          aircontrol2
# Required-Start:    $all
# Required-Stop:     $all
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Start AirControl2 at boot time after network init
# Description:       Enable Ubiquiti AirControl2 service provided by daemon.
### END INIT INFO

...

 

More on sysvinit files : 

Writing System V init scripts for Red Hat Linux
===============================================

All System V init scripts are named /etc/rc.d/init.d/<servicename>
where <servicename> is the name of the service.  There must be no
".init" suffix.

This path will very likely be moved to /etc/init.d in the future.
Once Red Hat Linux 7.0 is installed, you can access scripts as
/etc/init.d/<servicename>, via symlinks.

Sample Script
=============

#!/bin/bash
#
#	/etc/rc.d/init.d/<servicename>
#
#	<description of the *service*>
#	<any general comments about this init script>
#
# <tags -- see below for tag definitions.  *Every line* from the top
#  of the file to the end of the tags section must begin with a #
#  character.  After the tags section, there should be a blank line.
#  This keeps normal comments in the rest of the file from being
#  mistaken for tags, should they happen to fit the pattern.>

# Source function library.
. /etc/init.d/functions

<define any local shell functions used by the code that follows>

start() {
	echo -n "Starting <servicename>: "
	<start daemons, perhaps with the daemon function>
	touch /var/lock/subsys/<servicename>
	return <return code of starting daemon>
}	

stop() {
	echo -n "Shutting down <servicename>: "
	<stop daemons, perhaps with the killproc function>
	rm -f /var/lock/subsys/<servicename>
	return <return code of stopping daemon>
}

case "$1" in
    start)
	start
	;;
    stop)
	stop
	;;
    status)
	<report the status of the daemons in free-form format,
	perhaps with the status function>
	;;
    restart)
    	stop
	start
	;;
    reload)
	<cause the service configuration to be reread, either with
	kill -HUP or by restarting the daemons, in a manner similar
	to restart above>
	;;
    condrestart)
    	<Restarts the servce if it is already running. For example:>
	[ -f /var/lock/subsys/<service> ] && restart || :
    probe)
	<optional.  If it exists, then it should determine whether
	or not the service needs to be restarted or reloaded (or
	whatever) in order to activate any changes in the configuration
	scripts.  It should print out a list of commands to give to
	$0; see the description under the probe tag below.>
	;;
    *)
	echo "Usage: <servicename> {start|stop|status|reload|restart[|probe]"
	exit 1
	;;
esac
exit $?

Notes: 

- The restart and reload functions may be (and commonly are)
  combined into one test, vis:
    restart|reload)
- You are not prohibited from adding other commands; list all commands
  which you intend to be used interactively to the usage message.
- Notice the change in that stop() and start() are now shell functions.
  This means that restart can be implemented as
     stop
     start
  instead of
     $0 stop
     $0 start
  This saves a few shell invocations.

Functions in /etc/init.d/functions
=======================================

daemon  [ --check <name> ] [ --user <username>] 
	[+/-nicelevel] program [arguments] [&]

	Starts a daemon, if it is not already running.  Does
	other useful things like keeping the daemon from dumping
	core if it terminates unexpectedly.
	
	--check <name>:
	   Check that <name> is running, as opposed to simply the
	   first argument passed to daemon().
	--user <username>:
	   Run command as user <username>

killproc program [signal]

	Sends a signal to the program; by default it sends a SIGTERM,
	and if the process doesn't die, it sends a SIGKILL a few
	seconds later.

	It also tries to remove the pidfile, if it finds one.

pidofproc program

	Tries to find the pid of a program; checking likely pidfiles,
	and using the pidof program.  Used mainly from within other
	functions in this file, but also available to scripts.

status program

	Prints status information.  Assumes that the program name is
	the same as the servicename.


Tags
====

# chkconfig: <startlevellist> <startpriority> <endpriority>

	Required.  <startlevellist> is a list of levels in which
	the service should be started by default.  <startpriority>
	and <endpriority> are priority numbers.  For example:
	# chkconfig: 2345 20 80
	Read 'man chkconfig' for more information.

	Unless there is a VERY GOOD, EXPLICIT reason to the
	contrary, the <endpriority> should be equal to
	100 - <startpriority>
	
# description: <multi-line description of service>

	Required.  Several lines of description, continued with '\'
	characters.  The initial comment and following whitespace
	on the following lines is ignored.

# description[ln]: <multi-line description of service in the language \
#                  ln, whatever that is>

	Optional.  Should be the description translated into the
	specified language.

# processname:

	Optional, multiple entries allowed.  For each process name
	started by the script, there should be a processname entry.
	For example, the samba service starts two daemons:
	# processname: smdb
	# processname: nmdb

# config:

	Optional, multiple entries allowed.  For each static config
	file used by the daemon, use a single entry.  For example:
	# config: /etc/httpd/conf/httpd.conf
	# config: /etc/httpd/conf/srm.conf

	Optionally, if the server will automatically reload the config
	file if it is changed, you can append the word "autoreload" to
	the line:
	# config: /etc/foobar.conf autoreload

# pidfile:

	Optional, multiple entries allowed.  Use just like the config
	entry, except that it points at pidfiles.  It is assumed that
	the pidfiles are only updated at process creation time, and
	not later.  The first line of this file should be the ASCII
	representation of the PID; a terminating newline is optional.
	Any lines other than the first line are not examined.

# probe: true

	Optional, used IN PLACE of processname, config, and pidfile.
	If it exists, then a proper reload-if-necessary cycle may be
	acheived by running these commands:

	command=$(/etc/rc.d/init.d/SCRIPT probe)
	[ -n "$command" ] && /etc/rc.d/init.d/SCRIPT $command

	where SCRIPT is the name of the service's sysv init script.

	Scripts that need to do complex processing could, as an
	example, return "run /var/tmp/<servicename.probe.$$"
	and implement a "run" command which would execute the
	named script and then remove it.

	Note that the probe command should simply "exit 0" if nothing
	needs to be done to bring the service into sync with its
	configuration files.

Copyright (c) 2000 Red Hat Software, Inc.

/Paetur

Member
Posts: 205
Registered: ‎07-12-2014
Kudos: 20
Solutions: 2

Re: AC2 Beta17 released!

for mac version i cant use server version it ask for server host id.  

 

little detail please

Reply