destrugter
-
Posts
18 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by destrugter
-
-
6 hours ago, aptalca said:
Post your container settings
-
I'm having the following issue when trying to renew my certificate.
QuoteAttempting to renew cert (redacted.com) from /etc/letsencrypt/renewal/redacted.com.conf produced an unexpected error: Problem binding to port 80: Could not bind to IPv4 or IPv6.. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/redacted.com/fullchain.pem (failure)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/redacted.com/fullchain.pem (failure)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Running post-hook command: if ps aux | grep 's6-supervise nginx' | grep -v grep > /dev/null; then s6-svc -u /var/run/s6/services/nginx; fi; cd /config/keys/letsencrypt && openssl pkcs12 -export -out privkey.pfx -inkey privkey.pem -in cert.pem -certfile chain.pem -passout pass: && cat {privkey,fullchain}.pem > priv-fullchain-bundle.pem
Hook command "if ps aux | grep 's6-supervise nginx' | grep -v grep > /dev/null; then s6-svc -u /var/run/s6/services/nginx; fi; cd /config/keys/letsencrypt && openssl pkcs12 -export -out privkey.pfx -inkey privkey.pem -in cert.pem -certfile chain.pem -passout pass: && cat {privkey,fullchain}.pem > priv-fullchain-bundle.pem" returned error code 1
Error output from if:
cat: {privkey,fullchain}.pem: No such file or directory
1 renew failure(s), 0 parse failure(s)
[cont-init.d] 50-config: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Server readyI own the domain and have a Dynamic DNS service that updates the domain to point to my IP once per day. It resolves correctly.
-
I'm having an issue where I put a mariadb docker on another drive and it's not included in the resulting backup archive
-
I'm not trying to be bothersome, but I'm still having issues and if there's anything else I can do or any other kind of information you need please let me know. I've went through a complete reinstall of unraid plus all of my docker containers and stuff. I started from fresh settings too (as in, I renamed the old folder so that the docker would start with brand new downloaded files), the only thing I carried over was my array data. I do appreciate your time
This line shows up, I'll look into it but maybe it's helpful for you
2018-08-22 17:35:21,321 DEBG 'rutorrent-script' stderr output: [NOTICE] [pool www] 'user' directive is ignored when FPM is not running as root [NOTICE] [pool www] 'group' directive is ignored when FPM is not running as root
-
I'm having some network issues with unraid. I've been testing various things as to why my server has been acting up over the network. Slow file transfers, dropped packets seen in ping. I've pinged 8.8.8.8 and my router. It results in some high ping and sometimes even dropped packets. Today, I typed ifconfig and found this which has a worrying amount of dropped packets
I started investigating thinking it was a hardware issue. I put in a LIveCD of Ubuntu and ran a 500 ping test and got these results:
Quote--- 192.168.10.1 ping statistics ---
500 packets transmitted, 500 received, 0% packet loss, time 510942ms
rtt min/avg/max/mdev = 0.141/0.263/4.299/0.184 msFor comparison, when running the ping on unraid:
Quote--- 192.168.10.1 ping statistics ---
500 packets transmitted, 500 received, 0% packet loss, time 513011ms
rtt min/avg/max/mdev = 0.149/1.479/189.961/12.208 msWhat I wound up doing after this was disabled VM and docker to at least see if bridging my connection to them was having any effect at all and this was the result:
Quote--- 192.168.10.1 ping statistics ---
500 packets transmitted, 500 received, 0% packet loss, time 511166ms
rtt min/avg/max/mdev = 0.148/0.538/154.873/6.909 msI did a final test and did a ping with just unraid and no mounted array and got these results:
Quote--- 192.168.10.1 ping statistics ---
500 packets transmitted, 500 received, 0% packet loss, time 510983ms
rtt min/avg/max/mdev = 0.161/0.252/0.557/0.041 msI'm not sure what this really means, or if it's a huge deal, but something's causing me to drop a ton of packets which is causing instability, slow network file transfer, intermittently slow internet downloads.
Other things I tried:
- Tried another computer
- Tried another port on my router
- Tried another cable
I appreciate any and all help. I will post all of my ping files and my diagnostics zip file to the post for anyone interested in looking.
ping_test_array_no_smb_access.txt
ping_test_array_smb_access.txt
tower-diagnostics-20180819-1506.zip
Edit
It looks to me like the ping spikes only happen after turning the disk array on. I ran a few thousand pings when it was off and it all looked normal. The minute I turn it on and run a 500 ping test I get a > 600ms ping
I telnet'd into my router and ran a 500 ping test to 8.8.8.8 and got the following results. While there was a spike it was only 36ms
Other things I have tried:
- Bought all new cat6 cables
- Tried a usb3 to ethernet adapter
- Ran several ping tests from my dd-wrt router to 8.8.8.8
- Changed ports the server was connected to on the router
- Connected straight to modem
-
31 minutes ago, binhex said:
ok well that log now shows it has a valid incoming port, which will be a definite step in the right direction, are you an unraid user?, what are you saving incomplete downloads to, array?, cache?, unassigned device?.
I'm an unraid user, downloads are saved to a folder on the array
-
3 hours ago, binhex said:
if you can see the web ui then you are connected to pia, this wont be accessible otherwise. your issue is that the endpoint you are connecting to is an ip address, and thus not in the list of endpoints that support port forwarding, thus its skipping port forwarding completely, this is why you are seeing extremely slow speeds.
so the solution is this:-
1. switch endpoint to one that does enable port forwarding (recommended solution) - if you want to do this then go here to see the current list of port forward enabled endpoints, then download the ovpn zip pack from here unzip it and place the corresponding port forward enabled endpoint ovpn file in /config/openvpn/ and restart the container.
It doesn't matter which endpoint I choose, the result ends up being the same. Here's a new log from using CA Vancouver. I will note that this docker was working flawlessly until around Monday or so. I'm not sure if I downloaded an update to it. I don't know if that information helps but just wanted to note it in case it does help somehow. These are very well seeded torrents on prolific trackers. To test I had my friend add one to his client and it worked instantly for him.
-
19 hours ago, binhex said:
what makes you think its not connected to PIA?.
it will do, you have debug turned on.
I turned it on because that's what the FAQ told me to do and post the log.
I don't know if it's not connecting to PIA, but it's not downloading/uploading torrents. What's happening is all of my torrents will just stop working completely. Sometimes when I restart the docker they will download for a little bit but eventually they will stop. They will sometimes come back on in the middle of the night when I'm sleeping.
-
I'm having an issue where it seems that rtorrent isn't connecting to PIA. It keeps repeating the same message over and over again. I have the right login information, and I have the .ovpn file and certs in the openvpn folder
-
3 hours ago, dlandon said:
Show me the output from this command:
ls /dev/disk/by-id/root@Tower:~# ls /dev/disk/by-id/ ata-ST4000DM000-1F2168_W300N23H@ ata-ST4000DM000-2AE166_WCD00SKM-part1@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1RXZRX5@ ata-WDC_WD80EFAX-68LHPN0_7SGEH6ZC-part1@ wwn-0x15347340737589170177x@ wwn-0x17869328123984629760x-part1@ wwn-0x7337873558900592640x@ ata-ST4000DM000-1F2168_W300N23H-part1@ ata-ST4000DM000-2AE166_WCD00W9K@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1RXZRX5-part1@ ata-WDC_WD80EFAX-68LHPN0_7SGGS10C@ wwn-0x15347340737589170177x-part1@ wwn-0x2448360361219477504x@ wwn-0x7337873558900592640x-part1@ ata-ST4000DM000-1F2168_W301BFZE@ ata-ST4000DM000-2AE166_WCD00W9K-part1@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E5RF7ZFA@ ata-WDC_WD80EFAX-68LHPN0_7SGGS10C-part1@ wwn-0x16487769232413708288x@ wwn-0x2448360361219477504x-part1@ wwn-0x8009008642695254017x@ ata-ST4000DM000-1F2168_W301BFZE-part1@ ata-ST4000DM000-2AE166_WCD01D8E@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E5RF7ZFA-part1@ usb-SanDisk_Cruzer_Glide_20051941900F434249FC-0:0@ wwn-0x16487769232413708288x-part1@ wwn-0x2674452748132438016x@ wwn-0x8009008642695254017x-part1@ ata-ST4000DM000-1F2168_Z301EWPM@ ata-ST4000DM000-2AE166_WCD01D8E-part1@ ata-WDC_WD40EZRX-00SPEB0_WD-WCC4E2074065@ usb-SanDisk_Cruzer_Glide_20051941900F434249FC-0:0-part1@ wwn-0x16930046281319993344x@ wwn-0x2674452748132438016x-part1@ wwn-0x8049149434923208704x@ ata-ST4000DM000-1F2168_Z301EWPM-part1@ ata-ST500DM002-1BD142_Z3TS29S3@ ata-WDC_WD40EZRX-00SPEB0_WD-WCC4E2074065-part1@ wwn-0x10710563513610293248x@ wwn-0x16930046281319993344x-part1@ wwn-0x4942871422373482496x@ wwn-0x8049149434923208704x-part1@ ata-ST4000DM000-1F2168_Z3066X52@ ata-ST500DM002-1BD142_Z3TS29S3-part1@ ata-WDC_WD40EZRX-00SPEB0_WD-WCC4EME6RLLH@ wwn-0x10710563513610293248x-part1@ wwn-0x17180219197074984960x@ wwn-0x4942871422373482496x-part1@ wwn-0x9493789144843964417x@ ata-ST4000DM000-1F2168_Z3066X52-part1@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E0AHA407@ ata-WDC_WD40EZRX-00SPEB0_WD-WCC4EME6RLLH-part1@ wwn-0x12063343908222947328x@ wwn-0x17180219197074984960x-part1@ wwn-0x5796585026736902144x@ wwn-0x9493789144843964417x-part1@ ata-ST4000DM000-1F2168_Z306BCX1@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E0AHA407-part1@ ata-WDC_WD80EFAX-68LHPN0_7SG6BAPC@ wwn-0x12063343908222947328x-part1@ wwn-0x17553825102953598977x@ wwn-0x5796585026736902144x-part1@ ata-ST4000DM000-1F2168_Z306BCX1-part1@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E0XYDPLE@ ata-WDC_WD80EFAX-68LHPN0_7SG6BAPC-part1@ wwn-0x12945688142666682368x@ wwn-0x17553825102953598977x-part1@ wwn-0x604058783246864385x@ ata-ST4000DM000-2AE166_WCD00PES@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E0XYDPLE-part1@ ata-WDC_WD80EFAX-68LHPN0_7SG7KANC@ wwn-0x12945688142666682368x-part1@ wwn-0x17824789654740815873x@ wwn-0x604058783246864385x-part1@ ata-ST4000DM000-2AE166_WCD00PES-part1@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1RXZPUA@ ata-WDC_WD80EFAX-68LHPN0_7SG7KANC-part1@ wwn-0x1477663287396159489x@ wwn-0x17824789654740815873x-part1@ wwn-0x6059429298605936640x@ ata-ST4000DM000-2AE166_WCD00SKM@ ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E1RXZPUA-part1@ ata-WDC_WD80EFAX-68LHPN0_7SGEH6ZC@ wwn-0x1477663287396159489x-part1@ wwn-0x17869328123984629760x@ wwn-0x6059429298605936640x-part1@
-
8 hours ago, dlandon said:
1. Do you have the preclear plugin installed? Can I see a screen shot of the UD page?
2. Underscores are turned into spaces when renaming the mount point.
I do not have precede plugin.
It also looks like it's messing it up to give all of the disks the same mount point as well.
-
Let me start off by saying I really love your plugin. I actually have 2 issues with Unassigned Devices plugin. Some information:
- I am running unRAID Server OS version 6.3.5
- I am running Unassigned Devices plugin version 2017.09.20
- I am using this Mediasonic ProBox HF2-SU3S2 4 Bay 3.5' SATA HDD Enclosure over this Inateck Superspeed 4 Ports PCI-E to USB 3.0 Expansion Card. I am providing this information in case it's relevant in helping me, since the devices may not act correctly towards the plugin.
Now, my 2 issues:
- I am used to Unassigned Devices identifying my disks in the following fashion: {Model Number}-{Part Number}_{Serial Number}. For example: ST4000DM000-1F2168_XXXXXXXX. Instead what I'm getting is: 000-1F2168_000000000000
- I am used to Unassigned Devices mounting my disks in the following fashion: {Model Number}_{Part Number}_{Serial Number}. For example: ST4000DM000_1F2168_XXXXXXXX. I attempted to change this by unmounting the disk, clicking on the mount point, entering it in that format, and pressing enter. It results in the disk being mounted like this: ST4000DM000 1F2168 XXXXXXXX.
It doesn't matter the brand of the disk, all of my disks have appeared this way after recently reformatting the drives. I don't know if this is a bug or if it's simply the combination of devices I am using possibly misrepresenting the devices to unRAID and Unassigned Devices. This isn't something that kills the plugin for me, but if at all possible I would like to get the old behavior back for these devices.
I plugged the disk into the same array device where my pool lives, and the disk almost shows up correctly. The Identification part shows up 100% the way I'm used to seeing it, but the mount point was just set to: ST4000DM000_1F2168 and the issue with renaming with underscores turning into spaces still exists here. This is why I'm unsure if it's a bug or the combination of devices misrepresenting the data to unraid and unassigned devices.
Any and all help is appreciated.
-
16 minutes ago, bonienl said:
Replacing an existing drive with a new (bigger) drive isn't the same thing as adding a new drive to the array (extending the array). My understanding from your first post was that you extended the array.
With a drive replacement it will indeed to a disk rebuild. I assume your parity disk is also 8TB otherwise the rebuild is never successful. Anyway there is no format procedure required when replacing a disk.
The correct procedure to replace a disk is:
1. Stop the array
2. Remove the existing disk (you may need to power-off your system to do this)
3. Insert the new disk (and power-on your system if needed)
4. Select the new disk in the slot position of the old disk
5. Let unRAID do the disk rebuild
6. Once the rebuild is finished, your array is in operational state with all disks available
I followed that. When I start unraid it shows a blue square next to the 8tb drive indicating a new device. I start the array and it starts doing a parity rebuild, but says the disk is unmountable. That's when I saw and tried the format option.
I will edit the original post to indicate this is and disk replacement
EDIT:
So it sounds like what I should do is remove both the old and new devices, let parity rebuild, add the 8TB disk as a new disk, then copy the data from the old disk to the new disk?
-
Just now, Frank1940 said:
Did you use this disk to replace a current data disk in the array or did you add it as an additional disk to the array (thus increasing the number of data disks by one)?
I am replacing an old disk with this disk
-
4 minutes ago, bonienl said:
When you add a new drive to the array. The first thing unRAID wants to do is a "clear" action. Once the drive is cleared it will ask you to format it.
Did the drive clear action finish? If yes, you can set a specific file-system instead of the default "auto" setting (XFS is preferred) and retry the drive format procedure.
I didn't see a clear action. I followed the instructions to replace a data drive and when I start the array with the new disk, it starts to rebuild parity. At this point it says the disk is unmount able and presents me with an option to format so I stopped the parity rebuild and checked the box to format and then click the format button and the entire UI becomes unresponsive, and in fact the page fails to load.
-
I'll post a diagnostic file later when I get home, but to answer your 2nd question I did not preclear it, it went straight into the array.
Edit: The only way I can get a diagnostic file though is by powering down and interrupting the process if it's doing anything
-
Hello,
I am trying to add a brand new WD 8TB Red to my data disks, and when I click the format option in the unraid ui, it goes completely unresponsive. I figured it would take a while due to the huge disk and went to bed and when I woke up it still was in that state. I do not see any disk activity on the led for the drive either.
Is this normal and I just need to leAve it alone?
Edit: This is for a drive replacement. Nothing is wrong with the old drive, I am just upgrading it to a new bigger drive
[Support] kru-x - Godaddy ddns
in Docker Containers
Posted · Edited by destrugter
Does this support wildcard subdomains?
Edit:
Sorry I just read over the previous posts and figured out how to do it. Thanks!