Huh, this last go-round worked: mysql> show tables; +-------------------------+ | Tables_in_openmeetings | +-------------------------+ | OPENJPA_SEQUENCE_TABLE | | adresses | | appointmentcategory | | appointmentremindertyps | | appointments | | conferencelog | | conferencelogtype | | configuration | | errortypes | | errorvalues | | extensions | | fieldlanguage | | fieldlanguagesvalues | | fieldvalues | | fileexploreritem | | flvrecording | | flvrecording_log | | flvrecording_meta_delta | | flvrecording_metadata | | invitations | | ldapconfig | | meeting_members | | meetme | | naviglobal | | navimain | | om_timezone | | open_xg_return_object | | organisation | | organisation_users | | poll_types | | private_messages | | private_messages_folder | | room_poll_answers | | room_polls | | rooms | | rooms_moderator | | rooms_organisation | | roomtypes | | salutations | | sessiondata | | sipusers | | soaplogin | | states | | user_contacts | | user_sip_data | | userdata | | userlevel | | users | +-------------------------+ 48 rows in set (0.00 sec)
The only difference in what I did this time was that OM was running (restarting OM after db backup wasn't in the how-to). I checked persistence.xml's timestamp and, sure enough, it was set at approximately the time I ran admin.sh, so I'm assuming proper changes were made to it by admin.sh. I then restarted OM. How do I verify that MySQL is being used as the back-end? Dimitri On Thursday 02 August 2012 12:51:49 pm Maxim Solodovnik wrote: > OK > lets check admin command then > > As I can understand you have standard mysql installation on local host > and connect as root with password? > > so lets simplify things: > ./admin.sh -v -i -file backup.zip --db-user "root" --db-type "mysql" > --db-pass "your_password" --drop > > any useful stacktrace as a result? > > On Thu, Aug 2, 2012 at 11:12 PM, Dimitri Yioulos <dyiou...@onpointfc.com>wrote: > > Yes: > > > > mysql> show databases; > > +--------------------+ > > > > | Database | > > > > +--------------------+ > > > > | information_schema | > > | mysql | > > | openmeetings | > > | test | > > > > +--------------------+ > > 4 rows in set (0.00 sec) > > > > mysql> use openmeetings; > > Database changed > > > > I strictly followed your how-to. But, must I have OM running before I > > issue the > > admin.sh command? > > > > Dimitri > > > > On Thursday 02 August 2012 12:03:38 pm Maxim Solodovnik wrote: > > > have you created DB table openmeetings in your MySQL DB? > > > are you able to connect to mysql using command line? > > > > > > mysql -u <user> -p openmeetings > > > > > > On Thu, Aug 2, 2012 at 8:24 PM, Dimitri Yioulos <dyiou...@onpointfc.com > > > > > >wrote: > > > > Thanks, Rubens. > > > > > > > > Ran netstat to confirm that MySQL is listening on port 3306. After > > > > moving the > > > > original persistence.xml to persistence.xml.orig, I then copied > > > > mysql_persistence.xml to persistence.xml (even though I think that > > > > Maxim > > > > > > said > > > > that admin.sh should create a usable persistence.xml). > > > > Interestingly, when I > > > > look at persistence.xml, the MySQL username and password were > > > > correct. Despite > > > > all that, I still get: > > > > > > > > [ERROR] [main] org.openmeetings.cli.Admin - Install failed A > > > > connection could > > > > not be obtained for driver class "com.mysql.jdbc.Driver" and > > > > URL > > > > "jdbc:mysql://localhost:3306/openmeetings?autoReconnect=true&useUnicode=t > > > > > >rue& createDatabaseIfNotExist=true&characterEncoding=utf-8& > > > > connectionCollation=utf8_general_ci&cachePrepStmts=true&cacheCallableStat > > > > > >ements=true& > > > > cacheServerConfiguration=true&useLocalSessionState=true&elideSetAutoCommi > > > > > >ts=true& > > > > alwaysSendSetIsolation=false&enableQueryTimeouts=false&prepStmtCacheSize= > > > > > >3000&prepStmtCacheSqlLimit=1000". You may have specified an invalid > > > > URL. > > > > > > > > Hmmm. > > > > > > > > Dimitri > > > > > > > > On Thursday 02 August 2012 8:24:24 am Rubens Queiroz de Almeida wrote: > > > > > I had this very same problem yesterday. In my case, what happened, > > > > > is > > > > > > > > that > > > > > > > > > mysql was listening on another port, so I had to change the default > > > > > mysql port number (3306) for the number of the port actually used. > > > > You > > > > > > > should also check whether the user defined in the persistence.xml > > > > file > > > > > > > is > > > > > > > > allowed > > > > > > > > > to create databases, should this be the case. > > > > > > > > > > The file persistence.xml is located at > > > > > $OPENMEETINGS_HOME/webapps/openmeetings/WEB-INF/classes/META-INF/ > > > > > The directory META-INF/ contains several files, you should select > > > > > the database you're using and do the following: > > > > > > > > > > mv persistence.xml persistence.xml.backup > > > > > cp mysql_persistence.xml persistence.xml > > > > > (if you're using mysql. Jaime said that it works much better with > > > > > postgresql) > > > > > Also, if you're using mysql you should download the jdbc driver > > > > > from the MySQL site, it does not come with the openmeetings file, > > > > > due to licensing issues. > > > > > > > > > > You should then edit the file persistence.xml and change the > > > > > information regarding the database and connections: > > > > > > > > > > , Username=openmeetings > > > > > , Password=xxxxxx"/> > > > > > > > > > > I hope this helps, > > > > > > > > > > Best regards, > > > > > > > > > > Rubens > > > > > > > > > > On Thu, Aug 2, 2012 at 9:14 AM, Dimitri Yioulos < > > > > dyiou...@onpointfc.com > > > > > > >wrote: > > > > > > Ran the below steps. The last step produced the following error: > > > > > > > > > > > > [ERROR] [main] org.openmeetings.cli.Admin - Install failed A > > > > > > connection could > > > > > > not be obtained for driver class "com.mysql.jdbc.Driver" and > > > > > > URL "jdbc:mysql://localhost:3306/openmeetings?autoReconnect=true& > > > > useUnicode=true&createDatabaseIfNotExist=true&characterEncoding=utf-8 > > > > > > > >& connectionCollation=utf8_general_ci&cachePrepStmts=true& > > > > > > cacheCallableStatements=true&cacheServerConfiguration=true& > > > > useLocalSessionState=true&elideSetAutoCommits=true&alwaysSendSetIsolation > > > > > > > >=false& > > > > enableQueryTimeouts=false&prepStmtCacheSize=3000&prepStmtCacheSqlLimit=10 > > > > > > > >00". You may have specified an invalid URL. > > > > > > > > > > > > What am I missing? > > > > > > > > > > > > Dimitri > > > > > > > > > > > > On Thursday 02 August 2012 7:49:41 am Dimitri Yioulos wrote: > > > > > > > Thanks, Maxim. I'll give that a try in a while. I owe you a > > > > beer > > > > > > > > > or three :-) . > > > > > > > > > > > > > > Dimitri > > > > > > > > > > > > > > On Thursday 02 August 2012 7:44:37 am Maxim Solodovnik wrote: > > > > > > > > 1) cd OM folder > > > > > > > > 2) stop OM > > > > > > > > 3) ./admin.sh -b -file backup.zip > > > > > > > > 4) ./admin.sh -i -file backup.zip --db-type mysql --db-user > > > > root > > > > > > > > > > --db-pass <pass> --drop > > > > > > > > > > > > > > > > please check the admin syntax by running ./admin.sh with no > > > > > > > > params > > > > > > > > > > > > > > > > On Thu, Aug 2, 2012 at 6:40 PM, Dimitri Yioulos > > > > > > > > > > > > <dyiou...@onpointfc.com>wrote: > > > > > > > > > All, > > > > > > > > > > > > > > > > > > I'm moving along very nicely with my OM 2.0 installation. > > > > But, > > > > > > > > > > > I was wondering > > > > > > > > > if I can do this: > > > > > > > > > > > > > > > > > > I initially set up OM to use the internal database. I'd > > > > > > > > > like to move to MySQL. > > > > > > > > > Can it be done now that OM is already installed and, if so, > > > > how > > > > > > (is > > > > > > > > > > > > > there a how-to, or some-such, available?)? > > > > > > > > > > > > > > > > > > As always, thanks. > > > > > > > > > > > > > > > > > > Dimitri > > > > > > > > > > > > > > > > > > -- > > > > > > > > > This message has been scanned for viruses and > > > > > > > > > dangerous content by MailScanner, and is > > > > > > > > > believed to be clean. > > > > > > > > > > > > > > > > -- > > > > > > > > WBR > > > > > > > > Maxim aka solomax > > > > > > > > > > > > -- > > > > > > This message has been scanned for viruses and > > > > > > dangerous content by MailScanner, and is > > > > > > believed to be clean. > > > > > > > > -- > > > > This message has been scanned for viruses and > > > > dangerous content by MailScanner, and is > > > > believed to be clean. > > > > > > -- > > > WBR > > > Maxim aka solomax > > > > -- > > This message has been scanned for viruses and > > dangerous content by MailScanner, and is > > believed to be clean. > > -- > WBR > Maxim aka solomax -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
