dirtysanchez
-
Posts
949 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by dirtysanchez
-
-
While this is hindsight, problems like this is why all my computers are set to DHCP, and I set static IP's within the router. That way there's no issues if the router ever changes.
Agreed. I do address reservations in the router for all static devices as well. That said, I think going that route is a bit too advanced for this particular user, so was trying to get him back up and running as easily as possible.
The user could also just set DHCP to "yes" in the network.cfg file and let the server lease an address. If DNS is working correctly on the router he should be able to hit it via hostname.
-
So this is writing directly to the protected array. 80-90MBs is quite normal performance. This is due to the slower disks and the parity calculations. Hence the reason many people opt for a cache drive.
No, he said one is cache only and the other is "cached". By that I assume he means "cache enabled", i.e. it is written to the cache drive then copied to the array each night when mover runs.
-
Since you're not a frequent poster and you hadn't given us information about your hardware, I think we were just looking for more evidence that your numbers were believable. Not everyone who posts can be taken at their word regarding their diagnosis of their systems.
And you'd be surprised how many people think MB/s and Mb/s are the same thing. Obviously you know the difference.
My mistake on the "writing directly to the cache drive" statement. Again, sorry I can't be of more help than to say that writing to a "cache enabled" share on my server I can saturate GigE.
What are the specs of your system?
-
Is the cache drive an older, slower drive?
I have a couple that only make 53 MB/s.
It's most certainly an SSD as he stated he gets 220-240 MB/s when copying directly to the cache drive.
-
I can't speak as to your issue, but what I can say is it shouldn't be unRaid overhead causing that much of a slowdown. I can write to a cache enabled share on my server at 112MB/s, basically maxing out GigE.
-
Plex stores the metadata in the docker appdata location commonly called /config. /mnt/cache/appdata/plex for example.
-
Thank you very much D.S. (I have a hard time calling someone who is offering their expertise dirty...
I greatly appreciate your help.I was able to get into the tower and find the flash drive as well as open up the network.cfg file. I changed the Gateway and DNS_Server1 to the router IP address as you indicated. I located the other file, but I had another question (sorry). Is there a specific IP address needed for the IPADDR (i.e. computer)?
Thanks again!
No, no specific address. It's whatever address you want the server to use. You just need to make sure the address is not already being used. You said the server used to be 192.168.1.99, so how about using 10.0.0.99? You can use 10.0.0.x where x is any number between 2 and 254. You can't use 1 because 10.0.0.1 is your router.
To make sure it is not in use, assuming your other computer is a windows machine, open a command prompt (click start and type cmd and press enter). Type "ping 10.0.0.99" without the quotes (or whatever address you want to use) and press enter. If the response is no reply or destination host unreachable, that address is not in use and you can use it.
-
Yes, you can't adopt an AP in multiple controllers. You need to reset the AP to defaults before you can adopt it in another controller.
SSH into the AP and run the following command.
syswrapper.sh restore-default
The AP will restore to factory defaults and reboot. Once it reboots, reconnect and then run the commands in the previous post.
-
1
-
-
FWIW, after the container was updated by sparklyballs, that is all I get in the log. It no longer shows any other info like downloading repositories or such, but the container is running and working.
My docker has been running since last night and the only other entries in the log are the cron entries once an hour.
----------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io ----------------------------------- GID/UID ----------------------------------- User uid: 99 User gid: 100 ----------------------------------- We are now refreshing packages from apt repositorys, this *may* take a while Nov 17 18:48:46 1fdda773de16 syslog-ng[61]: syslog-ng starting up; version='3.5.3' Nov 17 19:17:01 1fdda773de16 /USR/SBIN/CRON[424]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 17 20:17:01 1fdda773de16 /USR/SBIN/CRON[464]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 17 21:17:01 1fdda773de16 /USR/SBIN/CRON[467]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 17 22:17:01 1fdda773de16 /USR/SBIN/CRON[470]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 17 23:17:01 1fdda773de16 /USR/SBIN/CRON[473]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 18 00:17:01 1fdda773de16 /USR/SBIN/CRON[476]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 18 01:17:01 1fdda773de16 /USR/SBIN/CRON[479]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 18 02:17:01 1fdda773de16 /USR/SBIN/CRON[482]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 18 03:17:01 1fdda773de16 /USR/SBIN/CRON[485]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 18 04:17:01 1fdda773de16 /USR/SBIN/CRON[488]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 18 05:17:01 1fdda773de16 /USR/SBIN/CRON[491]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 18 06:17:01 1fdda773de16 /USR/SBIN/CRON[494]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 18 06:25:01 1fdda773de16 /USR/SBIN/CRON[497]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )) Nov 18 07:17:01 1fdda773de16 /USR/SBIN/CRON[570]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 18 08:17:01 1fdda773de16 /USR/SBIN/CRON[586]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 18 09:17:01 1fdda773de16 /USR/SBIN/CRON[589]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 18 10:17:01 1fdda773de16 /USR/SBIN/CRON[592]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Is it possible the ports you are trying to use are already in use?
-
False is the default setting on settings.json
I agree was from your previous docker.https://github.com/linuxserver/docker-transmission/blob/master/defaults/settings.json
Good to know. Thank you.
-
the "issue" was because of an update to the unifi app itself.
Yes, I gathered that from your previous post. Would it make you feel better if I said "the issue with the app" instead of "the issue with the docker"?
I discovered an issue (an issue that anyone that actually attempted to USE the docker would have found), posted about it, and got told that I was basically doing it all wrong and "screaming that the container is broken". Nobody is attacking you or your work. Slow your roll.
-
There was, at least on mine (default admin/pass), but that may have been a remnant from a previous docker as I migrated to the Linuxserver docker from another one.
Anyway, I figured out how to disable it. Stop the docker, change the rpc-authentication-required setting to false in the settings.json file in the docker appdata directory. It will no longer prompt for a password.
-
Also as a sidenote nobody in the team does actually use the container
I figured as much as the issues with the docker weren't obvious until one actually configured the docker then restarted it, hence the reason I asked.
Big thanks to the group for all the great dockers you guys produce.
-
Updated container and docker now starts every time, stop/start and restart.
It did not "find" and use my previous config. I gather from your post that due to the issue it was stored inside the container and so would have been wiped out on container update.
Reconfigured controller again, adopted AP's, etc. Stop/start or restart container and config is now retained. All appears to be sorted.
Thanks for fixing it so quickly.
-
The easiest way would be to power down the server and remove the flash drive. Place the flash drive in another computer. In the config folder should be a file called network.cfg. Open the file and edit it, correcting the wrong bits. The only things you should have to change are IPADDR, GATEWAY, and DNS_SERVER1.
IPADDR is the address you want the server to use.
Both GATEWAY and DNS_SERVER1 should be your routers address 10.0.0.1
Make sure to use a Linux compliant text editor like Notepad++
-
I just done a test install of this docker (I don't use unifi products), here is my log output:
----------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io ----------------------------------- GID/UID ----------------------------------- User uid: 99 User gid: 100 ----------------------------------- We are now refreshing packages from apt repositorys, this *may* take a while ----------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io ----------------------------------- GID/UID ----------------------------------- User uid: 99 User gid: 100 ----------------------------------- We are now refreshing packages from apt repositorys, this *may* take a while (Reading database ... 15447 files and directories currently installed.) Preparing to unpack .../unifi_4.7.6-6357_all.deb ... Unpacking unifi (4.7.6-6357) over (4.7.5-6348) ... Removing any system startup links for /etc/init.d/unifi ... /etc/rc0.d/K08unifi /etc/rc1.d/K08unifi /etc/rc2.d/S92unifi /etc/rc3.d/S92unifi /etc/rc4.d/S92unifi /etc/rc5.d/S92unifi /etc/rc6.d/K08unifi Processing triggers for ureadahead (0.100.0-16) ... Setting up unifi (4.7.6-6357) ... Adding system startup for /etc/init.d/unifi ... /etc/rc0.d/K08unifi -> ../init.d/unifi /etc/rc1.d/K08unifi -> ../init.d/unifi /etc/rc6.d/K08unifi -> ../init.d/unifi /etc/rc2.d/S92unifi -> ../init.d/unifi /etc/rc3.d/S92unifi -> ../init.d/unifi /etc/rc4.d/S92unifi -> ../init.d/unifi /etc/rc5.d/S92unifi -> ../init.d/unifi * Starting Ubiquiti UniFi Controller unifi ...done. Nov 17 23:36:09 d7d25b3354a3 syslog-ng[223]: syslog-ng starting up; version='3.5.3'
and I can get to the Unifi wizard.
I think you misunderstood my post. I can get it to install and start. I can configure the controller, adopt my AP's, etc and all is well. But as soon as the container is restarted it will no longer run. The only way to get it to run is to "edit and save" the container without changing anything. Once the container rebuilds it will run again, but when you connect to the webGUI the config is lost and you are back to the UniFi Setup Wizard.....
-
i guess
"We are now refreshing packages from apt repositorys, this *may* take a while"
we have no way of knowing if your internet speed is terrible or you are downloading anything.
but just restarting a container mid update and expecting everything to work and then screaming that the container is broken.....
When it's hung it will sit there forever, I don't think that has anything to do with my Internet speed. But if you think it's pertinent my connection is 60/4. When it does in fact check and update it takes roughly 60 seconds or so.
I'm not "screaming that it's broken" and if it came off that way I apologize. That said, if I fully configure UniFi and have it operational, then stop the docker and start the docker (no different than what happens during a reboot of the server) IF it does in fact restart successfully, the config is lost and you are back at the UniFi Setup Wizard. Does that not sound broken to you?
-
This docker is pretty broken. Is anyone in the Linuxserver.io group actually using it?
I migrated to this docker today from the existing pducharme docker. I was unable to successfully migrate and keep the existing configuration. I eventually had to wipe the existing and start from scratch. No biggie really, as I wouldn't expect to always be able to migrate an existing docker config anyway.
As for how the docker is broken, there are 2 major issues.
1. If the docker is restarted, it will not come back online. If you watch the logs, it will just sit at "We are now refreshing packages from apt repositorys, this *may* take a while" indefinitely. The only way to get it running again is to "edit and save" the docker (without changing anything) causing it to rebuild the container which will cause it to actually refresh the packages from the apt repository and rebuild the container.
2. The much bigger issue is after the container is rebuilt, you connect to the webGUI all configuration is lost and you are presented with the UniFi Controller Setup Page again.
The one thing I haven't tried is if it will start successfully after a full server reboot.
If you need any further information, or testing (since I actively use UniFi Controller), please let me know.
-
Any way to remove the username and password for the webGUI?
Environment variable or via the settings.json file?
-
kept the standard ports, and still can't find it. maybe because the docker runs in bridge mode
It's not related to bridge mode. The AP doesn't know where the controller is unless you have your DHCP server specifically set up to issue the controller address as an option in the lease. Normally you would use the UniFi discovery tool to find the AP and tell it the IP of the controller, but the UniFi dockers don't have the discovery tool as it is a separate app.
To get the AP to show up in the controller so it can be adopted and provisioned, do the following:
Determine the IP the AP was leased
SSH to that IP
Login as ubnt / ubnt
mca-cli
set-inform http://address:port/inform (where address is IP of controller and port is the port you are using for inform, default is 8080)
Once you run the set inform command it should show in the controller. As soon as you click adopt you need to run the set inform command a second time on the AP.
EDIT: Syntax correction
-
3
-
2
-
-
got this installed moved some ports but it can't find my device
i guess the ports for the devices to be seen are immutable.
change the ports on the other dockers where you have a clash.
You can change the ports the Docker uses internally by editing the system.properties file in the docker config directory.
-
1
-
-
Hi all,
Server has been rock solid for 3 years, never crashed once. In the span of about 4 weeks, it has now crashed 4 times. Once crashed webGUI becomes unresponsive, unable to access shares, but dockers are still running, and can SSH into box. All attempts to shut down the system via command line fail and I have to power cycle the server, although it's entirely possible I'm not doing it correctly via cmd line.
It just crashed again this afternoon, and here is the relevant portion of the syslog which I pulled before power cycling the server.
Nov 16 14:09:28 Landfill kernel: general protection fault: 0000 [#1] PREEMPT SMP Nov 16 14:09:28 Landfill kernel: Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables kvm_intel kvm vhost_net vhost macvtap macvlan tun xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod i2c_i801 ahci libahci r8169 mii [last unloaded: md_mod] Nov 16 14:09:28 Landfill kernel: CPU: 1 PID: 13845 Comm: shfs Not tainted 4.1.7-unRAID #3 Nov 16 14:09:28 Landfill kernel: Hardware name: System manufacturer System Product Name/P8H77-I, BIOS 0904 10/15/2012 Nov 16 14:09:28 Landfill kernel: task: ffff88002ce3baa0 ti: ffff880006fd0000 task.ti: ffff880006fd0000 Nov 16 14:09:28 Landfill kernel: RIP: 0010:[<ffffffff811535ac>] [<ffffffff811535ac>] __discard_prealloc+0x98/0xb3 Nov 16 14:09:28 Landfill kernel: RSP: 0018:ffff880006fd3bb8 EFLAGS: 00010246 Nov 16 14:09:28 Landfill kernel: RAX: ffff88011a2af468 RBX: ffff88011a2af440 RCX: d1e528b18ebe2731 Nov 16 14:09:28 Landfill kernel: RDX: 1b1530a073d5c084 RSI: ffff88011a2af440 RDI: ffff880006fd3d00 Nov 16 14:09:28 Landfill kernel: RBP: ffff880006fd3be8 R08: 0000000000001199 R09: 000000000003ad6e Nov 16 14:09:28 Landfill kernel: R10: 00000000ffffffff R11: ffff880153d82e38 R12: ffff880006fd3d00 Nov 16 14:09:28 Landfill kernel: R13: ffff88011a2af4e0 R14: ffff880006fd3d00 R15: 00000000aec273c8 Nov 16 14:09:28 Landfill kernel: FS: 00002b7615618700(0000) GS:ffff88021fa80000(0000) knlGS:0000000000000000 Nov 16 14:09:28 Landfill kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 16 14:09:28 Landfill kernel: CR2: 00000000006fb808 CR3: 0000000208e3a000 CR4: 00000000001406e0 Nov 16 14:09:28 Landfill kernel: Stack: Nov 16 14:09:28 Landfill kernel: ffff88021416b200 ffff880006fd3d00 ffffc90001599000 ffffc900015b91e8 Nov 16 14:09:28 Landfill kernel: ffff880006fd3d00 ffff880214148800 ffff880006fd3c18 ffffffff8115362b Nov 16 14:09:28 Landfill kernel: ffff880006fd3d00 ffff88002ce3baa0 ffffc90001599000 ffffc90001599000 Nov 16 14:09:28 Landfill kernel: Call Trace: Nov 16 14:09:28 Landfill kernel: [<ffffffff8115362b>] reiserfs_discard_all_prealloc+0x44/0x4e Nov 16 14:09:28 Landfill kernel: [<ffffffff8116fe6c>] do_journal_end+0x4e7/0xc78 Nov 16 14:09:28 Landfill kernel: [<ffffffff81170b5c>] journal_end+0xae/0xb6 Nov 16 14:09:28 Landfill kernel: [<ffffffff81161249>] reiserfs_dirty_inode+0x6c/0x7c Nov 16 14:09:28 Landfill kernel: [<ffffffff8104d390>] ? ns_capable+0x3a/0x4f Nov 16 14:09:28 Landfill kernel: [<ffffffff8111cb25>] __mark_inode_dirty+0x2f/0x265 Nov 16 14:09:28 Landfill kernel: [<ffffffff8115cfd7>] reiserfs_setattr+0x262/0x297 Nov 16 14:09:28 Landfill kernel: [<ffffffff810ff408>] ? __sb_start_write+0x9a/0xce Nov 16 14:09:28 Landfill kernel: [<ffffffff8111367a>] notify_change+0x1db/0x2dc Nov 16 14:09:28 Landfill kernel: [<ffffffff811164d8>] ? __mnt_want_write+0x4a/0x61 Nov 16 14:09:28 Landfill kernel: [<ffffffff810fbe72>] chmod_common+0x7a/0x102 Nov 16 14:09:28 Landfill kernel: [<ffffffff810fcd75>] SyS_fchmodat+0x3f/0x77 Nov 16 14:09:28 Landfill kernel: [<ffffffff810fcdc1>] SyS_chmod+0x14/0x16 Nov 16 14:09:28 Landfill kernel: [<ffffffff815f562e>] system_call_fastpath+0x12/0x71 Nov 16 14:09:28 Landfill kernel: Code: 1c 75 bb 0f 0b 85 c0 74 12 48 8b 93 e8 00 00 00 4c 89 ee 4c 89 e7 e8 be 6e 00 00 48 8b 4b 28 44 89 7b 1c 48 8d 43 28 48 8b 53 30 <48> 89 51 08 48 89 0a 48 89 43 28 48 89 43 30 58 5b 41 5c 41 5d Nov 16 14:09:28 Landfill kernel: RIP [<ffffffff811535ac>] __discard_prealloc+0x98/0xb3 Nov 16 14:09:28 Landfill kernel: RSP <ffff880006fd3bb8> Nov 16 14:09:28 Landfill kernel: ---[ end trace 9726fa9b66052d85 ]---
There is nothing in the log prior that appears to be related to the issue. Nothing with the server has changed recently, hardware-wise, and software-wise the only differences in the last few months would be updated plugins and/or dockers. No new plugins or dockers installed in at least 3 months.
Possible RAM issue? I'll run a memtest overnight. Beyond that I'm at a loss as far as troubleshooting Linux kernel panics. Any help would be appreciated.
-
-
If your unRAID is set to DHCP and it is leasing an address, the address could have changed. You really should give it a static address by creating a DHCP reservation in your router so that it always gets the same IP. You can also just set it statically in the unRAID GUI, but better to do an address reservation for DNS reasons.
I greatly appreciate your help.
Quieter Fans
in Hardware
Posted
What bubbaQ said.
As for fans themselves, what garycase said. Noctua. Great fans.