Troubleshooting TFS 2013 - tfs

I have tfs installed locally on my machine. It used to work fine but for a week or so now, it does not work most of the time.
It is not possible to connect from Visual Studio 2013 now using the team menu item. It is able to connect only once in so many tries.
Git Fetch, Git Pull and Git Push commands from Git Bash take a long time to show the login prompts and sometimes does not even working reporting that it could not connect to localhost:8080
Fetch, Push and Pull from Visual Studio work once in a while.
Connecting with the web always works though sometimes slow.
Git Push with Git Bash and Gui of late gives the error below
POST git-receive-pack (8010 bytes)
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
error: RPC failed; result=7, HTTP code = 0
Pushing to http://localhost:8080/tfs/col1/_git/project1
Everything up-to-date
I've read so many articles and now seem to work. Is there a way to troubleshoot TFS to find out where it is coming from so that it can be corrected.

It turned out this had nothing to do with TFS as generally requests that have to do with local host fails most of the time. It may be an issue with the system when it comes to local host. In any case, I disabled IPv6 and it still didn't work.
What worked however was rawcap. I realized that when I run rawCap to monitor 127.0.0.1, all calls were going through successfully. It appears something it did rectified the issue. Hope it helps someone who also had the same issue with localhost.

Watch for -1 statuses in TFS Activity Log (http://localhost:8080/tfs/_oi). Right click -> Show Detail to get the full exception. Also look for errors in the IIS logs.

Related

Jenkins doesn't update GitHub check status sometimes

I'm using Jenkins 2.15 (GitHub plugin 1.29.3) based CI for my GitHub core repo. It works fine, but sometimes Jenkins build doesn't update GitHub check status.
I see nothing relevant into Jenkins log.
Any idea how to debug and hopefully fix this issue?
As I know, check status update is just an http request to the status api: https://developer.github.com/v3/repos/statuses/
I experienced a similar behavior with a database. The client application and the database had no errors. Each one was on a different host.
What I did was, create a bash script in host A to perform a ping to host B.
ping www.host_B.com | while read pong; do echo "$(date): $pong"; done >> /tmp/ping-test-$(date +%F).log
Then, when the sporadic error related to the connection of the database occurred, the log file helped me to detect that the error was related to:
Network issues
Latency issues
Internet service provider issues
In your case, you could perform a simple curl to the status api and compare to the sporadic behavior detected.

Stop GitKraken asking for login credentials

GitKraken has successfully cloned a repository hosted on Team Foundation Server, but on subsequent fetch and push it asks for login information. Even when provided it will ask again, offering no error or explanation. "Remember me" is checked.
Everything works perfectly fine using the cmd.
Note that the issue occurs on a virtual machine. I have tested interacting with the repository on my physical machine using GitKraken - no problem there. However, I have previously experienced the same type of problem with other projects on my physical machine. Seems GitKraken sometimes has problems with TFS, but not sure.
I have tried reinstalling GitKraken, but it didn't resolve the issue. Any ideas on how to fix this?
Edit 2018-01-24 as per #Cece Dongs comment
I am using GitKraken 3.3.3 - recently upgraded, but issue still occurs.
TFS is version 15.117.26714.0 and using the web portal does not give me problems. I login once like normally.
When cloning a GitHub repo everything is working properly. However, when attempting to clone a TFS repo from Visual Studio I get an unauthorized error. (TF30063). I assume it could be related to the Active Directory settings not set up properly because of the Hyper-V setup I am using. Will investigate further and provide more details here.
After using \domain\username instead of just username as login credentials to TFS everything is working.
Using only the username will work on my physical machine as that machine is recognized on the domain, but as the virtual machine is not, the domain is required.

Azure remote debugger from Visual Studio not working

I was able to remotely debug this website before. Now when I try to do it, through VS 2013 Server Explorer (Attach debugger), it is giving me
The following error occurred while launching remote debugging: Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named 'mywebsite.azurewebsites.net'. The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging.
This website has a certificate and it's running over https. The remote debugging is enabled in the Settings with the correct VS version.
I have two other websites on this host and I can attach a debugger to them.
It is driving me crazy, I have googled and tried all the suggested solutions but it just seems that the remote debugger is not responding form Azure.
Even when attaching manually (https://stackoverflow.com/a/35738995/1057052), I still get the same error in return.

Can't clone own github repository, get obscure fatal error

So I made changes to my rails app on my local machine that were never committed and that I decided to discard. Decided to rollback to most recent commit by deleting my rails app and all its files, and then cloning my most recent commit from my github repository. Unfortunately
git clone https://github.com/my_username/rails_app.git
results in the following error that cannot be found by just googling:
Cloning into 'sample_app2'...
fatal: unable to access 'https://github.com/IPX-/sample_app2.git/': SSLRead() return error -9806
I was recently pushing to the repo earlier today, even set up an SSH key for my this laptop, but all to no avail.
Why is git clone not working for my own repository?
Possible error due to low internet connection. This error occurred when you try to connect to server through ssl and net connection drop immediately. Or some time due to frequent disconnection. YOu can find more about this here http://flummox-engineering.blogspot.in/2014/04/sslread-return-error-9806-server.html
Possible duplicate of SSLRead() error using Git in Mavericks OS X 10.9.2
Anyhow, the answer mentioned here is that you download SSL and install.
When you have already set up SSH then why don't you access your repo over SSH?
You can use user.name#github.com:<your-repo> and it will not ask you for password if you have actually set-up SSH properly!
Enjoy!

Getting 502 bad request after deploying Play 2.1.0 app to Cloudbees

I tried to deploy a Play app to Cloudbees (only via push to git repo from which it is built by jenkins), it compiled and should work but I get a "502 Bad Gateway" error when loading the app. There is no error shown in the console only that it answers "502 Bad Gateway" when trying to access it. But that's what I see in the browser, too.
Cloudbees say that there is no other manipulation necessary, just cloning/pulling the ClickStart-Project, making it you application and pushing it back. The Play project works fine locally.
I am very grateful for any help. Please let me know if I need to provide any other information. Thanks a lot!
Edit: It works fine with Heroku only adding a Procfile. I don't get the problem with Cloudbees...
In this case the error is due to the database needing evolutions to be run before it can start:
[warn] play - Run with -DapplyEvolutions.default=true and -DapplyDownEvolutions.default=true if you want to run them automatically (be careful)
Oops, cannot start the server.
#6eg39l651: Database 'default' needs evolution!
You can see the error in your application console:
https://run.cloudbees.com/a/strehlst#app-manage/logs:strehlst/odzh
or via bees app:tail if you have the bees CLI installed.
You can also deploy direct from your desktop if you like:
play dist
bees app:deploy -t play2 dist/yourapp.zip
And it will push direct to your app (if you don't want a continuous deployment pipeline).

Resources