SynoAI keeps crashing

[TullingeHellMoppers]

I just started using the SynoAI setup which works great for a few image processes, but then it crashes. I have noticed the following error message in the log of SynoAI right before it crashes:

2022-06-06 07:58:33	stdout	Storing keys in a directory '/root/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.
2022-06-06 07:58:33	stdout	�[?1h�=�[40m�[1m�[33mwarn�[39m�[22m�[49m: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60]
2022-06-06 07:58:27	stdout	at System.Threading.ThreadPoolWorkQueue.Dispatch()
2022-06-06 07:58:27	stdout	at System.Threading.QueueUserWorkItemCallback.Execute()
2022-06-06 07:58:27	stdout	at System.Threading.ExecutionContext.RunForThreadPoolUnsafeTState
2022-06-06 07:58:27	stdout	at System.Threading.QueueUserWorkItemCallback.<>c.<.cctor>b__6_0(QueueUserWorkItemCallback quwi)
2022-06-06 07:58:27	stdout	at System.Threading.Tasks.Task.<>c.b__140_1(Object state)
2022-06-06 07:58:27	stdout	at SynoAI.Controllers.CameraController.Get(String id) in /src/Controllers/CameraController.cs:line 211
2022-06-06 07:58:27	stdout	at System.String.Join(String separator, IEnumerable`1 values)
2022-06-06 07:58:27	stdout	Unhandled exception. System.ArgumentNullException: Value cannot be null. (Parameter 'values')
2022-06-06 07:58:27	stdout	FrontDoor: Nothing detected by the AI at EVENT TIME 972ms

Any ideas?

[djdd87]

Provide your config, please.

[TullingeHellMoppers]

Not sure which config exactly, but here is the JSON:
{
"Logging": {
"LogLevel": {
"Default": "Information",
"Microsoft": "Warning",
"Microsoft.Hosting.Lifetime": "Information"
}
},

"Url": "http://192.168.0.166:5000",
"User": "xxxxxx",
"Password": "xxxxxx",

"MinSizeX": 50,
"MinSizeY": 50,

"DaysToKeepCaptures": 14,

"AI": {
"Type": "DeepStack",
"Url": "http://192.168.0.166:9099"
},

"Notifiers": [
{
"Type": "Pushbullet",
"ApiKey": "XXXXXX"
}
],

"Cameras": [
{
"Name": "FrontDoor",
"Types": [ ],
"Threshold": 30,
"MinSizeX": 50,
"MinSizeY": 50
}
]
}

I am running this setup on a Synology DS 918+.

SynoAI status page:

DeepStack status page:

Let me know if you need anything more.

[djdd87]

Can you try and specify something in the Type array, e.g. "Person"?

"Cameras":[
   {
      "Name":"FrontDoor",
      "Types":[
         "Person"
      ],
      "Threshold":30,
      "MinSizeX":50,
      "MinSizeY":50
   }
]

[TullingeHellMoppers]

Sure, just updated with Person. Let me try it a bit to see if it works better

…

On Mon, Jun 6, 2022 at 2:06 PM djdd87 ***@***.***> wrote: Can you try and specify something in the Type array, e.g. "Person"? "Cameras":[ { "Name":"FrontDoor", "Types":[ "Person" ], "Threshold":30, "MinSizeX":50, "MinSizeY":50 } ] — Reply to this email directly, view it on GitHub <#130 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZQADVHCQ4PRDZVYZU2JC23VNXSS7ANCNFSM5X6THMUQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[TullingeHellMoppers]

Yep, when only specifying Person it seems to be more stable, at least for now :). Any idea what is causing this? Another thing, the Time in the Container log is CET -2hrs, but when running the "Date" command in the Container Terminal it is correct CET time, any idea on this one? I have set the TZ env variable to "CET".

…

On Mon, Jun 6, 2022 at 2:08 PM David Moberg ***@***.***> wrote: Sure, just updated with Person. Let me try it a bit to see if it works better On Mon, Jun 6, 2022 at 2:06 PM djdd87 ***@***.***> wrote: > Can you try and specify something in the Type array, e.g. "Person"? > > "Cameras":[ > { > "Name":"FrontDoor", > "Types":[ > "Person" > ], > "Threshold":30, > "MinSizeX":50, > "MinSizeY":50 > } > ] > > — > Reply to this email directly, view it on GitHub > <#130 (reply in thread)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AZQADVHCQ4PRDZVYZU2JC23VNXSS7ANCNFSM5X6THMUQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[djdd87]

I think it's potentially a bug caused by some logging output caused by no types being specified. I think everyone using it to date must have specified at least one type.

In regards to the logging times, this is a Synology DSM issue and nothing to do with SynoAI. It's been discussed a few times in various places.