[caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2?

Le Bihan Stéphane (AMUNDI-ITS) stephane.lebihan at amundi.com
Thu May 24 07:39:45 MDT 2018


Log docker :

2018-05-24T15:31:45.955719+02:00 dl360o-101 dockerd[2055]: time="2018-05-24T15:31:45.954756307+02:00" level=warning msg="container kill failed because of 'container not found' or 'no such process': Cannot kill container f87327727cc5d4628082cb4d0c09503f82ddcbd6d8055db63cf8020c10f6cb11: rpc error: code = Unknown desc = containerd: container not found"
2018-05-24T15:31:45.955852+02:00 dl360o-101 dockerd[2055]: time="2018-05-24T15:31:45.954770487+02:00" level=warning msg="container kill failed because of 'container not found' or 'no such process': Cannot kill container bbb9a2b7215fdd144391d198e6a3c3a11bc9cc035d36701a21d3bb92a3799200: rpc error: code = Unknown desc = containerd: container not found"
2018-05-24T15:31:45.955985+02:00 dl360o-101 dockerd[2055]: time="2018-05-24T15:31:45.954773986+02:00" level=warning msg="container kill failed because of 'container not found' or 'no such process': Cannot kill container d4e3cad021df83cd9ba3bcb04d8c9cc0bd54a4f85c6935bec65fead9e2fa9840: rpc error: code = Unknown desc = containerd: container not found"

Support config is stuck :

root at dl360o-101:/root$ supportconfig
=============================================================================
                     Support Utilities - Supportconfig
                          Script Version: 3.0-105
                          Script Date: 2018 01 05

 Detailed system information and logs are collected and organized in a
 manner that helps reduce service request resolution times. Private system
 information can be disclosed when using this tool. If this is a concern,
 please prune private data from the log files. Several startup options
 are available to exclude more sensitive information. Supportconfig data is
 used only for diagnostic purposes and is considered confidential information.
 See http://www.novell.com/company/legal/privacy/
=============================================================================

Gathering system information
  Data Directory:    /var/log/nts_dl360o-101_180524_1401

  Basic Server Health Check...                 Done
  RPM Database...                              Done
  Basic Environment...                         Done
  System Modules...                            Done
  Memory Details...                            Done
  Disk I/O...                                  Done
  B-tree File System...                        Done
  YaST Files...                                Done
  File System List...                          Skipped
  Auditing...                                  Done
  Crash Info...                                Done
  NTP...                                       Done
  PROC...                                      Done
  Boot Files...                                Done
  SLERT...                                     Skipped
  Updates...                                   Done
  SMT...                                       Skipped
  HA Cluster...                                Skipped
  OCFS2...                                     Skipped
  DRBD...                                      Skipped
  HAPROXY...                                   Skipped
  PAM...                                       Done
  LDAP...                                      Skipped
  System Security Services...                  Skipped
  CIMOM...                                     Skipped
  Open Files...                                Done
  Environment...                               Done
  Command History...                           Excluded
  ETC...                                       Done
  SYSCONFIG...                                 Done
  SYSFS...                                     Done
  SystemD...                                   Done
  Docker...                                    

# ps axjf | egrep "PPID|13967"
 PPID   PID  PGID   SID TTY      TPGID STAT   UID   TIME COMMAND
12419 12427 12427 12427 pts/0    13967 Ss       0   0:00  |   \_ -bash
12427 13967 13967 12427 pts/0    13967 S+       0   0:28  |       \_ /bin/bash /sbin/supportconfig
13967 12731 13967 12427 pts/0    13967 S+       0   0:00  |           \_ bash
12731 12732 13967 12427 pts/0    13967 Sl+      0   0:00  |               \_ /usr/bin/docker top 843c6dd27ae7
26499 47700 47699 26499 pts/1    47699 S+       0   0:00          \_ egrep PPID|13967

# /usr/bin/docker top 843c6dd27ae7
^C
# docker logs 843c6dd27ae7
^C
# docker ps | grep 843c6dd27ae7
# docker ps -a | grep 843c6dd27ae7
843c6dd27ae7        sles12/pause:1.0.0                                           "/usr/share/suse-d..."   5 hours ago         Created                                         k8s_POD_influxtreon-1527151380-b879p_tick_7aafe27b-5f2e-11e8-8f7c-525400cfa2b7_1

# kill 12732
.... Nothing....

# kill 12731
/sbin/supportconfig: line 551: 12730 Done                    echo "$CMDLINE"
     12731 Terminated              | bash >> $LOGFILE 2>&1

Now support config is stuck on :
# ps axjf | egrep "PPID|13967"
 PPID   PID  PGID   SID TTY      TPGID STAT   UID   TIME COMMAND
12419 12427 12427 12427 pts/0    13967 Ss       0   0:00  |   \_ -bash
12427 13967 13967 12427 pts/0    13967 S+       0   0:28  |       \_ /bin/bash /sbin/supportconfig
13967 48779 13967 12427 pts/0    13967 S+       0   0:00  |           \_ bash
48779 48780 13967 12427 pts/0    13967 Sl+      0   0:00  |               \_ /usr/bin/docker inspect 843c6dd27ae7
26499 49026 49025 26499 pts/1    49025 S+       0   0:00          \_ egrep PPID|13967
    1 12732 13967 12427 pts/0    13967 Sl+      0   0:00 /usr/bin/docker top 843c6dd27ae7

I make "^C" on support config and relauch it.

Regards

Stéphane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com
@: sits.unix at amundi.com

Visit us on: 

        

-----Message d'origine-----
De : Le Bihan Stéphane (AMUNDI-ITS) 
Envoyé : jeudi 24 mai 2018 14:43
À : Le Bihan Stéphane (AMUNDI-ITS); lproven at suse.com; Yoshise, Junichi
Cc : caasp-beta at lists.suse.com
Objet : RE: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2?

For information another response from another develloper :

" Hi,

I've created new test cron job and even that generates the Terminating pods:

$ kp get pods -n tick
NAME                             READY     STATUS        RESTARTS   AGE
data-influxdb-5c7b44ff76-fcf5m   1/1       Running       2          9d
grafana-7dc9f4bccc-k6gbc         1/1       Running       3          9d
influxtreon-1527164760-64xf9     0/1       Terminating   0          5m
influxtreon-1527164940-27565     0/1       Completed     0          2m
influxtreon-1527165000-mh27k     0/1       Completed     0          1m
influxtreon-1527165060-d8jww     0/1       Completed     0          16s
sleeper-1527164640-9njtv         0/1       Terminating   0          7m
sleeper-1527164760-xm79v         0/1       Completed     0          5m
sleeper-1527164820-ptb64         0/1       Terminating   0          4m
sleeper-1527164880-q6f6d         0/1       Completed     0          3m
sleeper-1527164940-j2k8f         0/1       Completed     0          2m
sleeper-1527165000-bp5vx         0/1       Terminating   0          1m
sleeper-1527165060-72b9l         0/1       Completed     0          15s

Here's the cron configuraton:

---
apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: sleeper
spec:
  schedule: "*/1 * * * *"
  concurrencyPolicy: Replace
  successfulJobsHistoryLimit: 3
  failedJobsHistoryLimit: 3
  jobTemplate:
    spec:
      template:
        spec:
          containers:
            - name: sleeper
              image: <registry>/library/ubuntu:18.04
              args:
                - "/bin/sleep"
                - "5"
          restartPolicy: OnFailure
          imagePullSecrets:
            - name: regcred

Here's the source code for sleep: 
https://github.com/coreutils/coreutils/blob/master/src/sleep.c

I'd say there's definitely other pods that have the same issue. :D"

Regards

Stéphane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com
@: sits.unix at amundi.com

Visit us on: 

        


-----Message d'origine-----
De : caasp-beta-bounces at lists.suse.com [mailto:caasp-beta-bounces at lists.suse.com] De la part de Le Bihan Stéphane (AMUNDI-ITS)
Envoyé : jeudi 24 mai 2018 14:35
À : lproven at suse.com; Yoshise, Junichi
Cc : caasp-beta at lists.suse.com
Objet : Re: [caasp-beta] [Marketing Mail] Re: How to deploy CaaSP on EC2?

Thanks for your response.

I launch support_config, but it's stuck at Docker line ....
I wait.

Memory limit on server is not at limit (big server :D) 

             total       used       free     shared    buffers     cached
Mem:           377         14        363          0          0          9
-/+ buffers/cache:          4        373
Swap:            0          0          0

And for application developer say me :
   "Influxtreon consumes about 150kB to run"

I wait for support_config.

Regards,


Stéphane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com
@: sits.unix at amundi.com

Visit us on: 

        


-----Message d'origine-----
De : caasp-beta-bounces at lists.suse.com [mailto:caasp-beta-bounces at lists.suse.com] De la part de Liam Proven
Envoyé : jeudi 24 mai 2018 12:26
À : Yoshise, Junichi
Cc : caasp-beta at lists.suse.com
Objet : [Marketing Mail] Re: [caasp-beta] How to deploy CaaSP on EC2?

On Thu, 24 May 2018 06:34:27 +0000
"Yoshise, Junichi" <junichi.yoshise at hpe.com> wrote:

> I’m trying to deploy CaaSP 3.0 beta2 on AWS EC2. Since AMI is not
> available, I’ve converted qcow2 or vmdk file then tried to import to
> EC2, but it didn’t work. Is there any way to deploy CaaSP on EC2?

As I understand it, currently, for public cloud use, you should be
looking at CaaSP 2.1, not 3.0 -- and I believe it has not yet reached
beta phase.

-- 
Liam Proven - Technical Writer, SUSE Linux s.r.o.
Corso II, Křižíkova 148/34, 186-00 Praha 8 - Karlín, Czechia
Email: lproven at suse.com - Office telephone: +420 284 241 084


_______________________________________________
caasp-beta mailing list
caasp-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/caasp-beta
_______________________________________________
caasp-beta mailing list
caasp-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/caasp-beta


More information about the caasp-beta mailing list