I have set up a Mercurial server on IIS 7.5 on Windows 7 pro following this tutorial
http://stackingcode.com/blog/2011/02/24/running-a-mercurial-server-on-iis-7-5-windows-server-2008-r2
In contrast to the tuturial I use Windwos 7 Pro, Python 2.7 and Mercurial 3.5 and installed a real (not self signed) certificate and got everything up and running with https after applying the helpful answer of roengraft that can be found here (before it always stopped after pushing about 60MB).
IIS 7.5 Mercurial setup ignoring maxAllowedContentLength
BUT: Unfortunately I can only push a bit more than 100MB, I am not able to push a bigger changeset having about 350MB. I always receive Error 500 from the Server. I set all the limits of IIS to max to no avail, they changed nothing. Also all disks have enough space, I tried allowing "Everyone" full access to the repositiories, also to no avail. Now I cannot even checkin anymore and get "502 Bad Gateway" and "500" errors.
Does it make sense to go with linux (its a VM anyway) that hopefully should work better or is there anybody out there (outside the wall) who can help me solving this problem?
Thanks in Advance!
Micha
Like always, shortly after posting the question I find the answer on my own. After I have changed the Python command line to this
C:\Python27\python.exe -u -O -B "%s" "%s"
Not exactly knowing what this does in particular, I am happy as it works like a charm now!
After about transferring 120MB it stopped for quite a while but then did the rest in one go. Perhaps this is due to quite some binaries I have to check in as I don't compile them.
Michael
Related
For the last 3 days I have been trying to figure out how to install node.js. I tried every solution that I found on the internet, like disabling certain components during installation, installing both x86 and x64 etc, none of them worked.
My OS is Windows 10 x64. I tried different versions of node.js and they all return the same error shown in the screenshot below.
I tried installing through the command line and got the log. But I could not find anything useful from the log either. Please help.
The log can be found here: this path : https://drive.google.com/open?id=1OkkK36hlQeBX0xTNuOuilGaNr1u3S55e
MSI (s) (74:88) [20:49:45:955]: Executing op: ActionStart(Name=RegisterEventManifest,,)
MSI (s) (74:88) [20:49:45:961]: Executing op: CustomActionSchedule(Action=RegisterEventManifest,ActionType=3073,Source=BinaryData,Target=CAQuietExec,CustomActionData="wevtutil.exe" im "C:\Program Files\nodejs\node_etw_provider.man")
MSI (s) (74:A0) [20:49:45:969]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI33C1.tmp, Entrypoint: CAQuietExec
CAQuietExec: Error 0xc0000409: Command line returned an error.
This is the relevant part of the log and where the install keels over, noise removed. 0xc0000409 is very, very nasty. STATUS_STACK_BUFFER_OVERRUN is a stack corruption error, triggered by code that protects against viral attacks.
Searching for "nodejs install 0xc0000409" takes you to this bug report, notable from December 2015. This issue has been dogging users for a long time, but they are having trouble finding the root cause. The generic workaround is to disable this install step by disabling the installation of the ETW performance counters.
Which works, but is but a band-aid. I think macario1983's comment points at the real troublemaker. It got a lot of helpful votes in just two days. And points at the kind of viral rootkit that programmer's voluntarily install, the kind that can so easily cause a STATUS_STACK_BUFFER_OVERRUN error with no decent way to identify the code that causes it. Anti-malware has become a cure that is worse than the disease, Avast in particular is a truly awful product and does not belong on a programmer's machine.
So decent advice is to 1: disable the anti-malware product before installing Node. 2: get rid of completely if it is Avast. 3: disable the performance counter registration. 4: try the updated installer, patched 4 days ago.
I disabled the AVG antivirus(version 18.4.3056) but not windows firewall and then i was able to install nodejs.
Possible options to solve this:
1. Removing previous installations traces
If you have previous installations, make sure that they were uninstaled completely. If HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\_V2Providers\{1e2e15d7-3760-470e-8699-b9db5248edd5} record exist in your register, remove it.
2. Disabling Performance Counters
If you don't need Performance counters feature, try to install without it (or maybe even without Event Tracing).
3. Disabling security and giving the full permissions
Clean Temp Folder
Disable your antivirus/firewall for the period of installation.
C:/users/$user/AppData/Local/Temp- Right Click on Temp and go to Properties > select Security Tab > give the user permissions by checking Full Control on permission
Install Node.js
I had today the same problem with Windows 10 64 bit and Node.js 8.11.2: disabling completly Avast just for the time of the installation solved the issue.
I was trying to install Node.js through node-v8.11.2-x64.exe, but it was rolling back every time at the end. The error in the event log was about wevtutil.exe, version 10.0.17134.1
I had the same issue on a Windows 2012R2 server installing node-v8.11.2-x64, and disabled the McAfee anti-virus to no avail. When I went to clean out the TEMP folder as suggested in this thread, I noticed that several files and folders were locked and could not be deleted, so I rebooted the machine (with the anti-virus disabled). After the reboot, I noticed that the locked temp files had been deleted, and I was able to install node.js, including the Performance Counters and Event Tracking options.
I spent one day for that ....Best solutions is download zip example node-v12.16.2-win-x86.zip.
I just installed Winginx on fresh Windows 10 and nginx never start.
In log I have found:
CreateFile() "C:\Winginx/temp/nginx.pid" failed (2: The system cannot find the file specified)
Has anyone met with such problem before?
I found my solution by giving up and used WampDeveloper Pro Trial. Their installation goes through a check list of items to see if it will cause any problem. And the main problem that came out is the Host file is read only. Which is caused by many Firewall or Antispyware software. In my case it was Spybot.
I simply disabled the read only on my host file, and ran it again and it worked.
Although I got Winginx to work, it may not only be the host file causing the issue. It could be many more, but my WampDeveloper Pro Trial helped fix things I guess, it even check if there are other services uses Port 80 and 443 and disabled them for example. So now, my Winginx is working, that I can turn on and off and so is my WampDeveloper Pro trial, that I turn on and off. So I simply turn one of them on when I need it.
I've been fiddeling around with ElmahR for the last two days and was planning to push it to our dev-playground for testing.
However, it doesnt load properly when running on IIS 7.5
I've fired up the deployed solution on 3 different machines with IIS Express without problems.
On IIS 7.5 it gets stuck at "Loading..." or "Sending Command", depending if it is set up as a sub application under default website or as a standalone webapplication.
The used system is Windows Server 2008 r2 sp1, IIS 7.5 .NET 4 application pool integrated mode. (all 3 machines)
I can't find the problem at hand; hope you can help.
Kind regards.
This is not an answer yet, it should be a comment but I cannot comment here :) I'm the author of ElmahR, I was not aware of the issue, last time I tested it on IIS 7.5 was a while ago and I did not have any problem, I'll have to recheck. Right now I'm not at home but I'll have a look at it when back, possibly before next weekend. And thanks for using it :)
UPDATE: I think I solved the problem, I blogged about it here. Basically, there were a couple of javascript bugs:
in one point I was not correctly setting the root of the application
under IE7/8 a better check about the plugins object was needed (the same code was running fine on IE9/Chrome/Firefox/Safari...)
The online repo is up to date, and the sample setup zipped file too.
When I use WebMatrix (the latest version, on Windows 8 RP) to try to connect to an FTP site, it shows an error where files should be shown. I actually have no idea what could be causing this, and I can't find any log file that could help. Screenshot: http://imgur.com/aV7iR
I'm also using IIS 8 to host a local PHP/MySQL site, if that matters
Thanks,
Matthew
I think this might actually be a different issue. There is a bug in WebMatrix RC that causes the remote view to behave badly when connecting to directories with large numbers of files.
We've fixed this now, and it should not repro in our next release. Sorry for any inconveniences this has caused.
Ah, it turned out to be because I had a file called "CFLogo.png" and another file called "cflogo.png" on my server and WebMatrix wasn't able to deal with both of them having essentially the same name :\
I've got hgweb up and running on II7 7 (on windows server 2008). The web interface works, and I can view, pull, and clone the repositories there. But I cannot push, doing so gives me a 502 error right after "searching for changes". Using --debug shows the last few lines as:
sending unbundle command
sending 622 bytes
HTTP Error: 502 (Bad Gateway)
I am using TortoiseHG to push, but the result is the same when using the mercurial command line.
I had followed the tutorial here: http://www.sjmdev.com/blog/post/2011/03/30/setting-mercurial-18-server-iis7-windows-server-2008-r2.aspx to setup hgweb.
Looks like an old question but someone is bound to come across it again. I was close to drawing a black circle on a wall and ... anyhow the issue for us was the way central repository was created. We cloned it from BitBucket while being Remote connected to the machine as local administrator.
The issue was in [Repository].hg folder. You need to set correct permissions on it. Try it with adding Everyone -> Full permissions for test purpose. Please make sure you change this to a dedicated network login or appropriate local account afterwards.
I was seeing the exact same behaviour - even push worked fine with exception of getting a Bad Gateway after all the time. After correct permissions were set the issue was gone.
Thinking about it now, probably the best solution is to add each network login that uses the repo to machine users and then set up access permissions to .hg folder to local users.
Hope it helps someone.
Try using the ISAPI module method instead of the CGI that executes phython.exe as documented here. There's also another related, and possibly duplicate question here as well.
Take a look at the 'Push_ssl' setting in your hgweb.config file.
I was getting the same error (had mine set to '*'), and was able to resolve it by removing the line entirely. Granted, this makes Mercurial somewhat less secure, but it lets me get by the configuration issue (for now) while I investigate properly configuring SSL on the server.
You may also have to review the 'Allow_push' setting in order to get past further errors (or take another look at your authorization).
NOTE: At least in my case, having 'push_ssl = false' wasn't enough as that resulted in further errors (authorization failed).
(Again this is simply a temporary solution until the server can be properly secured.)
It could happen by different reasons, to get more details about the error run
hg push --config ui.usehttp2=true --config ui.http2debuglevel=info
For example, problem may occur because of proxy server or just in case when the Mercurial Web Server "forgets" about repositories it needs to serve: in case if you are using TortoiseHg workbench go to Workbench UI, Repository -> Start Web Server, make sure that your repository is in the list of the served repos.
Try use https instead http in .hg/hgrc, I have resolve this problem for code.google.com.
I had this issue, and the problem ended up being the server running out of disk space.