Frequently Asked Questions

You downloaded an add-on for a CPU architecture other then the one that your ReadyNAS is using. See the menu entry "Checksum Error" in our main navigation.

• Login to post comments
• Back to Top

There are many reasons why you cannot log into your local MySQL server using PHPMyAdmin. But before explaining those in some more detail, just a note: The PhpMyAdmin add-on was not intended to be used for accessing the local MySQL server only. Instead it is a general purpose tool with the ability to manager MySQL server on the ReadyNAS, in the local network or even over the internet. Thus there is no default configuration for the local MySQL server instance.

Ok, now let's see why PhpMyAdmin may fail to connect to the local MySQL server.

1. Reason #1: MySQL isn't running at all
   While many users believe that their ReadyNAS comes with it's MySQL server up and running, this actually isn't the case. Instead the MySQL server is either enabled by add-ons that need it (which PhpMyAdmin does not) like for example ReadyNAS Photos. Or it is activated by installing the MySQLOn add-on (-> Sparc version / -> x86 version). So the first action to take should be to make sure MySQL is actually running on your ReadyNAS.
   
   
2. MySQL (on the ReadyNAS) doesn't listen on TCP/IP ports
   For some or other reasons, the MySQL server on the ReadyNAS doesn't listen on any TCP/IP address and port. Instead it runs its communications through a socket connection only. So to access your MySQL server from PHPMyAdmin you have to configure PHPMyAdmin to use a socket connection. This is done on the first tab ("Basic Settings") of the Setup Wizard's dialogue like this:

   

   In addition, make sure to NOT use the IP address of your ReadyNAS for the "Server Hostname" setting on the same tab. Use "localhost" instead like in the following example:

   

3. MySQL (on the ReadyNAS) uses a non-standard socket location
   Again diverging from the original standard, the socket fpr communicating with the MySQL server on your ReadyNAS is placed in /var/run/mysqld/mysqld.sock whereas it normally resides in /tmp/mysql.sock. Since many applications use the standard location you have to tell PHPMyAdmin where the socket on the ReadyNAS is located. This is again done on the first tab ("Basic Settings") of the Setup Wizard:

   

4. The default root password for MySQL (on the ReadyNAS) is empty
   Not putting too much emphasis on security since the MySQL server is reachable through a local socket only the password for the admin user "root" of the MySQL server on the ReadyNAS is empty. This conflicts with the security conciousness of PhpMyAdmin which by default requires any account to use a password to connect. To change this, you have to modify the "Allow logins without a password" setting which can be found on the third tab ("Server Settings") of the Setup Wizard. Your setting to access the local MySQL server should look like this:

   

After having made all the neccessary changes and having saved your configuration twice - once to save the server info you entered, once again to commit the whole configuration to file - your PhpMyAdmin should connect fine with the local MySQL server instance on your ReadyNAS.

• Login to post comments
• Back to Top

That's because the "compression" option is not meant for Rsync over SSH but for pure Rsync transfers instead. Thus this option is not compatible with Rsync over SSH and must be turned off.

• Login to post comments
• Back to Top

That's a bug in Frontview's script system. When testing Rsync over SSH connections, wrong parameters are passed to the rsync program which then of course fails. To test your Rsync over SSH backup jobs just set them up and run them manually from the Backup Jobs overview page. Verify that the job does what you expect it to do.

• Login to post comments
• Back to Top

Most likely the problem isn't with the SABnzbd add-on. More likely the initial install of the Python add-on failed and this prevents SABnzbd from running properly.To determine whether Python was installed correctly do the following:

• Log into your ReadyNAS using SSH as the root user
• Issue the command "which python"

If the result of this command shows a path like "/usr/local/bin/python" then you previously installed Python manually which prevents the Python add-on from installing correctly.To fix this problem, do the following:

• Log into your ReadyNAS using SSH as the root user
• Issue the command "mv /usr/local /usr/local.bak"
• Restart your ReadyNAS using Frontview's "Shutdown and Restart" option
• Re-install the Python add-on
• Re-install the SABnzbd add-on

Note: By renaming the /usr/local directory you not only cut off the operating system's access to the old Python interpreter but also to any other tools you may have installed in that location. So to get those back either create a new /usr/local directory structure and copy/move back the files you need or just re-install them from source as you did before. 

• Login to post comments
• Back to Top

Most likely the problem isn't with the SickBeard add-on. More likely the initial install of the Python add-on failed and this prevents SickBeard from running properly.To determine whether Python was installed correctly do the following:

• Log into your ReadyNAS using SSH as the root user
• Issue the command "which python"

If the result of this command shows a path like "/usr/local/bin/python" then you previously installed Python manually which prevents the Python add-on from installing correctly.To fix this problem, do the following:

• Log into your ReadyNAS using SSH as the root user
• Issue the command "mv /usr/local /usr/local.bak"
• Restart your ReadyNAS using Frontview's "Shutdown and Restart" option
• Re-install the Python add-on
• (optional) Re-install the SABnzbd add-on
• Re-install the SickBeard add-on

Note: By renaming the /usr/local directory you not only cut off the operating system's access to the old Python interpreter but also to any other tools you may have installed in that location. So to get those back either create a new /usr/local directory structure and copy/move back the files you need or just re-install them from source as you did before.

• Login to post comments
• Back to Top