Support #6885
VNC crontabs for startup and tickets
Description
Will add uniform crontabs on Control Room VNC account
to start VNC sessions at boot
and renew Kerberos tickets every 2 hours.
This is already being done in some sessions, but not uniformly.
History
#1 Updated by Arthur Kreymer over 6 years ago
- Estimated time set to 3.00 h
Summary of crontabs on main VM accounts
FD novadaq-far-master-02
novacr01
@reboot sleep 60; ~/bin/start-vncserver.sh
novacr02
@reboot sleep 60; ~/bin/start-vncserver.sh
kinit 02
novacr03
@reboot sleep 60; ~/bin/start-vncserver.sh
ND novadaq-near-master
novacr01
none
novacr02
none
novacr03
none
NDOS novadaq-ctrl-master
novacr01
@reboot ssh novacr01@novadaq-ctrl-master /home/novacr01/bin/start-vncserver.sh
novacr02
kinint 55
novacr03
none
#2 Updated by Arthur Kreymer over 6 years ago
@reboot sleep 60; /usr/krb5/bin/kinit -5 -F -A -k -t $HOME/.krb5/nova-principle.keytab novadaq/nova/novadaq-ctrl-master.fnal.gov@FNAL.GOV 2>/dev/null
55 * * * * /usr/krb5/bin/kinit -5 -F -A -k -t $HOME/.krb5/nova-principle.keytab novadaq/nova/novadaq-ctrl-master.fnal.gov@FNAL.GOV 2>/dev/null
Adjust the time to avoid collisions
FD 1 01 FD 2 02 FD 3 03 ND 1 11 ND 2 12 ND 3 13 NDOS 1 21 NDOS 2 22 NDOS 3 23
#3 Updated by Arthur Kreymer over 6 years ago
Plan to put files like VNCND1.crontab in bin
CVS repository for bin is like
Online/pkgs/NovaControlRoom/bin/
FarDet/nova-daq-01 02 03
NearDet/nova-daq-01 02 03
NDOS/...
#4 Updated by Arthur Kreymer over 6 years ago
- % Done changed from 0 to 90
Created crontabs in bin Aug 29
11:50
FD-novacr01.crontab
FD-novacr02.crontab
FD-novacr03.crontab
12:05
ND-novacr01.crontab
ND-novacr02.crontab
ND-novacr03.crontab
12:12
NDOS-novacr01.crontab
NDOS-novacr02.crontab
NDOS-novacr03.crontab
#5 Updated by Arthur Kreymer over 6 years ago
The crontabs are active on all systems,
with reference DET-novacr0*.crontab files in ${HOME}/bin.
I do not seem to have write access to CVS,
so these files are not added or committed to CvS as we would like.
#6 Updated by Arthur Kreymer over 6 years ago
All kerberos tickets are updating as scheduled.
The one anomaly is the novacr01@nova-near-master virtual desktop,
which is not using the expected ticket file
/tmp/krb5cc_510, but instead
/tmp/krb5cc_510_JtxCPb7595
Perhaps the desktop was started from an ssh session,
and inherited a non-standard ticket name.
All other sessions have standard ticket names.