Update failed! Check polisy logs for details.

[Ross]

My first post.

When I "Check for Polisy Updates" under System, it says "Update Check complete. 100 packages available for update. Click the "Update Polisy" button to start."

When I click on "Update Polisy" under System, it says "Update failed! Check polisy logs for details."

Unfortunately, I'm not smart enough to understand the logs.  Please see the attached.

Seems there are users here who are quite advanced and others who want plug and play.  I'm more to the latter but willing to learn.

Thank you for your assistance,

Ross

 

Polisy Log 2020-03-25.txt

[Bumbershoot]

I don't think you want a Polyglot log, but a Polisy log, which you can find in '/var/log/messages'. 

I updated my Polisy yesterday and found that the FreeBSD update servers were getting absolutely clobbered (lots of people home with time on their hands these days), as the updates aren't specific to UDI but to FreeBSD in general.   A lot of packages were upgraded from FreeBSD 12.1_2 to 12.1_3.  I don't think there's anything that will cause you to see a noticeable improvement in Polisy performance, and generally, serious security issues will be patched piecemeal instead of waiting for a more generalized upgrade such as this one, though to be honest, I don't follow FreeBSD development.

If you're command line savvy, then you can always SSH into your Polisy and run this:

sudo pkg update && sudo pkg upgrade

I suspect that the likely cause of your failed update was server timeouts.  Too many people trying to update...

[DennisC]

I have not had much success with updating Polisy from within. I find it fails most of the time and I need to SSH in and run sudo pkg update && sudo pkg upgrade.

 

[Ross]

Bumbershoot & DennisC,

I was not command line savvy this morning and I wouldn't claim that I am now.  But, I figured out I needed PuTTY, downloaded it, typed in your command and it worked.

So, move me just a bit off the total newbie rung but there's much for me to learn here.

Thank you for your help.

[Bumbershoot]

@Ross, glad the update worked for you.  Under normal circumstances the "Update Polisy" menu item will most likely work.  It's nice to learn a new trick, though.

[asbril]

At the bottom of my Polisy Dashboard there was a message instructing me to update to 2.2.10 . I (think that I) followed the instructions, including a restart of Polyglot, but Polisy remains on 2.2.9.5

[Jimbo.Automates]

At the bottom of my Polisy Dashboard there was a message instructing me to update to 2.2.10 . I (think that I) followed the instructions, including a restart of Polyglot, but Polisy remains on 2.2.9.5

That is a known issue, the update is done by pkg now so use the top menu to check for and install updates.

Sent from my Pixel 3 XL using Tapatalk

[asbril]

6 minutes ago, Jimbo said:

That is a known issue, the update is done by pkg now so use the top menu to check for and install updates.

Sent from my Pixel 3 XL using Tapatalk
 

Weird, when I click on check for Polisy updates, it no longer tells me that there no updates or X updates. Even when I reboot Polisy anyway, it still remains on 2.2.9.5

 

[Jimbo.Automates]

Weird, when I click on check for Polisy updates, it no longer tells me that there no updates or X updates. Even when I reboot Polisy anyway, it still remains on 2.2.9.5
 

Uncheck the use beta options in settings, I guess the install updates doesn't understand the beta option yet. Need @einstein.42 help.

Sent from my Pixel 3 XL using Tapatalk

[larryllix]

25 minutes ago, asbril said:

Weird, when I click on check for Polisy updates, it no longer tells me that there no updates or X updates. Even when I reboot Polisy anyway, it still remains on 2.2.9.5

 

There are no further updates to 2.2.9-5. When I click on update checks it reports there are two more updates and goes through some song and dance but the version number has never changed for a few months now.

This has never worked for me from the Polisy admin panel, only from the polisy command line so far.

[Jimbo.Automates]

2.2.10 was.released to beta yesterday.

Sent from my Pixel 3 XL using Tapatalk

[macjeff]

I had the 2.2.10 beta also but cant get it to install.   It comes up in Polisy and says its installed but others have pointed out, when it reboots its still on the release version.  See screenshots.

I had this happen before and had to do update via SSH

I tried SSH but I think I need a different command to bring in the beta because it shows no updates.

 

Welcome to Polisy!
[admin@polisy ~]$ sudo service polyglot stop
Password:
Stopping polyglot.
[admin@polisy ~]$ sudo service udx stop
Stopping udx.
Waiting for PIDS: 1661.
[admin@polisy ~]$ sudo pkg update
Updating FreeBSD-base repository catalogue...
FreeBSD-base repository is up to date.
Updating udi repository catalogue...
udi repository is up to date.
All repositories are up to date.
[admin@polisy ~]$ sudo pkg upgrade
Updating FreeBSD-base repository catalogue...
FreeBSD-base repository is up to date.
Updating udi repository catalogue...
udi repository is up to date.
All repositories are up to date.
Checking for upgrades (0 candidates): 100%
Processing candidates (0 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.
[admin@polisy ~]$ sudo service polyglot start
Starting polyglot.
[admin@polisy ~]$ sudo service udx start
Starting udx.
[admin@polisy ~]$ ls
[admin@polisy ~]$ polyglot -v
-bash: polyglot: command not found
[admin@polisy ~]$ LS
-bash: LS: command not found
[admin@polisy ~]$

 

[Jimbo.Automates]

Turn off the beta firmware option in settings, then you won't get the notice until it goes to production which should be soon.  The only change is a new version of the aedes mqtt broker which has resolved the problem that only seemed to happen to me 

 

Doing the update from the Polyglot menus or manually running pkg update will not move you to beta.  If you really must try it then

sudo pkg install polyglot-beta

BUT I have no idea if this will cause any issues down the road, need @Michel Kohanim or @xKing to say if that is okay for anyone to use.

[macjeff]

On 4/10/2020 at 2:28 PM, Jimbo said:

Turn off the beta firmware option in settings, then you won't get the notice until it goes to production which should be soon.  The only change is a new version of the aedes mqtt broker which has resolved the problem that only seemed to happen to me 

 

Doing the update from the Polyglot menus or manually running pkg update will not move you to beta.  If you really must try it then

sudo pkg install polyglot-beta

BUT I have no idea if this will cause any issues down the road, need @Michel Kohanim or @xKing to say if that is okay for anyone to use.

I asked UDI support the same question but if I go to beta and have an issue can you go back.

Right now still on 2.2.9-5

I cant update internally as I posted earlier.  I had the same issue when I went to 2.2.9 release but was able to easily do it from SSH which is not an issue since it only updates once and a while.   I think the problem is for some reason on my network I cant go to admin@polisy    I have to go to admin@ "INTERNAL IP"

anyways... if I run the command that Jimbo posted in the quote above, what command do I run to go back?  Or can you go back?

I love running betas and helping find bugs (And getting new features and fixes even though they come with new bugs) but I always like to be able to roll back if needed.

[xlurkr]

Is there a thread that has version release notes in it like there is for the ISY?  I can't find one.

Also, why has no one from UDI commented (at least lately) on why the menu-based update mechanism keeps breaking, and when they are going to fix it?  Logging in and running commands isn't beyond my capability, but it is beneath my expectations, error-prone (potentially catastrophically), and falls short of the advertised robustness and simplicity of the Polisy.  If I'd wanted a Pi, I would have bought one.

-Tom

[jfai]

The update of Polisy using the System menu has worked for me the last half dozen times. No issues.

[xlurkr]

Like the OP, I have a hundred updates pending, according to my Polisy.  I get the same update failure message.  And I'm currently on 2.2.8.

-Tom

[macjeff]

I am on 2.2.9.5 (release version) and just ran all updates just fine.  

 

[gviliunas]

When this happens to me (not in several months though), I Login to Polisy via Putty (ssh) then:

sudo pkg update && sudo pkg upgrade.

When this finishes,

sudo reboot

[xlurkr]

Thanks gviliunas.  I have seen your helpful posts before.  I'm asking UDI to fix this so one need not log in and execute superuser commands.  I don't think it's an outrageous request.

If I find out that there is no other recourse, I will do it.  Perhaps it's the price of being an early adopter, and I will never need stray outside of the menu system ever again.  But I  need some convincing.

-Tom