MySQLON won't install, can't turn add-ons on in Frontview

[moonshadow]

Hi,

I believe I had some corruption in the MySQL database that caused my Newznab installation to crash. In Frontview, the MySQLON light was grey and I was unable to restart the add-on.

So, I thought it would be a good idea to remove and reinstall PRO-MySQLON, then reinstall Newznab. When attempting to reinstall PRO-MysqlOn_1.0.bin from Frontview, it returned the error: "Update file is not valid for this architecture." That's odd, because I had been running this add-on before Newznab crashed.

I looked around in /var/lib and /etc/frontview/addons/bin, and it appeared that MySQLON was still there, so I tried restarting it from the command line and got the following error:

mysqladmin: connect to server at 'localhost' failed
error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)'
Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!

I checked, and /var/run/mysqld/mysqld.sock does exist.

Bad to worse: It now appears I am unable to change the on-off behavior of any of my add-ons in Frontview. I had turned off SABnzbd, Sickbeard, and CouchPotato in preparation for the Newznab reinstall, and now I can't restart them. Very sad.

I am running a ReadyNAS Ultra 6 Plus with RAIDiator 4.2.27.

Anybody have any ideas?

[mdgm-ntgr]

Full 4GB OS partition, perhaps?

# df -h
# df -i
# ls -la /tmp

[moonshadow]

Thank you for your response mdgm, and once again you are spot on. The OS partition is full.

I had considered, and immediately dismissed, the possibility that the OS partition was full, because I had moved the MySQL databases to /c/databases (or so I thought) before installing Newznab, but I obviously did something wrong. I'm still too much of a Linux noob to figure out how to check the free space.

Anyway, now I have a research project to figure out how to clear out all the clutter in the OS partition, though I'm fairly apprehensive about tinkering around in there. I would welcome any suggestions.

Cheers,
Moonshadow

[mdgm-ntgr]

Some add-ons that use MySQL databases already use symlinks that point to the data volume. MySQL isn't the only thing that can fill up the OS partition.

[moonshadow]

Good to know. I located the data that was filling it up, copied it to the /c partition, and deleted the offending directory. All functionality is restored and I'm a little but wiser. Thank you for your help.

[bonsaier]

Just had the same situation, and didn't think about a full OS partition. Sure enough.... Thanks for the solution : )