前景提要:根据官方文档搭建步骤1-4步成功无报错。
# -*- coding: utf-8 -*-
from flask import Flask, jsonify, request
from aliyunsdkcore.client import AcsClient
from aliyunsdkcore.auth import credentials
import requests
import json
from aliyunsdkecs.request.v20140526 import DescribeInstancesRequest, DescribeInstanceStatusRequest
app = Flask(__name__)
metaUrl = 'http://100.100.100.200/latest/meta-data/ram/security-credentials/EcsRamRoleTest'
region = 'cn-beijing'
# 获取临时身份凭证
def getStsToken():
tokenResponse = requests.get(metaUrl)
return tokenResponse.json()
# 在app.route装饰器中声明响应的URL和请求方法
@app.route('/ecs/getServerInfo', methods=['GET'])
def getServerInfo():
tokenResult = getStsToken()
accessKeyId = tokenResult['AccessKeyId']
accessSecret = tokenResult['AccessKeySecret']
securityToken = tokenResult['SecurityToken']
credential = credentials.StsTokenCredential(accessKeyId, accessSecret, securityToken)
client = AcsClient(credential=credential, region_id=region)
# GET方式获取请求参数
instanceId = request.args.get("instanceId")
if instanceId is None:
return "Invalid Parameter"
# 查询实例信息
describeInstancesRequest = DescribeInstancesRequest.DescribeInstancesRequest()
describeInstancesRequest.set_InstanceIds([instanceId])
describeInstancesResponse = client.do_action_with_exception(describeInstancesRequest)
# 返回数据为bytes类型,需要将bytes类型转换为str然后反序列化为json对象
describeInstancesResponse = json.loads(str(describeInstancesResponse, 'utf-8'))
print(describeInstancesResponse)
if len(describeInstancesResponse['Instances']['Instance']) == 0:
return jsonify({})
instanceInfo = describeInstancesResponse['Instances']['Instance'][0]
# 查询实例状态
describeInstanceStatusRequest = DescribeInstanceStatusRequest.DescribeInstanceStatusRequest()
describeInstanceStatusRequest.set_InstanceIds([instanceId])
describeInstanceStatusResponse = client.do_action_with_exception(describeInstanceStatusRequest)
describeInstanceStatusResponse = json.loads(str(describeInstanceStatusResponse, 'utf-8'))
instanceStatus = describeInstanceStatusResponse['InstanceStatuses']['InstanceStatus'][0]['Status']
# 封装结果
result = {
# cpu数
'Cpu': instanceInfo['Cpu'],
# 内存大小
'Memory': instanceInfo['Memory'],
# 操作系统名称
'OSName': instanceInfo['OSName'],
# 实例规格
'InstanceType': instanceInfo['InstanceType'],
# 实例公网IP地址
'IpAddress': instanceInfo['PublicIpAddress']['IpAddress'][0],
# 公网出带宽最大值
'InternetMaxBandwidthOut': instanceInfo['InternetMaxBandwidthOut'],
# 实例状态
'instanceStatus': instanceStatus
}
return jsonify(result)
if __name__ == "__main__":
app.run()
[uwsgi]
#uwsgi启动时所使用的地址和端口
socket=127.0.0.1:5000
#指向网站目录
chdir=/data
#python启动程序文件
wsgi-file=get_server_info.py
#python程序内用以启动的application变量名
callable=app
#处理器数
processes=1
#线程数
threads=2
#状态检测地址
stats=127.0.0.1:9191
#保存启动之后主进程的pid
pidfile=uwsgi.pid
#设置uwsgi后台运行,uwsgi.log保存日志信息 自动生成
daemonize=uwsgi.log
而运行到下面这步时出现问题:
使用下面两条命令查看错误日志:
cat /var/log/nginx/error.log
cat /var/log/nginx/access.log
# 另外若想用其他方法查看,还可使用下面的代码:
cat /var/log/nginx/error.log
# 使用tail命令查看最后几行日志:
tail /var/log/nginx/error.log
# 如果你想实时查看日志,可以使用tail命令的-f参数:
tail -f /var/log/nginx/error.log
# 这些命令可以帮助你查看Nginx的错误日志,从而找到导致服务未配置成功的具体问题。
检查发现三条问题:
1."/usr/share/nginx/html/favicon.ico"文件不存在导致的404错误:
2024/01/11 14:10:58 [error] 45689#0: *2 open() "/usr/share/nginx/html/favicon.ico" failed (2: No such file or directory), client: 212.87.193.24, server: _, request: "GET /favicon.ico HTTP/1.1", host: "8.134.57.155", referrer: "http://8.xxx.xx.xxx/"
2."/ecs/getServerInfo"返回500错误:
127.0.0.1 - - [11/Jan/2024:14:23:11 +0800] "GET /ecs/getServerInfo HTTP/1.1" 500 290 "-" "curl/7.61.1" "-"
3.试图访问 "/ecs/var/log/nginx/error.log" 时返回404错误:
127.0.0.1 - - [11/Jan/2024:14:35:34 +0800] "GET /ecs/var/log/nginx/error.log HTTP/1.1" 404 232 "-" "curl/7.61.1" "-"
针对上述三个问题,可以采取以下解决方法:
-
favicon.ico文件丢失导致404错误:如果你的网站不需要favicon.ico,可以通过在Nginx配置中禁用它来解决。在Nginx配置文件中找到相关的
location
指令,添加如下配置:location = /favicon.ico { access_log off; log_not_found off; }
,然后重新加载Nginx配置。 -
/ecs/getServerInfo返回500错误:这可能是由于后端应用程序的错误导致的。你需要检查后端应用程序的日志,查找导致500错误的具体原因,并进行相应的修复。
-
访问/ecs/var/log/nginx/error.log返回404错误:这看起来像是一个URL路径配置错误。你需要检查Nginx配置文件,确保URL路径的映射是正确的。如果/ecs/var/log/nginx/error.log确实是一个存在的文件,那么你需要修改Nginx的配置来允许访问该文件。