Installing Newznab on QNAP

[umpa]

Thanks forkless that looks like just what I need, I'll be sure to have a bash at it.

[umpa]

Just to say YES!! its backing up my db just grand. I also managed to get it to run a cronjob even though the net said the job would be deleted on reboot. I figured it would be like the auto run fiasco, but no it survives the reboot.

This got me thinking, could cron run a script to 'test' if the newznab_screen is running and if not run it ? let it check once per hour ? could this be done ?

ump..

[umpa]

would this work ?

http://eiathenerd.com/2007/04/18/checki ... -it-alive/

[forkless]

I haven't looked at it. While checking the process with cron or some watchdog will work there is a reason you shouldn't do it. The loop usually crashes for a good reason, just restarting the script will not take away the cause of the crash in most instances.

As much as you (and me, trust me...) would like for this to be an automated process this app needs quite a fair bit of maintenance/administration.

[umpa]

Hi,
Like always I know your right. I guess I'm still looking at ways to get it to autostart. I saw on the wiki that cron would execute a job only once at boot up using the @reboot flag http://en.wikipedia.org/wiki/Cron I almost got exited until I tested it and found it did not work lol.

[umpa]

Hey guys,

Someone who is helping run my indexing site has asked me 'Are you processing all your releases upon download or just the first 100' and I don't know the answer, I am running forkless' modified newznab_screen script.

cheers

Ump..

[forkless]

The script by default only processes the last 100 releases. It's not really "my" script. It's just a slightly modified version of the already provided screen script (I only added the update_parsing, update_cleanup and deletespecial.php scripts to the screen loop. They will clean up/fix any obfuscated release names and/or delete them.


Ps. Deep RAR inspection is required for update_parsing to work properly.

Ps2. There is the $limited variable you can set to false in update_parsing.php and update_cleanup, however use with severe caution as it may backlog you quite a bit if you have a large database already.

[umpa]

After a reboot my server wont start giving this error

[~] # /etc/init.d/mysqld.sh restart
/mnt/ext/opt/mysql
/mnt/ext/opt/mysql
Try to shutting down MySQL
ERROR! MySQL manager or server PID file could not be found!
/mnt/ext/opt/mysql
Starting MySQL................................... ERROR!
[~] #

this is the second time it has done this any idea how to fix it ?

Also if I try to import a backup of the database it tells me its to large to import.

edit :- after looking at the php admin screen it seems the largest db I can import is 16mb which is why I cant import it ?

[forkless]

That's the limit of the web import. If you want to import databases larger than 16MB you need to use;

Code: Select all

/mnt/ext/opt/mysql/bin/mysql -u user -ppassword databasename < backup.sql

As far as the mysqld error goes, can you copy/paste the first 5 lines of your /etc/init.d/mysql.sh file please.

[umpa]

#!/bin/sh
export TMPDIR=/share/MD0_DATA/tmp
# Copyright Abandoned 1996 TCX DataKonsult AB & Monty Program KB & Detron HB
# This file is public domain and comes with NO WARRANTY of any kind

[umpa]

That's the limit of the web import. If you want to import databases larger than 16MB you need to use;

Code: Select all

/mnt/ext/opt/mysql/bin/mysql -u user -ppassword databasename < backup.sql

As far as the mysqld error goes, can you copy/paste the first 5 lines of your /etc/init.d/mysql.sh file please.

so I replace user and password with my db info, and backup.sql with my db name and location

/mnt/ext/opt/mysql/bin/mysql -u xxx -pxxx newznab < /share/MD0_DATA/Backup/mysql/newznab.sql

[umpa]

Ok - all done, backup worked and its all good - phew !!!

I don't understand why I keep having this, The newznab script stops, I reboot and bang I have this problem. I have rebooted the server on numerous times before, but it fails when the server has been running for a few days and there are loads of releases.

Anyway - thanks again to forkless who once again saves the day

[forkless]

I think you may have the old sed modification for mysql.sh in your autostart.sh (I fixed that two weeks ago or so, maybe you didnt catch that update).


PS. Have you blacklisted nzbcave and hdnectar?

[umpa]

hdnectar was banned but nzbcave was not - it is now

this is the autorun from /share/MD0_DATA/.qpkg

Code: Select all

#!/bin/sh

# Script to set up screen and run newznab_screen.sh

touch /var/run/utmp
chmod 777 /var/run/utmp
export TERMINFO=/opt/share/terminfo
export TERM=xterm

# Fix tmp path for MySQL

sed '2iexport TMPDIR=\/share\/MD0_DATA\/tmp' < /etc/init.d/mysqld.sh > tempfile
chmod 755 tempfile
mv tempfile /etc/init.d/mysqld.sh
echo "Restarting MySQL..."
/etc/init.d/mysqld.sh restart > /dev/null

# start screen
/share/MD0_DATA/.qpkg/Optware/bin/screen /bin/sh /share/MD0_DATA/Web/misc/update_scripts/newznab_screen.sh

from what we found out I don't think this autorun is executed is it ?

[forkless]

Copy everything inside your autorun.sh on the bootblock except for the #!/bin/sh line and remove the autorun.sh line that points to /share/MD0_DATA/.qpkg/autorun