I'm curious as well if the problem exists in 4.0.x or just 4.1.x? I'm
not seeing it and the one's I've seen respond have been 4.1.x?
Thanks, Howard
-----Original Message-----
From: Cisco Clean Access Users and Administrators
[mailto:[log in to unmask]] On Behalf Of Mike King
Sent: Tuesday, April 24, 2007 14:57
To: [log in to unmask]
Subject: Re: Slow Login to Clean Access Manager
Is the vacuum fixing the problem (is it the fix)?
Or is it just hiding the problem.
I'm still curious why 4 or 5 disparate customers all report "slowness"
at 10 am the same day.
Mike
On 4/24/07, Jackie Cheng (jaccheng) <[log in to unmask]> wrote:
>
>
> Bruce,
>
> Good question. I would recommend to run the following commands, which
does
> not require to stop perfigo service, when the system is under light
load as
> preventive maintenance. This could apply to HA CAM as well. You can
run
> these commands on both active and standby CAMs.
>
> 1. su -l postgres
> 2. vacuumdb -h 127.0.0.1 -a -f
>
> We are about to release 4.1.1 which will address this issue. After
upgrading
> to 4.1.1, the database will automatically vacuum itself without
external
> instruction. We are planning a 4.0 release which will include similar
> enhancement as well.
>
> A daily cron job would be a good workaround for now as well.
>
> Sorry for the inconvenience.
>
> Thanks,
>
>
>
> --Jackie
>
> ________________________________
> From: Cisco Clean Access Users and Administrators
> [mailto:[log in to unmask]] On Behalf Of Osborne, Bruce
W. (NS)
> Sent: Tuesday, April 24, 2007 4:45 AM
>
> To: [log in to unmask]
> Subject: Re: Slow Login to Clean Access Manager
>
>
>
>
>
> Jackie,
>
>
>
> Do you recommend that 4.0.x users do this regularly during a
maintenance
> window as preventive maintenance of the database?
>
>
>
> Bruce Osborne
>
> Liberty University
>
>
>
>
>
> From: Cisco Clean Access Users and Administrators
> [mailto:[log in to unmask]] On Behalf Of Jackie Cheng
> (jaccheng)
> Sent: Monday, April 23, 2007 5:06 PM
> To: [log in to unmask]
> Subject: Re: [CLEANACCESS] Slow Login to Clean Access Manager
>
>
>
> Sorry for the late response.
>
>
>
> The slowness is very likely due to the postgres database. The commands
> posted by Josh should fix the slowness introduced by postgres.
>
>
>
> Can you please confirm that you are seeing this on 4.0.x releases
only?
>
>
>
> Thanks,
>
> --Jackie
>
>
> ________________________________
>
>
> From: Cisco Clean Access Users and Administrators
> [mailto:[log in to unmask]] On Behalf Of Josh Hartranft
> Sent: Monday, April 23, 2007 10:41 AM
> To: [log in to unmask]
> Subject: Re: Slow Login to Clean Access Manager
>
> We too have had problems for a while now. We opened a TAC ticket with
Cisco
> and they recommended a rebuild also. I was waiting until the end of
the
> semester to do the rebuild when I was recommended to run the vaccuumdb
> utility in postgres. Since I did that (last Thursday 4/19) things
have been
> running much faster. Here is the procedure that was recommended.
>
>
>
>
> This will remove stale entries in the database. Perform this during a
> maintenance window. It should not take long, anywhere from 1-15
minutes.
>
>
>
>
> 1. service perfigo stop
>
>
> 2. su -l postgres
>
>
> 3. vacuumdb -h 127.0.0.1 -a -f
>
>
> 4. ctl d (or exit)
>
>
> 5. service postgresql restart
>
>
> 6. service perfigo start
>
>
>
>
>
> Josh Hartranft
>
>
> Manager - Student Tech
>
>
> Millersville University
>
>
> [log in to unmask]
>
>
> 717.871.5889
>
>
>
>
>
>
>
>
>
>
>
>
> On Apr 23, 2007, at 11:13 AM, King, Michael wrote:
>
>
>
>
>
>
> Over the past few weeks, it's been taking longer and longer to get
into
>
>
> my CAM.
>
>
>
>
>
> Right now, I'm at 5 minutes, and I'm still waiting for it to draw the
>
>
> login screen. (It prompted me for the Cert)
>
>
>
>
>
> It's taken me 2 minutes to get to the SSH prompt to come up. (and
each
>
>
> line is like 1 minute. 1 minute for user, 1 minute for password, etc)
>
>
>
>
>
> Anyone else experienced this?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
|