chengying-agent icon indicating copy to clipboard operation
chengying-agent copied to clipboard

EasyAgent is an infrastructure component, applied to manage the life-cycle of services on the remote host.

Results 6 chengying-agent issues
Sort by recently updated
recently updated
newest added

这里有好多接口, 仅仅只是提供了接口指针, 没有实现, 例如: 查询所有的 ```go // 查询所有的代理列表-未实现 func QueryAgentList(ctx context.Context) apibase.Result { return nil } // 查询所有的代理信息-未实现 func GetAgentInfo(ctx context.Context) apibase.Result { return nil } func GetAgentName(ctx context.Context) apibase.Result...

环境:windows 11,go v1.21.1,IDE goland v2023.2.1 已经参考 https://github.com/DTStack/chengying-agent/issues/4 安装protobuf的软件包 在chengying-agent目录下执行make all报错如下: ``` Generating protocol codes ... protoc -I=internal/proto -I=D:\Go_Workspace\chengying-1.1.1\chengying-server\matrix;D:\Go_Workspace\chengying-1.1.1\chengying-server;D:\Go_Workspace\chengying-1.1.1;C:\Users\Administrator\go/src/ -I=D:\Go_Workspace\chengying-1.1.1\chengying-server\matrix;D:\Go_Workspace\chengying-1.1.1\chengying-server;D:\Go_Workspace\chengying-1.1.1;C:\Users\Administrator\go/src/github.com/gogo/protobuf/protobuf/ \ --gogo_out=Mgoogle/protobuf/timestamp.proto=github.com/gogo/protobuf/types,Mgoogle/protobuf/duration.proto=github.com/gogo/protobuf/types,plugins=grpc:internal/proto internal/proto/service.proto D:Go_Workspacechengying-1.1.1chengying-servermatrix: warning: directory does not exist. Missing input...

Generating protocol codes ... protoc -I=internal/proto -I=/src/ -I=/src/github.com/gogo/protobuf/protobuf/ \ --gogo_out=Mgoogle/protobuf/timestamp.proto=github.com/gogo/protobuf/types,Mgoogle/protobuf/duration.proto=github.com/gogo/protobuf/types,plugins=grpc:internal/proto internal/proto/service.proto /src/: warning: directory does not exist. /src/github.com/gogo/protobuf/protobuf/: warning: directory does not exist. github.com/gogo/protobuf/gogoproto/gogo.proto: File not found. service.proto:7:1: Import "github.com/gogo/protobuf/gogoproto/gogo.proto"...

1、sidecar进程信息 2、kill -9 之前 mysql的进程状态如下 : 3、kill -9 4、此时mysql的拉起进程的ppid被根进程1接管 5、过了几分钟,crontab自动把easyagent-sidecar拉起, 此时easyagent-sidecar进程信息 mysql进程信息 **疑问: 1、sidecar启动时如何接管已经运行的服务,mysql启动脚本的ppid从1变更成sidecar的pid? 2、是重新运行mysql启动脚本? 3、mysql的服务进程id变了,是因为重启了mysql?影响正常运行的服务实例吗? **

easyagent-server已启动成功 ![image](https://user-images.githubusercontent.com/30715127/124404805-0d595a00-dd6f-11eb-9726-aa22470c3628.png) 执行quickstart的curl会出现以下报错 ![image](https://user-images.githubusercontent.com/30715127/124404699-a176f180-dd6e-11eb-8181-7b9aa01728f8.png) **请问**install.sidecar.sh**中的**easyagent.tar.gz**这个文件在哪里生成的?能否提供一份,[email protected],Thanks♪(・ω・)ノ**

能否介绍一些使用案例?