I keep getting this exception when people push to their repositories, it 
says that the push count since gc is 706 ... which is strange because I ran 
the repo_housekeeping script and it told me that it gc'ed this repository.

This is running on a stand-alone server, 2 dual core CPU's (4 cores total) 
with 16 GB of RAM and the repositories are on a md based mirror with 2 SATA 
drives and no other IO on it (MySQL and OS are on a different md backed 
mirror). I moved this off a VMWare based virtual server because of IO 
issues, this server has plenty of IO power.

Is there anything I can do to figure out why these are failing? Where 
should I start looking?

Here are some stats for the repository:

Commits: 3402
Repo size at fresh clone: 53M
Files in repo: 835
Directories: 343

I'm at a loss here. Worst case I will most likely simply modify Grit to set 
the timeout to something longer than 10 seconds and hope that it doesn't 
re-appear for a while.

An exception occured in #<PushProcessor:0x7f211f011980
 @repository=
  #<Repository id: 1, name: "<repo name removed>", project_id: 1, user_id: 
1, created_at: "2011-07-01 00:00:00", updated_at: "2012-08-02 00:00:00", 
parent_id: 1, ready: true, kind: 3, owner_type: "User", owner_id: 1, 
hashed_path: "<removed>", description: nil, last_pushed_at: "2012-08-02 
00:00:00", wiki_permissions: 0, deny_force_pushing: false, 
notify_committers_on_new_merge_request: true, last_gc_at: nil, 
merge_requests_enabled: true, disk_usage: 46292359, push_count_since_gc: 
706>,
 @spec=
  #<PushSpecParser:0x7f211eff8868
   @from_sha=
    #<PushSpecParser::Sha:0x7f211eff8700
     @sha="95e177ae088c5d365d1c7f88e8f8ac7aac50db3b">,
   @ref=
    #<PushSpecParser::Ref:0x7f211eff8480 @name="BUGFIX", @type="heads">,
   @to_sha=
    #<PushSpecParser::Sha:0x7f211eff8520
     @sha="0c1d189d13a38d53e17bc7b80bb68c0a2294d7b4">>,
 @user=
  #<Scrubbed for security purposes>
!

Grit::Git::GitTimeout: Grit::Git::GitTimeout

-- 
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]

Reply via email to