coppit

Hi all, As part of my move to unRAID 6.2 RC1, I thought I'd try moving my desktop into a VM. So I used "dd" to grab the system disk image, and used the nifty new Windows 10 template. I also used the nifty new VirtIO download feature to grab virtio-win-0.1.118-2.iso and mount it in the VM. I booted the VM and used VNC to install all the drivers. I didn't install the guest tools yet. I stopped the VM, and changed the system disk to use VirtIO. But during boot, Windows fails with the error INACCESSIBLE_BOOT_DEVICE. Help? Is the problem this? https://support.microsoft.com/en-us/kb/2795397 So I stopped the VM, switched the system disk to IDE, and started it. This time Windows tried to do startup repair. But I just selected the "reboot" option and the second time it came up clean. In a command prompt run as administrator, I ran the command: bcdedit /set {current} safeboot minimal as suggested by the Microsoft support site. This time the machine showed the automatic repair screen, followed immediately by SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. This webpage suggests that I should try to get into the recovery console and run "bootrec /fixmbr". But how do I do that? Is that the right answer? Luckily, I made a backup of the image before doing anything. I'll restore it, and will try telling windows to boot into safe mode after installing the VirtIO drivers. But I have no idea if I'm on the right track or not.

I'm stumped too. What do you get when you run this sequence?: cat /tmp/plugins/snmp/drive_temps.txt snmpwalk -v 2c localhost -c public 'NET-SNMP-EXTEND-MIB::nsExtendOutLine."disktemp"' cat /tmp/plugins/snmp/drive_temps.txt /usr/local/emhttp/plugins/snmp/drive_temps.sh cat /tmp/plugins/snmp/drive_temps.txt snmpwalk -v 2c localhost -c public 'NET-SNMP-EXTEND-MIB::nsExtendOutLine."disktemp"' cat /tmp/plugins/snmp/drive_temps.txt I'm wondering if there's an issue with the caching. Another thought: There's a "sleep 15" in the drive_temps.sh script. I don't remember why. Maybe removing it would allow the script to run faster, solving the problem for you? Try it let me know what happens.

This works nicely, thank you. But is there an easy way to make it permanent so that it survives a reboot? What you could try is putting something like this into your go script: echo "$(/sbin/ifconfig br0 | grep inet | awk '{print $2}') storage" >> /etc/hosts Then use the advanced container options to map /etc/hosts from the docker host to the container. The container will think that localhost is your server, but maybe that's okay?

Check out my FileBot container if you're looking for automated renaming, subtitle downloading, etc. Non-Linux apps can't be converted into docker containers or unraid plugins. Maybe later this year Windows apps might be containerizable though.

It will report failure if there are no files to move. Very confusing, I know. The UI doesn't show the cause of the failure. Please log into your server and run "docker logs FileBot" (use whatever your container name is). If it says "No files selected for processing", then that's to be expected. BTW, I've filed a bug about the UI here: http://lime-technology.com/forum/index.php?topic=47011.0

Sorry for being away. I've just pushed an update to the latest version, 1.2.12-1~ppa3~trusty1.

This seems like a mis-feature of the upgradepkg tool. I add the flag --install-new so that it will install perl if it's not already on the system. But it seems to also force-install the older version if a newer version already exists. If this is a big issue, I suppose I could write my own install tool wrapper that checks versions properly... In the meantime I'll just bump the version of perl to match nerdtools. I doubt it will break things. Let me test it.

Yeah, that's my setup too. You don't want the incomplete dir to be watched by filebot, since it apparently will try to process the file before it's done. Looking at the monitor, I do have it treating "file close" as an event. That's different then "file close after write", so I presume that event would be a "close after read". I haven't watched it closely enough to see if filebot only processes the file after seeding is over, or at least after no seeding has happened for the stabilization time. You could try setting a shorter stabilization time, or setting your seeding ratio lower. You can get FileBot to move instead of copy, but that can be a bit dangerous. Sometimes it mis-detects the files.

No, it doesn't exclude everything. I *processes* everything. As part of that work, it excludes the files it has processed. Are you sure you configured your output directory properly? It's writable? If you don't see any files there, log into your server, run a command to log into the container and look into its /output dir: docker exec -it FileBot bash ls /output If the container's /output has files, but outside of the container there are no files, then you've misconfigured the output dir. Correct. It waits a bit for the directory to stabilize before it runs. See the docs. https://hub.docker.com/r/coppit/filebot/ Within a few minutes it will run. Most likely it did eventually run, but if your output dir was not set right, you might not notice.

See the docs: https://hub.docker.com/r/coppit/filebot/ Specifically, the part about changing "copy" to "rename". Caveat emptor!

Did you mess with the settings in filebot.conf? Here are the defaults: SETTLE_DURATION=10 MAX_WAIT_TIME=01:00 MIN_PERIOD=05:00 Note that the MIN_PERIOD is 5 minutes, meaning that FileBot will at most run once every 5 minutes.

Unfortunately the UNRAID GUI doesn't capture the STDERR of docker logs. Can you guys log into your server and run: docker logs FileBot ? For example, if FileBot has already run and processed some files, it will say: Using excludes: /config/amc-exclude-list.txt (4725) No files selected for processing Failure (°_°) If you check the amc-exclude-list.txt, you would see the files there.

So you're telling the container to wait 3 minutes after the last event before running filebot? But you're also wanting filebot to try to run in 10 seconds? That's odd. Typically MIN_PERIOD would be more than SETTLE_DURATION. Is there any way that your Mac Mini is taking longer than 3 minutes to finish working on the files? One thing I can imagine is that the file is opened, and the container sees that event, but it doesn't see the writes that happen. So it doesn't know that there's still activity going on. I tried running "lsof" to see if we can detect that something outside the container has the file open still, but unfortunately it doesn't see it. As long as there is any duration in the creation of the file, there is going to be a risk that FileBot attempts to process the file. I recommend doing the unpacking in a separate directory, then do an atomic move of the files into the FileBot input directory. You can look for messages like this in the log to see why FileBot was run: Input directory didn't stabilize after $MAX_WAIT_TIME seconds. Triggering command anyway. Input directory stabilized for $SETTLE_DURATION seconds. Triggering command. Waiting an additional $remaining_time seconds before running command If you set DEBUG=1 in the config file, the monitor will dump a lot of information about the events that are detected. That would confirm my theory that it detects the opening of the file for writing, but not all the writes.

Yep. I just pushed a change. You'll need to add OpenSubtitles credentials and your preferred language to the config file. Update the container, run it, then compare filebot.conf against filebot.conf.new, and filebot.sh against filebot.sh.new.

Where are you expecting it to find those preferences? I think I'll need to update the container to allow you to specify the username and password, and also save it into the config directory on the host. I'll try to get to that soon. Some details are here: https://www.filebot.net/forums/viewtopic.php?f=3&t=228

What version of unraid?

Oh, I meant to reply to that. Why not map whatever you want to subdirectories within /output? The only thing I could think of is to create /output1 /output2, etc. so that you can map separate things to each of those. That's a bit awkward.

THIS CONTAINER IS NO LONGER SUPPORTED. (I'm using PiHole with OpenDNS Family Shield.) DansGuardian is a proxy that blocks naughty bits on the internet. Thes container are part of my template repository: https://github.com/coppit/docker-templates For more information on usage: https://hub.docker.com/u/coppit/dansguardian/ For source code: https://github.com/coppit/docker-dansguardian Of course, being a dummy, I noticed that DansGuardian has been superseded by e2guardian. Sigh. I may switch to that and drop support for this. It seems to be working okay though.

touch: cannot touch ‘/var/lib/tomcat7/logs/catalina.out’: No such file or directory ./run: line 8: /usr/lib/jvm/java-7-openjdk-amd64/bin/java: No such file or directory You're talking about the UI right? I'm not seeing that, at least with the 1.3 base I just updated to. How are you connecting to it? I'm using Microsoft remote desktop. If you're doing the same, try updating to the version I just pushed.

I'm now computing the temps in the background. So the initial call shouldn't time out. It won't have any data, but the next call should. Let me know how that works for you. I assume you mean this implementation? It looks like the code computes the drive manufacturer and uses that along with a user-configurable setting to determine whether to get the temps or not. I haven't seen my implementation spin up drives, so as long as the workaround above works, I think we're okay. But I concede that I may need to adapt the myMain code, before we can declare this done. Linux will use remaining space for file buffers and file cache. I don't think that's an unRAID behavior per se. Anyway, when I look in observium, it's reporting separately the used, buffers, cached, and free memory. Maybe it's a librenms problem?

In theory, yes, it can move the files. But I confess that I haven't played with it much.

Yeah, I was worried about that. The removal of the "if" condition suggested by Guzzi has the side effect of the script taking too long to run. I'll have to think about how to fix it.

Okay! Free space for shares is now reported by snmp: $ snmpwalk -v 2c localhost -c public 'NET-SNMP-EXTEND-MIB::nsExtendOutLine."sharefree"' NET-SNMP-EXTEND-MIB::nsExtendOutLine."sharefree".1 = STRING: Backups: 903213694976 NET-SNMP-EXTEND-MIB::nsExtendOutLine."sharefree".2 = STRING: Media: 2453300314112 NET-SNMP-EXTEND-MIB::nsExtendOutLine."sharefree".3 = STRING: Other: 3251798876160 NET-SNMP-EXTEND-MIB::nsExtendOutLine."sharefree".4 = STRING: TimeMachine-old: 3251798876160 NET-SNMP-EXTEND-MIB::nsExtendOutLine."sharefree".5 = STRING: temp: 104715132928 I still don't know how to get observium to display this data though. Help would be appreciated.

Right you are. I've included the dependency. Can you try it now? Note that if someone uninstalls NerdPack, it's going to uninstall libutempter and break mosh. I've pinged eschultz to see if we can resolve this.

Thanks. It will be in the next release. I guess you're looking for size? I suppose I could write a custom script like I did for the drive temps. Disk size is easy because query it is relatively fast. Looking at the unraid GUI, there's a "free" column next to the shares. It looks like that data comes from /var/local/emhttp/shares.ini, perhaps updated every few minutes by unraid. That would be easy. Would that work for you? If so, I need some recommendation on where the data should end up. Can I just "extend" something like I did for disk temps? Unfortunately computing the size is hard. That requires walking the whole tree, which for a big share could take several minutes. The other complexity is that you'll probably want a UI to configure which folders to monitor. This is a part of plugin design that I haven't waded into yet.