我有一个已经运行好几年的AWS EC2实例。 我有一个“letsencrypt”证书,我尝试使用certbot-auto脚本进行扩展。 脚本在安装/更新'cryptography'时卡住了,几分钟后,我从ssh得到'broken pipe'消息。 这是当时发生的事情:
Collecting certbot-apache==0.15.0 (from -r /tmp/tmp.RYkFrIBj5R/letsencrypt-auto-requirements.txt (line 184)) Downloading certbot_apache-0.15.0-py2.py3-none-any.whl (135kB) 100% |████████████████████████████████| 139kB 28.3MB/s Collecting certbot-nginx==0.15.0 (from -r /tmp/tmp.RYkFrIBj5R/letsencrypt-auto-requirements.txt (line 187)) Downloading certbot_nginx-0.15.0-py2.py3-none-any.whl (65kB) 100% |████████████████████████████████| 65kB 24.6MB/s Requirement already satisfied (use --upgrade to upgrade): setuptools>=11.3 in /root/.local/share/letsencrypt/lib/python2.7/site-packages (from cryptography==1.8.2->-r /tmp/tmp.RYkFrIBj5R/letsencrypt-auto-requirements.txt (line 45)) Installing collected packages: argparse, pycparser, asn1crypto, cffi, ConfigArgParse, six, configobj, idna, pyparsing, packaging, enum34, ipaddress, cryptography, funcsigs, linecache2, ordereddict, parsedatetime, pbr, pyOpenSSL, pytz, pyRFC3339, python-augeas, requests, traceback2, unittest2, zope.interface, zope.event, zope.component, mock, acme, certbot, letsencrypt, certbot-apache, certbot-nginx Running setup.py install for pycparser ... done Running setup.py install for cffi ... done Running setup.py install for ConfigArgParse ... done Running setup.py install for configobj ... done Running setup.py install for enum34 ... done Running setup.py install for cryptography ... \packet_write_wait: Connection to xx.xx.xxx.xxx port 22: Broken pipe
我无法重新连接,因此我重启了机器(通过AWS控制台),然后查看了系统日志(再次通过AWS控制台)。 日志的尾部显示了这一点:
Starting sshd: [ OK ] ntpdate: Synchronizing with time server: [ OK ] Starting ntpd: [ OK ] Starting S64mysqld: [ OK ] Starting sendmail: [ OK ] Starting sm-client: [ OK ] Starting tomcat7: [ OK ] Starting httpd: [ OK ] Starting crond: [ OK ] Starting atd: [ OK ] Starting cloud-init: Cloud-init v. 0.7.6 running 'modules:final' at Wed, 28 Jun 2017 17:33:48 +0000. Up 12.76 seconds. Cloud-init v. 0.7.6 finished at Wed, 28 Jun 2017 17:33:48 +0000. Datasource DataSourceEc2. Up 12.92 seconds starting DenyHosts: /usr/bin/env python /usr/local/bin/denyhosts.py --daemon --config=/usr/share/denyhosts/denyhosts.cfg Amazon Linux AMI release 2017.03 Kernel 4.9.27-14.31.amzn1.x86_64 on an x86_64 myserver login:
为什么login提示? 看“实例屏幕截图”也显示login提示。 我有另一个实例,即正常运行,并没有显示任何login提示,所以我不认为这是正常的,可能是我的问题的原因! 任何想法如何我可以解决这个问题?
谢谢!
所有Linux服务器在任何引导序列结束时显示login提示。 你可以运行一个现场实例来确认这一点。
当我这样做时,系统日志是一个黑色的矩形,但实例屏幕截图显示了非常相似的东西。