[Fwd: Re: 1.3.11 - it works!]

Looks like art's solution worked.  After deleting my current databases 
and re-creating all of them the error that I have has gone away..

-------- Original Message --------
Subject: Re: [Current-server] 1.3.11 - it works!
Date: Fri, 23 Aug 2002 08:39:31 -0700
From: Anthony Mendoza <[email protected]>
Organization: Embrace Networks
To: [email protected]
References: <4063D1C2F4F6A744B205D3120EF950264E7123@atl2msx1> 
<[email protected]> 
<[email protected]>

Also as an FYI,

My 7.2 clients are updating fine...it's for some reason something
related to 7.1.  I'll try Arthur's solution and delete my current
directories and re-create all the databaseses and see if that helps.

Arthur Clune wrote:
 > --On 22/08/02 17:45:18 -0400 Hunter Matthews wrote:
 >
 >> Anthony found that he needed to restart his server.
 >
 >
 > I seem to be having less trouble than anyone else for once.
 >
 > Stopped apahce
 > I rm -rf'd the current_dir, the re-created all the channels
 > Started apache
 >
 > All works (well, ok, I've only tested one client, but it has
 > successfully updated)
 >
 >> Please try recreating your ssl certificates with 1.3.11
 >
 >
 > I had no need to do this (which is good, cause that would be a *lot* of
 > work -
 > I don't admin all the boxes that update from this server)
 >
 > Arthur
 >
 > --
 > Arthur Clune [email protected]
 > We are the sum of the things we pretend to be, so we must be careful
 > who we pretend to be - Kurt Vonnegut
 > _______________________________________________
 > Current-server mailing list
 > [email protected]
 > http://lists.dulug.duke.edu/mailman/listinfo/current-server


-- 
Anthony Mendoza
IT & Customer Support
[email protected]
t: 408-585-5612 / c: 408-314-5038
p: 888-886-7205 / f: 208-247-5501

-- 
Anthony Mendoza
IT & Customer Support
[email protected]
t: 408-585-5612 / c: 408-314-5038
p: 888-886-7205 / f: 208-247-5501