Upgrade failure - I think

[xlurkr]

I just tried to upgrade my backup Polisy to 6.0.  I pulled it from storage and connected it, and the Launcher found it, but it said that I needed to upgrade to isy 6.0.  This is even though my main Polisy is still there, and still on 5.9.1.  Weird.  I said "no", and it exited.  Connected again from Launcher.  This time I said "yes", and it presented me with some kind of "don't interrupt" dialog, then exited, and the Polisy beeped a few times.  Since then, the Launcher is unable to find it, though it still finds the main Polisy and launches the AC on it just fine.

I don't know what to do next.  I can't launch the AC to start the upgrade on the backup Polisy.  When I ssh into it, it says it's still on FreeBSD 14.1, and the isy service isn't running.  So I guess that's why the Launcher can't find it, but how do I upgrade if I can't launch the AC?

-Tom

[xlurkr]

p.s. I followed all the recovery steps in the release announcement, but I can't get the isy service to start.  It also says the interface re0 does not exist.

-Tom

[Guy Lavoie]

Log in with ssh and do the "df" command to show the disk apace, and post a picture of the screen.

[xlurkr]

[xlurkr]

I doubt this has anything to do with the "small image size" issue.

I really don't understand why I was asked to upgrade to 6.0 when I connected via the launcher.  I haven't read anything about that anywhere.  And why doesn't it do that with my main Polisy?  The release notes suggest that the upgrade requires manually clicking "upgrade packages" in the AC.

-Tom

[Guy Lavoie]

That looks good, so it's not a messed up filesystem. 

1 minute ago, xlurkr said:

I doubt this has anything to do with the "small image size" issue.

I really don't understand why I was asked to upgrade to 6.0 when I connected via the launcher.  I haven't read anything about that anywhere.  And why doesn't it do that with my main Polisy?  The release notes suggest that the upgrade requires manually clicking "upgrade packages" in the AC.

-Tom

Normally when the upgrade finishes, it prompts you to reboot. See that at all?

 

[xlurkr]

Nothing is happening, and since I can't launch the AC, I don't know how it would tell me to reboot.

-Tom

[Guy Lavoie]

So you tried the recovery in the announcement:

sudo rm /var/udx/.udx_install_cleanup
sudo rm /var/udx/.upgrade_status
sudo pkg install -f isy
sudo service udx restart

The recovery instructions are written for a eisy, so it's normal that the interface re0 would not exist. For the polisy, that would be igb0 instead, so:

 

sudo dhclient igb0
sudo service udx restart

But first, what did you see when you did:    sudo pkg install -f isy  ?

[xlurkr]

I have a ticket in, and it wouldn't surprise me if UDI intervention will be required.  The system is responsive via ssh, it's still on FreeBSD 14.1, I don't think there's any upgrading going on, and for some reason their documented recovery steps don't get the isy service to start, or the Launcher to let me launch the AC.  So for the moment, it's a fully functional FreeBSD computer and a fully useless Insteon and home automation controller.  But I have faith.  At least it's more than a brick!

-Tom

[xlurkr]

Posts crossed.  Yes, I did all those steps, and thanks for explaining the re0 thing.  I'm assuming that just clears up IP addressing problems, but my Polisy has maintained the same address the whole time, and I have always been able to reach it via ssh.

Many messages scroll by when doing the pkg install and udx restart, and some of them look like error messages.

-Tom

[xlurkr]

I just tried it again.  The "pkg install" command doesn't have any error messages and installed one package - the rest were already there.  It's the udx restart that has the error messages - something about needing to use the -H flag when running pip via sudo, and a pkg named "serial" not found.

isy service still not running.  According to Michel's recovery instructions, it must start for the Launcher to find my Polisy, and let me launch the AC, and finish the upgrade by clicking on upgrade packages?

-Tom

[Guy Lavoie]

1 minute ago, xlurkr said:

Many messages scroll by when doing the pkg install and udx restart, and some of them look like error messages.

-Tom

It would be helpful to see what those are. Ok, dusting off some old unix tricks here... redo the pkg install as follows:

  sudo pkg install -f isy >/tmp/log 2>&1

This redirects standard output and error output to a log file (/tmp/log). Because screen output is being redirected to a file, you won't see the prompt for the admin password, so just type it in blindly about 3 seconds after starting the command. You also won't see the "do you want to proceed" question, so after about a minute, just type "y" and enter. When the prompt comes back, you can view the output in the /tmp/log file, and post it here.

[Guy Lavoie]

5 minutes ago, xlurkr said:

I just tried it again.  The "pkg install" command doesn't have any error messages and installed one package - the rest were already there.  It's the udx restart that has the error messages - something about needing to use the -H flag when running pip via sudo, and a pkg named "serial" not found.

isy service still not running.  According to Michel's recovery instructions, it must start for the Launcher to find my Polisy, and let me launch the AC, and finish the upgrade by clicking on upgrade packages?

-Tom

I also get the warnings about the polyglot owner not being right, the -H option, and a pkg names serial not found when doing a udx restart, but I can still log with with admin console.

[xlurkr]

No offense, but I think I'm going to wait for a response to my ticket at this point.  I promise I'll come back and post whatever I learn from UDI about what the problem was and how they fixed it.

Looking at my old posts, and some of yours and larryllix's I get the sense that they have a tendency to leave out a step or two in their automated upgrade procedures for Policys.  Understandable, if all they have and use these days are Eisys.

-Tom

[xlurkr]

btw, I should document for future posterity that your modified command for getting a new (different) dhcp lease did work for me, but since I was connected via ssh on a Polisy and not keyboard/monitor on an Eisy, as MIchel's instructions assume, I lost the connection, had to get my router to tell me the new address, establish a new connection to be able to restart udx again, only to still find that the isy service didn't start.  Kinda illustrating my point about how we Polisy owners are a bit of an afterthought.

-Tom

[Guy Lavoie]

I'm confident that UDI will get you running again soon, since your Polisy is booting up and is getting a network address. Yes, do tell us what it ends up being. I have two Polisys here running 6.0.0 so it definately works.

[larryllix]

3 hours ago, Guy Lavoie said:

I'm confident that UDI will get you running again soon, since your Polisy is booting up and is getting a network address. Yes, do tell us what it ends up being. I have two Polisys here running 6.0.0 so it definately works.

Both my Polisae work fine now but I re-imaged both of my Polisae.
I am not sure I needed to do that or buy a larger SSD either. I don't see any SSD crowding or excessive usage of RAM on either.

However, I did discover the long way around to login with my email address instead of "admin". I suppose that is what the obscure message to use ISY Portal login meant. 

In the end I believe that the update attempted to increase the partition size of existing Polisae SSDs and it messed up on most of them, maybe the older units?

[xlurkr]

6 minutes ago, larryllix said:

However, I did discover the long way around to login with my email address instead of "admin". I suppose that is what the obscure message to use ISY Portal login meant. 

@larryllix:

I saw you mention this in another thread.  In what place and at what time are you referring to this login?

As I said above, I plugged in my Polisy, the Launcher found it, and I clicked on its entry and attempted to launch the AC.  Without any login request appearing, it told me that I needed to upgrade to 6.0.  As I wrote, the first time I clicked no, and it terminated.  The second time I clicked yes, and it threw up a dialog warning not to interrupt it.  I dismissed it and my Polisy beeped a few times.  Since then, I can't get Launcher to find it, which I assume is because the isy service isn't starting.  Where can I log in with my email address?

-Tom

[larryllix]

9 minutes ago, xlurkr said:

@larryllix:

I saw you mention this in another thread.  In what place and at what time are you referring to this login?

As I said above, I plugged in my Polisy, the Launcher found it, and I clicked on its entry and attempted to launch the AC.  Without any login request appearing, it told me that I needed to upgrade to 6.0.  As I wrote, the first time I clicked no, and it terminated.  The second time I clicked yes, and it threw up a dialog warning not to interrupt it.  I dismissed it and my Polisy beeped a few times.  Since then, I can't get Launcher to find it, which I assume is because the isy service isn't starting.  Where can I log in with my email address?

-Tom

Most of the time I have had to manually type in my URLs for my Polisae. They are seldom found by any of the finder apps that have been released.

If, and when, the finder app finds your Polisy then you would use the same credentials you use for your ISY Portal login. In my case this was my email address, not "admin". This is in the usual IoX Finder login box with User: and Password: after you click the URL in the Finder.

I had a lot of trouble with this. My Polisy was not producing it's UUID,  (was 00:00:00:00:00:00) and then nothing would find it. After switching my SSD from one box to another I suspect I may have not plugged in the dual header security module properly. IIRC that would cause this.

If you didn't have your Polisy box apart this wouldn't apply to you.
 

Edited 15 hours ago by larryllix

[xlurkr]

OK.  While the Launcher has at times failed to find one or more of my Polisy automatically, it has never failed when I used the add button and put the address in manually.  Until now.  And never have I had to use portal credentials to log in.

-Tom

[Guy Lavoie]

I notice that when you log into with the launcher, the login box actually tells you what login to use. On both of my test units (both Polisy) the box has the User ID and Password fields, and underneath it tells me "Use your IoX userid/password". I imagine that for those who now log in with their portal credentials, it must tell you to use those instead? Because not everyone has portal subscriptions.

[xlurkr]

The one I was upgrading had a lapsed portal subscription, but I hope that didn't have anything to do with the failure.

btw, Michel got back to me and told me to flash it.  I have the USB device from back when they all had to be flashed if they had the old FreeBSD version, but I'd rather try anything else first.  Anyone have any suggestions?

-Tom

[Guy Lavoie]

No, if Michel tells you it needs flashing, then that's your next step. That's a more extreme solution because you're not recovering anything, so if you have no backups, this really sets you back.

About the portal subscription or not and my login screen comment above: I might have a bit of an exception here. I have two Polisy units, that I use for testing and learning. Polisy 1 has a few test nodes defined on it, and a lapsed portal subscription. Polisy 2 is one that I got recently, given to me for free by a generous forum member. He said it was messed up, it wouldn't even boot up. I ended up getting an image file from UDI and buying the needed USB adapter card to enable flashing the SSD using Rufus. That worked...I think. As I posted in another thread, it was seemingly working fine, and I picked that one to try the 6.0.0 upgrade. Well the upgrade failed (it stayed at 5.9.1) and when I started checking it out, I had the same issue as @apostolakisl: a 3 GB filesystem and the upgrade was failing due to disk being full. I haven't proven it but my thinking was that maybe I made a mistake when using Rufus to flash it's SSD. Well ok, so then I tried the upgrade on Polisy 1. That worked great. So I had an idea: make an image file of the SSD of Polisy 1 using Rufus, then I used that image file to reflash Polisy 2. So now I had a clone of Polisy 1 running fine on Polisy 2. Already upgraded to 6.0.0 too.

Now back to the portal subscription thing: Polisy 2 was eligible for the free 1 year portal trial subscription (the previous owner had never subscribed), which I enabled. Works fine. Portal access is up and running on it. But, it was running an image of Polisy 1, which had a lapsed portal subscription. The 6.0.0 upgrade process was done on that unit, then the image copied over to Polisy 2. So the 6.0.0 upgrade process must check if you have an active portal subscription, and configure the Admin console login to use the usual IoX login and password if you have no portal subscription, or use your portal credentials if you do. Since the upgrade had been done on a no subscription unit and then copied over, Polisy 2 is having me log in using the IoX login and password, but still has a working portal subscription.

I'm sure there must be a simple configuration file somewhere that tells the admin console login program which user name and password (IoX or portal) to use, and that could be easily changed to use one or the other.

[xlurkr]

17 minutes ago, Guy Lavoie said:

so if you have no backups, this really sets you back.

Fortunately, this is a spare unit, and it had no devices, programs, etc.  So I guess I'll reimage, check the size of the image, and try to upgrade again.  I might as well reenable the portal subscription, too: it doesn't cost much, goes to a company with great support, and would allow me to do more kinds of tinkering if I leave this unit in service.

-Tom

[larryllix]

2 hours ago, xlurkr said:

Fortunately, this is a spare unit, and it had no devices, programs, etc.  So I guess I'll reimage, check the size of the image, and try to upgrade again.  I might as well reenable the portal subscription, too: it doesn't cost much, goes to a company with great support, and would allow me to do more kinds of tinkering if I leave this unit in service.

-Tom

If you get supplied with the file poilsy_14.3p3.img then your polisy SSD will be at the current V6.0.x when it boots up.
Watch your credentials on the IoX Finder, set time zone, options, etc.  and reboot.

Edited 6 minutes ago by larryllix