Serviio 1.5.2 with MySQL on ReadyNAS Duo/NV+ V2
I've been using Serviio since version 1.0, and have always been impressed. During version 1.2 I created a Serviio package for the ReadyNAS NV+/Duo v2 (ARM architecture) which has always run well, as long as it didn't need to transcode (due to both memory and CPU limitations).
Having recently refreshed my NAS, I decided to refresh my Serviio package to the latest version too. Whilst investigating the configuration options, I found reference to using alternative DBs (thereby possibly moving the DB out of memory, which seems a good idea on a low memory, massive storage device). However, all talk of instruction seems to have died out sometime in 2012-ish.
I've followed the instructions in http://forum.serviio.org/viewtopic.php?f=6&t=15531, less those concerning replacing the SQL files as the Serviio changelog states that mysql interaction has been supported since version 1.4.1-2 (can't remember which). However, when I try and access the console, all REST requests return HTTP 500 Error, as shown in my server log file below.
N.B. If I get rid of the -DdbURL=jdbc:mysql://... option, thereby reverting to Derby, everything works perfectly.
I was wondering two things:
If it helps, I'm also attaching the java-level error reporting logs from both the derby and mysql startup process:
... and those for console requests in each case:
Having recently refreshed my NAS, I decided to refresh my Serviio package to the latest version too. Whilst investigating the configuration options, I found reference to using alternative DBs (thereby possibly moving the DB out of memory, which seems a good idea on a low memory, massive storage device). However, all talk of instruction seems to have died out sometime in 2012-ish.
I've followed the instructions in http://forum.serviio.org/viewtopic.php?f=6&t=15531, less those concerning replacing the SQL files as the Serviio changelog states that mysql interaction has been supported since version 1.4.1-2 (can't remember which). However, when I try and access the console, all REST requests return HTTP 500 Error, as shown in my server log file below.
N.B. If I get rid of the -DdbURL=jdbc:mysql://... option, thereby reverting to Derby, everything works perfectly.
I was wondering two things:
- What do people think might be going wrong?
- If MySQL is a supported alternative to Derby in Serviio, why is there no information concerning using any alternative database software on the wiki?
- Code:
2015-08-12 14:33:49,502 INFO [MediaServer] ------------------------------------------------------------------------
2015-08-12 14:33:49,524 INFO [MediaServer] Serviio DLNA media streaming server v 1.5.2 (rev. 4b9ce176daa1)
2015-08-12 14:33:49,525 INFO [MediaServer] Petr Nejedly 2009-2015
2015-08-12 14:33:49,526 INFO [MediaServer] http://www.serviio.org
2015-08-12 14:33:49,526 INFO [MediaServer]
2015-08-12 14:33:49,527 INFO [MediaServer] Java 1.8.0_51-Oracle Corporation arm
2015-08-12 14:33:49,527 INFO [MediaServer] OS Linux 2.6.31.8.nv+v2
2015-08-12 14:33:49,529 INFO [MediaServer] File encoding: UTF-8
2015-08-12 14:33:49,534 INFO [MediaServer] Headless mode enabled: true
2015-08-12 14:33:49,534 INFO [MediaServer] User: admin
2015-08-12 14:33:49,534 INFO [MediaServer] User home dir: /c/home/admin
2015-08-12 14:33:49,534 INFO [MediaServer] Temp dir: /tmp
2015-08-12 14:33:49,535 INFO [MediaServer] ------------------------------------------------------------------------
2015-08-12 14:33:51,618 INFO [WebServer] Socket buffer set to 65535 bytes
2015-08-12 14:33:51,626 INFO [RestletServer] Starting Restlet server (/rest) exposed on port 23423
2015-08-12 14:33:52,862 INFO [RestletServer] Starting Restlet server (/cds) exposed on port 23424
2015-08-12 14:33:52,865 INFO [RestletServer] Starting Restlet server (/mediabrowser) exposed on port 23424
2015-08-12 14:34:35,475 INFO [DatabaseManager] Using MYSQL database language
2015-08-12 14:34:40,324 WARN [ServiioStatusService] ExceptionInInitializerError occured. Returning error code 500 to the REST layer. Message: null
2015-08-12 14:34:42,491 WARN [ServiioStatusService] NoClassDefFoundError occured. Returning error code 500 to the REST layer. Message: Could not initialize class org.serviio.config.Configuration
2015-08-12 14:34:47,016 WARN [ServiioStatusService] NoClassDefFoundError occured. Returning error code 500 to the REST layer. Message: Could not initialize class org.serviio.config.Configuration
2015-08-12 14:34:47,223 WARN [ServiioStatusService] NoClassDefFoundError occured. Returning error code 500 to the REST layer. Message: Could not initialize class org.serviio.config.Configuration
2015-08-12 14:34:47,381 WARN [ServiioStatusService] NoClassDefFoundError occured. Returning error code 500 to the REST layer. Message: Could not initialize class org.serviio.config.Configuration
2015-08-12 14:34:48,408 WARN [ServiioStatusService] NoClassDefFoundError occured. Returning error code 500 to the REST layer. Message: Could not initialize class org.serviio.config.Configuration
2015-08-12 14:34:48,428 WARN [ServiioStatusService] PersistenceException occured. Returning error code 500 to the REST layer. Message: Cannot read all AccessGroups
2015-08-12 14:34:48,541 WARN [ServiioStatusService] NoClassDefFoundError occured. Returning error code 500 to the REST layer. Message: Could not initialize class org.serviio.config.Configuration
If it helps, I'm also attaching the java-level error reporting logs from both the derby and mysql startup process:
... and those for console requests in each case: