• A-Z
  • Directory
  • myUVM
  • Loading search...

Frank's Activity Log

11. February 2016: Thursday

Posted: February 12th, 2016 by fcs

Note: This was a vacation day!

LDAP/IdM:

  • Updates: Two (2) issues:
    • Two new STU employees lacking SSN.  Found and merged.
  • Development:
    • Released the new code to test.
  • Problems:
    • The Account creation process and the Exchange Email Sync process both die at 5:02 am.  Nobody notices until I am investigating why a particular account is not set up for email in the evening.

Backups:

  • Save Groups: The usual gang of three fail.

10. February 2016: Wednesday

Posted: February 12th, 2016 by fcs

LDAP/IdM:

  • Updates: No issues.
  • Accounts: No (0) errors in 397 new accounts.
  • Feeds:
    • New issue of the monthly RETIREE feed
    • Updated to go production
  • Development:
    • Debugging the code.  Finding lots of bugs to remove.

Backups:

  • Save Groups: The usual gang of three fail.
  • Clones: Tape continues

General:

  • CF-Engine 3.6 deployment party

9. February 2016: Tuesday

Posted: February 10th, 2016 by fcs

LDAP/IdM:

  • Updates: One (1) issue:
    • OSP reverted the SSN that they had me manually change last week.  This time, they did it without having me pre-change the value in LDAP and I got to clean up the mess in the morning.
  • Accounts: No (0) errors in 232 new accounts.
  • Development: Working on how to process the changetype: modify updates from ldif_diff.

Backups:

  • Save Groups:
    • The usual gang of three failures.  Right – the Save Set reorder from Monday made no difference.
    • cedar has recovered – running on the old kernel.
  • Clones:
    • COMIS finished.
    • DISK finished.

General:

  • Meeting on git usage to get the Windows brethren on board and going.

8. February 2016: Monday

Posted: February 9th, 2016 by fcs

LDAP/IdM:

  • Updates:
    • Friday: Two (2) issues – surname match failures
      • Student: A long time employee has become a student – but first and last names are reversed in Banner.
      • Employee: A current student has become a Temporary employee.  Looks like the surname was misspelled. Asked HR to confirm.
        • Confirmed.  Updated the PS feed data and merged.
    • Saturday and Sunday: No issues.
  • Accounts:
    • Saturday-Monday: No (0) errors in 292, 17, five (5) new accounts.
  • Development:
    • Processing ldif_diff output: got code from Geoff.
    • OpenLDAP 2.4.44:
      • Fixes for ITS#8226, 8360, 8351, 8327, 8354, 8281 and 8365 that seem to fit us.
      • Built RPM and installed on test systems

Backups:

  • Save Groups:
    • Friday: The usual gang of three failures
    • Saturday: The usual gang, plus nsnetbackup (raid card battery failure)
    • Sunday: The usual gang of failures
    • COMIS: reorder savesets in MED23A – maybe the VSS failure is positional? (straw grasping)
    • comet backup cancelled – kernel updated to one with network performance problem.  Admin is backing off kernel (tonight’s backup will tell if it was successful).
  • Tapes:
    • Reclaimed twelve (12) tapes for the vaults.
  • SSIDS:
    • Fixed the bad retention times of 180 save sets.
  • Clones:
    • Started

General:

  • Meeting with a new vendor rep.
  • Check-in with the boss.

 

5. February 2016: Friday

Posted: February 8th, 2016 by fcs

LDAP/IdM:

  • Updates: No issues
  • Accounts: No (0) errors in 263 new accounts
  • Development:
    • Completed testing of {d,r}eactivate_account scripts and released them to production.  Usage after 8:30am will properly {,un}block the Exchange mailbox for those that have them.
    • Refactoring nightly LDAP update code to utilize existing code instead.

Backups:

  • Save Groups:
    • The usual gang of three (3) failed.
      • CoM/IS confirms that they are seeing the same two VSS errors with WBS, so this is not a NetWorker issue (this time!).
    • hound – failed – not able to ping it – permanently gone?
      • Yes.  Decommissioned the client.

4. February 2016: Thursday

Posted: February 5th, 2016 by fcs

LDAP/IdM:

  • Updates:
    • OSP: two (2) failures – which was really the changing of their primary key on an entry.  Fortunately, they had contacted me on Wednesday and we’d pre-changed the entry so no new account was created.
  • Accounts:
    • No (0) errors in the one (1) account created.
  • Development:
    • Cleaned up the tangled git branches on tayra.
    • {de,re}activate_account: working on doing the Exchange block/unblock calls.
  • Education:
    • Meeting with the AD team about the LDAP->AD nightly process.

Backups:

  • Save Groups:
    • The usual gang of three (3) failed groups.
    • The new SB groups ran great!

Exchange:

  • Private entries: Maybe I’m wrong!  We limit what we put in AD for these entries, so without good reason, there is no real need to hide them from the GAL as well.   The one account that sparked this discussion may well be a special case.
  • Scheduled meeting for February 17 to discuss.

3. February 2016: Wednesday

Posted: February 4th, 2016 by fcs

LDAP/IdM:

  • Updates: No issues from last night
    • Issue from Monday: Matched.  Merged, Account created.
  • Accounts: No (0) errors in 210 new accounts.

Backups:

  • Save Groups:
    • The usual gang of failures
    • Restructured the Structured Biology group:
      • Three weekends (2nd, 3rd, 4th) and groups 1, 2, and 3).

Exchange:

  • Private entries are not so private in AD/Exchange… long discussion… maybe I’m wrong?

2. February 2016: Tuesday

Posted: February 3rd, 2016 by fcs

LDAP/IdM:

  • Updates:
    • Thursday: one (1) issue, new employee, no ssn
      • Found and merged.
    • Friday: five (5) issues:
      • Thursday’s issue modification – all set.
      • Four (4) new employees, no ssns
        • Found and merged (one spelling error)
    • Monday: two (2) issues:
      • One of Friday’s issues modification – all set
      • New employee, new name – off to HR for validation
  • Accounts:
    • No (0) errors in 110, 168, zero, zero, and 94 new accounts… Friday-Tuesday
  • Code:
    • IAM: mailalias script is not dealing well with people requesting the formerly invisible (deliverable only) aliases as their primary contact address.
      • Updated so all aliases (mailLocalAddress) are acceptable
      • Exit if no Account is entered to work with
      • Show caveats about Accounts that get mail in Exchange – and exit if they don’t understand.
      • Give a “hey, you let it sit too long” message when the LDAP connection times out.

Backups:

  • Save Groups:
    • The usual gang of failures
    • bbdb1 – no route to host – discovered it is gone – decommissioned the client
    • dpm1 – VSS error persists (it is now usual)
  • Clones:
    • Started and finished (fifth Saturday syndrome)
  • Tapes:
    • Reclaimed one (1) for the vaults.
  • Test System:
    • 45 Day freebie license expired – need to refresh before I do anything further.

28. January 2016: Thursday

Posted: February 2nd, 2016 by fcs

Note: Sorry for the delay in posting this – I’ve been ill.

LDAP/IdM:

  • Updates
    • two (2) issues
      • Employee, sans SSN
        • Found, merged.
      • Employee, new surname
        • Found, merged…
        • Created account
        • Updated FS Kerberos
  • Accounts
    • No (0) issues in 54 new accounts
  • Code
    • Updated mkacct (and ldapAccount.pl) to deal with creating principals in FS Kerberos when required.
    • Updated Transportation and Parking feed stream to limit middle names to 24 characters.

Backups:

  • Save Groups
    • The usual failures
    • SB still chugging on that weekend full
    • dpm1 – VSS error continues
    • openstack – fewer systems down
  • Clones:
    • DISK and TAPE continue
  • Tapes
    • Cleaning cartridge expired, replaced

SecurID:

  • RSA announces 8.1 SP 1 Patch 11
    • Downloaded: Looks like some interesting fixes here
    • Applied
      • Primary: 11:14 – 11:23
      • Replica: 11:24 – 11:32

27. January 2016: Wednesday

Posted: January 28th, 2016 by fcs

LDAP/IdM:

  • Updates: no issues.
  • Accounts: no issues in 190 new accounts.
  • Problems:
    • T&PS notices someone with a 25 character middle name and wants that field limited at 24 characters – due 2/5.

Backups:

  • Save Groups:
    • The usual list of failures
    • dpm1 is still VSS unhappy
    • much of openstack decided to be down/off
  • Clones:
    • COM done.
    • DISK and TAPE continue.
  • Tapes:
    • Reclaimed one (1) for the vaults.

General:

  • Assist with cleanup of departed team member’s permissions
    • footprints
    • entitlements
Contact Us ©2010 The University of Vermont – Burlington, VT 05405 – (802) 656-3131
Skip to toolbar