Jump to content

GitServer: Could not read from remote repository


eAi

Recommended Posts

We've just enabled GitServer for our (moderately large) repository and then tried to clone it, and get this error:

 

git clone git://<hostname>:9419/<repo name>

Cloning into '<repo name>'...

fatal: Could not read from remote repository.

 

Please make sure you have the correct access rights

and the repository exists.

 

The Plastic error log contains this error:

ERROR Git - GitTcpServer caught an error Sequence contains no elements

 

We've tried multiple clients, all with similar results. What are we doing wrong? Do we need to wait for Plastic to process the repository? Can we track the progress of this, if so?

 

Perhaps more critically, we're also noticing the /tmp volume (on linux) completely filling up with .pushed files. These aren't mentioned anywhere in the docs. What are these - and can we move them somewhere else with more space? Until we can do this, we're having to leave the GitServer disabled - which means we can't integrate with TeamCity.

Link to comment
Share on other sites

Hello,

 

We have a small guide at https://www.plasticscm.com/gitserver/

 

If you get an error like this, it means the repo wasn’t yet “indexed for git” so it is not visible yet.

By default, wait 5 minutes. Otherwise edit gitserver.conf and add

...

mapping.interval=30

...

Which means the mappings will be recalculated every 30 seconds. (This applies to changesets created doing checkins or push/pull in Plastic).

 

Regards,

Carlos.

Link to comment
Share on other sites

  • 5 months later...

Hello,

Please check the next link where we explain how to configure it: 

https://www.plasticscm.com/documentation/gitserver/plastic-scm-version-control-gitserver-guide.shtml#ConfiguringGitServer).

# mapping storage - the mappings between git and plastic objects 
# the default path is automatically generated by the server 
storage.baseDirectory=e:\gitserver\mappings

 

Regards,

Carlos.

Link to comment
Share on other sites

Hi calbzam:

 This describes the gitserver behavior under Ubuntu 14.04LTS.    

 It's true that after the gitserver finishes exporting a repo, it will store the results in storage.baseDirectory and clean up /tmp.

 But during the process of initial export, gitserver would still fill up the /tmp directory. I think this might be a problem with hard coding /tmp during initialization and first time export of a repo. The code should probably be edited to make this tunable, because large repos may not fit into a /tmp directory (especially if it an intentionally constrained, separate logical partition).

Link to comment
Share on other sites

Hello Cyan,

I'm sorry but the Plastic SCM server will use the temporal directory of the OS, it can't be changed though a config parameter.

I'm thinking about changing the startup daemon script, maybe you can edit it and export a new value for the tmp and tmpdir environment variables. what do you think?

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...