Reply
Ubiquiti Employee
Posts: 3,740
Registered: ‎12-10-2015
Kudos: 1330
Solutions: 292

New UCRM hotfix version 2.14.5 released!

Hi all,

new UCRM hotfix 2.14.5 is now available. Please upgrade to this latest stable version using the in-app upgrade button.

 

Feature requests

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

 

Changelog

2.14.5 (2019-01-10)

Fixed

  • Fixed form validation for "created date" in manual invoice form.
  • UX Optimization - slow ticket view and failing ticketing assignments in case UCRM contains a huge number of clients.

 

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!

New Member
Posts: 14
Registered: ‎12-26-2016

Re: New UCRM hotfix version 2.14.5 released!

Hello all,

 

The update has been executed successfully to v2.14.5, The form validation for "created date" has been fixed, so I can modify dates on my invoices without stress.

 

Also, no more need for the backdoor means of updating I mentioned for the previous version. The update took its full course to success:

Thu Jan 10 15:23:46 WAT 2019 --- Update successful.

 

Thanking the UBNT/UCRM team for their swift action, effective debugging and being able to resolve the issues. I am just too happy... Ubnt Banana

 

See the full log script below:

Thu Jan 10 15:20:01 WAT 2019 --- Initializing UCRM update to version 2.14.5.
Thu Jan 10 15:20:01 WAT 2019 --- Using update-cron.sh v1.0
Thu Jan 10 15:20:01 WAT 2019 --- Downloading current updater.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
 27 46322   27 12951    0     0  11681      0  0:00:03  0:00:01  0:00:02 11678
100 46322  100 46322    0     0  38023      0  0:00:01  0:00:01 --:--:-- 38000
Thu Jan 10 15:20:02 WAT 2019 --- Starting the update process.
+------------------------------------------------+
| UCRM - Complete WISP Management Platform       |
|                                                |
| https://ucrm.ubnt.com/          (updater v3.2) |
+------------------------------------------------+

Setting UPDATE_TO_VERSION=2.14.5
Setting CRON=true
Skipping auto-update permissions setup.
Backing up docker compose files.
Updating elastic service
Pulling rabbitmq (rabbitmq:3)...
3: Pulling from library/rabbitmq
Digest: sha256:09f02eca2bbb52620187c8a0d03b0eb31cd911d1ac5d9589a67a1670226dc9a6
Status: Image is up to date for rabbitmq:3
Pulling postgresql (postgres:9.5)...
9.5: Pulling from library/postgres
Digest: sha256:cf812f5d6f47360cfe33072114dc11d9bccb99548143e850bd338049542496c3
Status: Image is up to date for postgres:9.5
Pulling elastic (elastic/elasticsearch:6.2.4)...
6.2.4: Pulling from elastic/elasticsearch
Digest: sha256:9ae20c753f18e27d1dd167b8675ba95de20b1f1ae5999aae5077fa2daf38919e
Status: Image is up to date for elastic/elasticsearch:6.2.4
Pulling web_app (ubnt/ucrm-billing:2.14.5)...
2.14.5: Pulling from ubnt/ucrm-billing
Digest: sha256:5ab3c71b06611197d835e1a8d1bb4a5a929d9e8fa21b2b1c27c4651b58715d49
Status: Downloaded newer image for ubnt/ucrm-billing:2.14.5
Stopping ucrm_web_app_1 ... 

Stopping ucrm_web_app_1 ... done
Stopping ucrm_rabbitmq_1   ... 
Stopping ucrm_elastic_1    ... 
Stopping ucrm_postgresql_1 ... 

Stopping ucrm_postgresql_1 ... done

Stopping ucrm_elastic_1    ... done

Stopping ucrm_rabbitmq_1   ... done
--all flag is obsolete. This is now the default behavior of `docker-compose rm`
Removing ucrm_web_app_1    ... 
Removing ucrm_rabbitmq_1   ... 
Removing ucrm_elastic_1    ... 
Removing ucrm_postgresql_1 ... 

Removing ucrm_web_app_1    ... done

Removing ucrm_rabbitmq_1   ... done

Removing ucrm_postgresql_1 ... done

Removing ucrm_elastic_1    ... done
Going to remove ucrm_web_app_1, ucrm_rabbitmq_1, ucrm_elastic_1, ucrm_postgresql_1
Creating ucrm_postgresql_1 ... 
Creating ucrm_postgresql_1

Creating ucrm_postgresql_1 ... done
/usr/src/ucrm/scripts/init_log.sh
/usr/src/ucrm/scripts/dirs.sh
Thu Jan 10 14:22:36 UTC 2019 --- Creating directories.
Thu Jan 10 14:22:36 UTC 2019 --- Done creating directories.
Thu Jan 10 14:22:36 UTC 2019 --- Creating symbolic links.
Thu Jan 10 14:22:36 UTC 2019 --- Creating symbolic link for /usr/src/ucrm/app/data.
Thu Jan 10 14:22:36 UTC 2019 --- Creating symbolic link for /usr/src/ucrm/app/EmailQueue.
Thu Jan 10 14:22:36 UTC 2019 --- Creating symbolic link for /usr/src/ucrm/app/logs.
Thu Jan 10 14:22:36 UTC 2019 --- Creating symbolic link for /usr/src/ucrm/app/letsencrypt_logs.
Thu Jan 10 14:22:36 UTC 2019 --- Creating symbolic link for /usr/src/ucrm/web/uploads.
Thu Jan 10 14:22:36 UTC 2019 --- Creating symbolic links for /data/updates.
Thu Jan 10 14:22:36 UTC 2019 --- Publishing current /usr/src/ucrm/app/config/version.yml.
Thu Jan 10 14:22:36 UTC 2019 --- Done creating symbolic links.
/usr/src/ucrm/scripts/parameters.sh
Thu Jan 10 14:22:36 UTC 2019 --- Replacing configuration parameters.
Thu Jan 10 14:22:36 UTC 2019 --- Done replacing configuration parameters.
su-exec nginx /usr/src/ucrm/scripts/migrate.sh
Thu Jan 10 14:22:37 UTC 2019 --- Creating database backup.
Thu Jan 10 14:22:39 UTC 2019 --- Migrating database.
Thu Jan 10 14:22:49 UTC 2019 --- Migration complete.
Thu Jan 10 14:22:49 UTC 2019 --- Removing database backup.
--all flag is obsolete. This is now the default behavior of `docker-compose rm`
Removing ucrm_migrate_app_run_1 ... 

Removing ucrm_migrate_app_run_1 ... done
Going to remove ucrm_migrate_app_run_1
Configuring auto-update.
* * * * * /home/ucrm/update-cron.sh > /dev/null 2>&1 || true
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  3652  100  3652    0     0   3848      0 --:--:-- --:--:-- --:--:--  3848
no crontab for ucrm
ucrm_postgresql_1 is up-to-date
Creating ucrm_rabbitmq_1 ... 
Creating ucrm_elastic_1 ... 
Creating ucrm_rabbitmq_1
Creating ucrm_elastic_1

Creating ucrm_rabbitmq_1 ... done

Creating ucrm_elastic_1 ... done
Creating ucrm_web_app_1 ... 
Creating ucrm_web_app_1

Creating ucrm_web_app_1 ... done
      Name                     Command               State                                               Ports                                             
-----------------------------------------------------------------------------------------------------------------------------------------------------------
ucrm_elastic_1      /usr/local/bin/docker-entr ...   Up      9200/tcp, 9300/tcp                                                                            
ucrm_postgresql_1   docker-entrypoint.sh postgres    Up      5432/tcp                                                                                      
ucrm_rabbitmq_1     docker-entrypoint.sh rabbi ...   Up      25672/tcp, 4369/tcp, 5671/tcp, 5672/tcp                                                       
ucrm_web_app_1      make server                      Up      0.0.0.0:2055->2055/udp, 0.0.0.0:443->443/tcp, 0.0.0.0:80->80/tcp, 0.0.0.0:81->81/tcp, 9000/tcp
Unable to find image 'ubnt/ucrm-conntrack:latest' locally
latest: Pulling from ubnt/ucrm-conntrack
627beaf3eaaf: Pulling fs layer
aadec8da6837: Pulling fs layer
627beaf3eaaf: Download complete
aadec8da6837: Verifying Checksum
aadec8da6837: Download complete
627beaf3eaaf: Pull complete
aadec8da6837: Pull complete
Digest: sha256:5ed724152a396c413db84cdb412146d9f2f655a2ef96ed45b26e4d2e2c4ebee3
Status: Downloaded newer image for ubnt/ucrm-conntrack:latest
conntrack v1.4.4 (conntrack-tools): 0 flow entries have been deleted.
Booting UCRM
Initializing: Web 07/18
Initializing: Web 08/18
Initializing: Web 10/18
Initializing: Web 11/18
Initializing: Web 12/18
Initializing: Web 13/18
Initializing: Web 14/18
Initializing: Web 15/18
Initializing: Web 16/18
UCRM ready
Removing old UCRM images
Untagged: ubnt/ucrm-billing:2.14.4
Untagged: ubnt/ucrm-billing@sha256:c5c247472dec46ba0885e123d8a99293c82c19648ba9a56cfae3904ac9a12987
Deleted: sha256:524330feaa2b3437473541b7cd8231dbe7535451eb9aaeb63a6cd59b6a98b37c
Deleted: sha256:d8ba2bbd0b623073a3102c3f991961b6ec58aa37c571c7ff9b8b4df6e428cb9b
Deleted: sha256:f7c02da00baeca3391dc2787e6d7321009ed537ad4fd977e1e23bce9533eaa48
Deleted: sha256:8ed449ee4f6995a1d0edc597674cbacfd01d3f34877a43ac9d23fd24ddc11bd3
Deleted: sha256:40a472d9a0882e3c96c7d5b3336642ed1e9119d7fbfd8b0429a2b090c494f464
Deleted: sha256:c8738d73e4309cdf0a63093b8d19abbfd236098c5afa2d4a202c9ba70dc879bb
Deleted: sha256:1029249d288b1a79a46953c332adb35a1403c9add237ca729e7b0445057027ed
Deleted: sha256:3a5e1ad6082f228685089644ab45a7acb0886d316e1f05eb514baf5f2d56c200
Deleted: sha256:44fd3378ef78159e0deaa63bb92771ec9eea230c67db877bcb3c767d01f45354
Deleted: sha256:b232b664b3ac636e1bb24d6465c69aa432f2ddf6fb08f5fc8f30d9aab3a222c3
Deleted: sha256:be47cf11ee238bd15917640cae2aa3736eeeb93842af4858fa25e4ba5b523092
Deleted: sha256:7f08ee0c673a7506cc7030ad5e570aed967195a2601de3ab09e2fe7c540481e0
Deleted: sha256:1f44dbb1141d65325b714f2f9b047706cd9afd4aa470a41f2585dbb74ef7a64b
Deleted: sha256:1060931ae41486c5957faf6c873c7708ad36255ef85f50780e41edb71143a284
Deleted: sha256:7d5b40e8eb09d451a72fd8371e9796befb05c1a366352b2b38b669708955057d
Deleted: sha256:2f9732920ff44e60f063dc1940cb7328ad34f91f653c04ddbe30297c9694a1eb
Deleted: sha256:202fc8150ac98c450209e66093610d3a5217b1f4526a9ca1e40e423aa76c8591
Deleted: sha256:963fe584cfd6b100b37b83f75c21c726f42dc2f8142fb6e5fa938c54e7c5bb4d
Deleted: sha256:f93b773e06d61e5395f7c183e23dc3977f77877c2f0492071c60097b70a89f80
Deleted: sha256:3e81e0d061a36063b293d8bd28303a76bd618b354e44f68ad75426ec64552812
Deleted: sha256:2072c07fdf385c2aada651e71c6b61d7bcad5966cf51d7740b2690859d52550e
Deleted: sha256:188fca2a402267d7d27cde59cf9a5055f32dd824d771b0b485552a9b6d64a1eb
Deleted: sha256:dbdf22f97f40473c972eadb597c0fd5019366ddae7a2712618d4eeece58ac371
Deleted: sha256:406ac444f6f44fe8db613bf9927ea5a5acf6e5ebf583de4e20da93d057640ff7
Deleted: sha256:11df9dbe0c2d9d9767397a62a1624a8f83f7681d12696d1a80642275fb6d8a62
Deleted: sha256:6fe456705d4be7e59e84a08f510e0e5b277876a6e0da5e080328c5211d572076

----------------

We recommend running "docker system prune" once in a while to clean unused containers, images, etc.
You can determine how much space can be cleaned up by running "docker system df"
Thu Jan 10 15:23:46 WAT 2019 --- Update successful.

 

New Member
Posts: 30
Registered: ‎01-24-2016

Re: New UCRM hotfix version 2.14.5 released!

Thanks

A life saver...

Emerging Member
Posts: 74
Registered: ‎02-04-2014
Kudos: 41
Solutions: 2

Re: New UCRM hotfix version 2.14.5 released!

I think I got a bug, when I export my payment the put UCRM costomer ID instead of personalized ID

New Member
Posts: 30
Registered: ‎01-24-2016

Re: New UCRM hotfix version 2.14.5 released!

Hello,

 

same problem that was solved for the invoice date now shows up in log export:

Schermata 2019-01-11 alle 09.23.13.png

No idea if it was present on 2.14.4 also.

Thanks

Ciao

Ubiquiti Employee
Posts: 1,266
Registered: ‎03-21-2016
Kudos: 201
Solutions: 146

Re: New UCRM hotfix version 2.14.5 released!

Hello @stefanormc, we're already working on a fix for this. Thank you for the report. In the meantime you can just export the whole client log and delete the lines you don't want manually, at least in case of CSV.

Ubiquiti Employee
Posts: 1,266
Registered: ‎03-21-2016
Kudos: 201
Solutions: 146

Re: New UCRM hotfix version 2.14.5 released!

Hello @synertic, can you please specify which export you're talking about?

New Member
Posts: 19
Registered: ‎10-16-2014
Kudos: 1
Solutions: 1

Re: New UCRM hotfix version 2.14.5 released!

Not critical but you could take a look at the System->Settings->Ticketing-->Email blacklist_Add
Whenever Delete tickets is set to Yes, it will still behave like it was set to No. So one would need to edit again to set it to Yes a second time.

Great Job !!!
ubnt_banana.gif

Ubiquiti Employee
Posts: 3,740
Registered: ‎12-10-2015
Kudos: 1330
Solutions: 292

Re: New UCRM hotfix version 2.14.5 released!

@emax_afang we will check it out, thanks for the heads up.
New Member
Posts: 17
Registered: ‎01-15-2014
Kudos: 2

Re: New UCRM hotfix version 2.14.5 released!

Hi,

 

I'm new to UCRM having installed v2.14.5 just yesterday and so far very impressed will it. Looks like it will do almost everything we need, but disappointed that the Data Limit value on Service Plans is only informational and not used to limit customers' data usage. I'll have to create some integration with our exisitng RADIUS system to handle account suspension when data limit exceeded.

 

Also, one small wrinkle, there appears to be a bug in the APIs when adding Service Plans. If you supply a non-integer price, e.g. 49.99, you get an error:-

 

{"code":422,"message":"Validation failed.","errors":{"price":["This value is not in valid type. Double expected."]}}

 

But if you supply an integer, e.g. 49 or 50, the API validation quite happily accepts it.

 

Since the field in the GUI accepts non-integer values, I suspect this is simply a bug in the API validation code checking for the wrong data type for this attribute.

 

Regards

 

Chris Macneill

Ubiquiti Employee
Posts: 1,266
Registered: ‎03-21-2016
Kudos: 201
Solutions: 146

Re: New UCRM hotfix version 2.14.5 released!

Hello @cmmacneill53, I think you might be sending the price value wrong, it works absolutely fine for me. This is working command for UCRM demo with price 49.99:

curl -X POST \
  https://ucrm-demo.ubnt.com/api/v1.0/service-plans \
  -H 'Content-Type: application/json' \
  -H 'X-Auth-App-Key: 5YbpCSto7ffl/P/veJ/GK3U7K7zH6ZoHil7j5dorerSN8o+rlJJq6X/uFGZQF2WL' \
  -H 'cache-control: no-cache' \
  -d '{
    "name": "testing price",
    "periods": [
        {
            "period": 1,
            "price": 49.99,
            "enabled": true
        }
    ]
}'

Maybe you're trying to send the price as string instead of number?

New Member
Posts: 17
Registered: ‎01-15-2014
Kudos: 2

Re: New UCRM hotfix version 2.14.5 released!

Thanks UBNT-Ondra, the problem with the API was indeed caused by the value being passed as text.

 

I'm using Perl and LWP::UserAgent as my interface to the APIs.

 

The price value was derived from a PostgreSQL field of type numeric(5,2), but that seems to be stored internally in Perl as a text value rather than a double, which I hadn't realised before. This isn't visually apparent if you print the value as debug output. When converting to JSON the encoder was surrounding the value in quotes. Doing a debug print of the encoded JSON  immediately shows the problem.

 

The UCRM API validator must be especially strict, as I've been using this PostgreSQL numeric(5,2) type with JSON for nearly 10 years and never hit a problem before when passing to APIs from other vendors. I guess other vendors are simply checking that the value evaluates to a numeric type irrexpective of whether the source is numeric or text.

 

 

Reply