larryllix

See (to fix)

Seems to be the winner for me! The pkg utility version was the snag. Despite all the rrors the system threw at me it seemed to upgrade it and made all the other upgrades possible. sudo pkg install -r udi pkg After that, I reset udx and isy, and then ISY booted properly, finally. sudo service udx stop sudo service udx start sudo service isy restart I remembered some of the last ticket help with @Michel Kohanim how udx controlled the UUID assignment (mine was coming up 00.00.00.00.00.01) and the outdated pkg utility was prevented it from installing the newer packages. Thanks all! /Panic off

Thanks. already been done many times now. Best was service stop service start of each udx, isy polyglot Mongol that got me up with an actual UUID but after few minutes the UUID collapses again to 00.00.00.00.00.01 again and Insteon, and all i/o stops functioning again. This thing is just continuously crashing. Power cycled several times and clicked update several times now. May have to try my spare polisy or return to my ISY for the third time. Sent from my SM-G781W using Tapatalk

It seems the update package is permission locked. [admin@polisy ~]$ sudo pkg install -r udi pkg Password: Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. New version of pkg detected; it needs to be installed first. The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pkg: 1.18.4 -> 1.19.0 [udi] Number of packages to be upgraded: 1 8 MiB to be downloaded. Proceed with this action? [y/N]: y [1/1] Fetching pkg-1.19.0.pkg: 100% 8 MiB 8.6MB/s 00:01 Checking integrity... done (0 conflicting) [1/1] Upgrading pkg from 1.18.4 to 1.19.0... [1/1] Extracting pkg-1.19.0: 100% Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. process with pid 17542 still holds the lock process with pid 17542 still holds the lock process with pid 17542 still holds the lock pkg: Cannot get an advisory lock on a database, it is locked by another process [admin@polisy ~]$ [admin@polisy ~]$ sudo pkg install -r udi pkg Password: Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. New version of pkg detected; it needs to be installed first. The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pkg: 1.18.4 -> 1.19.0 [udi] Number of packages to be upgraded: 1 8 MiB to be downloaded. Proceed with this action? [y/N]: y [1/1] Fetching pkg-1.19.0.pkg: 100% 8 MiB 8.6MB/s 00:01 Checking integrity... done (0 conflicting) [1/1] Upgrading pkg from 1.18.4 to 1.19.0... [1/1] Extracting pkg-1.19.0: 100% Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. process with pid 17542 still holds the lock process with pid 17542 still holds the lock process with pid 17542 still holds the lock pkg: Cannot get an advisory lock on a database, it is locked by another process [admin@polisy ~]$

After mine rebooting and showing v5.5.0 it has now crashed and shows v5.4.5 with UUID:00.00.00.00.01 ISY Portal cannot find it. Currently running sudo reboot again. UPDATE: IoX Finder found proper UUID but would not launch Admin Console after IoX refresh now shows UUID 00.00.00.00.00.01 and now launches IoX but System Busy will not go away.

Modulus arithmetic is still defective and hasn't supported decimal fractions since v5.0.1. Notification customisations still hasn't been fixed as reported the last three or four versions. Selection menus also fail occasionally.

Interesting how these tags can remember eons of data updates internally but when the server goes down there is just permanent holes. Do the Tags only get one shot at updating their data and then the memory is cleaned out or does the Tag server just not bother recouping missing data? Am I missing some refresh cycle process to get missing data?

Mine are missing all data from 3:04 AM to 12:55 PM today.

Tag server down from Dom. Rep. also. Sent from my SM-G781W using Tapatalk

@Michel Kohanim

Yeah. Went from the great wide open to tight spaces 26 floors up with lots of city lights. Back to my roots.

I had my Tag Manager do that about 8 months ago once. Haven't seen it again since but mine have been reduced from 8 units down to three units at the moment, and they are not connected into my ISY anymore. I have never used the Tag NS either, except to test it before PG3 existed. Note location change. I don't drive past your door anymore.

Mine all look fine from Dom. Rep.

I thought the migration software was complete. I moved mine when there was more mess than savings over to polisy. However, all is good living on the polisy exclusively. Much faster but a few outstanding quirks yet. Sent from my SM-G781W using Tapatalk

Sound slike the classic non-technical management micro-managing things. When things get tough they make it cheaper and eventually the product is crap. Wrong path.

Sounds like a barrel connector should be installed and use external power supply adapters to feed it that can be replaced every few years and protect/isolate the grid power from the electronics. Oh yeah, the grid signals would require some passthrough...hmmmmm.

Oh Jeeezzzz! I never thought of that! I love the support in this group.

Since a good portion of us live close to this repair guy, we could ship to, and then drive over to pick it up again. Would be several days faster and also save a shipping fee. Square One would be a side trek making it more worth while. Tell the wifely you are taking her shopping. Maybe the guy would try same day service with a shopping mall gap in the timing??

I think mobilinc totally captured the datastream and therefore didn't play well with polyglot and ISY portal. It became one or the other. I believe that is why it has settled where things current are. ISY software paraphernalia doesn't have a large user base and it just became too much work for a small software writer to keep up the work required for no money. Sent from my SM-G781W using Tapatalk

I would think an overall, high level comm success would be the best to start. The most important factor is to gather attention from the user that something isn't functioning. Then where and why is up to the user to find by troubleshooting, if they have the tech skills, or gain assistance from more techie people. Sent from my SM-G781W using Tapatalk

@bmercier My Alexa is complaining about no contact with ISY Portal again also. ooops...didn't see you were on it already.

Have you done a Restore on the device from the Admin Console yet? Sometimes specific links get deleted or confused.

Look in the Admin Console|Configuration tab for later polisy versions. The SSH method doesn't function any more.

Another problem with this is [[SMTP ERROR--1]] is undocumented and offers no explanation of how to resolve it for the user. Other error numbers 2.... are documented.

@bmercier already responded several times. These occurrences have been very rare over the last 3 or 4 years. Sent from my SM-G781W using Tapatalk