Hello,
I installed the latest version of Dapper on Ubuntu, running MySQL 5. I had no problem with getting the dapperload.sh working, and verified that it's loading data into the database. The Dchart application is also functional.
However, the Dapper/DODS interface is not functioning correctly. Specifically, I'm getting errors (in the jakarta logs) when trying to connect to the MySQL server. I assume this is a problem with JDBC, but I don't know enough to track it down other than verifying that the appropriate Connector/J binary is in the dapper folders.
I would like to use the package to interface with MySQL to server in situ data, but this connectivity issue has me at a roadblock. Is there something that I should be doing when configuring the server? I can provide the logfile error trace if that's useful.
Thanks!
Hi Raphael, If dapperload is
Hi Raphael,
If dapperload is working, then you should verify that the etc/dapper.properties is configured with the same values for hostname, user, password, and database as the ones you used when you ran dapperload. You might also see if you can connect to your mysql server via the mysql command line using the same values for hostname, user, and password that are configured in the etc/dapper.properties files, e.g. something like:
mysql -h hostname -u username -ppassword database
where hostname, username, password, and database are the dbhost, user, password, and one of the cdp_databases properties.
If that doesn't work, send me your log file (jakarta/logs/catalina.out)
- Joe
Thanks!
Joe, thank you for the quick reply. I'm not sure exactly what was configured wrong, but it was either an invisible character in the dapper.properties file, or I needed to explicitly define the host as localhost. The user, pass, and db were all correct, but I erased and retyped them--I also added the localhost designation. That got DODS running OK. I still am having some java error issues occasionally when I stop and restart dapper, but that appears to be an issue with my machine specifically, and rebooting fixes it.