-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not load ECAL docs #487
Comments
We need this functionality for high voltage running Thur evening. I'm assuming this is the result of http->https? |
If it's due to https, you should be able to change the couchdb address to point to dbug.sp.snolab.ca on port 6984 (assuming the ECALs were loaded to the newer version of couchdb). If they were loaded to the older version of couchdb they should probably be re-uploaded to the newer version. @mastbaum can probably comment on where they were uploaded given the address and port used in penn daq. |
@tannerbk @tlatorre-uchicago -- see email. |
Still could not get this working on the teststand. |
Can you list the steps to reproduce and I'll give it try? |
Thanks Andy. In the crate view there is a "Fetch ECAL to GUI" (or something very similar). If you click that and wait 10 seconds you'll get an error in the orca logs like the ones in my first comment in this thread. I then played around with the debugdb database settings in the settings tab of the standard run control panel. Changing the settings to the ones suggest in the email did not seem to help. |
It appears this was due to DB settings -- please reopen if it happens again with the recommended setup. |
Still having an issue with loading ECAL documents at the teststand. Can you remind me what the database settings are supposed to be? I've tried several different sets of DB settings and I always get: |
When trying to load ECALs today we got (for both crate 12 and 13):
18-02-06 00:22:23 XL3 crate 13 didn't receive all the ECAL documents.
Missing slots: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
We did this from operug.
The text was updated successfully, but these errors were encountered: