I get this error when just cloning the mozilla source code repository, can you tell me what the problem is?
or
When cloning via TortoiseHg GUI I get the following error
The remote host forcibly terminated the existing connection
code 255
Related
I'm using Mercurial and somehow rbt tools fail to run rbt diff on the repository because of missing http authorization
below is the error I get
Failed to execute command: [u'hg', u'-q', u'outgoing', u'--template', u'{rev}\\t
{node|short}\\t{branch}\\n', u'default', u'-r', u'.']
abort: http authorization required for http://abc.xyz.com/hg/foo/com.my.repository/
I tried giving the --username and --password, but they are for review board, not for repository. How can i give credentials for Mercurial repository and gain access?
Figured out the issue. Apparently, i need to enable Mercurial Keyring for the repository to allow access to it.
I've been using tortoisehg to work with a repo using ssh and everything is in order. But now i'm trying to clone another repo that uses only https, and I'm welcomed with the following error message:
URLError: [Errno 10061] No connection could be made because the target machine actively refused it
[command returned code 255. . .]
I tried to localized the settings of my current repo, i.e. remove them from global settings, to ...\.hg\hgrc, but i still get the same error when i try to clone.
Any ideas on this?
A bit late response but perhaps its a proxy error...
see:
How to clone a codeplex mercurial repository behind a proxy?
but instead use
[https_proxy]
host = proxy name / ip:port
user = xxxxxxx
passwd = xxxxxxx
I have an internal mercurial web server that is served using IIS, using window security, and another server on my external web server set up the same way.
Developers commit code to the internal server, and teamcity builds from there.
However we are now working on a customer portal on the web site that can list some mercurial information. This connects to the local instance of mercurial (i.e. the one on the external server)
I have installed the mercurial autosync plug-in onto the internal server, with the intention of updating the master copy of the code on the external server, and allowing the website to read it's information from there. Code will never be checked in directly to the external server, all updates will come from the internal server. All repositories are clones of the ones on the external server.
I have run the autosync command in the repositories on the internal server "hg autosync -D" and I have tried it with "hg autosync -D -u username" but when I check the autosync log all I see is this:
------------------------------ 06/08/12 08:54:56 ------------------------------
sync: commit working copy changes
nothing changed
sync: fetch changes from other repository
http authorization required
realm: www.mydomain.co.uk
user: response expected
sync: an error occurred, will retry at next interval
anyone have any idea how to specify the user (and password?) correctly?
You probably need to add credentials to the C:\Users\<username>\mercurial.ini file of the user running Mercurial:
[auth]
mydomain.prefix = mydomain.co.uk
mydomain.username = <username>
mydomain.password = <password>
I am using windows explorer to clone a repository from a folder in a mapped drive into my local working folder. I have never encountered this problem before with any of my previous repositories, but I keep getting an error while the directory is cloned. The error points to a file that is of "unkown format". This is the exact error:
abort: index data/Scripts/tiny_mce/themes/advanced/skins/default/dialog.css.i unknown format 5661!
About half of the repository gets cloned, but it never finishes because of that error half way through. I have used a remote command that supposedly skips over unknown formats (I found it somewhere online), but it doesn't work. This would be the complete command:
hg clone --remotecmd skip-unknown-format --verbose -- Q:\mercurial-repository\east C:\working
Any pointers on how I can skip that one file and/or how I can fix this error?
This is my hg version info:
version 2.4
with Mercurial-2.2.1, Python-2.6.6, PyQt-4.8.6, Qt-4.7.4
Trying to configure Jenkins CI. Currently just running it from the .war (eventual intention as a service). Jenkins is aware of the CVS executable (i.e. will read the version [Concurrent Versions System (CVSNT) 2.0.62.1817 (client/server)]).
The .cvspass is not specified, because they apparently do not play nice with CVSNT (which prefers to keep passwords in the registry.) I've specified the password in the job config by using the :pserver:user:passg#server:/dir pattern for CVSROOT, which I found suggested in some places. Regardless of whether I run using that, or :pserver:userg#server:/dir as the CVSROOT I get the blinking red ball, jenkins stuck with a nearly full progress bar for 2 and a half minutes. It then fails. The console output yells with something like
FATAL: hudson.scm.ChangeLogSet.iterator()Ljava/util/Iterator;
java.lang.AbstractMethodError: hudson.scm.ChangeLogSet.iterator()Ljava/util/Iterator;
at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:282)
at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:279)
at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:596)
at hudson.model.Run.run(Run.java:1400)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:175)
Both CVSROOTs I'm using provide no trouble with TortoiseSVN. I've found some mention of difficult of logging into SVN from jenkins as a service and related user/system issues, but considering I'm running it from the .war I don't think that's the issue.
EDIT:
Interestingly the console log if I use an invalid user or password recognizes such.
cvs [checkout aborted]: authorization failed: server rejected access to /dir for user FOO
FATAL: CVS failed. exit code=1
Finished: FAILURE
which indicates that Hudson is talking to the CVS server and authenticating, but something else goes wrong.
/EDIT
Cheers
Answer to the question found, thanks to rpetti on #jenkins on freenode. Problem was I had switched between Hudson and Jenkins and there were some incompatible configuration files that were mucking things up. Deleting and recreating the home directory solved the problem.
CVSNT 2.0.62.1817 is very very old and has several known security issues. Please upgrade to the latest 2.8.01.