setConfiguration causes crash

[JuliusFruitfly]

Hi,
I'm using the setConfiguration command over MQTT to change monitoring mode (move/significant) and the moveModeLocatorInterval timer to optimise battery use. For example slow updates at night and faster updates when moving.

This often causes owntracks to crash.

On a restart I see entries in the log such as:-

[main] App: Historical process exit reason: 2 - Description:
[main] App: Historical process exit reason: 2 - Description:
[main] App: Historical process exit reason: 13 - Description: OneKeyClean
[main] App: Historical process exit reason: 2 - Description:
[main] App: Historical process exit reason: 3 - Description:
[main] App: Historical process exit reason: 4 - Description: crash
[main] App: Historical process exit reason: 2 - Description:
[main] App: Historical process exit reason: 3 - Description:
[main] App: Historical process exit reason: 2 - Description:
[main] App: Historical process exit reason: 2 - Description:

I'd appreciate some clues as to where I'm going wrong,

Thanks

• App build number: 2.5.0
• Android version: 14
• Device: Xiaomi/Redmi Note 12
• Installation source: Google Play

[jpmens]

Please show us exactly how to reproduce the crash, i.e. the command you use to publish and the payload.

[JuliusFruitfly]

Thanks for getting back to me so quickly. I wasn't clear in my first message - the crash isn't on (or soon after?) every setConfiguration but does occur every few days at maybe 4-10 updates per day. I've tried triggering the problem by sending updates every few minutes but this works fine I'll try to gather more data on the next occurrence Thanks

…

On Mon, 9 Sept 2024 at 17:55, Jan-Piet Mens ***@***.***> wrote: Please show us exactly how to reproduce the crash, i.e. the command you use to publish and the payload. — Reply to this email directly, view it on GitHub <#1838 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARWEFQHFU33J62IVJ47CD3DZVXHHFAVCNFSM6AAAAABN44PTQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZYGYYTGMZWGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- - Neil

[JuliusFruitfly]

Crash probably not directly related to setConfiguration, so closing pending better analysis. Thanks for your help

[JuliusFruitfly]

I'm reopening this issue as I have more context.
(Note: now on 2.5.3)

In summary:
Owntracks seems to disconnect MQTT on a config update, then exits on a second update when a location update triggers a reconnect.

---

Timeline is:-

20:48:57 Owntracks reconnects to MQTT

21:41:53 setConfiguration used to update parameters:
{'monitoring': 2, 'locatorDisplacement': 50, 'moveModeLocatorInterval': 60, 'locatorPriority': 3}
This causes owntracks to disconnect MQTT

23:13:54 Owntracks reconnects MQTT and sends a location update

setConfiguration used again:
{'monitoring': 1, 'locatorDisplacement': 200, 'locatorInterval': 1800, 'locatorPriority': 2}

Owntracks exits.

When restarted Owntracks log contains:
App: Historical process exited at 2024-09-28T23:10:05.300Z. reason:
(no reason given)

---

I've attached the config - there's nothing of interest in the log.

Thanks for your help

config NS crash 2809.json

[growse]

That's... Weird. Neither of those two things should happen.

Some config changes cause an MQTT reconnect (usually the ones related to the connection), but not those.

Will try and reproduce. Hopefully it's something simple to fix.

[JuliusFruitfly]

I have modified my app to notify me of a disconnect after a config update. If this works I'll send the log. Usually exits every few days.

[JuliusFruitfly]

The MQTT disconnect maybe part of the cause of the owntracks 'exit' , but it is not a bug of itself. The disconnect is generated by the MQTT server or the home assistant integration. Possibly the HA integration doesn't like seeing the setConfiguration cmd.

[JuliusFruitfly]

I've been trying to find the trigger for this problem for the last few weeks without progress so far. All I can say for sure is that Owntracks will exit every few days. One difficulty is that there is nothing in the event log, just a line such as

2024-10-17 13:38:25.486 I [main] App: Historical process exited at 2024-10-17T12:31:04.232Z. reason:

Is there any way you can enhance this message to supply a reason or some other clue as to what is going on? Happy to take a diagnostic build if that is possible.

Thanks

[growse]

The reason: tries to print the description of the ApplicationExitInfo structure defined here: https://developer.android.com/reference/android/app/ApplicationExitInfo#getDescription()

Next version I'll add in the status and reason fields into the log, which should help provide a little more colour of what the exit trigger was.