August 26, 201213 yr Author Thanks for the info, interesting though as the plugin downloads multiple files before ever starting the git downloads. I suppose some would be installed from previous boots so wouldn't be an issue anymore. I could add a check to the actual app install but it wouldn't help the other files. Once everything is updated and I'm sure of stability, I want to start adding more checks anyway to allow graceful exits instead of hanging on boot.
August 26, 201213 yr Also, I don't know if it has to do with changes in sickbeard plugin 2.5, but once you start sickbeard, it takes quite a few minutes for the sickbeard webui to become accessible. It used to be fairly instant. I'm seeing the same thing on both of my unraid boxes.
August 26, 201213 yr Author It will take a little bit when bringing the webui up the first time after the upgrade, but should get quicker. Sickbeard is quite slow reading its database into cache. Only changes were how I get sickbeards version. This causes Sickbeard to use git now to check for updates, but this should actually be quicker than downloading from source.
August 26, 201213 yr I think I found the issue with CouchPotato V2 not auto starting when the array starts. Line 794 of the CP plg you missed the code to read from the config just before the next bit of code checks if the service is set to enabled then starts it... Missing: source /boot/config/plugins/couchpotato_v2/couchpotato_v2.cfg The rest is fine... if [ $SERVICE = enable ]; then /etc/rc.d/rc.couchpotato_v2 start fi Seems to have fixed the issue for me.... Thanks!
August 26, 201213 yr Author It should read that as soon as rc.couchpotato_v2 is called, and gets passed to the other parts after that. Adding to that section patches it, but something is amiss elsewhere, thanks for the heads up, ill check it out.
August 26, 201213 yr Oh I see. I just saw the Sickbeard PLG had that "source" line just before it did the same check and saw it was missing in the Couch Potato PLG so I added and tested. This band-aid will do till you can find the issue and release a proper fix Thanks again for your hard work! Also any chance of you managing the transmission plugin?
August 26, 201213 yr Just a minor bug I just noticed in Sickbeard: The status is as following: Status: RUNNING with version ____ Even though I just updated to the newest version via the SickBeard webinterface. The plugin itself is running fine though. This is fixed. Its official, I will only work on ONE plug-in at a time. I missed a line that needed to be changed. Thank you very much Influencer, appreciate your A-level support.
August 26, 201213 yr Sorry to bother you again Influencer, but Headphones seems to be have a semicolon missing: Parse error: syntax error, unexpected ';' in /usr/local/emhttp/plugins/headphones/headphones.php on line 14
August 26, 201213 yr Author Haha, if I wasn't convinced before I am now. The autosave must've kicked in and I pushed incomplete files. The way I do it is I have the repo on my pc, and then I have the plugin directory open. I make the changes on the dev branch then load the plugin to the directory and install to test. Any minor changes, such as missed punctuation, I make to the plugin directly to test. When I'm done I pull them all back to the repo and commit. I was working on multiple things so I still had the editor open on the repo, it must've autosaved after I had pulled back the minor fixes, basically creating them again and I unknowingly committed with the errors. I'll fix this when I get home and put them all through another test to make sure.
August 26, 201213 yr Author Oh I see. I just saw the Sickbeard PLG had that "source" line just before it did the same check and saw it was missing in the Couch Potato PLG so I added and tested. This band-aid will do till you can find the issue and release a proper fix Thanks again for your hard work! Also any chance of you managing the transmission plugin? Either I've got the location of the check confused or noticed the problem on the Sickbeard plugin and put it in and forgot to do the same to the others... I really need a vacation! I'm brain fried apparently, I basically broke the plugins this last go round, maybe I should change my Sig from always working to usually working plugins
August 26, 201213 yr Haha, if I wasn't convinced before I am now. The autosave must've kicked in and I pushed incomplete files. The way I do it is I have the repo on my pc, and then I have the plugin directory open. I make the changes on the dev branch then load the plugin to the directory and install to test. Any minor changes, such as missed punctuation, I make to the plugin directly to test. When I'm done I pull them all back to the repo and commit. I was working on multiple things so I still had the editor open on the repo, it must've autosaved after I had pulled back the minor fixes, basically creating them again and I unknowingly committed with the errors. I'll fix this when I get home and put them all through another test to make sure. No worries, things like that happen all the time. Thank you for taking your time!
August 26, 201213 yr Hadn't hit update so I didn't see that error. You can manually add it to the config.ini file(located in data directory), then restart sickbeard. The option is already in the INI file, so you just have to fill it in, it'll look like this git_path = "" CHANGE TO git_path = /usr/bin/git I'll look at having the plug-in add this automatically in an upcoming update Weird, that doesn't work for me.
August 26, 201213 yr awhile back you said NOT to update sickbeard via its WebGUI, is this still the case?
August 26, 201213 yr Author I said it messed up my install but I wasn't sure if it was a one off issue or something messed up. Last night I updated via the webgui and it worked fine, so I'm assuming it was a one off issue. If you try and it does mess uo the install you can delete the install directory and install from the plugin again, it will work again.
August 26, 201213 yr Author Weird, that doesn't work for me. Make sure git exists at that location, and you will need to restart sb for it to take effect. If this continues to be an issue I can switch back to the old method for Sickbeard.
August 26, 201213 yr I did that, but to no avail. I tried with and without quotation marks, with restart and with deleting the sickbeard folder in ram and re-installing. I think the old method is better.
August 26, 201213 yr Author I'll switch it back, but out of curiosity, would you mind sending me your config.ini, you can delete anything that should remain hidden, api keys and such. I don't know why it wouldn't be working... If you will, also send the output of ls -l /usr/bin/
August 26, 201213 yr Thank you, what about this Couchpotato Autostart issue, I am having the same problem as "DigitalDrifta". Is his fix good to go? Can I somehow assist in debugging Headphones?
August 26, 201213 yr Author Going to push headphones in a couple minutes, and also add the fix to couchpotato and push it as well. Just testing everything as thoroughly as possible so this doesn't happen again, Alright, headphones is fixed, I tested and didn't find anything, doesn't mean a user won't! Added source to couchpotato, and reverted sickbeard to not use git for versioning. Also double checked other apps and didn't see any errors created by using git for versioning so I left them be. Headphones DOES say it doesn't know what version and to update, I did both with using git and without and got the same message, so that is a problem with headphones' update method. Hopefully we are all set now! Anymore feadback with htpc_manager? Seemed to be quite a bit of interest for little feedback on it,
August 26, 201213 yr Great thank you, maybe I will try htpc_manager tomorrow so I can give you feedback.
August 26, 201213 yr Author No problem. Sorry for all the mess! I do believe ill turn the auto save feature off. Working from my laptop so sudden loss of power isn't really an issue, ill just risk losing my changes if I get a bsod. Far less headaches!
August 26, 201213 yr Anymore feadback with htpc_manager? Seemed to be quite a bit of interest for little feedback on it, Ooo, shiny. Must try. I just downloaded it & ran the exe file. It created a userdata directory & a file named htpc.exe.log. Was not sure what to do next (fine, I will read the forum on htp_manager) Ok, next opened my browser to http:localhost:8084. Only option appears to be settings & that all looks self explanatory. Filled it out with my information fairly quickly. Clicked on the link for HTPC Manager to go back to the main page... & it works! I am not using Headphones atm, so I have no recently added music, but everything else appears to be there. I think I will really like this. Is there anything I can test & provide feedback about? Or did you just want an overall opinion (like this post)? I have had it installed for less than 5 minutes, but I am very happy to have it. Thank you for bringing it to my attention =D
August 26, 201213 yr Author A few posts back I linked to a plug-in for it from the dev branch, its moved to the Master branch now. You could tell me if it installs just as(or more) easily with the plug-in, I want to make sure everything is good and stable so I can update the OP and move my focus to potential new plug-ins, and yes, I'm going to look at some of the other plug-ins users have requested me to.
Archived
This topic is now archived and is closed to further replies.