Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Newznab Plug-in

Featured Replies

I have PHPMyAdmin setup on unRAID & have it connecting to my Ubuntu Newznab VM. It is nice to have the web interface for MySQL.

 

I use the following query to check how big my Newznab db is getting through the web interface of PHPMyAdmin without having to ssh into Ubuntu, log into MySQL & run it there.

 

SELECT table_schema "DB Name", SUM( data_length + index_length ) /1024 /1024 "DB Size in MB"
FROM information_schema.TABLES
GROUP BY table_schema
LIMIT 0 , 30

 

Results will look similar to the following:

DB Name  DB Size in MB

information_schema  0.00878906

mysql  0.64589024

newznab  702.05424500

performance_schema  0.00000000

 

  • Replies 523
  • Views 105.9k
  • Created
  • Last Reply

I have PHPMyAdmin setup on unRAID & have it connecting to my Ubuntu Newznab VM. It is nice to have the web interface for MySQL.

 

Was the installation straight forward? Any tips or pitfalls to be aware of? I'm going to install it on my Unraid box where I run Newznab.

I have PHPMyAdmin setup on unRAID & have it connecting to my Ubuntu Newznab VM. It is nice to have the web interface for MySQL.

 

Was the installation straight forward? Any tips or pitfalls to be aware of? I'm going to install it on my Unraid box where I run Newznab.

 

Installation is easy, especially if you already have a web server (lighttpd, apache, nginx, etc...) configured & mysql installed. Unzip/untar the files into a directory in your web root path; I named the directory "myadmin" (looks something like http://tower:8080/myadmin).

 

You have to edit config.inc.php with your mysql settings. My file looks similar to this:

/* Servers configuration */
$i = 0;

/* Server: Newznab  */

$i++;
$cfg['Servers'][$i]['verbose'] = '';
$cfg['Servers'][$i]['host'] = 'localhost';
$cfg['Servers'][$i]['port'] = 3306;
$cfg['Servers'][$i]['socket'] = '/tmp/mysqld.sock';
$cfg['Servers'][$i]['connect_type'] = 'tcp';
$cfg['Servers'][$i]['extension'] = 'mysql';
$cfg['Servers'][$i]['auth_type'] = 'http';
$cfg['Servers'][$i]['user'] = 'pmauser';
$cfg['Servers'][$i]['password'] = 'pmapass';


/* End of servers configuration */

$cfg['blowfish_secret'] = 'xxxxxxxxxxxxxx.xxxxxxxx';
$cfg['DefaultLang'] = 'en';
$cfg['ServerDefault'] = 1;
$cfg['UploadDir'] = '';
$cfg['SaveDir'] = '';
?>

 

That was it for setting phpmyadmin to connect to mysql on the same system.

 

If you have phpmyadmin on one system & are connecting to a db on another system, you have to prep the mysql permissions to allow access from a remote system. I used this cyberciti guide to configure my Ubuntu VM. Then made changes in the "config.inc.php" file to have "localhost" be the IP address of the VM.

 

You can find out where your "mysqld.sock" file is by logging into mysql & typing "status" without quotes.


 

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.

Thanks for this plugin. Made setup VERY easy. Very much appreciated. In my Admin section of Newznab is get the following warnings.

 

1	MySql my.cnf setting group_concat_max_len is too low, should be >= 8192.	
2	MySql my.cnf setting max_allowed_packet is too low, should be >= 12582912.

 

I went into my.cnf in the /etc/ folder and made the adjustment to max_allowed_packet. I could not find the group_concat_max_len setting. I restarted the server after a save and I still have these errors. Am I editing the correct file?

 

Thanks again for doing this.

I started calling it with this cron line:

 

*/5 * * * * /mnt/cache/AppData/Newznab/misc/update_scripts/nix_scripts/cron_newznab_process.sh -qi

 

It checks for a lock file, so this will run the script very frequently...but while I'm importing I needed that.  If you aren't importing you can likely change the 5 to 10 and remove the i flag.

 

I am a total Linux noob.  Until I went to unraid, i did not utilize Linux so am not very familiar with it.  Can you point me in the direction on how to add this to cron to get it to execute script.  Would you put it in your go script?

 

I currently have the script supplied with nn+ running in a screen session.  If I were to reboot the server I would have remember to restart the script.

 

 

Edit for historical purposes

 

After doing some research, i have the following code that can be added to the go script to update crontab with the required information.  You will need to update the path as appropriate for your system.  Also don't forget t update the paths in the cron_newznab_process.sh script also.

 

crontab -l > /tmp/file; echo '#Run Newznab every 10 minutes' >> /tmp/file; echo '*/10 * * * * /mnt/cache/server/misc/update_scripts/nix_scripts/cron_newznab_process.sh -qp' >>/tmp/file; crontab /tmp/file; rm /tmp/file

 

If you have Simple features installed, you can open the log viewer and select the "cron_newznab_process.log" log on the left side to see the output of the script when it is running.

I just added it to /boot/config/plugins/mysql/my.cfg on stopping and starting the instance it will go into the etc/my.cnf

 

You need to make sure you add the following heading [mysqld]

"

[mysqld]

max_allowed_packet=128M

group_concat_max_len=10000"

 

My values are probably wrong but its higher then what they recommend.

 

Will

 

 

Thanks for this plugin. Made setup VERY easy. Very much appreciated. In my Admin section of Newznab is get the following warnings.

 

1	MySql my.cnf setting group_concat_max_len is too low, should be >= 8192.	
2	MySql my.cnf setting max_allowed_packet is too low, should be >= 12582912.

 

I went into my.cnf in the /etc/ folder and made the adjustment to max_allowed_packet. I could not find the group_concat_max_len setting. I restarted the server after a save and I still have these errors. Am I editing the correct file?

 

Thanks again for doing this.

Hi all,

 

I signed up for NN+, but how tho DL the new software an install this from unraid? don't know what to do with the SVN link ;-)

 

can I update the plugin ?

 

 

//Peter

 

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 Installed the MyphpAdmin package to my web root and cannot access the setup file.  I suspect it's due to my Newznab rewrite rules in lighttpd.cfg.  Anyone have the proper lighttpd.cfg for MyphpAdmin and Newznab on the same Unraid box?

I would like to have one  lighttpd.cfg that works both for Newznab & spotweb ;-)

 

Running OK now with NN+ :-)

 

//Peter

I would like to have one  lighttpd.cfg that works both for Newznab & spotweb ;-)

 

Running OK now with NN+ :-)

 

//Peter

 

Look in the spotweb thread.

Thanks! That worked.

 

I just added it to /boot/config/plugins/mysql/my.cfg on stopping and starting the instance it will go into the etc/my.cnf

 

You need to make sure you add the following heading [mysqld]

"

[mysqld]

max_allowed_packet=128M

group_concat_max_len=10000"

 

My values are probably wrong but its higher then what they recommend.

 

Will

OK, I am up am running and it appears to be working really well. The problem was with the .cfg file and once I replaced it, restarted the server and then restarted the web server it was good to go.

 

I have already managed to snatch some nzb with SickBeard with the free version by running in the regex's into the database so the process works and I will now get the donate version.

 

The issues I have remaining are:

a. Auto-starting the web service (lighttpd)

b. Auto-running the update scripts - what is the best way to do this? The script newznab.sh appeared to run fine for me for about 24 hours but then no groups appeared to be updated - it didn't appear as if it was running although it wouldn't let me stop it either. I tried the screen script but this didn't seem to find the right folders either.

 

Any ideas - I have scouted the forums and can't seem to find anyone who has got this working properly - I understand cron jobs are not the best way forward but is this right? When I get the donate version, are the scripts different.

 

Thanks in advance

I just added it to /boot/config/plugins/mysql/my.cfg on stopping and starting the instance it will go into the etc/my.cnf

 

You need to make sure you add the following heading [mysqld]

"

[mysqld]

max_allowed_packet=128M

group_concat_max_len=10000"

 

My values are probably wrong but its higher then what they recommend.

 

Will

 

 

Thanks for this plugin. Made setup VERY easy. Very much appreciated. In my Admin section of Newznab is get the following warnings.

 

1	MySql my.cnf setting group_concat_max_len is too low, should be >= 8192.	
2	MySql my.cnf setting max_allowed_packet is too low, should be >= 12582912.

 

I went into my.cnf in the /etc/ folder and made the adjustment to max_allowed_packet. I could not find the group_concat_max_len setting. I restarted the server after a save and I still have these errors. Am I editing the correct file?

 

Thanks again for doing this.

 

I add did this to /boot/config/plugins/mysql/my.cfg

 

 

[mysqld]
max_allowed_packet=512M
group_concat_max_len=10000

 

 

But I got the same warning anyway, I only restart mysql, what more do I need do do ;-)

 

using this plg file for mysql mysql5_20120805.plg

 

//Peter

What does your mysql error log say in /plugininstalldir/mysql/"servername.err"

 

 

What does your mysql error log say in /plugininstalldir/mysql/"servername.err"

This

 

121224 09:12:11 mysqld_safe A mysqld process already exists
121224 09:24:35 mysqld_safe Starting mysqld daemon with databases from /mnt/cache/web/mysql/
121224  9:24:35 InnoDB: The InnoDB memory heap is disabled
121224  9:24:35 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121224  9:24:35 InnoDB: Compressed tables use zlib 1.2.5
121224  9:24:35 InnoDB: Using Linux native AIO
121224  9:24:35 InnoDB: Initializing buffer pool, size = 128.0M
121224  9:24:35 InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file /mnt/cache/web/mysql/ibdata1 did not exist:
InnoDB: a new database to be created!
121224  9:24:35  InnoDB: Setting file /mnt/cache/web/mysql/ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
121224  9:24:36  InnoDB: Log file /mnt/cache/web/mysql/ib_logfile0 did not exist: new to be created
InnoDB: Setting log file /mnt/cache/web/mysql/ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
121224  9:24:36  InnoDB: Log file /mnt/cache/web/mysql/ib_logfile1 did not exist: new to be created
InnoDB: Setting log file /mnt/cache/web/mysql/ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: 127 rollback segment(s) active.
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
121224  9:24:37  InnoDB: Waiting for the background threads to start
121224  9:24:38 InnoDB: 1.1.8 started; log sequence number 0
121224  9:24:38 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
121224  9:24:38 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
121224  9:24:38 [Note] Server socket created on IP: '0.0.0.0'.
121224  9:24:38 [Note] Event Scheduler: Loaded 0 events
121224  9:24:38 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.28-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
121224  9:28:59 [Note] /usr/sbin/mysqld: Normal shutdown

121224  9:28:59 [Note] Event Scheduler: Purging the queue. 0 events
121224  9:28:59  InnoDB: Starting shutdown...
121224  9:29:00  InnoDB: Shutdown completed; log sequence number 1595675
121224  9:29:00 [Note] /usr/sbin/mysqld: Shutdown complete

121224 09:29:00 mysqld_safe mysqld from pid file /var/run/mysql/mysql.pid ended
121224 09:29:01 mysqld_safe Starting mysqld daemon with databases from /mnt/cache/web/mysql/
121224  9:29:01 InnoDB: The InnoDB memory heap is disabled
121224  9:29:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121224  9:29:01 InnoDB: Compressed tables use zlib 1.2.5
121224  9:29:01 InnoDB: Using Linux native AIO
121224  9:29:01 InnoDB: Initializing buffer pool, size = 128.0M
121224  9:29:01 InnoDB: Completed initialization of buffer pool
121224  9:29:01 InnoDB: highest supported file format is Barracuda.
121224  9:29:02  InnoDB: Waiting for the background threads to start
121224  9:29:03 InnoDB: 1.1.8 started; log sequence number 1595675
121224  9:29:03 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
121224  9:29:03 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
121224  9:29:03 [Note] Server socket created on IP: '0.0.0.0'.
121224  9:29:03 [Note] Event Scheduler: Loaded 0 events
121224  9:29:03 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.28-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
121224  9:29:44 [Note] /usr/sbin/mysqld: Normal shutdown

121224  9:29:44 [Note] Event Scheduler: Purging the queue. 0 events
121224  9:29:44  InnoDB: Starting shutdown...
121224  9:29:45  InnoDB: Shutdown completed; log sequence number 1595675
121224  9:29:45 [Note] /usr/sbin/mysqld: Shutdown complete

121224 09:29:45 mysqld_safe mysqld from pid file /var/run/mysql/mysql.pid ended
121224 09:29:46 mysqld_safe Starting mysqld daemon with databases from /mnt/cache/web/mysql/
121224  9:29:47 InnoDB: The InnoDB memory heap is disabled
121224  9:29:47 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121224  9:29:47 InnoDB: Compressed tables use zlib 1.2.5
121224  9:29:47 InnoDB: Using Linux native AIO
121224  9:29:47 InnoDB: Initializing buffer pool, size = 128.0M
121224  9:29:47 InnoDB: Completed initialization of buffer pool
121224  9:29:47 InnoDB: highest supported file format is Barracuda.
121224  9:29:47  InnoDB: Waiting for the background threads to start
121224  9:29:48 InnoDB: 1.1.8 started; log sequence number 1595675
121224  9:29:48 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
121224  9:29:48 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
121224  9:29:48 [Note] Server socket created on IP: '0.0.0.0'.
121224  9:29:48 [Note] Event Scheduler: Loaded 0 events
121224  9:29:48 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.28-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
121224  9:31:18 [Note] /usr/sbin/mysqld: Normal shutdown

121224  9:31:18 [Note] Event Scheduler: Purging the queue. 0 events
121224  9:31:18  InnoDB: Starting shutdown...
121224  9:31:19  InnoDB: Shutdown completed; log sequence number 1595675
121224  9:31:19 [Note] /usr/sbin/mysqld: Shutdown complete

121224 09:31:19 mysqld_safe mysqld from pid file /var/run/mysql/mysql.pid ended
121224 09:31:20 mysqld_safe Starting mysqld daemon with databases from /mnt/cache/web/mysql/
121224  9:31:21 InnoDB: The InnoDB memory heap is disabled
121224  9:31:21 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121224  9:31:21 InnoDB: Compressed tables use zlib 1.2.5
121224  9:31:21 InnoDB: Using Linux native AIO
121224  9:31:21 InnoDB: Initializing buffer pool, size = 128.0M
121224  9:31:21 InnoDB: Completed initialization of buffer pool
121224  9:31:21 InnoDB: highest supported file format is Barracuda.
121224  9:31:21  InnoDB: Waiting for the background threads to start
121224  9:31:22 InnoDB: 1.1.8 started; log sequence number 1595675
121224  9:31:22 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
121224  9:31:22 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
121224  9:31:22 [Note] Server socket created on IP: '0.0.0.0'.
121224  9:31:22 [Note] Event Scheduler: Loaded 0 events
121224  9:31:22 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.28-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
121224  9:34:39 [Note] /usr/sbin/mysqld: Normal shutdown

121224  9:34:39 [Note] Event Scheduler: Purging the queue. 0 events
121224  9:34:39  InnoDB: Starting shutdown...
121224  9:34:40  InnoDB: Shutdown completed; log sequence number 1595675
121224  9:34:40 [Note] /usr/sbin/mysqld: Shutdown complete

121224 09:34:40 mysqld_safe mysqld from pid file /var/run/mysql/mysql.pid ended
121224 09:34:42 mysqld_safe Starting mysqld daemon with databases from /mnt/cache/web/mysql/
121224  9:34:42 InnoDB: The InnoDB memory heap is disabled
121224  9:34:42 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121224  9:34:42 InnoDB: Compressed tables use zlib 1.2.5
121224  9:34:42 InnoDB: Using Linux native AIO
121224  9:34:42 InnoDB: Initializing buffer pool, size = 128.0M
121224  9:34:42 InnoDB: Completed initialization of buffer pool
121224  9:34:42 InnoDB: highest supported file format is Barracuda.
121224  9:34:42  InnoDB: Waiting for the background threads to start
121224  9:34:43 InnoDB: 1.1.8 started; log sequence number 1595675
121224  9:34:43 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
121224  9:34:43 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
121224  9:34:43 [Note] Server socket created on IP: '0.0.0.0'.
121224  9:34:43 [Note] Event Scheduler: Loaded 0 events
121224  9:34:43 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.28-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
121224  9:36:17 [Note] /usr/sbin/mysqld: Normal shutdown

121224  9:36:17 [Note] Event Scheduler: Purging the queue. 0 events
121224  9:36:17  InnoDB: Starting shutdown...
121224  9:36:18  InnoDB: Shutdown completed; log sequence number 1595675
121224  9:36:18 [Note] /usr/sbin/mysqld: Shutdown complete

121224 09:36:18 mysqld_safe mysqld from pid file /var/run/mysql/mysql.pid ended
121224 09:40:33 mysqld_safe Starting mysqld daemon with databases from /mnt/cache/web/mysql/
121224  9:40:33 InnoDB: The InnoDB memory heap is disabled
121224  9:40:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121224  9:40:33 InnoDB: Compressed tables use zlib 1.2.5
121224  9:40:33 InnoDB: Using Linux native AIO
121224  9:40:33 InnoDB: Initializing buffer pool, size = 128.0M
121224  9:40:34 InnoDB: Completed initialization of buffer pool
121224  9:40:34 InnoDB: highest supported file format is Barracuda.
121224  9:40:35  InnoDB: Waiting for the background threads to start
121224  9:40:36 InnoDB: 1.1.8 started; log sequence number 1595675
121224  9:40:36 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
121224  9:40:36 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
121224  9:40:36 [Note] Server socket created on IP: '0.0.0.0'.
121224  9:40:37 [Note] Event Scheduler: Loaded 0 events
121224  9:40:37 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.28-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
121224  9:47:29 [Note] /usr/sbin/mysqld: Normal shutdown

121224  9:47:29 [Note] Event Scheduler: Purging the queue. 0 events
121224  9:47:29  InnoDB: Starting shutdown...
121224  9:47:30  InnoDB: Shutdown completed; log sequence number 1595675
121224  9:47:30 [Note] /usr/sbin/mysqld: Shutdown complete

121224 09:47:30 mysqld_safe mysqld from pid file /var/run/mysql/mysql.pid ended
121224 11:17:30 mysqld_safe Starting mysqld daemon with databases from /mnt/cache/web/mysql/
121224 11:17:30 InnoDB: The InnoDB memory heap is disabled
121224 11:17:30 InnoDB: Mutexes and rw_locks use GCC atomic builtins
121224 11:17:30 InnoDB: Compressed tables use zlib 1.2.5
121224 11:17:30 InnoDB: Using Linux native AIO
121224 11:17:30 InnoDB: Initializing buffer pool, size = 128.0M
121224 11:17:30 InnoDB: Completed initialization of buffer pool
121224 11:17:30 InnoDB: highest supported file format is Barracuda.
121224 11:17:30  InnoDB: Waiting for the background threads to start
121224 11:17:31 InnoDB: 1.1.8 started; log sequence number 1595675
121224 11:17:31 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
121224 11:17:31 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
121224 11:17:31 [Note] Server socket created on IP: '0.0.0.0'.
121224 11:17:31 [Note] Event Scheduler: Loaded 0 events
121224 11:17:31 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.28-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution

What is the best way to make sure the newznab_screen script runs automatically after a reboot. Should i add it to my go scripts file? Also what is the difference between the  newznab_screen script and Tybio's cron script?

Delta between Screen script and Cron script:

 

The screen script requires installing "Screen" which is an easy to do thing, but needs 3 packages in /boot/extra.  I'm thinking of adding it to my new SphinxSearch plg.

 

The Cron script is a /bit/ more complex, but it doesn't leave "screen" running on your system and it doesn't require learning how to use screen.  The other upside is that there are lots of options in it that you can enable/disable as you need from the crontab rather than having to edit the file like you do with the screen script.

 

Honestly, it is mostly preference as to which you use.  The screen script is the most simple once you install screen.  However /I/ believe the cron is more supportable long term as you can build a plugin around it (which I am working on, just wanted to finish the SphinxSearch plugin first.

 

 

pleases forgive my ignorance but how would I install "screen" is it a package? Also is this and you cron the only way to have the update scripts run recursively ?

Ok, to make life more easy for people, I've added some "file gets" to the SphinxSearch package.  If you download and install it you will get:

 

sphinxsearch

screen

htop

 

And all the dependencies for them to run properly.

 

You don't have to turn SphinxSearch on, and if you are still figuring out what Screen and htop are..I'd recommend leaving it off.  But this way they will get auto installed on reboot.

 

I will be working to extend the addon over the next few days and add control for the crontab I wrote to the UI.  There is a learning curve getting in the way and I really need to beg Influencer or one of the other more experienced plugin designers for some mentoring time.

 

Once everything is working properly, I'll likely rename the addon to "Newznab_extras".

 

But, any updates from here wait until after the 25th ;).

  • Author

After Christmas I'd be more than happy to help out. I'll pm you my email, you can catch me on google talk.

Sounds great man, I'm only doing fly-bys of the forum myself for the next day or two.  I'll PM/IM you later in the week!

Ok so after spending most of the day trying to figure things out (i admit it im stupid when it comes to unraid) ive managed to get simplefeatures (with webserver and mysql) set up and running (both list running) and hey i even got sabnzbd and sickbeard working perfectly! Pretty impressive for me!

 

This is on the latest 5.0 rc8a

 

So i moved on to newznab. Seems ot be working fine now. For some reason my desktop was just being stupid and wouldnt work at all trying ot install it/configure it. But turned it off and moved to the laptop and viola I can run it and do the setup....but now im lost.

 

First under the "preflight check"

PHP Memory i get a warning and it says i should change it to >=256mb

I also get a warning for "The Apache module mod_rewrite is not loaded. This module is required, please enable it if you are running Apache"

 

Are either of those an issue? If so how do i even change them?

 

 

Then on the second setup for database.....yeah im lost i have no clue what to put. I tried just hitting next and its says "unable to select database"

What i have for it is...

Hostname: Localhost

Username:

Password:

Database: newznab

 

I guess i just dont know what should be put there.

 

For reference each directory from each plugin is

newznab - /mnt/cache/server/

mysql- /mnt/cache/appdata/mysql

webserver- /mnt/cache/server/www

 

 

Im sure i just dont have something setup right but searching just hasnt given me any real help so rather than keep searching i figured i would just ask for help.

Ok, I'm a noob right along with ya.

 

There is a php.ini file that you can change the memory limit in the normal version of newznab. I found php.ini in unraid but cant find the memory_limit section. Mine is pulling fast on unraid with 256 than my vm was pulling with unlimited memory.

 

The apache thing isnt needed. Apache is a web server and you already have the unraid version so you dont need it. I dont even know if its compatible.

 

I set my nzbfile path to a share so it doesnt fill up my small cache drive. I may be wrong in this(hence the first sentance"noob") but I think that is how I want it. The nzbfiles directory should grow larger and larger as you update and backfill.

 

Now, I have a problem or a question. When I start up my unraid server, I cant access my newznab. I have to disable webserver then re enable it to be able to access the web gui for newznab.

 

I have my newznab set up great if anyone needs and small noobish advice. Merry Christmas

Thanks i found the php.ini file and just searched for memory limit and found it was set at 128...so changed it to 256. Will have to restart the server im sure but for now its good enough.

 

Im still not sure i understand the Database setup on step 2 of the newznbd setup.

 

Hostname: localhost

Username:

Password:

Database: newznbd

 

 

Thats how its filled out by default but gives an error if i just click next. So what exactly goes there?

 

 

Told you i was a noob since any guide ive seen just says follow on screen directions haha

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.