December 26, 201213 yr try root root. somehow thats what mine was. if not go to your unmenu and find the mysql package and there is an edit configuration there. you should be able to type it in there.
December 26, 201213 yr i installed the mysql server via simplefeatures not unmenu so not sure if that matters? Either way i tried some other options and it just kept giving the unable to connect to database and unable ot select datatbase errors. So Ill wait and give it another go in the morning
December 26, 201213 yr If you used the mysql plugin that installs with the newznab plugin then it will say the password is root on the config screen. There is a root user so root/root should work fine. Make sure that mysql is running. Once you get through the install then in the admin put in your assigned ID that you were emailed and pick a few newsgroups. Then, log-in and cd to the /*where you installed it*/newsznab/misc/update_scripts directory and run "php update_binaries.php". It should scan the newsgroups you selected and download 50000 headers from each newsgroup. Now, run "php update_releases.php". It will run through a bunch of things (7 steps I believe) and show a bunch of releases. At this point, you can go to the main newznab user web page and look at the releases. Now, to update automatically, I just cd'd down into the nix_scripts directory and edited newznab_screen.sh. Put in the directory where you installed it and change the php5 to just php. Next, do a chmod +x newznab_screen.sh to make it executeable and run it - "newznab_screen.sh". It should run through the updates and then say it's waiting 600 seconds. If that works, then you can do a <ctrl>c to stop it and do "nohup newznab_screen.sh > /dev/null 2>&1 &" to stick it into the background so it just keeps running. To stop it again, type kill and the process ID that it shows.
December 26, 201213 yr I don't get so many releases, but I changed the backfilling to 50 days, and then run php backfill.php since the most group only have that set to 1, so you don't get so many releases, buy is take some time yo fill it up ;-) //Peter
December 26, 201213 yr If you used the mysql plugin that installs with the newznab plugin then it will say the password is root on the config screen. There is a root user so root/root should work fine. Make sure that mysql is running. I restarted my server and the php warning is gone so got that fixed for sure. mysql is running, initial root password is "root" Web Server status is running Go to the second step in newznab and root/root doesnt work
December 26, 201213 yr Like I said I'm a noob and I experiment and break stuff but with a google search, you can try this.... mysqladmin -u root password NEWPASSWORD and try to set a new password. maybe there isnt one. Have you tried root and nothing for the password? I dont know if you need to log into mysql to run that command or not. Pro win 7 user here.
December 26, 201213 yr Like I said I'm a noob and I experiment and break stuff but with a google search, you can try this.... mysqladmin -u root password NEWPASSWORD and try to set a new password. maybe there isnt one. Have you tried root and nothing for the password? I dont know if you need to log into mysql to run that command or not. Pro win 7 user here. haha root for username and password blank worked. The one combo i didnt try d'oh. Now for the real fun part of getting it all setup Thanks !
December 26, 201213 yr LOL, too funny. See, thats the type of crap I run into. OMFG. Well anyways, if you need any help hollar at us. I'm going to bed.
December 26, 201213 yr Mmm.. I think I have reset this thing (the program, not the plugin) about 4 times now... It all starts out working until after a day or so the webinterface shows no releases anymore and the update script does not seem to find any binaries anymore.. I also installed spotweb, for those that have not yet seen it, check it out. Its free, a lot faster and takes a motherload less bandwidth.. (Note: pretty sure that the fact newznab does not work for me is my own fault though !)
December 26, 201213 yr Update to the cron script: I've added the ability to use update_binaries_threaded.php. Notes/Warnings: update_binaries_threaded does not support command line "thread limit", so you have to set it in the file. It defaults to 10 which is going to kill most systems. Remember, for each thread in update_binaries_threaded that is running, mysql will fire up another thread for the DB updates. Secondly, you can't just edit update_binaries_threaded to change the thread limit (even if it LOOKS like you can). You have to update it in: <NewznabDir>/www/lib/powerspawn.php Also, run the update by hand a few times and watch the CPU usage with htop..just to make sure. That said, I've attached the update. Just add -t when you call it to enable threaded update_binaries. cron_newznab_process.zip
December 26, 201213 yr A potential pitfall... Newznab has you make rewrite changes to your web server... sometimes it does not allow other types of websites to view correctly. I did at some point try installing newznab directly on unRAID... phpmyadmin displayed correctly with the rewrites most of the time, but I had trouble getting phpVirtualBox to display with the Newznab rewrites... so I opted for a VM. I've read up some more since then on apache & lighthttp sites & think I know what I should have done to get phpVirtualBox to work alongside Newznab... however, since my VM is working, I have not tried those changes. I can run phpMyAdmin with the following rewrite rules: url.rewrite-once = ( "/(.*)\.(.*)" => "$0", "/(phpmyadmin|css|img|js)/" => "$0", "^/([^.]+)$" => "/index.php/$1" ) and Newznab with the included rewrite rules: url.rewrite-once = ( "^/.*\.(css|jpg|jpeg|gif|png|js|ico)" => "$0", "^/(admin|install).*$" => "$0", "^/([^/\.]+)/?(?:\?(.*))$" => "index.php?page=$1&$2", "^/([^/\.]+)/?$" => "index.php?page=$1", "^/([^/\.]+)/([^/]+)/?(?:\?(.*))$" => "index.php?page=$1&id=$2&$3", "^/([^/\.]+)/([^/]+)/?$" => "index.php?page=$1&id=$2", "^/([^/\.]+)/([^/]+)/([^/]+)/?$" => "index.php?page=$1&id=$2&subpage=$3" "/(.*)\.(.*)" => "$0", ) However they won't work when I combine them, for example: url.rewrite-once = ( "^/.*\.(css|jpg|jpeg|gif|png|js|ico)" => "$0", "^/(admin|install).*$" => "$0", "^/([^/\.]+)/?(?:\?(.*))$" => "index.php?page=$1&$2", "^/([^/\.]+)/?$" => "index.php?page=$1", "^/([^/\.]+)/([^/]+)/?(?:\?(.*))$" => "index.php?page=$1&id=$2&$3", "^/([^/\.]+)/([^/]+)/?$" => "index.php?page=$1&id=$2", "^/([^/\.]+)/([^/]+)/([^/]+)/?$" => "index.php?page=$1&id=$2&subpage=$3" ) url.rewrite-once = ( "/(.*)\.(.*)" => "$0", "/(phpmyadmin|css|img|js)/" => "$0", "^/([^.]+)$" => "/index.php/$1" ) I've tried modifying them with rewrite-once +=, rewrite-repeat, But to no avail. Obviously I'm missing something. Anyone have any suggestions? BTW, when combined, Newznab works, but not phpMyAdmin.
December 26, 201213 yr Woodpusherghd, Check out this post in the spotweb thread: http://lime-technology.com/forum/index.php?topic=24804.msg215883#msg215883. Jangjong shows using multiple ports to run sites with different rewrite rules on the same machine. Using this I have phpmyadmin & phpvirtualbox on one port; spotweb on another port... & newznab on it's own port (I am working on moving newznab from my vm to just be on unraid since this seems to be working... slow process since I am trying to keep the data from the VM).
December 27, 201213 yr Mmm.. I think I have reset this thing (the program, not the plugin) about 4 times now... It all starts out working until after a day or so the webinterface shows no releases anymore and the update script does not seem to find any binaries anymore.. I also installed spotweb, for those that have not yet seen it, check it out. Its free, a lot faster and takes a motherload less bandwidth.. (Note: pretty sure that the fact newznab does not work for me is my own fault though !) Had this exact same problem, the first few times I ran the scripts to download releases everything was fine, then out of the blue i'd go into the web interface and all of my releases would be gone. If I ran a mysqlcheck -u root -p newznab --auto-repair it would show corruptions in my database and report problems that it couldnt change the permissions of some of the tables, unfortunately the auto-repair could never fix the problems and rerunning scripts would give various errors. At this point there was nothing I could do to recover the situation so I would re-run the install which nuked the mysql database and start again only for the same thing to happen. What fixed it for me was moving the mysql data directory off the array and onto my cache drive. I originally wanted to protect my databases by keeping them on the array but I didnt configure the split function so presumably the files got spread across the array instead of being kept together on one disk. When i saw the permissions errors I had a hunch this may have been the cause of the problem. Since moving the database onto the cache drive my releases have been fine for the past 2 days and that includes running a backfill for all of December. Hope that helps.
December 27, 201213 yr when i hit "update newznab" do i have to restart my server in order for the updates to take?
December 27, 201213 yr Woodpusherghd, Check out this post in the spotweb thread: http://lime-technology.com/forum/index.php?topic=24804.msg215883#msg215883. Jangjong shows using multiple ports to run sites with different rewrite rules on the same machine. Using this I have phpmyadmin & phpvirtualbox on one port; spotweb on another port... & newznab on it's own port (I am working on moving newznab from my vm to just be on unraid since this seems to be working... slow process since I am trying to keep the data from the VM). Thanks, got both working using the "Server Socket" method.
December 27, 201213 yr when I hit update newznab for some reason it seam as its not updating the update_scripts. I can see that the date last modified of the folder has changed to the current date but the modified date of the files has not changed and i know one of the file has been updated. any ideas? I have the plus version and i have my svn log in info in the correct fields.
December 27, 201213 yr WARNING: The mysql5 plugin can REALLY mess with disk-space when using the default options. WARNING #2: Some users are reporting these fixes make their DBs unusable. Procede at your own risk! By default the plugin enables bin-logging, this records every SQL statement to a mysql-bin file in the mysql root directory. With all the importing I'd been doing, I had over 300G of log files. To solve this I copied /etc/mysql/my-medium.cfg to /boot/config/plugins/mysql and renamed it my.cfg Then edited this section: # Replication Master Server (default) # binary logging is required for replication log-bin=mysql-bin to comment out the line: # Replication Master Server (default) # binary logging is required for replication #log-bin=mysql-bin Reinstalled the plg and removed the mysql-bin files Thought others might like to know
December 28, 201213 yr WARNING: The mysql5 plugin can REALLY mess with disk-space when using the default options. Thank you for this!!!! I had completely removed mySQL, Lighttpd and NewzNab yesterday because they went through the space on my 1TB cache drive in no time while importing, backfilling, and loading from the mega NZB torrent pack. Maybe I'll reinstall these now, Thanks Tybio!
December 28, 201213 yr WARNING: The mysql5 plugin can REALLY mess with disk-space when using the default options. By default the plugin enables bin-logging, this records every SQL statement to a mysql-bin file in the mysql root directory. With all the importing I'd been doing, I had over 300G of log files. To solve this I copied /etc/mysql/my-medium.cfg to /boot/config/plugins/mysql and renamed it my.cfg Then edited this section: # Replication Master Server (default) # binary logging is required for replication log-bin=mysql-bin to comment out the line: # Replication Master Server (default) # binary logging is required for replication #log-bin=mysql-bin Reinstalled the plg and removed the mysql-bin files Thought others might like to know Can you elaborate more on what you did to resolve this? I seen the files growing and did exactly as you said but now my newznab isn't picking up any releases Edit: Seen this in the script. Group 1 of 17 Processing alt.binaries.tv Group alt.binaries.tv has 3,843 new parts. First: 209770075 Last: 536466388 Local last: 536462545 Getting 3,843 parts (536462546 to 536466388) - 0 in queue Received 3843 articles of 3843 requested, 0 blacklisted, 0 not binaries WARNING: 3843 Parts failed to insert 76 new, 0 updated, 3,843 parts. 0.59 headers, 1.55 update, 2.14 range. Group processed in 2.24 seconds Also in the MySQL error log file is. 121228 18:12:33 [ERROR] /usr/sbin/mysqld: Table './newznab/parts' is marked as crashed and last (automatic?) repair failed 121228 18:12:33 [ERROR] /usr/sbin/mysqld: Table './newznab/parts' is marked as crashed and last (automatic?) repair failed 121228 18:12:33 [ERROR] /usr/sbin/mysqld: Table './newznab/binaries' is marked as crashed and last (automatic?) repair failed 121228 18:12:33 [ERROR] /usr/sbin/mysqld: Table './newznab/binaries' is marked as crashed and last (automatic?) repair failed 121228 18:12:33 [ERROR] /usr/sbin/mysqld: Table './newznab/parts' is marked as crashed and last (automatic?) repair failed 121228 18:12:33 [ERROR] /usr/sbin/mysqld: Table './newznab/parts' is marked as crashed and last (automatic?) repair failed 121228 18:12:33 [ERROR] /usr/sbin/mysqld: Table './newznab/parts' is marked as crashed and last (automatic?) repair failed 121228 18:12:33 [ERROR] /usr/sbin/mysqld: Table './newznab/partrepair' is marked as crashed and last (automatic?) repair failed Not sure what I did but it seems they're not getting added to the database now that I made the change?
December 28, 201213 yr Question for Tybio. If I start the cron_newznab_process script without the “q” flag, should it echo the various echo messages into the log file. I am currently starting mine with the –qp flags set. I am trying to make sure the testing/update_parsing.php script is being called. It appears it should be running every 12 hours. When I search the log I only get the final message stating it has finished with the times and no other "INFO:" messages. I tried running it without any flags and still did not get any additional messages in the cron_newznab_process.log. My next attempt was going to be to uncomment the “set –xv” line. Can you tell me the correct method to enable the status messages? I have also concluded that I need to delete this log every few days as mine had over a 100K entries and really slows the simple features log viewer down. A potential solution would be for the script to copy the current log to an .old file after first deleting the previous old file if it exists. This way you would have a a day or two worth of data if needed, but would keep the file from growing too large. Another question on the plug-in itself. Is there any way to have the pluggin download the latest commit of nn+ checked in to the SVN and install it if it is newer than the currently installed version..The reason I ask is that I saw some comment in another location to the affect that the “update_releases.php” script is being improved upon. I have not checked yet to see if there is an updated version. Now that it is in fact installed, I could probably just download and copy it across from my PC if desired, but would believe it would be safer if the plug-in did it. Another side question. Do you know where the php.ini file lives. When I initially installed the nn+ the install check complained that not enough memory was allocate. I believe the number was 186M and it wanted 256M. Again, thanks for all of the work you are doing on this.
December 28, 201213 yr Question for Tybio. If I start the cron_newznab_process script without the “q” flag, should it echo the various echo messages into the log file. I am currently starting mine with the –qp flags set. No, quiet blockes the INFO messages as they will mess with cron...if you run from cron and get output to STDOUT cron will try to email those to the user (root in this case). So -q is used to suppress all messages to SDTOUT. I am trying to make sure the testing/update_parsing.php script is being called. It appears it should be running every 12 hours. When I search the log I only get the final message stating it has finished with the times and no other "INFO:" messages. I tried running it without any flags and still did not get any additional messages in the cron_newznab_process.log. My next attempt was going to be to uncomment the “set –xv” line. Can you tell me the correct method to enable the status messages? Good thought, let me change the logic so it doesn't block the STDOUT messages, but if you flag quiet it redirects them to the log. Give me an hour or so and I'll have a new version up. The idea was that you could run it by hand without -q and see what is going on for testing. No reason those messages shouldn't go to the log. I have also concluded that I need to delete this log every few days as mine had over a 100K entries and really slows the simple features log viewer down. A potential solution would be for the script to copy the current log to an .old file after first deleting the previous old file if it exists. This way you would have a a day or two worth of data if needed, but would keep the file from growing too large. Another good point, I was going to install logrotate at one point....but I'll toss in a temp solution Another question on the plug-in itself. Is there any way to have the pluggin download the latest commit of nn+ checked in to the SVN and install it if it is newer than the currently installed version..The reason I ask is that I saw some comment in another location to the affect that the “update_releases.php” script is being improved upon. I have not checked yet to see if there is an updated version. Now that it is in fact installed, I could probably just download and copy it across from my PC if desired, but would believe it would be safer if the plug-in did it. It does it on request right now. but I might add a section to the cron script to call the svn update part of Influencers plugin once a day or something. Another side question. Do you know where the php.ini file lives. When I initially installed the nn+ the install check complained that not enough memory was allocate. I believe the number was 186M and it wanted 256M. It lives at /boot/config/plugins/simpleFeatures/php.ini When simpleFeatures gets installed, that php.ini is copied over.
December 29, 201213 yr I can't seem to get this thing working. I keep getting the 404 error on the install screen. When I enter tower:81 it redirects to the install address but with a 404. nn: /mnt/cache/appdata/webroot/ SF: /mnt/cache/appdata/webroot/www I used the replacement lighttpd.cfg All the files seemed to have install correctly in the web root and www folder. Ok so I re downloaded the file from drop box directly the the correct path and it worked.
Archived
This topic is now archived and is closed to further replies.