主页 / server / 问题

问题[rkt](server)

Martin Hope
Darakir
Asked: 2016-12-01 02:46:10 +0800 CST
  • -1

我正在尝试在 rkt 中设置一个 LEMP 堆栈（使用 Docker 文件），所以我使用 Supervisord 让所有东西都在同一个容器中运行。当我单独构建和启动 Mariadb 容器时，它工作正常。只要我尝试通过 Supervisord 运行它，MariaDB 就会立即退出。我究竟做错了什么？

我也想将 Supervisord 用于其他事情，所以我每次运行它时都会发送它： RUN printf "\n[program:mysqld]\ncommand=sleep 5; mysqld_safe --skip-syslog\nstartretries=10\n" >> /etc/supervisor/conf.d/supervisord.conf

我为测试目的添加了 Sleep 5 和 startretries。

错误日志如下所示：

161130  9:32:25 [Note] InnoDB: Using mutexes to ref count buffer pool pages
161130  9:32:25 [Note] InnoDB: The InnoDB memory heap is disabled
161130  9:32:25 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
161130  9:32:25 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
161130  9:32:25 [Note] InnoDB: Compressed tables use zlib 1.2.8
161130  9:32:25 [Note] InnoDB: Using Linux native AIO
161130  9:32:25 [Note] InnoDB: Using CPU crc32 instructions
161130  9:32:25 [Note] InnoDB: Initializing buffer pool, size = 128.0M
161130  9:32:25 [Note] InnoDB: Completed initialization of buffer pool
161130  9:32:25 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
161130  9:32:25 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
161130  9:32:25 [Note] InnoDB: Database physically writes the file full: wait...
161130  9:32:25 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
161130  9:32:25 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
161130  9:32:26 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
161130  9:32:26 [Warning] InnoDB: New log files created, LSN=45781
161130  9:32:26 [Note] InnoDB: Doublewrite buffer not found: creating new
161130  9:32:26 [Note] InnoDB: Doublewrite buffer created
161130  9:32:26 [Note] InnoDB: 128 rollback segment(s) are active.
161130  9:32:26 [Warning] InnoDB: Creating foreign key constraint system tables.
161130  9:32:26 [Note] InnoDB: Foreign key constraint system tables created
161130  9:32:26 [Note] InnoDB: Creating tablespace and datafile system tables.
161130  9:32:26 [Note] InnoDB: Tablespace and datafile system tables created.
161130  9:32:26 [Note] InnoDB: Creating zip_dict and zip_dict_cols system tables.
161130  9:32:26 [Note] InnoDB: zip_dict and zip_dict_cols system tables created.
161130  9:32:26 [Note] InnoDB: Waiting for purge to start
161130  9:32:26 [Note] InnoDB:  Percona XtraDB (link removed) 5.6.32-79.0 started; log sequence number 0

[这里有很多重复]

161130  9:32:44 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
161130  9:32:45 [Note] InnoDB: Shutdown completed; log sequence number         1623609
161130  9:32:45 [Note] InnoDB: Using mutexes to ref count buffer pool pages
161130  9:32:45 [Note] InnoDB: The InnoDB memory heap is disabled
161130  9:32:45 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
161130  9:32:45 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
161130  9:32:45 [Note] InnoDB: Compressed tables use zlib 1.2.8
161130  9:32:45 [Note] InnoDB: Using Linux native AIO
161130  9:32:45 [Note] InnoDB: Using CPU crc32 instructions
161130  9:32:45 [Note] InnoDB: Initializing buffer pool, size = 128.0M
161130  9:32:45 [Note] InnoDB: Completed initialization of buffer pool
161130  9:32:45 [Note] InnoDB: Highest supported file format is Barracuda.
161130  9:32:45 [Note] InnoDB: 128 rollback segment(s) are active.
161130  9:32:45 [Note] InnoDB: Waiting for purge to start
161130  9:32:46 [Note] InnoDB:  Percona XtraDB (link removed) 5.6.32-79.0 started; log sequence number 1623609
161130  9:32:46 [Note] Plugin 'FEEDBACK' is disabled.
161130  9:32:46 [Note] InnoDB: FTS optimize thread exiting.
161130  9:32:46 [Note] InnoDB: Starting shutdown...
161130  9:32:47 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
161130  9:32:48 [Note] InnoDB: Shutdown completed; log sequence number 1623619

没有一个错误，它只是开始关闭。

想法？

docker mariadb supervisord rkt
Martin Hope
ufk
Asked: 2016-09-15 11:50:17 +0800 CST
  • 1

我有两台coreos stable v1122.2.0机器，每台都配置了tls的etcd2。

我使用https://github.com/coreos/etcd/tree/master/hack/tls-setup创建了证书。

现在我正在尝试配置 calico-node 以使用 rkt 在我的 coreos 主节点上运行。

我在 cloud-config 配置中有以下内容：

write_files:
 - path: "/etc/kubernetes/cni/net.d/10-calico.conf"
   content: |
     {
     "name": "calico",
     "type": "flannel",
     "delegate": {
         "type": "calico",
         "etcd_endpoints": "https://10.79.218.2:2379,https://10.79.218.3:2379",
         "log_level": "none",
         "log_level_stderr": "info",
         "hostname": "10.79.218.2",
         "policy": {
             "type": "k8s",
             "k8s_api_root": "http://127.0.0.1:8080/api/v1/"
             }
         }
     }
 - path: "/etc/kubernetes/manifests/policy-controller.yaml"
   content: |
    apiVersion: v1
     kind: Pod
     metadata:
       name: calico-policy-controller
       namespace: calico-system
     spec:
       hostNetwork: true
       containers:
         # The Calico policy controller.
         - name: k8s-policy-controller
           image: calico/kube-policy-controller:v0.2.0
           env:
             - name: ETCD_ENDPOINTS
               value: "https://10.79.218.2:2379,https://10.79.218.3:2379"
             - name: K8S_API
               value: "http://127.0.0.1:8080"
             - name: LEADER_ELECTION
               value: "true"
         # Leader election container used by the policy controller.
         - name: leader-elector
           image: quay.io/calico/leader-elector:v0.1.0
           imagePullPolicy: IfNotPresent
           args:
             - "--election=calico-policy-election"
             - "--election-namespace=calico-system"
             - "--http=127.0.0.1:4040"
...
units:
 - name: calico-node.service
   enable: true
   command: start
   content: |
    [Unit]
    Description=Calico per-host agent
    Requires=network-online.target
    After=network-online.target

    [Service]
    Slice=machine.slice
    Environment=CALICO_DISABLE_FILE_LOGGING=true
    Environment=HOSTNAME=10.79.218.2
    Environment=IP=10.79.218.2
    Environment=FELIX_FELIXHOSTNAME=10.79.218.2
    Environment=CALICO_NETWORKING=false
    Environment=NO_DEFAULT_POOLS=true
    Environment=ETCD_ENDPOINTS=https://10.79.218.2:2379,https://10.79.218.3:2379
    ExecStart=/usr/bin/rkt run --inherit-env --stage1-from-dir=stage1-fly.aci \
   --volume=modules,kind=host,source=/lib/modules,readOnly=false \
   --mount=volume=modules,target=/lib/modules \
   --trust-keys-from-https quay.io/calico/node:v0.19.0

   KillMode=mixed
   Restart=always
   TimeoutStartSec=0

   [Install]
   WantedBy=multi-user.target

请忽略空格缩进..我认为我没有正确复制/粘贴它:)

当我尝试启动 calico-node 服务时，出现以下错误：

Sep 14 05:45:17 localhost systemd[1]: Started Calico per-host agent.
Sep 14 05:45:17 localhost rkt[1644]: image: using image from file /usr/lib64/rkt/stage1-images/stage1-fly.aci
Sep 14 05:45:18 localhost rkt[1644]: image: using image from local store for image name quay.io/calico/node:v0.19.0
Sep 14 05:45:25 localhost rkt[1644]: Traceback (most recent call last):
Sep 14 05:45:25 localhost rkt[1644]:   File "startup.py", line 292, in <module>
Sep 14 05:45:25 localhost rkt[1644]:     client = IPAMClient()
Sep 14 05:45:25 localhost rkt[1644]:   File "/usr/lib/python2.7/site-packages/pycalico/datastore.py", line 228, in __init__
Sep 14 05:45:25 localhost rkt[1644]:     "%s" % (ETCD_CA_CERT_FILE_ENV, etcd_ca))
Sep 14 05:45:25 localhost rkt[1644]: pycalico.datastore_errors.DataStoreError: Invalid ETCD_CA_CERT_FILE. Certificate Authority cert is required and m
Sep 14 05:45:25 localhost rkt[1644]: Calico node failed to start
Sep 14 05:45:25 localhost systemd[1]: calico-node.service: Main process exited, code=exited, status=1/FAILURE
Sep 14 05:45:25 localhost systemd[1]: calico-node.service: Unit entered failed state.
Sep 14 05:45:25 localhost systemd[1]: calico-node.service: Failed with result 'exit-code'.
Sep 14 05:45:25 localhost systemd[1]: calico-node.service: Service hold-off time over, scheduling restart.
Sep 14 05:45:25 localhost systemd[1]: Stopped Calico per-host agent.
Sep 14 05:45:25 localhost systemd[1]: Started Calico per-host agent.
Sep 14 05:45:25 localhost rkt[1714]: image: using image from file /usr/lib64/rkt/stage1-images/stage1-fly.aci
Sep 14 05:45:26 localhost rkt[1714]: image: using image from local store for image name quay.io/calico/node:v0.19.0
Sep 14 05:45:28 localhost rkt[1714]: Traceback (most recent call last):
Sep 14 05:45:28 localhost rkt[1714]:   File "startup.py", line 292, in <module>
Sep 14 05:45:28 localhost rkt[1714]:     client = IPAMClient()
Sep 14 05:45:28 localhost rkt[1714]:   File "/usr/lib/python2.7/site-packages/pycalico/datastore.py", line 228, in __init__
Sep 14 05:45:28 localhost rkt[1714]:     "%s" % (ETCD_CA_CERT_FILE_ENV, etcd_ca))
Sep 14 05:45:28 localhost rkt[1714]: pycalico.datastore_errors.DataStoreError: Invalid ETCD_CA_CERT_FILE. Certificate Authority cert is required and m

第 2-25 行

所以我明白了Invalid ETCD_CA_CERT_FILE.。我并没有真正向 calico 指定要使用的键..所以我想我缺少一些配置。

我在 /etc/ssl/etcd 有以下等相关的键

8 -rw-------. 1 etcd etcd 1050 Sep 14 05:45 ca.pem
8 -rw-------. 1 etcd etcd  289 Sep 14 05:45 etcd1-key.pem
8 -rw-------. 1 etcd etcd 1058 Sep 14 05:45 etcd1.pem
8 -rw-------. 1 etcd etcd  227 Sep 12 03:49 server1-key.pem
8 -rw-------. 1 etcd etcd  822 Sep 12 03:49 server1.pem

我尝试添加Environment=ETCD_CA_CERT_FILE=/etc/ssl/etcd/ca.pem到 calico-node systemd 文件，但得到完全相同的结果。

有任何想法吗 ？

更新

所以我尝试手动运行 calico，而不是使用 systemd。我还添加了 calico 所需的所有环境变量

export CALICO_DISABLE_FILE_LOGGING=true
export HOSTNAME=10.79.218.2
export IP=10.79.218.2
export FELIX_FELIXHOSTNAME=10.79.218.2
export CALICO_NETWORKING=false
export NO_DEFAULT_POOLS=true
export ETCD_ENDPOINTS=https://10.79.218.2:2379,https://10.79.218.3:2379
export ETCD_AUTHORITY=10.79.218.2:2379
export ETCD_SCHEME=https
export ETCD_CA_CERT_FILE=/etc/ssl/etcd/ca.pem
export ETCD_CERT_FILE=/etc/ssl/etcd/etcd1.pem
export ETCD_KEY_FILE=/etc/ssl/etcd/etcd1-key.pem

当我尝试使用以下命令执行印花布容器时：

/usr/bin/rkt run --inherit-env --stage1-from-dir=stage1-fly.aci \
 --volume=modules,kind=host,source=/lib/modules,readOnly=false \
 --mount=volume=modules,target=/lib/modules \
 --trust-keys-from-https quay.io/calico/node:v0.19.0

我明白了

image: using image from file /usr/lib64/rkt/stage1-images/stage1-fly.aci
image: using image from local store for image name quay.io/calico/node:v0.19.0
Traceback (most recent call last):
  File "startup.py", line 292, in <module>
   client = IPAMClient()
  File "/usr/lib/python2.7/site-packages/pycalico/datastore.py", line 221, in __init__
    ETCD_CERT_FILE_ENV, etcd_cert))
pycalico.datastore_errors.DataStoreError: Cannot read ETCD_KEY_FILE and/or ETCD_CERT_FILE. Both must be readable file paths. Values provided: ETCD_KEY_FILE=/etc/ssl/etcd/etcd1-key.pem, ETCD_CERT_FILE=/etc/ssl/etcd/etcd1.pem

我将证书文件的文件权限更改为 666，但这并不能解决问题。而且我知道这些证书是有效的，因为 etcd tls 可以正常工作。所以我错过了什么？

更新 2

看来我缺少将证书目录安装在印花布容器上。

所以现在我正在运行印花布容器

/usr/bin/rkt run --volume etcd-ssl,kind=host,source=/etc/ssl/etcd/,readOnly=true --inherit-env --stage1-from-dir=stage1-fly.aci  --volume=modules,kind=host,source=/lib/modules,readOnly=false  --mount=volume=modules,target=/lib/modules  --trust-keys-from-https quay.io/calico/node:v0.19.0 --mount volume=etcd-ssl,target=/etc/ssl/etcd

我得到以下输出：

image: using image from file /usr/lib64/rkt/stage1-images/stage1-fly.aci
image: using image from local store for image name quay.io/calico/node:v0.19.0
Traceback (most recent call last):
  File "startup.py", line 292, in <module>
client = IPAMClient()
  File "/usr/lib/python2.7/site-packages/pycalico/datastore.py", line 246, in __init__
allow_reconnect=True)
  File "/usr/lib/python2.7/site-packages/etcd/client.py", line 204, in __init__
set(self.machines))
  File "/usr/lib/python2.7/site-packages/etcd/client.py", line 299, in machines
return self.machines
  File "/usr/lib/python2.7/site-packages/etcd/client.py", line 301, in machines
    raise etcd.EtcdException("Could not get the list of servers, "
etcd.EtcdException: Could not get the list of servers, maybe you provided the wrong host(s) to connect to?
Calico node failed to start

我有点接近..但仍然没有解决方案。

更新 3

我尝试通过运行将 ETCD_ENDPOINTS 设置为 coreos 机器上的 etcd 服务器export ETCD_ENDPOINTS=https://10.79.218.2:2379，现在当我尝试运行 calico rkt 映像时，我得到：

image: using image from file /usr/lib64/rkt/stage1-images/stage1-fly.aci
image: using image from local store for image name quay.io/calico/node:v0.19.0
Traceback (most recent call last):
  File "startup.py", line 295, in <module>
main()
  File "startup.py", line 251, in main
warn_if_hostname_conflict(ip)
  File "startup.py", line 192, in warn_if_hostname_conflict
current_ipv4, _ = client.get_host_bgp_ips(hostname)
  File "/usr/lib/python2.7/site-packages/pycalico/datastore.py", line 132, in wrapped
"running?" % (fn.__name__, e.message))
pycalico.datastore_errors.DataStoreError: get_host_bgp_ips: Error accessing etcd (Connection to etcd failed due to SSLError(CertificateError("hostname '10.79.218.2' doesn't match u'etcd'",),)).  Is etcd running?
Calico node failed to start
etcd coreos rkt