3.0.14 wont start

[macjeff]

It said an update is needed.  I was on 3.0.13.  I did the restart method and waited.  

It installed (or it said it did) but never restarted.  I get an error in the logs.  If I hit start it will say already running.  If I wait a couple minutes I can hit start and it says started successfully but then the error comes back in log. 

It was working fine.

I tried doing a manual reinstall but same issue.  (go to store, click install, and click the reinstall same slot button)

Log Attached

Kasa_11-16-2022_63106-AM.zip

[macjeff]

it does show I have 3.0.14 now.  It just wont start up.

I will do an erase and install later if you say to.   Except for a few programs, this Node server is very simple to reinstall

 

[Jimbo.Automates]

For some reason the PG3 MQTT connection is failing, I asked @bpwwer for help

2022-11-16 06:30:19,320 MQTT       udi_interface.interface ERROR    interface:_connect: MQTT Failed to connect, invalid identifier

It's possible there are two copies running, log into your Polisy and run:

ps -uax | grep kasa

You should only see one kasa line like this:

polyglot 90285   0.0  1.2 107180  51788  -  I    06:16        0:09.53 python3 ./kasa-poly.py (python3.9)

If you see more, then run "kill n" for each, where n is the process Id from second column.
 

[macjeff]

I will do this later on today but I can’t do now

[macjeff]

I have

polyglot  5729   0.0  1.3  102320  51952  -  I    Tue07       1:02.36 python3 ./kasa-poly.py (python3.9)
admin    31538   0.0  0.1   12840   2420  0  S+   14:55       0:00.01 grep kasa

I might be doing something wrong but did

kill 31538 and it says no such process

what am I missing?

[macjeff]

would a Pg3 reboot fix?

[Jimbo.Automates]

1 hour ago, macjeff said:

I have

polyglot  5729   0.0  1.3  102320  51952  -  I    Tue07       1:02.36 python3 ./kasa-poly.py (python3.9)
admin    31538   0.0  0.1   12840   2420  0  S+   14:55       0:00.01 grep kasa

I might be doing something wrong but did

kill 31538 and it says no such process

what am I missing?

You can't kill the grep that command is done.  But that does look fine, I expected to see 2 kasa-poly.py lines.

Can you "kill 4728" then try to start the NS and watch the log for errors?

 

[bpwwer]

The PS shows the kasa node server has been running since sometime on Tuesday.  So it was running when you tried to restart it today.  However, for some reason PG3 thinks it is not running. That's why you got the message that it wasn't running when you tried to restart it.

When you re-installed it, it started the kasa node server (copy 2) but PG3 rejects it's attempt to connect because copy 1 is still connected.

If you kill copy 1 (4728), it will disconnect from MQTT and if copy 2 is still attempting to connect, it will succeed.  If not, it should now start by either pressing Start or Restart. 

[Jimbo.Automates]

Thanks @bpwwer ! I didn't notice the date.

And @macjeff Please don't always resort to "reinstall", that should rarely be needed, and when you do that it makes debugging the original issue more difficult.

 

[bpwwer]

2 minutes ago, Jimbo.Automates said:

Thanks @bpwwer ! I didn't notice the date.

And @macjeff Please don't always resort to "reinstall", that should rarely be needed, and when you do that it makes debugging the original issue more difficult.

The current auto-upgrade process in 3.1.14 is buggy which is why I think he resorted to a re-install.  But that's good advice in general.

[macjeff]

3 hours ago, bpwwer said:

The current auto-upgrade process in 3.1.14 is buggy which is why I think he resorted to a re-install.  But that's good advice in general.

Yes.  Restarting does not work at all.  The reinstall is the only way I have been able to update recently.  I have reported the bug and waiting for the fix.

I am running now fine on KASA.  Just had to reboot PG3

[macjeff]

3 hours ago, bpwwer said:

The PS shows the kasa node server has been running since sometime on Tuesday.  So it was running when you tried to restart it today.  However, for some reason PG3 thinks it is not running. That's why you got the message that it wasn't running when you tried to restart it.

When you re-installed it, it started the kasa node server (copy 2) but PG3 rejects it's attempt to connect because copy 1 is still connected.

If you kill copy 1 (4728), it will disconnect from MQTT and if copy 2 is still attempting to connect, it will succeed.  If not, it should now start by either pressing Start or Restart. 

Nothing worked.  Start or restart would show up 1, 2, 3, 4 and by the time it hit 5 seconds it would stop counting but would still say connected.

I did a reboot of pg3 and now ok.

[Jimbo.Automates]

Nothing worked.  Start or restart would show up 1, 2, 3, 4 and by the time it hit 5 seconds it would stop counting but would still say connected.
I did a reboot of pg3 and now ok.

Did you watch the log while restarting? You will see it get stopped if it was running, and then after a while, possibly a couple minutes depending on what needs upgrading, it will show that it is starting.

Also, it looks like there is a bug, if you press restart while a restart is still in progress you will end up with an orphaned Node server. Bob is looking into it. That was part of your problem.


Sent from my Pixel 6 Pro using Tapatalk

[macjeff]

yes.  It would stop on the MQTT error.

7 hours ago, Jimbo.Automates said:

Did you watch the log while restarting? You will see it get stopped if it was running, and then after a while, possibly a couple minutes depending on what needs upgrading, it will show that it is starting.

Also, it looks like there is a bug, if you press restart while a restart is still in progress you will end up with an orphaned Node server. Bob is looking into it. That was part of your problem.


Sent from my Pixel 6 Pro using Tapatalk
 

 

[Jimbo.Automates]

13 hours ago, macjeff said:

yes.  It would stop on the MQTT error.

That shouldn't have happened if you manually killed the process.