Print

Print


​The problem seems​ to be that the database can't be accessed from the JLab guest network.  I was able to login into one of the jlabl* computers and access the database from there.

Jeremy, we should have fallback database that the conditions will connect to in case the JLab database is down or inaccessible.  Can you implement this?

Also, I  know you mentioned that you were going to clone the JLab database to over to SLAC.  Is that still the plan?  Has this been done? 

On Tue, Feb 24, 2015 at 8:10 AM, Hansson Adrian, Per Ola <[log in to unmask]> wrote:
Ciao,

it doesn’t seem to work. 

/Pelle

No input files in XML file.
java.lang.RuntimeException: Failed to connect to database: jdbc:mysql://hpsdb.jlab.org:3306/
at org.hps.conditions.database.ConnectionParameters.createConnection(ConnectionParameters.java:120)
at org.hps.conditions.database.DatabaseConditionsManager.openConnection(DatabaseConditionsManager.java:188)
at org.hps.conditions.database.DatabaseConditionsManager.initialize(DatabaseConditionsManager.java:342)
at org.hps.conditions.database.DatabaseConditionsManager.setDetector(DatabaseConditionsManager.java:290)
at org.lcsim.event.base.BaseLCSimEvent.<init>(BaseLCSimEvent.java:52)
at org.lcsim.lcio.LCIOEvent.<init>(LCIOEvent.java:62)
at org.lcsim.lcio.LCIOEvent.<init>(LCIOEvent.java:25)
at org.lcsim.lcio.LCIOReader.read(LCIOReader.java:59)
at org.lcsim.util.loop.LCIOEventSource.next(LCIOEventSource.java:129)
at org.freehep.record.loop.DefaultRecordLoop.fetchRecord(DefaultRecordLoop.java:809)
at org.freehep.record.loop.DefaultRecordLoop.loop(DefaultRecordLoop.java:648)
at org.freehep.record.loop.DefaultRecordLoop.execute(DefaultRecordLoop.java:566)
at org.lcsim.util.loop.LCSimLoop.loop(LCSimLoop.java:153)
at org.lcsim.job.JobControlManager.run(JobControlManager.java:427)
at org.hps.job.JobManager.run(JobManager.java:36)
at org.lcsim.job.JobControlManager.run(JobControlManager.java:185)
at org.hps.job.JobManager.main(JobManager.java:18)
Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure


On Feb 23, 2015, at 3:48 PM, McCormick, Jeremy I. <[log in to unmask]> wrote:

Hi,

The JLAB Computing Division requested some time ago that we move our MySQL server from the general jmysql host to a dedicated application server that they have setup for us.

I am in the process of performing the switch over this week.  Hopefully, this should be relatively seemless, as our database and user accounts have been replicated there.

There will also be an automatically updated external replica available for read only access, so we should not need a database at SLAC any longer.

For the time being, let's "freeze" the current production conditions database at JLAB and not modify it for now, until we have switched over to the new one.  I'm hoping this will be complete in the next day or two, pending some relatively minor fix-up of the new database's configuration.

Also, I am going to change the password on the hpscalibrations account to a strong password from the current weak one.  If you need this password on the new database, then please email me.  There are several people who I know need this for calibratiions work, and so I will go ahead and send them this information.

Thanks.

--Jeremy

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the HPS-SOFTWARE list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1



Use REPLY-ALL to reply to list

To unsubscribe from the HPS-SOFTWARE list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1




Use REPLY-ALL to reply to list

To unsubscribe from the HPS-SOFTWARE list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1