Skip Menu | Logged in as guest | Logout
 
Ticket metadata
Id: 5083
Status: open
Priority: -3/0
Queue: vdt-support

Fixed in: (no value)
Fix scheduled: CUR

Owner: Scot Kronenfeld
Requestors: Alain Roy
Cc:
AdminCc:

New reminder:

Created: Mon Mar 23 17:36:11 2009
Starts: Not set
Started: Not set
Last Contact: Thu Apr 02 09:48:35 2009
Due: Not set
Closed: Not set
Updated: Sun Aug 23 14:44:26 2009 by kronenfe



History Brief headersFull headers
Subject: Bestman not properly preserving configuration?
Date: Mon, 23 Mar 2009 17:35:45 -0500
To: Alain Roy via RT <vdt-support@OPENSCIENCEGRID.ORG>
From: Alain Roy <roy@cs.wisc.edu>
Download (untitled) / with headers
text/plain 1.3k
We've had a complaint about Bestman not properly preserving
configuration. We should investigate and fix any problems that exist.

-alain

Begin forwarded message:
> From: Peter Doherty <doherty@crystal.harvard.edu>
> Date: March 20, 2009 10:57:25 AM CDT
> To: VDT-DISCUSS@OPENSCIENCEGRID.ORG
> Subject: Recent VDT update broke my SE
>
> Hi
>
> I recently did a VDT update on a cluster that admittedly was behind
> in it's version. I updated from 1.10.1k to the current version of
> 1.10.1u.
>
> Most things ran smoothly, but Bestman had some issues. After the
> update, Bestman had ignored the previous configuration, and was
> running with just the basic settings, the bestman.rc file had been
> overwritten.
> And secondly, the osg-rsv probes were no longer probing the SRM.
> I had to restore the bestman.rc file, and reconfigure the osg-rsv
> probes (including the settings for the directory paths for the SE,
> and the port is was running on)
>
> I'm wondering if something in my config.ini is incorrect that caused
> these two packages to act like there wasn't an SE installed, and
> just proceed as such.
>
> Everything is running okay now, but I'd like to figure out what
> happened so that when the next update comes out, I don't have to go
> through all the steps it took to get it running again.
>
> Thanks,
> Peter
Download (untitled) / with headers
text/plain 236b
#5083
- Fixed some problems in how the conf directory is preserved.
- Make a backup copy of bestman.rc if it exists before we call Bestman's
configure script. This can be used to revert back to previous
settings
after an update.
Subject: [vdt-support #5083] SVN commit, rev 8992
To: vdt-support@cs.wisc.edu
From: kronenfe@cs.wisc.edu
Download (untitled) / with headers
text/plain 285b
Commit comment:
Tim pointed out that when preserving the bestman.rc file, "cp -p" should be used
instead of just "cp"


Changed files:
U vdt/branches/vdt-1.10.1-gums-prima/Configure-Bestman/vdt/setup/configure_bestman

To generate a diff:
svn diff -c 8992 file:///p/vdt/workspace/svn