DigitalOcean: Puma 서비스가 더 이상 systemctl에서 작동하지 않습니다.

DigitalOcean: Puma 서비스가 더 이상 systemctl에서 작동하지 않습니다.

내 DigitalOcean 환경이 뚜렷한 이유 없이 충돌했습니다. 안타깝게도 서비스를 시작할 수 없어 pumaRails 앱이 완전히 실패합니다.

서비스를 시작하는 데 사용하는 명령은 다음과 같습니다.

systemctl start puma

내가 잘 모르는 신비한 오류가 있습니다.

Job for puma.service failed because a configured resource limit was exceeded. See "systemctl status puma.service" and "journalctl -xe" for details.

systemctl status puma.service

생산하다:

● puma.service - Puma HTTP Server
   Loaded: loaded (/etc/systemd/system/puma.service; enabled; vendor preset: enabled)
   Active: inactive (dead) (Result: resources) since Wed 2018-04-11 17:45:20 EDT; 6min ago

sudo journalctl -xe:

Subject: Unit puma.service has failed
Defined-By: systemd
Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Unit puma.service has failed.

Apr 11 17:56:30 app-master sshd[1124]: Invalid user wp from <some ip>
Apr 11 17:56:30 app-master sshd[1124]: input_userauth_request: invalid user wp [preauth]
Apr 11 17:56:30 app-master sshd[1124]: pam_unix(sshd:auth): check pass; user unknown
Apr 11 17:56:30 app-master sshd[1124]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=<some ip>
Apr 11 17:56:32 app-master sshd[1124]: Failed password for invalid user wp from 114.32.120.181 port 39504 ssh2
Apr 11 17:56:33 app-master sshd[1124]: Received disconnect from <some ip> port 39504:11: Normal Shutdown, Thank you for playing [preauth]
Apr 11 17:56:33 app-master sshd[1124]: Disconnected from <some ip> port 39504 [preauth]
Apr 11 17:56:37 app-master sshd[1126]: Connection closed by <some ip> port 49964 [preauth]
Apr 11 17:56:41 app-master sshd[1128]: Did not receive identification string from 103.89.91.78
Apr 11 17:56:48 app-master sshd[1129]: fatal: Unable to negotiate with 103.89.91.78 port 51781: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1 [preauth]
Apr 11 17:56:49 app-master sshd[1131]: Did not receive identification string from 103.89.91.78
Apr 11 17:56:50 app-master sshd[1132]: fatal: Unable to negotiate with 103.89.91.78 port 55251: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1 [preauth]
Apr 11 17:56:53 app-master sshd[1134]: fatal: Unable to negotiate with 103.89.91.78 port 60600: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1 [preauth]
Apr 11 17:56:54 app-master sshd[1136]: Did not receive identification string from 103.89.91.78
Apr 11 17:57:06 app-master sshd[1137]: Invalid user wp from <some ip>
Apr 11 17:57:06 app-master sshd[1137]: input_userauth_request: invalid user wp [preauth]
Apr 11 17:57:06 app-master sshd[1137]: pam_unix(sshd:auth): check pass; user unknown
Apr 11 17:57:06 app-master sshd[1137]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=<some ip>
Apr 11 17:57:08 app-master sshd[1137]: Failed password for invalid user wp from 114.32.120.181 port 41202 ssh2
Apr 11 17:57:08 app-master sshd[1137]: Received disconnect from <some ip>port 41202:11: Normal Shutdown, Thank you for playing [preauth]
Apr 11 17:57:08 app-master sshd[1137]: Disconnected from <some ip> port 41202 [preauth]
Apr 11 17:57:10 app-master sshd[1139]: Connection closed by <some ip> port 34578 [preauth]
Apr 11 17:57:15 app-master sshd[1141]: Did not receive identification string from 103.89.91.78
Apr 11 17:57:42 app-master sshd[1142]: Invalid user wp from <some ip>
Apr 11 17:57:42 app-master sshd[1142]: input_userauth_request: invalid user wp [preauth]
Apr 11 17:57:42 app-master sshd[1142]: pam_unix(sshd:auth): check pass; user unknown
Apr 11 17:57:42 app-master sshd[1142]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=<some ip>
Apr 11 17:57:44 app-master sshd[1142]: Failed password for invalid user wp from 114.32.120.181 port 42864 ssh2
Apr 11 17:57:44 app-master sshd[1142]: Received disconnect from <some ip> port 42864:11: Normal Shutdown, Thank you for playing [preauth]
Apr 11 17:57:44 app-master sshd[1142]: Disconnected from <some ip> port 42864 [preauth]
Apr 11 17:58:11 app-master sshd[1144]: Did not receive identification string from <some ip>
Apr 11 17:58:17 app-master sudo[1147]:   <hidden> : TTY=pts/0 ; PWD=/home/<hidden> ; USER=root ; COMMAND=/bin/journalctl -xe
Apr 11 17:58:17 app-master sudo[1147]: pam_unix(sudo:session): session opened for user root by <hidden>(uid=0)

여기서 문제가 무엇인지 전혀 모르겠습니다. 나는 평생 사용자를 본 적이 없어서 wp그것이 무엇인지조차 모릅니다. 왜 갑자기 DigitalOcean Droplet에서 퓨마를 더 이상 실행할 수 없는지 이해가 되지 않습니다.

답변1

부족한 리소스는 메모리 관련이거나 CPU 관련일 가능성이 높습니다.

DigitalOcean 계정에는 대시보드의 Droplet에 대한 CPU 및 메모리 모니터링이 포함되어 있습니다. 꼭 확인해 보세요. Droplet이 충돌하기 전에 CPU 메모리를 모두 소모했습니까?

Puma에 대한 모든 시스템 관련 리소스 제한을 확인할 수도 있습니다.

 systemctl show puma

출력과의 상호 참조시스템 리소스 제어 지시어에 대한 문서.

마지막으로 저널에서 퓨마에 대한 모든 언급을 검색하십시오.

 journalctl -x | grep puma

어떤 리소스가 고갈되었는지에 대한 단서를 찾을 수 있습니다.

관련 정보