dstark4

Members
  • Posts

    35
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

dstark4's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Is there any way to improve the Notifications sent by unraid for docker containers? Specifically, in a scenario where Image Utilization is high. Looking to have a way of having it run a command and appending it to the notification email. Such as, If utilization is >70% - run "docker ps -a" and append result. My issue currently is a remote unraid box, behind satellite internet, so I don't have good remote access, and by the time I can get to it. The usage is back to normal. Ps. my suspicion is plex being the cause, however the typical scenario of transcode having a bad path, has been rechecked as pointing to /tmp/transode. There are several other possible culprit containers, but no way of figuring out which to start with.
  2. Awesome, Thank you for working on this. Do you plan on supporting more than vm's attached to unraid? I have use-case's for usb hardware keys, where this would be a great feature for moving between multiple machines on local networks. (Windows is the biggest hurdle at the moment.) I was able to use this in conjunction with unraid cli to share to other machines on the network.
  3. I believe I have narrowed down the problem, the lancache container has a config file for sni, which is not following the above max file size. To fix the problem I have edited the container to have a path for /etc/nginx/stream-enabled/ to appdata. I have edited the conf file to commit out the offending access log. So far nothing is being written, I will watch the docker img to make sure nothing else is being written. I will mark this post solved in a couple days if nothing else occurs.
  4. That's the thing, log file size limit was set when I first configured this server. I have added a path to the container to send that log to share outside of the docker image, but that's a bandaid. The file has grown to about 1gig in 6hrs. I am unsure what to do otherwise
  5. I have a server that is experiencing a problem where the lancache container is bypassing the 50m limit set in docker settings. I have also add the "--log-opt max-size=50m --log-opt max-file=1" to the extra parameters field. Is there another recommended command to add? I know its the access.log that is the culprit. My googlefu keeps pointing me to posts adding the parameters to the container. Such as Squid's excellent docker faq and even red hat articles
  6. Well it did it again. Attached diagnostics, and below this appears to be the relevant info from the log for the drive. I am going to go ahead and update the LSI 9300 firmware, but to me this seems to be a harddrive problem. If there a large number of bad sectors should it not fail smart tests? I'd like to gather the info to warranty return the drive. Dec 25 02:01:23 Tower kernel: sd 11:0:2:0: [sde] tag#4535 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Dec 25 02:01:23 Tower kernel: sd 11:0:2:0: [sde] tag#4535 Sense Key : 0x5 [current] Dec 25 02:01:23 Tower kernel: sd 11:0:2:0: [sde] tag#4535 ASC=0x20 ASCQ=0x0 Dec 25 02:01:23 Tower kernel: sd 11:0:2:0: [sde] tag#4535 CDB: opcode=0x88 88 00 00 00 00 04 03 84 5c 28 00 00 01 00 00 00 Dec 25 02:01:23 Tower kernel: print_req_error: critical target error, dev sde, sector 17238875176 Dec 25 02:01:23 Tower kernel: sd 11:0:2:0: [sde] tag#4535 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Dec 25 02:01:23 Tower kernel: sd 11:0:2:0: [sde] tag#4535 Sense Key : 0x5 [current] Dec 25 02:01:23 Tower kernel: sd 11:0:2:0: [sde] tag#4535 ASC=0x20 ASCQ=0x0 Dec 25 02:01:23 Tower kernel: sd 11:0:2:0: [sde] tag#4535 CDB: opcode=0x8a 8a 00 00 00 00 04 03 84 5c 28 00 00 01 00 00 00 Dec 25 02:01:23 Tower kernel: print_req_error: critical target error, dev sde, sector 17238875176 tower-diagnostics-20201225-1015.zip
  7. Yes it is in IT Mode, could the diagnostics being anonymized be why it does not show up? It was rebuilding at the time I uploaded. Yes it takes ~14hrs, it was the second time rebuilding because of that particular drive putting the array in error state. Model Family: Seagate Enterprise Capacity 3.5 HDD Device Model: ST10000NM0086-2AA101 Serial Number: ZA2CNXB7
  8. Here's the diagnostics, I believe I have not rebooted between error coming up again. (Lack of sleep on my end)tower-diagnostics-20201222-1213.zip
  9. Hello, I am experiencing issues with a new server. It has put a disk in an error twice so far, with (Dec 21 20:36:32 Tower kernel: print_req_error: critical target error, dev sde, sector 6442451176). This harddrive is passing smart tests and I have attached the smart report. It is attached to an lsi 9300 hba. Any suggestions are greatly appreciated. tower-smart-20201221-2108.zip edit: Updating the hba appears to have stopped this error from occurring again
  10. I haven't had an opportunity to use the restore yet, but am glad to say that the docker is working for me. Any chance that we can have the ability to change the docker from host to it's own IP? I have a server I would like to use this on, however it suffers from a bug that cause the entire host to become unresponsive at random if dockers are on the same vlan as the host.
  11. Updated, Reinstalled the docker with config pointed to cache. Still have the same problem of the appdata missing the majority of files. If this caused by the sqlite bug, I can wait until the limetech team has a fix. Thanks for the help
  12. Yes, 6.7.0. Hadn't moved to newest version as I haven't had any problems. Will upgrade to 6.7.2 and retry just in case.
  13. Correct, there are folders however of the four folders within the folder only the config folder has anything and it is one file. The urbackupsrv. Would I be correct in assuming that there should be more files?
  14. Sorry, I should have specified that the screenshot was from after deleting the folder from appdata, but before reinstalling the image. The folder was created when I hit apply. I did however go ahead and run the command. ~# ls -al /mnt/user/appdata/ total 16 drwxrwxrwx 1 nobody users 202 Aug 1 10:06 ./ drwxrwxrwx 1 nobody users 52 Jul 31 15:16 ../ drwxrwxrwx 1 nobody users 62 Dec 1 2018 MakeMKV/ drwxrwxrwx 1 nobody users 20 Dec 1 2018 PlexMediaServer/ drwxrwxrwx 1 nobody users 12 Dec 13 2018 QDirStat/ drwxrwxrwx 1 root root 22 Jul 28 13:28 Shinobi/ drwxrwxrwx 1 nobody users 96 Dec 31 2018 Sync/ drwxrwxrwx 1 nobody users 96 Dec 31 2018 SyncWan/ drwxrwxr-x 1 nobody users 64 Aug 1 10:02 binhex-krusader/ drwxrwxr-x 1 nobody users 64 Aug 1 10:07 binhex-urbackup/ drwxrwxrwx 1 nobody users 80 Jun 26 23:27 clamav/ drwxrwxrwx 1 nobody users 44 Jul 19 20:44 grocy/ drwxrwxrwx 1 999 users 6642 Jul 31 15:29 mongodb/ drwxrwxrwx 1 nobody users 110 Dec 1 2018 unifi/
  15. I deleted the image from appdata, and re-downloaded the docker and left everything default with the exception of pointing /Media to an empty share. Still having the same problem. I have attached a screenshot of the config. ur docker log.txt