php-fpm进程在Kubernetes中接收SIGKILL信号

时间:2017-10-10 18:14:36

标签: php nginx kubernetes kubernetes-helm

我已经在其中配置了Nginx,PHP和php-fpm创建了ubuntu docker镜像。当我在Docker实例上运行它时工作正常。

但是当我在kubernetes中运行相同的图像时,php-fpm进程收到SIGKILL(9)信号,我们得到502个网关错误。

我猜是kubernetes将SIGKILL信号发送到kubernetes pods。我没有在kubernetes模板中使用任何准备和生动性探测。

感谢任何帮助。提前谢谢。

查找下面的docker文件和php-fpm日志以获取详细信息,

Dockerfile

[supervisord]
nodaemon=true

[program:php-fpm]
command=/usr/sbin/php-fpm5.6 --nodaemonize

[program:nginx]
command=/usr/sbin/nginx
autostart=true
autorestart=true
priority=10
stdout_events_enabled=true
stderr_events_enabled=true
stdout_logfile=/dev/stdout
stdout_logfile_maxbytes=0
stderr_logfile=/dev/stderr

supervisor.conf

[10-Oct-2017 16:52:02] NOTICE: fpm is running, pid 56
[10-Oct-2017 16:52:02] NOTICE: ready to handle connections
[10-Oct-2017 16:52:02] NOTICE: systemd monitor interval set to 10000ms
[10-Oct-2017 16:52:30] WARNING: [pool www] child 57 exited on signal 9 (SIGKILL) after 28.399445 seconds from start
[10-Oct-2017 16:52:30] NOTICE: [pool www] child 61 started
[10-Oct-2017 16:52:38] WARNING: [pool www] child 59 exited on signal 9 (SIGKILL) after 36.796172 seconds from start
[10-Oct-2017 16:52:38] NOTICE: [pool www] child 62 started
[10-Oct-2017 16:53:15] WARNING: [pool www] child 58 exited on signal 9 (SIGKILL) after 73.299127 seconds from start
[10-Oct-2017 16:53:15] NOTICE: [pool www] child 63 started
[10-Oct-2017 17:45:02] WARNING: [pool www] child 62 exited on signal 9 (SIGKILL) after 3143.801344 seconds from start
[10-Oct-2017 17:45:02] NOTICE: [pool www] child 64 started

PHP-fpm.log

2017/10/10 16:53:15 [error] 11#11: *162 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.244.2.49, server: _, request: "GET /admin/index.php?route=common/dashboard&token=V4iXjKHenn2ZOIldfn4pmIHcTIHiFoxk HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "shop9.homesourcesystems.net", referrer: "https://domain_name/admin/"
2017/10/10 17:45:02 [error] 11#11: *166 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.244.2.49, server: _, request: "GET /admin/index.php?route=common/dashboard&token=sFiMAItAgX22BarBfcNNVuyin50ZauIa HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "shop9.homesourcesystems.net", referrer: "https://domain_name/admin/"

Nginx日志

Name:           bumptious-beetle-3107682338-qlvcf
Namespace:      testns
Node:           k8s-agent-1/10.240.0.4
Start Time:     Wed, 11 Oct 2017 09:26:21 +0000
Labels:         app=testapp
                pod-template-hash=3107682338
                release=bumptious-beetle
Annotations:    checksum/config=466a2fbe40164c0f5a10a06e26417c92a47422720e96c4fb51562eb8388d282f
                kubernetes.io/created-by={"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"ReplicaSet","namespace":"testns","name":"bumptious-beetle-3107682338","uid":"3e2745b7-ae66...
Status:         Running
IP:             10.244.0.205
Controllers:    ReplicaSet/bumptious-beetle-3107682338
Containers:
  hstestns:
    Container ID:       docker://31477927d3d0ac1b3f2fe662601d1d65d2a6d1fb442e580f9c1836e921a85f75
    Image:              phpnginx:1.9
    Image ID:           docker-pullable://phpnginx@sha256:7dfb96e283f0802e72249aeb252d3e6290dec00591c442da80bfa4727cef7ca5
    Port:               80/TCP
    State:              Running
      Started:          Wed, 11 Oct 2017 09:26:42 +0000
    Ready:              True
    Restart Count:      0
    Limits:
      cpu:      100m
      memory:   50Mi
    Requests:
      cpu:      10m
      memory:   40Mi
    Environment Variables from:
      bumptious-beetle     ConfigMap       Optional: false
    Environment:                        <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-ptkqw (ro)
Conditions:
  Type          Status
  Initialized   True
  Ready         True
  PodScheduled  True
Volumes:
  default-token-ptkqw:
    Type:       Secret (a volume populated by a Secret)
    SecretName: default-token-ptkqw
    Optional:   false
QoS Class:      Burstable
Node-Selectors: <none>
Tolerations:    <none>
Events:
  FirstSeen     LastSeen        Count   From                            SubObjectPath                   Type            Reason          Message
  ---------     --------        -----   ----                            -------------                   --------        ------          -------
  13m           13m             1       default-scheduler                                               Normal          Scheduled       Successfully assigned bumptious-beetle-3107682338-qlvcf to k8s-agent-1
  13m           13m             1       kubelet, k8s-agent-1   spec.containers{hsecommerce}    Normal          Pulling         pulling image "phpnginx:1.9"
  13m           13m             1       kubelet, k8s-agent-1   spec.containers{hsecommerce}    Normal          Pulled          Successfully pulled image "phpnginx:1.9"
  13m           13m             1       kubelet, k8s-agent-1   spec.containers{hsecommerce}    Normal          Created         Created container with id 31477927d3d0ac1b3f2fe662601d1d65d2a6d1fb442e580f9c1836e921a85f75
  13m           13m             1       kubelet, k8s-agent-1   spec.containers{hsecommerce}    Normal          Started         Started container with id 31477927d3d0ac1b3f2fe662601d1d65d2a6d1fb442e580f9c1836e921a85f75

Pod定义

{{1}}

此致 拉胡

1 个答案:

答案 0 :(得分:1)

考虑到你想在php-fpm管理的内部运行多个PHP进程,你的内存限制非常低。由于此内存限制,您的进程很可能会被终止。我建议将内存限制切换为400Mi并重新检查。