Azure Agent.Listener-配置挂起 [英] Azure Agent.Listener -Configure Hangs

问题描述

我有一个asp.net核心网站，我想使用devops(VSTS)管道将其部署到本地IIS服务器上.

I have an asp.net core website that I'd like to deploy to an on-prem IIS server using devops (VSTS) pipeline.

构建管道可以正常工作，但是在配置发布管道时遇到了问题.

The build pipeline works fine but I've hit a problem when configuring the release pipeline.

遵循的过程:

1. 创建新的发布管道-选择"IIS网站部署"作为模板
2. 在部署组作业"刀片上，有一个下拉列表，需要选择部署组".
3. 单击此下拉菜单右侧的齿轮图标，然后创建一个名为"Integration-Dev"的新部署组.我的理解是，生成的PowerShell脚本必须在部署组内的每个目标服务器上运行吗?
4. 创建具有所需部署组访问权限的PAT令牌
5. 登录到我要将网站发布到的本地IIS服务器(新部署组的成员).
6. 在管理员提升的Powershell会话中，从部署组" devops页面运行PowerShell脚本
7. 提示输入PAT令牌
8. 挂了好几分钟
9. 出现以下错误消息: 发送请求时发生错误.连接失败.

1. Create new Release Pipeline - selected "IIS website deployment" as the template
2. On the "Deployment group job" blade there's a drop-down that requires selection of a "Deployment group".
3. Clicked the cogs icon to the right of this drop-down and created a new deployment group called "Integration-Dev". My understanding is that the generated PowerShell script must be run on each target server within the deployment group?
4. Created a PAT token with the required deployment group access
5. Logged onto the on-prem IIS server that I want to release the website to (the member of the new deployment group).
6. Ran the PowerShell script from the "Deploment groups" devops page in an Admin elevated Powershell session
7. Prompted to enter the PAT token
8. Hangs for many minutes
9. Following error message presented: An error occurred while sending the request. Failed to connect.

我能够在浏览器会话中从目标服务器浏览到devops站点( https://companydomain.visualstudio .com )

I am able to browse to the devops site from the target server within a browser session (https://companydomain.visualstudio.com)

我是否已正确理解需要在每个目标服务器上安装代理? 任何想法为什么它无法连接?我猜这是一些公司代理/防火墙问题，但我不知道如何访问任何诊断或日志.我本以为通过443访问.visualstudio.com就足够了吗?

Have I understood correctly that the agent needs to be installed on each target server? Any ideas why it's failing to connect? I guess it's some corporate proxy / firewall issue but I don't know how to access any diags or logs. I would have thought access to .visualstudio.com over 443 would be good enough?

推荐答案

我遇到了相同的问题. 带有最新修补程序的Vanilla Azure Windows 2019 VM. Powershell脚本下载代理zip，然后将其解压缩，但是在运行Config.cmd连接到服务器"时只是挂起 在取消之前，我将其放置了30分钟.

I encountered the same issue. Vanilla Azure Windows 2019 VM with latest patches. Powershell script downloads the agent zip, extracts it, but then just hangs when running Config.cmd "connecting to the server" I left it for 30 min before cancelling.

花了几个小时之后，我最终尝试通过正常的命令提示符(以管理员身份)运行Config.cmd

After spending a couple of hours on this I eventually tried to just run Config.cmd via normal Command Prompt (As Admin)

这对我有用，并且已正确注册为服务.

That worked for me and it registered as a service correctly.

我想可能有一些关于Powershell和连接性的默认系统策略.

I suppose there may be some default system policy around powershell and connectivity.

谢谢， 布鲁斯VS

这篇关于Azure Agent.Listener-配置挂起的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！