an Assistent not limited to conversion of VDR-recordings to DVD-images
License
Frequently asked questions
FAQ (nicht zu verwechseln mit dem Wort, das mit 'u' geschrieben wird) steht im neudeutschen für "frequently asked questions", was im deutschen nichts anderes heißt, als häufig gestellte Fragen -
oder für Leute mit AKÜFI eben
HGF
... recordings or jobs. Database contains lots of both ...
That happens, when you update your system, while the services are running. Doing so is quite ok, ...
... but after update, you'll need to restart the services. The ServiceManager is the only service, that must be restarted manually (as root user):
/etc/init.d/SRServiceManager restart
All other services can be restarted from WebIF. Same is true for the "Service-Backend" service, which usually runs with autostart enabled. Select the service in the WebIF list and hit "Stop". After 3-5 minutes the service should be up again an reply to your requests.
After restart, recordings and jobs should be displayed again.
If that's not true, don't hesitate to use ML
... but anytime I start VDRAssistant, it comes up with the settings dialog
That shows, that connection to the database engine fails. Using java u can't log into the database with localhost, so MySQL has to be configured to accept connections over the network.
Take a look at the setting of bind-address in the file my.cnf. If bind-address is followed by localhost or 127.0.0.1, the database engine does not accept connections over the network. Replace the address with the network address, you use to ping the database-server from a different host.
I.e
bind-address = 192.168.1.1
If bind-address already reflects the network address of your database-server, please check, whether the database engine accepts connections from the host, you'd installed VDRAssistant - like
mysql -D dbVDRAssistant -h <DBServer> -u vaUser -pIf that works, and i.e. a "list databases;" gives you a reasonable result, it should work with java too. If it does not work, you have to change the permission for the user.
... but now it always comes up with the settings dialog
That indicates a problem connecting to the database engine. Some linux network assistants have the undesired ability to add the hostname to the local ip address. After that, nothing works as expected, so take a look at /etc/hosts whether the hostname follows the address 127.0.0.1 - if so, just remove the hostname (but leave the entry "127.0.0.1 localhost") and anything should be fine again.
... but I get the error message: The current settings from DBServer don't allow access to known database objects.
Could it be, that your database users don't have a password? That's a security hole and VDRAssistant will never support that! Every (!) user should have a password.
... but nothing more happens.
That will happen at linux systems, that have a gnu-java active instead of a real java. So if you're sure, that a real java (sun jdk or sun jre) has been installed, it's possible, that the real java needs to get activated.
That's what's galternatives is for. But that tiny tool needs superuser rights to execute it. Install sux and you're fine. After getting superuser access to the X-server, start galternatives and activate the real java (don't ever let you get fooled by a gnu-java - gcj).
There are 2 possible reasons for this error:
The user executing the installer is not allowed to use sudo. Please check /etc/sudoers.
if the first reason is not true, the java may be patched on the linux you are using.
That will probabely happen at Suse-systems. They patched (even the Sun-)java so that it can't save the system properties at the well known places. The next version of the installer should contain a workaround - at least for Suse-Systems.
Of cause, there are a lot of geniuses out there, that need to improve standards ...
In that case the only workaround is to install VDRAssistant beeing root.
... the log contains lots of errors and the overview of recordings stays empty.
This happens with an elder version of handbrake. They changed the output and unfortunatelly the tool does not support a version, so it is hard to determine, which one will work ...
So my recommendation is: use handbrake from svn trunk (as I do) and build it by yourself. If the trunk happens to fail, use the latest snapshot, that works.
