CLEANACCESS Archives

April 2007

CLEANACCESS@LISTSERV.MIAMIOH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Simon Bell <[log in to unmask]>
Reply To:
Cisco Clean Access Users and Administrators <[log in to unmask]>
Date:
Tue, 24 Apr 2007 13:17:07 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (84 lines)
We're running 4.1.0.2 and had to run the vacuumdb command today. All of a sudden we started getting lots of time out calls with error 12002. Ran the script, took about 10min restarted and everything seems to be fixed.

Thanks Josh for the post.

Simon

>>> 
From: 	"Jackie Cheng (jaccheng)" <[log in to unmask]>
To:	<[log in to unmask]>
Date: 	4/23/2007 5:08 PM
Subject: 	Re: 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?

ATOM RSS1 RSS2