jedimstr

July 7, 2016

For the drives, just make sure /mnt/ is assigned on Host Path 4

Slightly confused by this statement, I understand how to assign, but what does "Host Path 4" mean? Here's the docker command I'm preparing:

docker run -t -v /var/run/docker.sock:/var/run/docker.sock -v "/mnt":"??" --name="telegraf" --net="host" -e INFLUXDB_URL=http://192.168.1.127:8086 -e HOSTNAME=tower jjungnickel/telegraf

What would I need to map /mnt to?

Thanks jedimstr!

I meant in the unRAID interface for the Docker Container for "Host Path 4". The reason you want to map /mnt in the container is to have recognizable /disk1 - /diskn and /user available for any storage based stats in InfluxDB. I also mapped the customized config file as well as "Host Path 2" /mnt/cache/appdata/telegraf/telegraf.conf.tpl to Container Path: /etc/telegraf/telegraf.conf.tpl .

Here are my mappings in my Telegraf Container settings:

width=900 http://i.imgur.com/kI9SeTu.png[/img]

July 7, 2016

This is my docker run command:

docker run -d --name="telegraf" --net="bridge" --privileged="true" -e HOST_PROC="/rootfs/proc" -e HOST_SYS="/rootfs/sys" -e HOST_MOUNT_PREFIX="/rootfs" -e HOST_ETC="/rootfs/etc" -e TZ="America/Denver" -v "/mnt/user/appdata/telegraf/telegraf.conf":"/etc/telegraf/telegraf.conf":ro -v "/proc":"/rootfs/proc":ro -v "/":"/rootfs":ro -v "/var/run/docker.sock":"/var/run/docker.sock":ro -v "/sys":"/rootfs/sys":ro -v "/etc":"/rootfs/etc":ro telegraf

This requires you to put in your own telegrafl.conf file at /mnt/user/appdata/telegraf/telegraf.conf

This has been working for me. The only thing that doesn't look right is my network sent and received. Haven't figured that out yet. But everything else is accurate.

Two things about the way Network sent and received are set in Telegraf.

[*]Data is stored as BYTES

[*]Data is progressive total

To get your sent and received you need to *8 the values to get bits per second and then to translate the values into recognizable graphs you have to use non_negative_derivative which will track the changes in value rather than just spouting out the growing total.

Example:

July 7, 2016

Have you experimented with using an SMB share with your Mac instead?

I know it's "common wisdom" that Mac's are slower with SMB than AFP, but in the last few versions of OSX SMB is actually the primary share format and AFP is deprecated. Apple considers AFP a "Legacy Service". From Mavericks and higher, OSX tries to connect to shares via SMB first before falling back to AFP.

On my 10GbE fiber connections, my old Mac Pro 1,1 on Yosemite transfers upwards of 600MB/s to an SMB share which compares favorably to my Windows 10 PC which transfers around 800MB/s on average to the same share. Bottleneck for my Mac Pro is probably the old PCIe 1 bus that the SFP+ card is connected to rather than what SMB on OSX can do. I keep AFP off now.

July 1, 2016

I mentioned this in other threads, but this applies here too...

I just did a migration of my Plex Server stuff from the Limetech repo to the LinuxServer.io repo.

I got tired of waiting for a a version update so I just switched to the LinuxServer.io repo for Plex from the Limetech one since LinuxServer.io keeps theirs up to date.

Here are the steps I took:

[*]Make note of your container mapped custom media path settings if you have them specifically set for PMS (for instance mine map /Media to /mnt/user/Media)

[*]Shutdown the Limetech PMS container, but don't delete it yet

[*]Backup your appdata config for PlexMedia Server (mine was in /mnt/cache/appdata/PlexMediaServer) to another folder for safety

[*]Add the LinuxServer.io Plex container. It can coexist with the other one temporarily as long as the other one isn't running since they're named differently

[*]Add the mapped media path you had in the Limetech container settings if you had it set there. It's not there by default in LinuxServer.io (although you could use the /user mapping that it does come with, I prefer a direct reference for isolation)

[*]The LinuxServer.io container will automatically startup after you're done setting it up and saving/apply. Access the server via the webUI and log in.

[*]Once the new Plex container is up and running after initial wizards, shut that container down again.

[*]With both containers shutdown, copy all the content from /mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server to /mnt/cache/appdata/plex/Library/Application Support/Plex Media Server (or whatever old and new Plex paths you have for the appdata stuff)

[*]Once you're done copying all the appdata stuff, startup your new Plex container again.

[*]Access the new Plex server via WebUI or from the Plex.tv site. Verify all your content, settings, channels, and custom Agents survived the transition, and that you're on the latest 1.0.0.2261 version in the Settings/Server page

[*]When you're satisfied everything survived the transition, you can delete the old Plex Media Server container.

[*]Update any other container paths that refer to your Plex Media Server install (i.e. the logs path for plexpy) since it will be under a new location in appdata

Hope this helps.

June 24, 2016

is there any easy was to change from one repo to another? i know i saw something in the forums once but cant seem to find it anymore.

Thanks