mlounsbury

Not sure if you figured this out, but I had the same issue. After doing some searching, I found someone on the Home Assistant Community that said they needed to change to their FQDN and that worked for them. They were using a duckdns for their reverse proxy, and I have my own domain. But entering my FQDN fixed this for me.

Thanks. The only reason I thought it might be a memory issue which was causing the high CPU utilization is because Fix Common Problems shows this: I did not see the same issue again this past Saturday, so I'm at a loss as to what could be causing it. I will keep watching it and see if it happens again and will grab the diags while it is at 100% if/when it gets there again.

I noticed the last two Saturday mornings (8/29 and 9/5) that when I wake up in the morning my Unraid server has maxed out memory and all cores/threads of my CPU are pretty much pegged at 100% (Ryzen 7 2700). When it happened on 8/29, I checked the Unraid GUI and it appeared Mover was running. I have a directory for Windows PC backups and I had been using cache to have the backups go there first and then move to the array, and I noticed once or twice in the past it takes a while to move the backups to the array, so I thought that might have been the problem. I stopped mover in the command line, but it did not seem to impact CPU or memory usage, so I stopped the array. Once it stopped, I restarted it and everything seemed fine. I then changed that backup directory to no longer use cache, hoping that might solve the problem. However this past Saturday morning I awoke to find the server in the same state. I stopped the array and started it again, and everything appeared normal, and does at this current point in time. I have Grafana set up, and I've looked back at both of those time frames, and I don't see anything coming from my docker containers at that point in time that would indicate something going wrong. I don't see any apparent increase in CPU or memory from any of the containers. The one thing I do note is both graphs pretty much stop right after 12am on Saturday morning, which is right when Unraid CPU activity shows a spike up to 100%. I have 16GB of RAM and I can see that memory usage did gradually increase over the week: Is this just a case of docker containers using up all of the memory? I do have two user scripts that run on Saturday mornings, and the first that runs is the one that deletes the dangling images at 12am on Saturday. Is that running just exacerbating another issue? Or is that script actually the issue? I've also attached diagnostics which should have both instances in the file. unraid-diagnostics-20200908-1516.zip

Looks like the swag image is in the same directory as the LE png file: https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/swag.gif

Not sure if you saw, but there is an issue for this in the paperless github: https://github.com/the-paperless-project/paperless/issues/651. Looks like there is a pull request to fix it but has not yet been merged.

Looks like I figured it out and I don't get the error any longer. It had to do with line endings. For anyone else, the entrypoint needs to go into Extra Parameters. I was getting the following error when I had it in Extra Parameters: standard_init_linux.go:211: exec user process caused "no such file or directory" I found this post: https://forums.docker.com/t/standard-init-linux-go-175-exec-user-process-caused-no-such-file/20025/9 I created the file in VS Code, which I needed to change the End of Line Sequence from CRLF to LF.

I'm having an issue getting the container to run with both webserver and consumer in one container using the script. This is what shows in the container log: Mapping UID and GID for paperless:paperless to 99:100 Operations to perform: Apply all migrations: admin, auth, contenttypes, documents, reminders, sessions Running migrations: No migrations to apply. Unknown command: '--entrypoint' Type 'manage.py help' for usage. I've got the script in Post Arguments: I've also tried it in Extra Parameters to no avail. Tried quotes also. I've changed the script like @dcoens mentions above as well. The script is executable as well. Any ideas what I'm doing wrong here?

At what point is your traceroute dying? I am able to traceroute without an issue, and it's only one hop from my firewall to Amazon. I am on the east coast of the United States, not sure where you're located. Sounds like it could be a regional issue.

Ah, my bad. Totally forgot to check the github. Thanks for the information and the update to the template. Much appreciated.

So I've been able to get the BitWarden container installed and working via LE/reverse proxy. I was having the same issue as those on the previous page, so thanks for the tips on that. I was able to get a new user registered using Chrome as well. The one thing I was curious about was whenever you go to the URL for BitWarden, it comes up to a login page and anyone can register. I'm not sure if anyone will come across my instance, but anything is possible. I did some searching, and it is possible to turn off registrations: https://github.com/bitwarden/core/issues/131 I looked through some of the directories in the docker, but I wasn't able to find the location or file they're referring to. Is it possible to do this in this docker container? Also, I was wondering if there was an admin portal, and I found another document that said the admin portal should be available at https://bitwarden-domain.com/admin, however when I go to /admin I get a 404 error. I am assuming that was not included in the docker container? Is it possible to have it added?

Was coming to ask this specific question. I'm running into issues with the Home Assistant flows not working because they require v8 but the latest docker is using Node V6. I went into the docker itself and ran the command to download the older Home Assistant flows, but I don't feel comfortable leaving it that way. I'll be giving this a try later though. Thanks for the information!

Since that's a Plex Pass thread, not everyone will have access to view it. That being said, have you tried pasting the version number into the field on the Docker to see if it can download it and deploy it?

Not sure if there's an answer to this, and I know not everyone has Plex Pass, but is there an option for us to be able to do post processing of DVR'd shows? I know that there's an option for a post processing script in the DVR section, and there's some guides out there that show how to do it with MCEBuddy and Comskip and a post processing script, but I think that only really applies to people running it on Windows, Linux, or Mac. Are we out in the cold when it comes to this, and our only real option is to come up with something outside of Plex that removes the commercials from shows after Plex has recorded the show and puts it into the library? EDIT: Guess I should have searched the thread first, looks like someone asked a few months ago:

I just had the same issue after I upgraded regular Plex to Plex Pass. I went into the web GUI and had to sign in, and it didn't find my local server. I logged out and back in without doing anything else, and it showed up. Not sure if you tried doing just that without anything else, but it might be worth a shot.

So I got my server built on Thursday and started the preclear on both of my drives. Here are the diff results on each drive. They look good to me, although sda has a weird error: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. I did a search on the forum but didn't see anything specific to this message. Here's the rest. sda: root@Lounsbury-unRAID:/tmp# diff smart_start1376 smart_finish1376 19,20c19,20 < Offline data collection status: (0x80) Offline data collection activity < was never started. --- > Offline data collection status: (0x84) Offline data collection activity > was suspended by an interrupting command from host. 54c54 < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 58c58 < 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 --- > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 26 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 27 67c67 < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 --- > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 sdb: sdb root@Lounsbury-unRAID:/boot# diff smart_start8573 smart_finish8573 54c54 < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 24 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 25 67c67 < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 --- > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Also I've got these errors in the syslog after sdb finished. Everything from the SMART report looks good, so I'm not sure what happened here. Dec 3 16:30:56 Lounsbury-unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen (Errors) Dec 3 16:30:56 Lounsbury-unRAID kernel: ata2.00: failed command: READ FPDMA QUEUED (Minor Issues) Dec 3 16:30:56 Lounsbury-unRAID kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:30:56 Lounsbury-unRAID kernel: ata2.00: failed command: READ FPDMA QUEUED (Minor Issues) Dec 3 16:30:56 Lounsbury-unRAID kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:30:56 Lounsbury-unRAID kernel: ata2: hard resetting link (Minor Issues) Dec 3 16:31:27 Lounsbury-unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen (Errors) Dec 3 16:31:27 Lounsbury-unRAID kernel: ata2.00: failed command: READ FPDMA QUEUED (Minor Issues) Dec 3 16:31:27 Lounsbury-unRAID kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:31:27 Lounsbury-unRAID kernel: ata2.00: failed command: READ FPDMA QUEUED (Minor Issues) Dec 3 16:31:27 Lounsbury-unRAID kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:31:27 Lounsbury-unRAID kernel: ata2: hard resetting link (Minor Issues) Dec 3 16:31:58 Lounsbury-unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen (Errors) Dec 3 16:31:58 Lounsbury-unRAID kernel: ata2.00: failed command: READ FPDMA QUEUED (Minor Issues) Dec 3 16:31:58 Lounsbury-unRAID kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:31:58 Lounsbury-unRAID kernel: ata2.00: failed command: READ FPDMA QUEUED (Minor Issues) Dec 3 16:31:58 Lounsbury-unRAID kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:31:58 Lounsbury-unRAID kernel: ata2: hard resetting link (Minor Issues) Dec 3 16:32:29 Lounsbury-unRAID kernel: ata2.00: NCQ disabled due to excessive errors (Errors) Dec 3 16:32:29 Lounsbury-unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen (Errors) Dec 3 16:32:29 Lounsbury-unRAID kernel: ata2.00: failed command: READ FPDMA QUEUED (Minor Issues) Dec 3 16:32:29 Lounsbury-unRAID kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:32:29 Lounsbury-unRAID kernel: ata2.00: failed command: READ FPDMA QUEUED (Minor Issues) Dec 3 16:32:29 Lounsbury-unRAID kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:32:29 Lounsbury-unRAID kernel: ata2: hard resetting link (Minor Issues) Dec 3 16:33:00 Lounsbury-unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Dec 3 16:33:00 Lounsbury-unRAID kernel: ata2.00: failed command: READ DMA EXT (Minor Issues) Dec 3 16:33:00 Lounsbury-unRAID kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:33:00 Lounsbury-unRAID kernel: ata2: hard resetting link (Minor Issues) Dec 3 16:33:31 Lounsbury-unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Dec 3 16:33:31 Lounsbury-unRAID kernel: ata2.00: failed command: READ DMA EXT (Minor Issues) Dec 3 16:33:31 Lounsbury-unRAID kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:33:31 Lounsbury-unRAID kernel: ata2: hard resetting link (Minor Issues) Dec 3 16:33:32 Lounsbury-unRAID kernel: end_request: I/O error, dev sdb, sector 3876852784 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606598 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606599 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606600 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606601 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606602 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606603 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606604 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606605 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606606 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606607 (Errors) Dec 3 16:34:02 Lounsbury-unRAID kernel: ata2.00: limiting speed to UDMA/100:PIO4 (Minor Issues) Dec 3 16:34:02 Lounsbury-unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Dec 3 16:34:02 Lounsbury-unRAID kernel: ata2.00: failed command: READ DMA EXT (Minor Issues) Dec 3 16:34:02 Lounsbury-unRAID kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:34:02 Lounsbury-unRAID kernel: ata2: hard resetting link (Minor Issues) Dec 3 16:34:33 Lounsbury-unRAID kernel: ata2.00: limiting speed to UDMA/33:PIO4 (Minor Issues) Dec 3 16:34:33 Lounsbury-unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Dec 3 16:34:33 Lounsbury-unRAID kernel: ata2.00: failed command: READ DMA EXT (Minor Issues) Dec 3 16:34:33 Lounsbury-unRAID kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:34:33 Lounsbury-unRAID kernel: ata2: hard resetting link (Minor Issues) Dec 3 16:34:34 Lounsbury-unRAID kernel: end_request: I/O error, dev sdb, sector 3876852528 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606566 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606567 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606568 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606569 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606570 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606571 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606572 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606573 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606574 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606575 (Errors) Attached are the SMART start and finish logs. Can anyone provide any feedback? Thanks in advance! smart_start1376.txt smart_finish1376.txt smart_start8573.txt smart_finish8573.txt