Everything posted by MikaelTarquin
-
Memory Log 100% Full after making new boot USB drive
Thanks! Is there a recommend way to run that on my unRAID server, or do I just need to run that on its own boot device?
-
Memory Log 100% Full after making new boot USB drive
Ok, is the best way to do a memtest from the boot menu, and let it run for a few days? I replaced the cache drive very recently. It seems Plex and others are working, how best should I handle the corrupted file system? EDIT: I saw this post from a few years back saying it's pointless to run memtest with ECC RAM. Is that true? My ram is ECC (Dell poweredge t630). https://forums.unraid.net/topic/91204-how-to-run-memtest-headless/?do=findComment&comment=846406
-
Memory Log 100% Full after making new boot USB drive
A few days ago I had a power outage. My ups allowed the server to gracefully shutdown, but then I was unable to bring it back up the next day. It turns out the USB drive was bad. I didn't have a flash back up, so I made a new USB and used the registration tool to reclaim my license. Everything seemed to go very smoothly, at first. Today I was notified that my Ombi page isn't working, and sure enough I can't login either. In looking for possible causes, I noticed on my dashboard that my log is using 100% of its memory. I am unsure what is causing this, so I attached the diagnostics here. Would anyone be able to help me figure out why this is happening? Thank you! nnc-diagnostics-20220424-0943.zip
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
So SWAG has been working just fine on my server for several months, but today suddenly I can't access the two dockers I have that utilize it, Nextcloud and Ombi. Checking the log for SWAG, all I see is: ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support the app dev(s) visit: Certbot: https://supporters.eff.org/donate/support-work-on-certbot To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... Variables set: PUID=99 PGID=100 TZ=America/Los_Angeles URL=[REDACTED] SUBDOMAINS=ombi,cloud EXTRA_DOMAINS= ONLY_SUBDOMAINS=true VALIDATION=http CERTPROVIDER= DNSPLUGIN= EMAIL=[REDACTED] STAGING=false Using Let's Encrypt as the cert provider SUBDOMAINS entered, processing SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d ombi.[REDACTED].com -d cloud.[REDACTED].com E-mail address entered: [REDACTED] http validation is selected Certificate exists; parameters unchanged; starting nginx [cont-init.d] 50-config: exited 0. [cont-init.d] 60-renew: executing... The cert does not expire within the next day. Letting the cron script handle the renewal attempts overnight (2:08am). [cont-init.d] 60-renew: exited 0. [cont-init.d] 70-templates: executing... **** The following nginx confs have different version dates than the defaults that are shipped. **** **** This may be due to user customization or an update to the defaults. **** **** To update them to the latest defaults shipped within the image, delete these files and restart the container. **** **** If they are user customized, check the date version at the top and compare to the upstream changelog via the link. **** /config/nginx/ssl.conf /config/nginx/site-confs/default /config/nginx/proxy.conf /config/nginx/nginx.conf /config/nginx/authelia-server.conf /config/nginx/authelia-location.conf **** The following reverse proxy confs have different version dates than the samples that are shipped. **** **** This may be due to user customization or an update to the samples. **** **** You should compare them to the samples in the same folder to make sure you have the latest updates. **** /config/nginx/proxy-confs/ombi.subdomain.conf /config/nginx/proxy-confs/nextcloud.subdomain.conf [cont-init.d] 70-templates: exited 0. [cont-init.d] 90-custom-folders: executing... [cont-init.d] 90-custom-folders: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Server ready I don't know if those **** lines in blue are the cause of my issue, or if it's something else. Can anyone offer some assistance? UPDATE: I found the problem was my ISP had pushed an update to my gateway that broke port forwarding. I resolved the issue by removing the port forwarding from the static IP of my server, and instead applied it to the "friendly name" entry in the device list. This was a Pace 5268AC AT&T Fiber router, if that helps anyone looking at this in the future.
-
[Support] Linuxserver.io - Plex Media Server
Well I'm at a loss. Suddenly Plex has been inaccessible today. My client players can't connect to the server, and the web UI is inaccessible. The log doesn't show anything particularly out of place: ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 45-plex-claim: executing... [cont-init.d] 45-plex-claim: exited 0. [cont-init.d] 50-gid-video: executing... [cont-init.d] 50-gid-video: exited 0. [cont-init.d] 60-plex-update: executing... Docker is used for versioning skip update check [cont-init.d] 60-plex-update: exited 0. [cont-init.d] 90-custom-folders: executing... [cont-init.d] 90-custom-folders: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Starting Plex Media Server. I've restarted Docker and then the whole server just to make sure. Any ideas? Edit: fixed by removing the container and re-adding it from the template.
-
Read Errors found in new (<3 mo old) HDD
What would be the best practice, then?
-
Read Errors found in new (<3 mo old) HDD
I'm going to try RMAing the drive. With 2 parity drives, am I okay to just stop the array, pull the drive out, and start the array again with that drive in emulated mode until the replacement is here?
-
Read Errors found in new (<3 mo old) HDD
I'm not exactly sure what this means. Is it most likely a problem with the drive or with the connection?
-
Read Errors found in new (<3 mo old) HDD
The extended test just finished and looks like there's definitely a problem. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate PO-R-- 100 100 001 - 0 2 Throughput_Performance --S--- 133 133 054 - 108 3 Spin_Up_Time POS--- 083 083 001 - 345 (Average 345) 4 Start_Stop_Count -O--C- 100 100 000 - 10 5 Reallocated_Sector_Ct PO--CK 100 100 001 - 0 7 Seek_Error_Rate -O-R-- 100 100 001 - 0 8 Seek_Time_Performance --S--- 140 140 020 - 15 9 Power_On_Hours -O--C- 100 100 000 - 1972 10 Spin_Retry_Count -O--C- 100 100 001 - 0 12 Power_Cycle_Count -O--CK 100 100 000 - 10 22 Unknown_Attribute PO---K 100 100 025 - 100 192 Power-Off_Retract_Count -O--CK 100 100 000 - 3197 193 Load_Cycle_Count -O--C- 100 100 000 - 3197 194 Temperature_Celsius -O---- 044 044 000 - 37 (Min/Max 24/43) 196 Reallocated_Event_Count -O--CK 100 100 000 - 0 197 Current_Pending_Sector -O---K 100 100 000 - 8 198 Offline_Uncorrectable ---R-- 100 100 000 - 0 199 UDMA_CRC_Error_Count -O-R-- 100 100 000 - 0 nnc-smart-20210801-1758.zip nnc-diagnostics-20210801-1804.zip
-
Read Errors found in new (<3 mo old) HDD
Ok, I'm running an extended test now.
-
Read Errors found in new (<3 mo old) HDD
I just now got a Warning message from my server that my array has errors. However, it only lists it as a warning, and I just ran a SMART test on that drive and got "Completed without error." I'm not sure what, if anything, I should do about this. I sure would hate to have to replace such a new (and expensive!) drive. Event: Unraid array errors Subject: Warning [NNC] - array has errors Description: Array has 1 disk with read errors Importance: warning Disk 15 - WDC_WD160EDFZ-11AFWA0_2BH4U4PN (sdt) (errors 698) nnc-diagnostics-20210801-0325.zip
-
[SOLVED] All user shares have disappeared from unRAID GUI
Darn, I thought the hardware issues were behind me when I replaced the cache drive. Things have been working so well for about 2 months, and now I'm right back in there. I rebooted just now and things are at least working again, but I'm fully expecting things to crash again soon. I feel like a broken record at this point, but I don't know what else could be bad. It's ECC RAM in a T630 PowerEdge, I can't imagine something like the mobo or CPUs are failing. And no SATA cables to worry about, either.
-
[SOLVED] All user shares have disappeared from unRAID GUI
I just encountered this issue. At the same time, multiple Dockers refuse to load, and I have 2 uncorrectable errors on a brand new 2TB SSD cache. Attached are my diagnostics. Here's a copy of the recent log. Jul 26 02:54:50 NNC root: plugin: running: /boot/config/plugins/dynamix.my.servers/dynamix.unraid.net.txz Jul 26 02:54:51 NNC root: plugin: creating: /boot/config/plugins/dynamix.my.servers/unraid-api.tgz - downloading from URL https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/unraid-api/unraid-api-2.23.2.tgz Jul 26 02:54:57 NNC root: plugin: running: anonymous Jul 26 02:54:58 NNC root: plugin: running: anonymous Jul 26 02:54:59 NNC root: plugin: running: anonymous Jul 26 02:55:02 NNC root: plugin: creating: /boot/config/plugins/dynamix.my.servers/libvirt.node - downloading from URL https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/unraid-api/libvirt.node Jul 26 02:55:04 NNC root: plugin: running: anonymous Jul 26 02:55:04 NNC root: plugin: creating: /boot/config/plugins/dynamix.system.temp/dynamix.system.temp.txz - downloading from URL https://raw.githubusercontent.com/bergware/dynamix/master/archive/dynamix.system.temp.txz Jul 26 02:55:06 NNC root: plugin: checking: /boot/config/plugins/dynamix.system.temp/dynamix.system.temp.txz - MD5 Jul 26 02:55:06 NNC root: plugin: running: /boot/config/plugins/dynamix.system.temp/dynamix.system.temp.txz Jul 26 02:55:06 NNC root: plugin: running: anonymous Jul 26 02:55:06 NNC root: Starting unraid-api v2.23.2 Jul 26 02:55:06 NNC root: Connecting to the "production" environment. Jul 26 02:55:08 NNC root: plugin: running: anonymous Jul 26 02:55:08 NNC root: plugin: running: anonymous Jul 26 02:55:08 NNC root: plugin: creating: /boot/config/plugins/community.applications/community.applications-2021.07.24-x86_64-1.txz - downloading from URL https://raw.githubusercontent.com/Squidly271/community.applications/master/archive/community.applications-2021.07.24-x86_64-1.txz Jul 26 02:55:08 NNC root: plugin: checking: /boot/config/plugins/community.applications/community.applications-2021.07.24-x86_64-1.txz - MD5 Jul 26 02:55:08 NNC root: plugin: running: /boot/config/plugins/community.applications/community.applications-2021.07.24-x86_64-1.txz Jul 26 02:55:08 NNC root: Daemonizing process. Jul 26 02:55:08 NNC root: Daemonized successfully! Jul 26 02:55:08 NNC flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup.php update Jul 26 02:55:09 NNC root: plugin: running: anonymous Jul 26 02:55:09 NNC root: plugin: running: anonymous Jul 26 02:55:09 NNC root: plugin: running: anonymous Jul 26 02:55:09 NNC root: plugin: creating: /boot/config/plugins/ca.update.applications/ca.update.applications-2021.07.19-x86_64-1.txz - downloading from URL https://raw.githubusercontent.com/Squidly271/ca.update.applications/master/archive/ca.update.applications-2021.07.19-x86_64-1.txz Jul 26 02:55:09 NNC root: plugin: checking: /boot/config/plugins/ca.update.applications/ca.update.applications-2021.07.19-x86_64-1.txz - MD5 Jul 26 02:55:09 NNC root: plugin: running: /boot/config/plugins/ca.update.applications/ca.update.applications-2021.07.19-x86_64-1.txz Jul 26 02:55:09 NNC root: plugin: running: anonymous Jul 26 02:56:03 NNC root: Fix Common Problems Version 2021.05.03 Jul 26 02:56:07 NNC root: Fix Common Problems: Warning: Docker application openvpn-as has moderator comments listed Jul 26 02:57:56 NNC ool www[902]: /usr/local/emhttp/plugins/dynamix/scripts/btrfs_scrub 'start' '/var/lib/docker' '' Jul 26 02:57:56 NNC kernel: BTRFS info (device sde1): scrub: started on devid 1 Jul 26 02:59:49 NNC kernel: BTRFS warning (device sde1): checksum error at logical 43328684032 on dev /dev/sde1, physical 43328684032, root 5, inode 9392254, offset 0, length 4096, links 1 (path: appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Metadata/Movies/3/83438a0636fb68cb11177e21109aa852b8da507.bundle/Contents/com.plexapp.agents.imdb/posters/2b543ef4e80169114c84e6fd534d6783fc2afa01) Jul 26 02:59:49 NNC kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 Jul 26 02:59:49 NNC kernel: BTRFS error (device sde1): unable to fixup (regular) error at logical 43328684032 on dev /dev/sde1 Jul 26 02:59:49 NNC kernel: BTRFS warning (device sde1): checksum error at logical 43328688128 on dev /dev/sde1, physical 43328688128, root 5, inode 9392254, offset 4096, length 697, links 1 (path: appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Metadata/Movies/3/83438a0636fb68cb11177e21109aa852b8da507.bundle/Contents/com.plexapp.agents.imdb/posters/2b543ef4e80169114c84e6fd534d6783fc2afa01) Jul 26 02:59:49 NNC kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 Jul 26 02:59:49 NNC kernel: BTRFS error (device sde1): unable to fixup (regular) error at logical 43328688128 on dev /dev/sde1 Jul 26 03:07:13 NNC kernel: BTRFS info (device sde1): scrub: finished on devid 1 with status: 0 nnc-diagnostics-20210726-1012.zip
-
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
Hi all. I upgraded from Lets Encrypt to SWAG this week, and initially things were fine. But then a separate cache corruption issue occurred, and I had to reformat my cache drive. Now that I've ran Mover twice (once to move everything to the array, and again after the reformat back to the cache), things aren't working as expected. SWAG is failing to run and seems to be missing certain files. Honestly I'm not much of an expert here, I can follow along @SpaceInvaderOne's videos and google enough to be dangerous, but this has me stuck. Would anyone be kind enough to provide some guidance on what I should try? I don't have a CA backup because the last one ran before I had SWAG, and I can't restore Lets Encrypt because the app has been delisted and I no longer have the template saved. To support the app dev(s) visit: Certbot: https://supporters.eff.org/donate/support-work-on-certbot To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... Variables set: PUID=99 PGID=100 TZ=America/Los_Angeles URL=[***OMITTED***] SUBDOMAINS=ombi,cloud EXTRA_DOMAINS= ONLY_SUBDOMAINS=true VALIDATION=http CERTPROVIDER= DNSPLUGIN= EMAIL=[***OMITTED***] STAGING=false Using Let's Encrypt as the cert provider SUBDOMAINS entered, processing SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d ombi.[***OMITTED***] -d cloud.[***OMITTED***] E-mail address entered: [***OMITTED***] http validation is selected Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Renewing an existing certificate for ombi.[***OMITTED***] and cloud.[***OMITTED***] An unexpected error occurred: There were too many requests of a given type :: Error creating new order :: too many certificates already issued for exact set of domains: cloud.[***OMITTED***],ombi.[***OMITTED***]: see https://letsencrypt.org/docs/rate-limits/ Please see the logfiles in /var/log/letsencrypt for more details. Can't open privkey.pem for reading, No such file or directory 22963416648520:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('privkey.pem','r') 22963416648520:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76: unable to load private key cat: privkey.pem: No such file or directory cat: fullchain.pem: No such file or directory New certificate generated; starting nginx Starting 2019/12/30, GeoIP2 databases require personal license key to download. Please retrieve a free license key from MaxMind, and add a new env variable "MAXMINDDB_LICENSE_KEY", set to your license key. [cont-init.d] 50-config: exited 0. [cont-init.d] 60-renew: executing... Can't open /config/keys/letsencrypt/fullchain.pem for reading, No such file or directory 23299000830792:error:02001002:system library:fopen:No such file or directory:crypto/bio/bss_file.c:69:fopen('/config/keys/letsencrypt/fullchain.pem','r') 23299000830792:error:2006D080:BIO routines:BIO_new_file:no such file:crypto/bio/bss_file.c:76: unable to load certificate The cert is either expired or it expires within the next day. Attempting to renew. This could take up to 10 minutes. <-------------------------------------------------> <-------------------------------------------------> cronjob running on Sat Apr 17 11:46:29 PDT 2021 Running certbot renew Saving debug log to /var/log/letsencrypt/letsencrypt.log - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/ombi.[***OMITTED***]-0001.conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cert not yet due for renewal - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Processing /etc/letsencrypt/renewal/ombi.[***OMITTED***].conf - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/certbot/_internal/renewal.py", line 70, in _reconstitute renewal_candidate = storage.RenewableCert(full_path, config) File "/usr/lib/python3.8/site-packages/certbot/_internal/storage.py", line 468, in __init__ self._check_symlinks() File "/usr/lib/python3.8/site-packages/certbot/_internal/storage.py", line 538, in _check_symlinks raise errors.CertStorageError( certbot.errors.CertStorageError: expected /etc/letsencrypt/live/ombi.[***OMITTED***]/cert.pem to be a symlink Renewal configuration file /etc/letsencrypt/renewal/ombi.[***OMITTED***].conf is broken. Skipping. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The following certificates are not due for renewal yet: /etc/letsencrypt/live/ombi.[***OMITTED***]-0001/fullchain.pem expires on 2021-07-16 (skipped) No renewals were attempted. No hooks were run. Additionally, the following renewal configurations were invalid: /etc/letsencrypt/renewal/ombi.[***OMITTED***].conf (parsefail) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 0 renew failure(s), 1 parse failure(s) [cont-init.d] 60-renew: exited 0. [cont-init.d] 70-templates: executing... **** The following reverse proxy confs have different version dates than the samples that are shipped. **** **** This may be due to user customization or an update to the samples. **** **** You should compare them to the samples in the same folder to make sure you have the latest updates. **** /config/nginx/proxy-confs/ombi.subdomain.conf /config/nginx/proxy-confs/nextcloud.subdomain.conf [cont-init.d] 70-templates: exited 0. [cont-init.d] 99-custom-files: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-files: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. nginx: [emerg] cannot load certificate "/config/keys/letsencrypt/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/config/keys/letsencrypt/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)