deusxanime

Yeah I couldn't believe it even started for me as it was. I pretty much had to fix and/or redo every line of my file.

I noticed that my watch/import directories weren't working, even after I got rtorrent going again from my previous startup issues. Upon investigation, it seems that there are tons of updated commands and parameters (see the page I linked above) and I ended up having to basically rewrite/recreate my rc file from scratch! FYI in case anyone else is seeing things not working as expected since the latest update, you may have outdated parameters that don't work or aren't recognized correctly anymore. Here's the new "base" rc file example from github if you need to start from scratch like I did.

Thanks for the info. It appears that system.method.* was deprecated and I should now just be using method.* for those parameters. Had a few in there that I changed and got it to start up. They must have fully removed them now in this release. Found the info here for anyone wondering (under the Method section). Also, I tried what you said and clicked the container and opened the console (when it still wasn't working), but when I put in and try to run "/usr/bin/rtorrent" I get a "no such file or directory" error. Was able to get it working luckily without needing that, but for future reference something that I might have done wrong? edit: Must have been some weird character coming over from copy-pasting from webpage, because if I type the "/usr/bin/rtorrent" in manually it works just as you said (and tab-completes yay!). Thanks again!

Here's my rc file. Hopefully it's something simple like that.

Updated rTorrent+VPN just now (not sure when the update came out, but only got a chance to do the update today) and now it won't start. Was running fine before. I see this in the log just repeating over and over now: 2018-06-12 21:04:06,902 DEBG 'rtorrent-script' stdout output: [warn] Wait for rTorrent process to start aborted 2018-06-12 21:04:37,030 DEBG 'rtorrent-script' stdout output: [info] rTorrent not running 2018-06-12 21:04:37,031 DEBG 'rtorrent-script' stdout output: [info] Removing any rTorrent session lock files left over from the previous run... 2018-06-12 21:04:37,030 DEBG 'rtorrent-script' stdout output: [info] rTorrent not running 2018-06-12 21:04:37,031 DEBG 'rtorrent-script' stdout output: [info] Removing any rTorrent session lock files left over from the previous run... 2018-06-12 21:04:37,032 DEBG 'rtorrent-script' stdout output: [info] Attempting to start rTorrent... 2018-06-12 21:04:37,033 DEBG 'rtorrent-script' stdout output: Script started, file is /home/nobody/typescript 2018-06-12 21:04:37,059 DEBG 'rtorrent-script' stdout output: Script done, file is /home/nobody/typescript 2018-06-12 21:04:37,060 DEBG 'rtorrent-script' stdout output: [info] Autodl-irssi not enabled, skipping startup

That's kind of a loaded question, so I'm going to say... it depends. I have Plex Pass and tried to load up my music into Plex and it frustrated me. I have pretty meticulous tagging including embedded artwork and all I really wanted it to do was just use what was already there. It tries to be "helpful" and download all sorts of info for you on the songs and completely overwrites a bunch of the info for you and grabs whatever artwork it decides it should use, etc. That was especially annoying for me as I have a lot of anime music and it replaced my artists, song titles, etc that I had tagged in romanji (basically English letters representing the Japanese words) with actual Japanese text. Needless to say, while I enjoy anime and its music, I can't read a lick of Japanese and it rendered it completely useless to me. There is a way to try to get Plex music to just use the embedded metadata, but even when I turned those settings on, it still seemed to be grabbing the wrong artwork for some things and messing up some titles etc so I'm not sure what it is doing. That led me to subsonic, then to libresonic, and now finally to airsonic (this docker container). I like that it uses my embedded artwork and metadata and so far has not tried to "help" me by grabbing a bunch of extra crap I don't need. I did have to redo my folder structure as it is very stringent/dependent/expected on that being in a specific format, but once I did so it has been working well for me. It is nice now as I don't have to manually copy music to my phone anymore either. I can install DSub on a new device and sync playlists very easily with minimal effort. And the nice thing about DSub is it stores mp3s as mp3s actually on the device (can't say about non-mp3 because that is all I have) so you can see them with other music players as well. The one thing I don't like about airsonic goes back to the folder structure and why I had to redo it. It takes all files in a single folder as an album, so it just grabs the artwork out of the first file as the artwork and applies it to everything in there. So I couldn't have stuff from different albums in the same folder. As I said though after I re-did my folder structure to be more "standard", it works great. So TL;DR would be that if you have spent a lot of time making your metadata and tags perfect and want to use it, then don't use Plex and use something like *sonic (I recommend airsonic, given the issues the others have). On the other hand, if your music is pretty messy and you haven't spend any time organizing or tagging it (and it is in English or a language you understand/can read), then Plex music might be a good way to have it organize it for you.

I saw there was an update to the container and, looking at the notes, it appears you now included node/nodejs. I've taken the manual install out of my post-start install-apps-script and I'll report back if I continue to get any errors still related to that, but I'm guessing I won't. Thanks! Also, it is now saying that I'm only "3 commits behind" rather than over ten thousand, which seems more reasonable. =)

@CHBMB @sparklyballs As I said I just wanted to rattle the cage a bit to make sure this was still being worked on, as posts going back nearly 6 months (including a couple of my own from back then) never really got answered or even responded to. I realize you are busy but I don't think it hurts just to verify that someone is still there, especially when there are bugs/issues. I do get the updates weekly still, so I assumed something was going on, but for all I know that could have just been automated pulls and wasn't sure if there were actively people looking at it or not. As for the "you are NNNNN commits behind" and nodejs issues, luckily they seem to be mostly cosmetic and not breaking anything major, but still they have been around quite a while, across multiple updates, so I just wanted to be sure someone was aware and hopefully eventually fixing them as they do get to be a nuisance. Thanks guys!

Thanks for getting back and letting me know someone is out there listening! =) Let us know what you find.

As far as my previous post, I'm manually installing nodejs every time I restart the docker (along with a couple other things I'm already installing for my post-processing script), so I've at least gotten around that until it is included in the container. FYI, in case anyone is wondering how to do that: /sbin/apk add nodejs --update-cache --repository http://dl-cdn.alpinelinux.org/alpine/edge/community/ --allow-untrusted I have another question though as well... Lately my SR always has "There is a newer version available (you're NNNNN commits behind) — Update Now" at the top. Even after a new container update comes out, it seems we are still behind. Should the container include those updates when it gets updated? Can or should I manually update SR using the "Update Now" link? Will that break the container if I do so? I also assume any time the container gets updated, it will reset that again and I'd have to update SR manually again? It just seems like this container is getting further behind and I'm starting to wonder if I should switch to a new one. I don't think I've seen a dev answer any posts on here in months. Being this is linuxserver.io, I usually assume that it is pretty well supported and frequently updated, but I wonder if that is still the case? I still see updates to the container itself so I assume not, but the lack of posts on here and unresolved issues is making me start to wonder.

Noticing a bunch of these node.js errors since the last update. Did something get missed in latest build? 2018-03-06 00:36:15 FINDPROPERS :: [Torrent9] :: [6e3a1dc] Request failed: Missing Node.js runtime. Node is required. Please read the cfscrape README's Dependencies section: https://github.com/Anorov/cloudflare-scrape#dependencies. 2018-03-05 12:03:40 SEARCHQUEUE-BACKLOG-80379 :: [Torrent9] :: [6e3a1dc] Request failed: Missing Node.js runtime. Node is required. Please read the cfscrape README's Dependencies section: https://github.com/Anorov/cloudflare-scrape#dependencies. edit: Looks like maybe a new dependency recently introduced? Can it be added to the container?

Did a recent container upgrade also update or upgrade python or maybe something else? I use a Plex agent & scanner plug-in for anime (ASS/HAMA) that is written in python and suddenly it stopped working correctly. I have not changed/updated the plug-in for months, so there shouldn't have been any changes to the plug-in code itself. One thing it does is pull down an xml from github and now that part is throwing an error as of yesterday. Creating: /tmp/anime-list-corrections.xml Error downloading ScudLee's file mod from local/GitHub 'http://rawgit.com/Dingmatt/AMSA/master/Plug-in%20Support/Data/com.plexapp.agents.amsa/DataItems/anime-list-corrections.xml', Exception: '<urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)>' Creating: /tmp/ASS-tmp-anime-list-master.xml Error parsing ScudLee's file mod content, Exception: '<urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)>' I've dug through the code/py file some and it is using urlopen(URL).read() to try to grab the xml file. The creator isn't sure the cause, so trying to cover all bases to see where it stems from. Plex forums link in case there is any interest.

Yeah I just got Airsonic going really to use as my phone music sync app via DSub, but it is nice to have music playing on my system while I'm working on stuff too occasionally. I did try clearing the cookies for the site on Chrome, but haven't gone nuclear yet on cache and such. I don't think it is a Chrome extension as I haven't changed those and it was just working a couple days ago. Honestly I'm kind of digging having it running on Edge instead as notifications actually work on there so I see a Windows notification pop up when it changes songs and such. Google has seen fit to block Chrome notifications from working on local websites (technically non-trusted sites, but that includes stuff running on my unraid server). If it gets too frustrating for me I can open an issue on the Airsonic github. Thanks!

I've been setting up and playing with my Airsonic container over the past week or two and suddenly I started running into a problem over the past couple days where, when playing back music in Chrome browser, it stops at the end of every song. I have to select or skip to the next song in the queue and then it will play that song, until the end of that one and it stops playing again. Rinse and repeat. It seems like it is similar to what is seen in this Subsonic bug thread, but all my files are just regular mp3s, no FLAC or anything else really exotic or otherwise. But after reading that, I noticed that for almost every song the time in the player would show as 1 second longer than the length listed in the playlist. I tried going in to the settings and under "Players" select the "web" player and unchecked all the "Active Transcoding" boxes to make sure it wasn't a transcoding issue (I assume unchecking those disables transcoding). I don't see anything in the /config/airsonic.log file, just the file playback info messages. No errors or even warnings when this happens. I found out I can just open up Airsonic in Microsoft Edge browser instead and it seems to work fine there, so the problem looks to be specific to Chrome. I've tried restarting Chrome and also restarting the container. Anyone seen this before or any ideas?

Great, thanks!

OK I added it to all entries and saved it, so it looks like this now: label unRAID OS menu default kernel /bzimage append initrd=/bzroot nomodeset label unRAID OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui nomodeset label unRAID OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode nomodeset label unRAID OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode nomodeset label Memtest86+ kernel /memtest That should be all I need correct?

FYI - This was an upgrade from v6.3.5 direct to v6.4.1. Someone pointed me to this thread (really wish I'd seen it before upgrading!) and the Aspeed IMPI fix got video working again for my ASRock motherboard. It would boot up but at the point the login prompt should appear the screen would just go blank, which was irritating but at least the web GUI and SSH still worked. The fix just has you add the "nomodeset" parameter to the main/default unRAID OS label/boot option's append line. Do I need to or should I add that "nomodeset" parameter to the other labels as well - GUI and Safe Modes? Just want to be sure I won't run into the problem again, especially if I need to go in to safe mode. Another issue I have is that after the upgrade I can't get a VM to boot. My VM Manager starts up fine, so it isn't to do with the common problem of the paths getting lost or messed up mentioned in the OP. But when I try to start my Windows 10 VM after the upgrade I get bluescreen/frowny face with "your pc ran into a problem and needs to restart" in the VM. It proceeds to do so but ends u p just going to a "your pc did not start correctly" screen. Shutting down and rebooting it the same thing happens again and again. I tried a startup repair from that screen, but that didn't work. The only other thing I've tried changing so far is upping the q35-2.7 to the latest q35-2.10. No luck there either. Attaching the [removed xml] for that VM. Frustrating as that VM was chugging along fine just a couple hours ago under v6.3.5. My Windows 7 VM seems to be doing just fine, but it is running seabios+i440fx rather than the Win10 one above which uses ovmf+q35, though I'm not sure that makes a difference or not. Also have a CentOS 7 VM that comes up fine and that uses seabios/q35. None have any physical hardware passed through to them. I've made a quick copy of my disk *.img files for the VMs in case anything corrupts my Windows install hopefully I can revert back if needed. edit: Got it to boot by deleting the VM and recreating it, pointing back to my same .img file again for the C: drive. I remembered I made some tweaks to that VM from this thread a while back to do with SSD optimization and best guess is those settings messed things up with the new version of unRAID/KVM. Leaving this here though in case someone runs into the same issue.

Thanks, the Aspeed IMPI fix did the trick! Another thing I need to add to my tweak list in case I ever have to reinstall unRAID. =/ Wish I had seen that whole thread before doing the upgrade.... Do you know if the "nomodeset" only needs to be added to the default "unRAID OS" label/boot option's append line? Wondering if I should also add it to the GUI and Safe Modes entries as well so if I ever have to boot into Safe Mode, for example, I don't end up with the same problem.

This isn't a major issue since unRAID still boots up and I can access the web GUI as well as remote in via SSH, but still odd. I have a motherboard, ASRock EP2C602, that has built in IPMI for my server. This may or may not be related as it should still act like a real monitor+keyboard+mouse is hooked up, but mentioning anyway just in case. With v6.3.5 I could see it boot up, post, scan for drives, etc. and then unRAID would start up and I'd see the normal linux/unix text fly by as things are loaded. After it was all done I'd see the last remaining text from loading and a text login prompt near the bottom. Pretty standard linux/unix text-only mode prompt as expected. After upgrading to 6.4.1 (I skipped 6.4.0 since I didn't have the downtime until now and so installed the latest instead), I still get the same thing up until the last/final step. After all the linux/unix loading text goes flying by instead of ending with the text login prompt, I just end up with a blank screen. I've tried pushing buttons (space, enter, up, down, etc) to try to wake up the screen as I thought it might go into a screen saver mode of sorts. I even tried Ctrl+Alt+Del because old habits are hard to break I guess. =/ That rebooted my server for me... =( Not sure if it was a clean shutdown as I couldn't see if it was doing the normal shutdown process due to the blank screen, but luckily it at least seem to come back up fine and the array started with no problems. But again blank screen on the console monitor. I tried another (proper) soft reboot as well as a full power down and then back on, but still every time it just goes to a blank screen. Is that expected and changed from the previous version? Honestly I think I've only used the console login once or twice, but it is nice knowing it is there if I absolutely can't connect over the network via web interface, SSH, or any other way, so I wanted to check and see if there was any way to fix it?

Funnily enough, that link recommends using the preclear plugin on unRAID v6 systems...

Sounds like this issue. Are you running v6.4.X now? Still debate about whether it is fixed or not. I can attest it was still not in v6.3.5, so wondering whether you have upgraded yet or not.

Thanks for quick fix/revert. Applied latest update and working again.

Just noticed there was an update to this container tonight and so I was going to run it quick before going to bed (famous last words...) and now after applying the update it is not starting correctly. The container runs but nothing comes up. I can connect to the web UI but it says it can't connect to rtorrent itself. Connecting to the container via docker exec -it and switch to nobody user, there is no tmux session running like normal. I don't believe openvpn is connecting either so might be why rtorrent isn't even trying to start yet. root@yggdrasil:/mnt/user/appdata/rtorrentvpn-binhex/rtorrent/config# docker exec -it rtorrentvpn-binhex /bin/bash [root@97ce8ed60181 /]# su nobody [nobody@97ce8ed60181 /]$ tmux ls no server running on /tmp/tmux-99/default [nobody@97ce8ed60181 /]$ Looking at the docker log, this just continually is cycling in there (changed IP obviously): 2017-12-18 23:26:21,475 DEBG 'start-script' stdout output: Mon Dec 18 23:26:21 2017 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2017-12-18 23:26:21,476 DEBG 'start-script' stdout output: Mon Dec 18 23:26:21 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]1.2.3.4:443 Mon Dec 18 23:26:21 2017 Socket Buffers: R=[212992->212992] S=[212992->212992] Mon Dec 18 23:26:21 2017 UDP link local: (not bound) Mon Dec 18 23:26:21 2017 UDP link remote: [AF_INET]1.2.3.4:443 2017-12-18 23:27:21,337 DEBG 'start-script' stdout output: Mon Dec 18 23:27:21 2017 [UNDEF] Inactivity timeout (--ping-restart), restarting 2017-12-18 23:27:21,338 DEBG 'start-script' stdout output: Mon Dec 18 23:27:21 2017 SIGHUP[soft,ping-restart] received, process restarting 2017-12-18 23:27:21,339 DEBG 'start-script' stdout output: Mon Dec 18 23:27:21 2017 WARNING: file 'credentials.conf' is group or others accessible Mon Dec 18 23:27:21 2017 OpenVPN 2.4.4 x86_64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Sep 26 2017 Mon Dec 18 23:27:21 2017 library versions: OpenSSL 1.1.0f 25 May 2017, LZO 2.10 2017-12-18 23:27:21,340 DEBG 'start-script' stdout output: Mon Dec 18 23:27:21 2017 Restart pause, 5 second(s) I usually update my containers over the weekend. I know I checked on all of mine and ran the updates. Can't be sure if there was a rtorrentvpn update or not, but I would have at least checked. So that makes me think this update would have came out within the past day or two. Was working fine just minutes before applying the update.

Yeah 192.168.1.X is extremely common as the default on consumer routers and you are going to run into routing problems like that especially when trying to VPN from other locations (where others haven't bothered to change the defaults either). Also, since it is so common, it would probably be the first thing someone would try when trying to hack through a NAT. I always make sure to pick some other random uncommon subnet to use when first setting up my local network, and would recommend doing the same to avoid stuff like this and also to make it ever so slightly harder for someone to get into your network.

@puma1824 Thanks for putting that info/procedure together for me, and so quickly. It worked great! Now able to connect from my phone. I'm at home so can't test from my laptop right now (well easily anyway, would have to start up a tethering session or something), but now that the phone is working I'm pretty confident it will. I'll probably give it a try remotely before taking off this weekend, but puts my mind at ease. Was a bit panic-y. =) Thanks again! edit: Btw, re-noticed the first quote you had there. Is this related to running a cache pool with mirroring? I've had trouble with cache mirroring and trying to run torrent containers, wonder if this is another ding on that setup. Might be getting time to convert back to single drive cache instead.