kevin182

My server keeps losing internet access. I have my DNS Set to Google in network settings. When I changed my router to OpenDNS, the internet immediately came back up but only for a few minutes. It is now back down. Any help would be appreciated. Thank you lucifer-diagnostics-20230513-1456.zip

Disregard. I got it working. For anyone interested. What I did is pull down original paperless-ng to the container. Made sure it was working properly. Then I just changed the repository to ghcr.io/paperless-ngx/paperless-ngx:latest. It worked this time. I do not know what I did wrong the first time.

I converted my paperless-ng container to ngx as described earlier in this post. I cannot access any of my files through the UI. Here is the error I get. Anyone else get this? Thanks.

Also, I should mention that I have 2 Unraid servers and the other does not have this issue. Both servers are now on 6.10.0-rc5 but the problem was on rc4 also.

I am having an intermittent network issue. I cannot get traffic in or out from the internet but local networking is fine. If I restart docker, the issue goes away temporarily but then comes back. Would someone be able to look at my log files? I looked but did not see anything glaring. Nginx errors are normal from what I understand. Thanks. lucifer-diagnostics-20220503-0656.zip

I have 2 servers. 1 main and 1 backup. Both of them this morning started with dockers not working. I tried restarting both and they look like they are doing something but then just come back to the main screen after a minute like I never initiated a shutdown or array stop. Diagnostics from 1 server attached. Can't get the other to finish. There strange thing is 1 server has 1 out of 16 hyper thread at 100%. The other server 4/8 at 100%. I am tempted to just hard reboot the backup server to see if that fixes the issue. I know I will get an unclean shutdown. lucifer-diagnostics-20220225-0737.zip

This is the second time this has happened. The first time, I thought it was corrupted memory causing the problem but I replaced those modules. I tested the memory again after with no issues. Unraid says my cache is full but at the same time reporting 406 GB free out of 500. Cache is a 2 disk raid pool (500 GB each). Dockers will not load. If someone could please look at my diagnostics and help find this new cause. Thank you. chloe-diagnostics-20220224-0805.zip

I did have 2 DIMMS bad. Once I removed that pair, the other pair tested fine. After bringing the system back up, all the shares reappeared as if nothing happened. Thank you for the help. I appreciate it.

OK. Running memtest now. How bad is this? Is all my data lost? If I find an issue with the RAM and fix it, will I be able to restore my shares? Like I said this is my backup server, other than time, I really have not lost anything critical. It is just that Crashplan will take a few weeks to backup to the cloud.

I have no shares present on 1 of 2 servers. The server that has no shares is my backup server. I just started backup up to this server using Duplicati the 2 days ago. Dockers obviously are not started. I have attached my diagnostics and have not rebooted the server in case something else is needed. Let me know if you can help me. Thank you. backup-diagnostics-20220212-0656.zip

I do see firmware on the Samsung site but no indication on what it is for or what it solves. It is a different firmware from what I have. I might just install it to see if it goes away. Apparently it happens quite often. At least once every 5 minutes as I have been watching it. It only gets caught by the Unraid sensor every once in a while I guess.

If that temp is any period within 30 seconds there is no physical way the temperature would go from 24 to 84 and back to 24 within 90 seconds. That is physically impossible. No? I can raise the temperature threshold to stop getting the warnings. But it is just going to stop the notifications. The drive is still reporting 84 and throttling according the the post I referenced above. Say I do raise the temp to 85 for the upper threshold. What if my drive hits 75 for real? I will never know unless I constantly monitor it.

Looks like it is a manufacturer problem. https://us.community.samsung.com/t5/Monitors-and-Memory/SSD-980-heat-spikes-to-84-C-183-F/td-p/2002779

It lasts for 3 seconds. Now I know it is not for real. Temperature goes from 24 to 84 and back to 24 all within 5 seconds? Hmmmm. btw this is the twin raid 1 drive (same make and model) to the 1 I mentioned above. Maybe a manufacturing defect? I wish I could have the alarm for high temp but it must last for more than X minutes or seconds before sending the alert.

That would be a welcome update. Thanks for the update. Thank you. I reduced the polling interval to 900. I am not sure I want to increase the threshold above 84. If it is a bug, I want to see it happen again and get notified. If it is not a bug, I want to find out what is causing it. I do not think it is a cooling issue as not of my other 4 nvme drives report anywhere close to this. I don't think any have gotten above 40. Thanks for this tip. I have netdata already installed. I could not figure out where the temp was last night but I will increase the interval to something like 6 hours.

I have an NVME drive (nvme2n1) in raid 1 cache pool used for Plex only. The 2 drives are identical make and model (Samsung SSD 980 1 TB). 1 drive has reported overheat twice. The first time I was not home and could not monitor it. The second time was less than 1 hour ago reporting 84 degrees. Mover was not running and nobody was even watching Plex. However, there was 1 download happening at 21:14 for 1 minute. I got the overheat notice for 84 degrees at 21:16. I was looking at all different areas to find what was causing it. While doing that, I noticed that in the disk smart information, it was reporting the drive at 23 degrees all while still reporting 84 on the dashboard and the main screen. At first I thought the smart info was old info but after pressing F5 a few times, it updated to 24. As far as I can tell the temperature never deviated from 84 for the next half hour. Then at 21:47 the server reported the disk returned to normal temperature. It was now showing 26 on the dashboard. How could a drive drop almost 60 degrees in 30 minutes? I am attaching my diagnostics and screen shots of the temperatures. Thank you. lucifer-diagnostics-20220121-2159.zip

Another question. I have hyperthreading enabled. I have 8 physical cores and 16 logical threads. Regardless of the settings of the workers and threads/worker, the 2nd thread in each core never gets utilized. Right now I have it on 6 workers and 4 threads per worker. I know this is not recommended but I have been trying multiple configurations to get it to work. This is just he latest.

Paperless does not seem to be handling dates in the original file name correctly. It is ignoring the filename date and picking it up from the document instead. The documentation says that filename is used and document is ignored when PAPERLESS_FILENAME_DATE_ORDER is set. However, the consumer is still pulling from the OCR contents. My date format in the file is YYYY-MM-DD. As you can see from my date settings, I have a different date format for filenames for sorting purposes. I should note the the date is usually at the end of the filename too. "<document description> YYYY-MM--DD.pdf". Any thoughts? Thanks.