I'm planning on doing this today. Sorry for asking this again.
Can anyone provide quick steps for wiping the fossology database, and then
essentially doing a re-install/initialize either automated with postinstall
script or manually so I can add new agents into my cluster? I ran a test
with server and 3 agents and looks good, now would like to include remaining
2 agents.
Matt or anyone,
Do you mind telling me quick steps in wiping database to start over in
regards to my question about resetting up more agents (Hosts.conf). Since
we're still sort of testing this, it's pretty easy to redo at the moment.
Wiping directories well that's easy, but how would I be able to accomplish
removing the fossology database and in a sense doing a re-install to reset
this up?
I would imagine something like:
1. delete directories,
2. remove fossology database
3. Creating or initializing fossology database or doing some re-install that
will perform the database portion for you
I have decent IT admin skills but not so much on the dba (database) side.
-Regards,
Gibran
On Sat, Nov 28, 2009 at 12:43 AM, Furosh One wrote:
> Matt,
> Do you mind telling me quick steps in wiping database to start over in
> regards to my question about resetting up more agents (Hosts.conf). Since
> we're still sort of testing this, it's pretty easy to redo at the moment.
>
> Wiping directories well that's easy, but how would I be able to accomplish
> removing the fossology database and in a sense doing a re-install to reset
> this up?
>
> I would imagine something like:
> 1. delete directories,
> 2. remove fossology database
> 3. Creating or initializing fossology database or doing some re-install
> that will perform the database portion for you
>
>
> I have decent IT admin skills but not so much on the dba (database) side.
> -Regards,
> Gibran
> On Wed, Nov 25, 2009 at 5:07 PM, Matt Taggart wrote:
>
>> > What are the ramifications if I did something like change Hosts.conf
>> from
>> > clear1 * 00 54
>> > clear2 * 55 aa
>> > clear3 * ab ff
>> >
>> > to:
>> > clear1 * 00 32
>> > clear2 * 33 65
>> > clear3 * 66 99
>> > clear4 * 9a cc
>> > clear6 * cd ff
>> >
>> > Can I wipe the existing directories to allow it to create the new ones
>> in
>> > new_Hosts.conf?
>>
>> Well anything in those old dirs is still referenced in the database and if
>> you tried to browse it via the ui it would break. If you are willing to
>> throw away any processing you've done, you could delete the repo and
>> database and start over.
>> > Does the scheduler or DB simply just look at the Hosts.conf file?
>>
>> When trying to determine where to unpack a file, or where an already
>> unpacked file resides, it reads down the Hosts.conf file until it gets a
>> match. If you start adjusting a Hosts.conf file on a cluster that already
>> has stuff in it, you better move the repo dirs around to match or it will
>> get really confused.
>>
>> > Earlier
>> > today I saw an error where it seemed to fail when clear1 was trying to
>> find
>> > something in a directory that would've been in clear3 according to
>> > Hosts.conf.
>> > Clear1 was trying to do something in files/bf/ee/20/ but failed.
>>
>> Did you maybe make changes to Hosts.conf after there was data in the repo
>> that would have caused this? Note it's OK for agents to be accessing
>> things that are stored on other agents, Hosts.conf helps them determine
>> where to find things. But if it's failing then something is wrong.
>>
>> > I can't find the log for this, i know you need this so this is why I'm
>> > asking if I can simply change the Hosts.conf file and expect it to
>> > locate/setup these directories on its own.
>>
>> Not for existing stuff, but all new stuff will go to the right place.
>>
>> --
>> Matt Taggart
>> tagg...@fossology.org
>>
>>
>>
>
___
fossology mailing list
fossology@fossology.org
http://fossology.org/mailman/listinfo/fossology
