Mango box crash

[Mircea]

Hi Phil,
After the above message mango stop.
Here is what I have for point clean interval.

Here I put the log file too.
[0_1492798979097_ma (1).log](Uploading 100%)

[0_1492799016072_ma (1).log](Uploading 100%)
Thanks
Mircea

[phildunlap]

I think 1000 for the point clean interval may be too fast. The default is 60000. This setting is probably the cause of that message.

[Mircea]

Hi Phil,
Since i changed the point clean interval I get no record or update.

[phildunlap]

Hi Mircea,

That's really bizarre. I'll look into that, but the easy/fast resolution to that is probably to restart Mango.

[phildunlap]

Do point values report being logged on the internal metrics page? Did you get any errors when updating the settings? What version of Mango and Mango NoSQL is this?

[Mircea]

Hi Phil,
Do point values report being logged on the internal metrics page?
I don't know where I can find that info.
Did you get any errors when updating the settings?
No
What version of Mango and Mango NoSQL is this?

I can give you access to mongo at 2222 port if you need.
Thansk
Mircea

[phildunlap]

That shouldn't be needed. I would advise updating the MangoNoSql module

[Mircea]

I get this when I try to check for updates

[phildunlap]

If you check Mango/logs/ma.log I'm sure it's an UnknownHostException (ok, relatively sure) and the gateway or DNS settings may need adjustment.

[Mircea]

Hi Phil,
I updated mango with the latest MangoNoSql.
There are at least 2 variable that mango don't pull them.

The read and blue lines are the 2 variable that with out reason stop recording.
The green and yellow are the same temperature but offset ( after a heat exchanger).
Zone 1 is previous updating mango.
Zone 2 when the sensor record on change ( not on time every 3 minute) .
Zone 3 after a wile the data base don`t record red line.
[0_1493033224309_ma_new.log](Uploading 100%)
I also attached the log file.
Thanks
Mircea

[Mircea]

Hi Phill,
One more think. I found that if i stop and start that data base for that point the point start to be recorded for a wile but after stop to record. The period after which stop recording is sometime one hour sometime 10 hours.

[phildunlap]

Hi Mircea,

it looks like the log file didn't get uploaded quite right.

It looks like you're using BACnet, based on the port of that point. Is the point a COV subscription point, or regular polling?

[mihairosu]

I haven't had time to investigate any deeper and build up a case, but I also have trouble with BACnet subscription.

The first time the BACnet data source is activated, the subscription works fine, but it does not renew.

My current workaround is to poll every 10 sec, but I'd like to get that resolved as well at some point.

[Mircea]

Hi Phil,
This is one point.

And this is the second with the same problem.

[Mircea]

More info

[phildunlap]

Hmm.

With regards to the OP, I am wondering if the lack of data getting polled is what is referred to in the title as crashing (I wouldn't think so).

I know Matthew, Mango and BACnet4J's original author, has been doing work on BACnet4J to bring it up to date with some new specifications and to fix some bugs. That's the version that will be in Mango 3's initial release. I believe he's finished, so I'll try to take some time tomorrow to produce a 2.8 version of that code, and I can pass it along to you two if you'd like to test it out.

[mihairosu]

I'll wait for Mango 3. I don't have the time to devote to this at the moment, so it won't be worth your time.

[phildunlap]

That may be for the best. When I started looking into doing this today I noticed the new BACnet4J was written using Java 8, while the 2.8.x series is limited to requiring Java 7.

Also, you might be interested in checking out https://store.infiniteautomation.com/core

But we'll have more announcements today.