Issues logging into daqdtp after deploying the New DAQ.
#1 Updated by Arthur Kreymer over 5 years ago
- Priority changed from Normal to High
- Estimated time set to 2.00 h
The first problem I found was that the .k5login on daqtpc
was missing -- not sure how that happened.
But after restoring it, still getting errors on the copy:
debug1: Local version string SSH-2.0-OpenSSH_5.3
debug1: Unspecified GSS failure. Minor code may provide more information
Server host/daqtpc.minos-soudan.org@FNAL.GOV not found in Kerberos database
Checked the /etc/hosts file, as suggested in the FNAL kerberos
help pages, but that looks OK. Maybe Art as some
ideas at this point?
#6 Updated by Arthur Kreymer over 5 years ago
- Due date set to 03/07/2014
- Status changed from New to Resolved
- % Done changed from 0 to 100
Date: Fri, 7 Mar 2014 13:59:50 -0600
From: David Wayne Saranen <firstname.lastname@example.org>
Rather than introduce maintenance nightmare by using the
/opt/minos-online/bin, I created /home/minos/OLDDAQ, added a script to scp
the SpillServer and TimeMaster kvp files, then ran the script from cron. Not
knowing how loaded minos-daq02-fd is, I opted to run the cron job every
other minute. Change as needed. (For the ssh transfers I set up a host key,
adding it on daqsrv.)
There is no sanity checking yet. Eventually, when the issues for upgrading
or modifying daqtpc are resolved. The script and all can go away.
I also changed on farweb, the daq_status_newDaq.cgi to point to the correct
ND DAQ status page. (It had been pointing at minos-om.) I see that the ND
daq_status page is still pointing to the old FD DAQ_status page.