I wouldn’t say it’s wrecked just yet.
It’s more resilient than most think.
The key to that resilience is having Database Backups enabled in Scheduled Tasks with the NAS on when they are scheduled to run.
While this looks bad:
Jan 12, 2020 09:10:26.896 [0x7f3290a13700] ERROR - Error issuing curl_easy_perform(handle): 28
Jan 12, 2020 09:10:41.528 [0x7f3290d01700] WARN - Held transaction for too long (../Statistics/StatisticsBandwidth.cpp:50): 0.180000 seconds
Jan 12, 2020 09:10:48.062 [0x7f3290d01700] WARN - Held transaction for too long (../Statistics/StatisticsBandwidth.cpp:50): 0.180000 seconds
Jan 12, 2020 09:10:53.688 [0x7f3290d01700] WARN - Held transaction for too long (../Statistics/StatisticsBandwidth.cpp:50): 0.160000 seconds
Jan 12, 2020 09:10:54.348 [0x7f3290d01700] WARN - Held transaction for too long (../Statistics/StatisticsManager.cpp:248): 5.790000 seconds
Jan 12, 2020 09:12:52.373 [0x7f3243d11700] WARN - SLOW QUERY: It took 1090.000000 ms to retrieve 1 items.
Jan 12, 2020 09:13:29.681 [0x7f3243d11700] WARN - SLOW QUERY: It took 2250.000000 ms to retrieve 0 items.
Jan 12, 2020 09:13:45.027 [0x7f3243d11700] WARN - SLOW QUERY: It took 1090.000000 ms to retrieve 0 items.
Jan 12, 2020 09:13:50.502 [0x7f3243d11700] WARN - SLOW QUERY: It took 320.000000 ms to retrieve 0 items.
Jan 12, 2020 09:15:56.962 [0x7f3243d11700] WARN - SLOW QUERY: It took 5500.000000 ms to retrieve 20 items.
Jan 12, 2020 09:17:58.498 [0x7f3227447700] WARN - SLOW QUERY: It took 730.000000 ms to retrieve 1 items.
Jan 12, 2020 09:20:04.772 [0x7f3227447700] WARN - SLOW QUERY: It took 7880.000000 ms to retrieve 18 items.
Jan 12, 2020 09:22:33.706 [0x7f32265a1700] WARN - SLOW QUERY: It took 850.000000 ms to retrieve 1 items.
Jan 12, 2020 09:24:59.750 [0x7f3214e31700] ERROR - getaddrinfo(192-168-1-10.abcdefghijklmnopqrstuvwxyz012345.plex.direct) failed: -5
Jan 12, 2020 09:32:58.444 [0x7f3293d11700] ERROR - Error issuing curl_easy_perform(handle): 28
Jan 12, 2020 09:33:03.105 [0x7f3293d11700] WARN - MyPlex: Updating device connections failed, retrying in 20 seconds.
Jan 12, 2020 09:41:20.534 [0x7f3291e95700] ERROR - Error issuing curl_easy_perform(handle): 28
Jan 12, 2020 09:41:25.667 [0x7f3291e95700] WARN - MyPlex: Updating device connections failed, retrying in 40 seconds.
Jan 12, 2020 09:50:42.625 [0x7f3214e31700] ERROR - Error issuing curl_easy_perform(handle): 28
Jan 12, 2020 09:50:45.848 [0x7f3214e31700] WARN - MyPlex: Updating device connections failed, retrying in 80 seconds.
Jan 12, 2020 09:50:45.842 [0x7f3291e95700] ERROR - Error issuing curl_easy_perform(handle): 28
Jan 12, 2020 09:58:20.412 [0x7f3225fc5700] ERROR - [PlexRelay] kex protocol error: type 7 seq 11
Jan 12, 2020 09:58:21.343 [0x7f31fbfff700] INFO - [PlexRelay] Allocated port 24967 for remote forward to 127.0.0.1:32401
Jan 12, 2020 10:20:15.742 [0x7f3290a13700] ERROR - Error parsing content.
Jan 12, 2020 10:20:18.718 [0x7f3290a13700] ERROR - Error parsing XML response for update.
It’s not all that bad UNLESS the system is really that overloaded.
The D2700 is on the edge as a PMS server. It DirectPlay & some DirectStream video, music, and photos but not much more than that.
If, while attempting to perform those operations, it’s also trying to add content, it will become overloaded. One must remember, it’s only a dual core. Playing content will use 1 core (about 20-30% of one). Converting audio can be up to 1 1/2 cores (7.1 -> 2 channel for example.
This means, it’s viability as a server is highly dependent on the content being played.
First, let’s find out what’s happening.
Please note, in the logs, I see sync attempts from someone not authorized to sync?
You may wish to check up on that. Also, syncing content is transcoding (background mode) and will use all the available resources. If this is happening then it will easily trigger what I see and have highlighted above.