Reply
Ubiquiti Employee
Posts: 3,272
Registered: ‎12-10-2015
Kudos: 1158
Solutions: 253

New UCRM upgrade released: 2.12.3

Hi all,

new UCRM hotfix release is now available with several fixes and improvements.

 

Feature requests

please add a new one or upvote an existing one in  UCRM Feature Requests

 

Changelog

2.12.3 (2018-08-08)

Fixed

  • Fixed IMAP ticket loader for emails coming from Office 365.
  • "Linked subscription" now visible in the Client Zone.
  • These email placeholders were empty for business customers: %CLIENT_FIRST_NAME% and %CLIENT_LAST_NAME% Now, company contact person's first name and last name are used for these placeholders.
  • Fixed failing IPpay subscription creating in some rare cases.
  • Minor fixes.

 

reply Hit Reply and let us know what do you think

Please let us know what you like or dislike about the latest improvements. Thank you for your feedback!

Veteran Member
Posts: 5,433
Registered: ‎07-03-2008
Kudos: 1706
Solutions: 134

Re: New UCRM upgrade released: 2.12.3

Very quick fixes -- thank you.

 

For some reason, I don't see this update offered in-app:

in-app-update-20180808.png

Ubiquiti Employee
Posts: 3,272
Registered: ‎12-10-2015
Kudos: 1158
Solutions: 253

Re: New UCRM upgrade released: 2.12.3

Hi @MimCom you don't see the update to 2.12.3 offered because you are running 2.13beta (which would mean to downgrade UCRM - which is not allowed because it could cause some data loss or data inconsistencies)

Note that any hotfixes added to stable version will be soon comprised in the next beta version: 2.13.0-beta3
Highlighted
Veteran Member
Posts: 5,433
Registered: ‎07-03-2008
Kudos: 1706
Solutions: 134

Re: New UCRM upgrade released: 2.12.3

My bad.  What with 2.13, 2.12.3, 0.12, and 0.13 all in regular discussion at the moment I need to read more carefully.

Member
Posts: 213
Registered: ‎01-18-2017
Kudos: 59
Solutions: 10

Re: New UCRM upgrade released: 2.12.3

We could really use a stable release that included the option to click and pay before the September 1 invoices go out. Any chance that might happen? It would be very valuable for some of our senior subscripers to be able to click and pay.

 

TIA

Ubiquiti Employee
Posts: 3,272
Registered: ‎12-10-2015
Kudos: 1158
Solutions: 253

Re: New UCRM upgrade released: 2.12.3

@clarkraymond yes, 2.13beta comprising this feature should be released by the end of this month. Just don't forget you need to extend your email notification in the Customization Settings.
Regular Member
Posts: 308
Registered: ‎03-28-2014
Kudos: 54
Solutions: 6

Re: New UCRM upgrade released: 2.12.3

@UBNT-Petr,

 

I've had the last couple of updates to UCRM fail on my Ubuntu 16.0.4LTS server from running the update via the web UI. The server is fully up-to-date in terms of packages. After clicking update in the UCRM web UI after a while the service shuts down and the web page goes unresponsive. Checking docker with 'docker ps' shows UCRM is no longer there.

 

I've been able to fix the previous failures by running the following upgrade command that I found in your beta to stable migration page on UBNT Support's page, specifying the version number I want to upgrade to:

 

/home/ucrm# curl -fsSL https://raw.githubusercontent.com/Ubiquiti-App/UCRM/master/update.sh | sudo bash -s -- 2.12.3 | sudo tee update.log

 

This time I cannot recover the application. The CLI output when manually attempting to recover is:

 

 

root@server:/home/ucrm# curl -fsSL https://raw.githubusercontent.com/Ubiquiti-App/UCRM/master/update.sh | sudo bash -s -- 2.12.3 | sudo tee update.log
+------------------------------------------------+
| UCRM - Complete WISP Management Platform       |
|                                                |
| https://ucrm.ubnt.com/          (updater v2.8) |
+------------------------------------------------+

Setting UPDATE_TO_VERSION=2.12.3
Configuring auto-update permissions.
Backing up docker compose files.
Updating elastic service
Your docker-compose contains old Elasticsearch image, trying to upgrade.
Converting Elasticsearch volumes.
Creating Elasticsearch config.
Pulling rabbitmq (rabbitmq:3)...
3: Pulling from library/rabbitmq
Digest: sha256:14a4f6c871e3218c383ac38be6e3af6af547fff46bf38c8fe113aca6f1b49697
Status: Image is up to date for rabbitmq:3
Pulling postgresql (postgres:9.5)...
9.5: Pulling from library/postgres
Digest: sha256:1920c42aee2092a17bca805501f4c2095188dacf3c4b191c71c6125c4c44fb22
Status: Image is up to date for postgres:9.5
Pulling elastic (elastic/elasticsearch:6.2.4 - ./elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml:latest)...
ERROR: invalid reference format
Image for version "2.12.3" not found.
Reverting docker compose files.

 

The update log file /home/ucrm/data/ucrm/updates/update.log shows:

 

Wed Aug 15 12:21:01 EDT 2018 --- Initializing UCRM update to version 2.12.3.
Wed Aug 15 12:21:01 EDT 2018 --- Downloading current updater.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
^M  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0^M  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0^M100 44626  100 44626    0     0   110k      0 --:--:-- --:--:-- --:--:--  110k
Wed Aug 15 12:21:01 EDT 2018 --- Starting the update process.
+------------------------------------------------+
| UCRM - Complete WISP Management Platform       |
|                                                |
| https://ucrm.ubnt.com/          (updater v2.8) |
+------------------------------------------------+

Setting UPDATE_TO_VERSION=2.12.3
Setting CRON=true
Skipping auto-update permissions setup.
Backing up docker compose files.
Updating elastic service
Your docker-compose contains old Elasticsearch image, trying to upgrade.
Pulling rabbitmq (rabbitmq:3)...
3: Pulling from library/rabbitmq
Digest: sha256:14a4f6c871e3218c383ac38be6e3af6af547fff46bf38c8fe113aca6f1b49697
Status: Downloaded newer image for rabbitmq:3
Pulling postgresql (postgres:9.5)...
9.5: Pulling from library/postgres
Digest: sha256:1920c42aee2092a17bca805501f4c2095188dacf3c4b191c71c6125c4c44fb22
Status: Downloaded newer image for postgres:9.5
Pulling elastic (elastic/elasticsearch:6.2.4)...
6.2.4: Pulling from elastic/elasticsearch
Digest: sha256:9ae20c753f18e27d1dd167b8675ba95de20b1f1ae5999aae5077fa2daf38919e
Status: Downloaded newer image for elastic/elasticsearch:6.2.4
Pulling web_app (ubnt/ucrm-billing:2.12.3)...
2.12.3: Pulling from ubnt/ucrm-billing
Digest: sha256:996b9b60a1de0d1860a0b53493711482b28fc689d4f90869766168f96e2298fc
Status: Downloaded newer image for ubnt/ucrm-billing:2.12.3
Stopping ucrm_web_app_1 ... ^M
Stopping ucrm_elastic_1 ... ^M
Stopping ucrm_rabbitmq_1 ... ^M
Stopping ucrm_postgresql_1 ... ^M
^[[4A^[[2K^MStopping ucrm_web_app_1 ... done^M^[[4B^[[3A^[[2K^MStopping ucrm_elastic_1 ... done^M^[[3B^[[1A^[[2K^MStopping ucrm_postgresql_1 ... done^M^[[1B^[[2A^[[2K^MStopping ucrm_rabbitmq_1 ... done^M^[[2B--all flag is obsolete. This is now the default behavior of `docker-compose rm`
Removing ucrm_web_app_1 ... ^M
Removing ucrm_elastic_1 ... ^M
Removing ucrm_rabbitmq_1 ... ^M
Removing ucrm_postgresql_1 ... ^M

ERROR: for ucrm_postgresql_1  UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

ERROR: for ucrm_elastic_1  UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

ERROR: for ucrm_web_app_1  UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

ERROR: for ucrm_rabbitmq_1  UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)
An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
Going to remove ucrm_web_app_1, ucrm_elastic_1, ucrm_rabbitmq_1, ucrm_postgresql_1
Wed Aug 15 12:23:32 EDT 2018 --- Update failed.

Is anyone else experiencing this behavior during updates?

 

Thanks!

Certified UEWA / UBRSS
Member
Posts: 213
Registered: ‎01-18-2017
Kudos: 59
Solutions: 10

Re: New UCRM upgrade released: 2.12.3

Is it possible to send an email with the option to click to pay in it manually in 2.12.2?

Ubiquiti Employee
Posts: 3,272
Registered: ‎12-10-2015
Kudos: 1158
Solutions: 253

Re: New UCRM upgrade released: 2.12.3

[ Edited ]

@Mtec This error "UnixHTTPConnectionPool(host='localhost', port=None): Read timed out." is some strange docker behavior. Could you please send us the output of this?

 sudo docker info

 

Anyway, these commands could help you solve the issue.

export DOCKER_CLIENT_TIMEOUT=120
export COMPOSE_HTTP_TIMEOUT=120

 

Ubiquiti Employee
Posts: 3,272
Registered: ‎12-10-2015
Kudos: 1158
Solutions: 253

Re: New UCRM upgrade released: 2.12.3

@clarkraymond no it's not possible. You can either wait for the 2.13 stable release (late this month) or upgrade to the beta branch: 2.13.0-beta2

Ubiquiti Employee
Posts: 1,054
Registered: ‎03-21-2016
Kudos: 166
Solutions: 121

Re: New UCRM upgrade released: 2.12.3

Hello @Mtec, the error you see (ERROR: invalid reference format) is because of a bug in our update script, which got fixed earlier today. Sadly it corrupted your "docker-compose.yml" file and you will have to fix it manually.

 

The problem is with the "elastic" container, to fix it, open your /home/ucrm/docker-compose.yml file in an editor of choice (e.g. nano) and fix the elastic part of the file to look like this:

  elastic:
    image: elastic/elasticsearch:6.2.4
    volumes:
      - ./data/elasticsearch6:/usr/share/elasticsearch/data
      - ./elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml
    restart: always
    logging:
      driver: "json-file"
      options:
        max-size: "10m"
        max-file: "3"

Or you can copy a backup which has this section looking fine from the "docker-compose-backups" directory in /home/ucrm, there should be a backed up file from just before you ran the update script.

 

Afterwards, please run the update script again, as it's fixed now it won't corrupt your installation again.

 

If you need any help, feel free to PM me or post here.

Regular Member
Posts: 308
Registered: ‎03-28-2014
Kudos: 54
Solutions: 6

Re: New UCRM upgrade released: 2.12.3

@UBNT-Ondra,

 

Thanks so much, that got me fixed and I'm online again! Ubnt Banana

Certified UEWA / UBRSS
Reply