Error on CLI / odd logs and no images showing up #551
Description
Expected behavior:
- Damselfly shows images from mounted docker volume (confirmed to be mounted as expected via
docker exec -it damselfly bash
Actual:
- No images show up after hours (could also be due to having millions of images, but I'm not sure
Two issues indicate that something isn't working:
The docker log shows this:
[03:53:06.836-.NET TP Worker-WRN] HTTP Exception: net_http_message_not_success_statuscode_reason, 500, Internal Server Error (/api/basketdefault)
[03:53:06.851-.NET TP Worker-ERR] System.Net.Http.HttpRequestException: net_http_message_not_success_statuscode_reason, 500, Internal Server Error
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
at System.Net.Http.Json.HttpClientJsonExtensions.<<FromJsonAsyncCore>g__Core|12_0>d`2[[Damselfly.Core.Models.Basket, Damselfly.Core.DbModels, Version=4.2.3.0, Culture=neutral, PublicKeyToken=null],[System.Text.Json.JsonSerializerOptions, System.Text.Json, Version=9.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51]].MoveNext()
at Damselfly.Core.ScopedServices.ClientServices.RestClient.<CustomGetFromJsonAsync>d__9`1[[Damselfly.Core.Models.Basket, Damselfly.Core.DbModels, Version=4.2.3.0, Culture=neutral, PublicKeyToken=null]].MoveNext()
at Damselfly.Core.ScopedServices.ClientBasketService.SwitchToDefaultBasket(Nullable`1 userId)
at Damselfly.Web.Client.Components.SideBarControls.BasketManager.OnInitializedAsync()
at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync()
at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task , ComponentState )
System.Net.Http.HttpRequestException: net_http_message_not_success_statuscode_reason, 500, Internal Server Error
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
at System.Net.Http.Json.HttpClientJsonExtensions.<<FromJsonAsyncCore>g__Core|12_0>d`2[[Damselfly.Core.Models.Basket, Damselfly.Core.DbModels, Version=4.2.3.0, Culture=neutral, PublicKeyToken=null],[System.Text.Json.JsonSerializerOptions, System.Text.Json, Version=9.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51]].MoveNext()
at Damselfly.Core.ScopedServices.ClientServices.RestClient.<CustomGetFromJsonAsync>d__9`1[[Damselfly.Core.Models.Basket, Damselfly.Core.DbModels, Version=4.2.3.0, Culture=neutral, PublicKeyToken=null]].MoveNext()
at Damselfly.Core.ScopedServices.ClientBasketService.SwitchToDefaultBasket(Nullable`1 userId)
at Damselfly.Web.Client.Components.SideBarControls.BasketManager.OnInitializedAsync()
at Microsoft.AspNetCore.Components.ComponentBase.RunInitAndSetParametersAsync()
at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task , ComponentState )
[03:54:20.046-.NET TP Worker-WRN] HTTP Exception: net_http_message_not_success_statuscode_reason, 400, Bad Request (/api/tasks/enqueue)
Damselfly logs show this:
04:35:16.263 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:16.145 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:15.632 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:15.237 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:14.971 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:14.169 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:13.781 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:13.293 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:12.939 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:12.547 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:11.955 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:11.691 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:11.506 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:11.148 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:10.806 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:10.486 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:10.182 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:09.900 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:09.569 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:09.233 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:09.214 INF Flagging new jobs state for IndexingService
04:35:08.929 INF FileWatcher: adding to queue: /pictures/robots/MR203 Renamed
04:35:08.921 INF Flagging change for folder: /pictures/robots/MR203
04:35:08.594 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:08.284 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:07.947 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:07.660 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:07.367 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:06.828 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:06.400 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
04:35:06.085 INF FileWatcher: folder was not added to the queue: /pictures/robots/MR203 Renamed
...
I'm not sure if either of these odd logs are the root cause of the issue, or if it's just taking longer than 12 hours to index even a single image.
The folder structure is /pictures/robots/[20+ subfolders]/[500k-3m photos per subdirectory].
I know that Damselfly was designed for large image galeries, but maybe this is a bit much?