2 Replies Latest reply: May 11, 2014 6:37 AM by Syed_Fayaz_Solaris RSS

    Application running in Solaris 9 container generating core files. what to do?

    Syed_Fayaz_Solaris

      My solaris 9 zone configuration in solaris 10 looks like:

      zonecfg:sms> info

      zonename: sms

      zonepath: /zone/sms

      brand: solaris9

      autoboot: true

      bootargs:

      pool:

      limitpriv: default,proc_priocntl,proc_clock_highres,proc_lock_memory,sys_time,priv_proc_priocntl,priv_sys_time,net_rawaccess,sys_ipc_config,priv_proc_lock_memory

      scheduling-class:

      ip-type: exclusive

      hostid:

      [max-shm-memory: 4G]

      [max-shm-ids: 100]

      [max-sem-ids: 100]

      fs:

        dir: /var

        special: /dev/dsk/c1t0d0s5

        raw: /dev/rdsk/c1t0d0s5

        type: ufs

        options: []

      net:

        address not specified

        physical: bge0

        defrouter not specified

      device

        match: /dev/dsk/c1t0d0s5

      device

        match: /dev/rdsk/c1t0d0s5

      device

        match: /dev/dsk/c1t0d0s6

      device

        match: /dev/rdsk/c1t0d0s6

      device

        match: /dev/dsk/c1t0d0s7

      device

        match: /dev/rdsk/c1t0d0s7

      capped-cpu:

        [ncpus: 2.00]

      capped-memory:

        physical: 4G

        [swap: 8G]

        [locked: 2G]

      attr:

        name: hostid

        type: string

        value: 84b18f64

      attr:

        name: machine

        type: string

        value: sun4u

      rctl:

        name: zone.max-sem-ids

        value: (priv=privileged,limit=100,action=deny)

      rctl:

        name: zone.max-shm-ids

        value: (priv=privileged,limit=100,action=deny)

      rctl:

        name: zone.max-shm-memory

        value: (priv=privileged,limit=4294967296,action=deny)

      rctl:

        name: zone.max-swap

        value: (priv=privileged,limit=8589934592,action=deny)

      rctl:

        name: zone.max-locked-memory

        value: (priv=privileged,limit=2147483648,action=deny)

      rctl:

        name: zone.cpu-cap

        value: (priv=privileged,limit=200,action=deny)

       

      Solaris 9 zone /etc/system file looks like:

      * The directive below is not applicable in the virtualized environment.

       

       

      * The directive below is not applicable in the virtualized environment.

       

       

      * The directive below is not applicable in the virtualized environment.

       

       

      * The directive below is not applicable in the virtualized environment.

       

       

      * The directive below is not applicable in the virtualized environment.

       

       

      * The directive below is not applicable in the virtualized environment.

      set noexec_user_stack=1

      set semsys:seminfo_semmni=100

      set semsys:seminfo_semmns=1024

      set semsys:seminfo_semmsl=256

      set semsys:seminfo_semvmx=32767

      set shmsys:shminfo_shmmax=4294967295

      set shmsys:shminfo_shmmin=1

      set shmsys:shminfo_shmmni=100

      set shmsys:shminfo_shmseg=10

       

       

      set rlim_fd_max=65536

      set rlim_fd_cur=60000

      * The directive below is not applicable in the virtualized environment.

       

      My questions are:

      1. 1. Application running in solaris 9 container generating core files. what to do???
      2. 2. My prstat -Z for zone shows almost 95% percent cpu usage. what to do???
      3. 3. Kindly can share how to move solaris 9 into solaris 10 containers ??