Notification

Michel Kohanim · May 23, 2019

What do you mean exactly?

With kind regards,

Michel

Bert2013 · April 29, 2020

Hi,

I think Michel was wondering about the 815 (MAX Subscribers Reached).

I actually hit that problem also, on and off. And a reboot is the only way out, as far as I know. And I have seen someone else on the forum complaining about this also.

What I do is to create a subscription. If the subscription seems broken, I close it and re-subscribe. I decide that the subscription is broken when heartbeats are missing and/or variable updates are not being reported via the event stream. Once in a while, I end up with and ISY subscription state like this:

</Subscriptions>

Note that even the portal is not subscribed anymore. This state persists until I reboot the ISY.

This is what I think is contributing to the problem:

- I believe that the ISY must be bogged down to start the chain of events leading to this problem. I have seen heartbeats missing for 3 minutes.

- When my program decides to unsubscribe and resubscribe, the ISY might return 817 (already subscribed). My program treats 817 and a failure; can I do something better?

- Even though my program spaces out the retries (30 seconds or so), the ISY doesn't seem to be able to recover and gets stuck in the 'max subscribes reached'.

Any insight is appreciated.

Bert

Michel Kohanim · April 30, 2020

Hi @Bert2013,

At this state, what happens if you try to unsubscribe? You get 817? That does not make sense ... can you try again?

With kind regards,
Michel

xlurkr · May 17, 2020

I'm getting this state, immediately after rebooting:

<?xml version="1.0" encoding="ISO-8859-1"?>
<Subscriptions>










</Subscriptions>

Is this expected?

-Tom

Michel Kohanim · May 17, 2020

Tom,

Except for the Admin Console, what other clients are connecting to ISY?

With kind regards,

Michel

xlurkr · May 17, 2020

AFAIK, just CQC. I'll shut it down and retry.

-Tom

xlurkr · May 17, 2020

@Michel Kohanim:

I just shut down CQC and rebooted the ISY. I get the same response.

Maybe this is what it's supposed to say? Does it always return a list of 10?

I'm trying to get the latest PyISY example program to run. It starts out OK by dumping the node list, but then it's supposed to stay in a loop where it reports events. Instead, it keeps telling me it has reached the subscription limit, then disconnects for 60 seconds and tries again, over and over. Sounded similar to what's going on here, so I thought I'd reply

.We're trying to figure out what's wrong. The thread is over here:

xlurkr · May 17, 2020

Another similarity to this thread is that I do have some legacy web server code on the ISY. It was written long ago as an interface to the ISY - you put your lights in the old rooms interface and this web server dished up a graphical representation for controlling your lights. I forget what it was called, but Michel, you might remember. I don't access it anymore, however, because somewhere along the line a firmware update broke it. But I can remove it if you think it would help.

-Tom

xlurkr · May 17, 2020

TouchSwitch is the ISY web app I have.

-Tom

Michel Kohanim · May 18, 2020

@xlurkr,

It could be any of those. But, if you shutdown CQC and you still have the same issue, then it's not CQC.

With kind regards,
Michel

xlurkr · May 18, 2020

@Michel Kohanim:

Could you check out the other thread I referenced above? We're trying to get the PyISY code and example program to work, and it keeps failing with max subscriptions reached.

-Tom

Michel Kohanim · May 19, 2020

@xlurkr,

Not really sure what I am checking out. I had already read your post fully before. The only thing I didn't answer is: yes, it will return 10 all the time. The bottom line is this: something is subscribing to ISY but it's not releasing the subscription. Not really sure how to debug this except shutting things down one at a time and see whether or not there are any improvements.

With kind regards,
Michel

xlurkr · May 20, 2020

@Michel Kohanim:

OK, thanks. I think I'll make a private network with just the ISY and my laptop and reboot the ISY to see what happens then.

What should the 10 lines look like if no one is subscribed to the ISY? The lines I copied above were what the ISY returned literally seconds after rebooting.

-Tom

xlurkr · May 22, 2020

@Michel Kohanim @shbatm:

Today I disconnected my ISY from the rest of my network and made a private network with just my laptop and the ISY. I rebooted it, connected via the console, and got the following response back from /rest/subscriptions:

<?xml version="1.0" encoding="ISO-8859-1"?>
<Subscriptions>










</Subscriptions>

I launched PyCharm, and ran the PyISY connection_test.py program. It timed out like before, with the too many subscribers error. I power-cycled the ISY and repeated, except this time I didn't launch the console. I got this:

<?xml version="1.0" encoding="ISO-8859-1"?>
<Subscriptions>










</Subscriptions>

connection_test.py kept timing out as before.

Seems to me, either the program is doing something wrong, or there's something about the state of the ISY that's out of whack, causing the program to fail to subscribe.

Michel, are the responses above what I should expect if nothing is trying to subscribe to the ISY? What is the normal line that should be returned from a freshly-restarted ISY?

-Tom

simplextech · May 22, 2020

Do you have the Network Module?

xlurkr · May 22, 2020

Yes. Why?

-Tom

simplextech · May 22, 2020

8 hours ago, xlurkr said:

Yes. Why?

-Tom

Just checking. I've seen errors, problems when people try to setup connections or even Polyglot and do not have the ISY Network Module (it's required) and spend lots of time troubleshooting and then it comes down to no they actually don't have the network module.

Michel Kohanim · May 22, 2020

@xlurkr,

You got that error when /rest/subscription returns this:

<?xml version="1.0" encoding="ISO-8859-1"?>
<Subscriptions>










</Subscriptions>

With kind regards,
Michel

xlurkr · May 22, 2020

@Michel Kohanim:

I still don't know if what /rest/subscriptions is returning is what you would expect on a just-rebooted ISY with no subscribers. Is it? If not, what should I be seeing, and what do you recommend I do to return it to that state?

-Tom

Bert2013 · May 23, 2020

Hi Michel,

Going back to my comment/question from April 29.

I probably was not clear enough.

Most of the time, if a subscription is 'bad', I unsubscribe and resubscribe successfully. And the ISY behaves properly.

Sometimes (every 4 months or so), the ISY doesn't behave properly and the result is that the ISY runs out of subscriber slots and never reclaims them (i.e. I wait for 12 hours without any change in the ISY subscriber state), forcing me to reboot. This "not behaving properly" is accompanied by errors 817 from subscribe, which I don't know what to do with except to treat it as a failed subscribe and try again. It is also accompanied by the ISY being very busy to the point that heartbeats are missed for up to 3 minutes.

Is there anything better I can do with error 817?

Also, I got into the same bad situation today again. The interesting thing is that I noticed "out of memory" in the summary page of the programs.I didn't find a clear answer in the forum, but I deleted a bunch of programs and any "out of memory" is gone now. After that, I got into the bad situation where the ISY doesn't reclaim subscription slots. So I suspect that this problem is somehow related to the "out of memory". Note that my usage is not excessive compared to what I read in the forum: I have about 200 PLM links, 180 programs, 250 (sub)devices (insteon, zwave, nodeserver items)

Interestingly, the Admin Console also got "already subscribed" error, so it doesn't know what to do with that error either...

I'm rebooting my ISY now.

Your insight is appreciated.

Bert

xlurkr · May 23, 2020

@Bert2013:

If Michel won't answer, can you help me? You've seen what /rest/subscription is returning on my ISY. Would you expect it to throw an error if PyISY attempted to subscribe? Can you tell me what /rest/subscriptions should return if there are no subscribers? So far, all I've gotten is people asking me to provide the information, and telling me (I think) that I shouldn't be seeing what I'm seeing, without telling me what's wrong with the response, what a correct response looks like, and most importantly, what I should do to my ISY to fix it.

-Tom

Bert2013 · May 23, 2020

xlurkr,

If sid == -1 and/or isExpired == 'yes' then that entry is free. Most of what you have shows that pretty much everything is free. Look at mine and you see that none of them are free, resulting in 'Max subscribers reached' when anything tries to subscribe at that time.

There is most likely something wrong with your python code, of with PyISY itself. You should debug where your error comes from and what your error is exactly. 'Max subscribers reached' is error 815 while 'Already subscribed' is error 817.

Bert

Michel Kohanim · May 24, 2020

Hi @Bert2013,

The only reason subscriptions do not expire is because the end client is still responding to heartbeat events. Next time you see this issue, unplug your client, wait a while (sometimes, it could be up to 14 hours = TCP fin_wait timeout) and see whether or not the subscriptions clear.

@xlurkr, precisely what @Bert2013 said.

With kind regards,
Michel

Sign In

Notification

Recommended Posts

Michel Kohanim

Bert2013

Michel Kohanim

xlurkr

Michel Kohanim

xlurkr

xlurkr

xlurkr

xlurkr

Michel Kohanim

xlurkr

Michel Kohanim

xlurkr

xlurkr

simplextech

xlurkr

simplextech

Michel Kohanim

xlurkr

Bert2013

xlurkr

Bert2013

Michel Kohanim

Archived

Recently Browsing

Who's Online (See full list)

Forum Statistics

Browse

Activity