Conference pamsrc::decmessageq

2865.0. "* URGENTLY * IPC error starting DMQ 3.2a on Unix 4" by ROM01::OLD_BOCCANER () Mon May 05 1997 16:14

    Hi 
    We have a serious problem with Unix 4.0a and DMQ 3.2a (ECO1 applied)
    when we have to start group and bus.
    We get an error, about IPC failure, when we start group that is log
    from 
    dmqgcp -b 1 -g 1 -f /dev/null -n TEST > log.gcp 
    
    >>>
    ************ ./dmqgcp (517) 05-MAY-1997 21:06:33 ************
    gcp, group control process for group 1 is running
    
    ************ ./dmqgcp (517) 05-MAY-1997 21:06:33 ************
    spi, file or object not found
    
    ************ ./dmqgcp (517) 05-MAY-1997 21:06:33 ************
    gcp, error initializing group information
    
    ************ ./dmqgcp (517) 05-MAY-1997 21:06:33 ************
    gcp, initialization failure
    
    ************ ./dmqgcp (517) 05-MAY-1997 21:06:33 ************
    ipi, semaphore operation failed
    
    ************ ./dmqgcp (517) 05-MAY-1997 21:06:33 ************
    gcp, operation failed to complete
    
    ************ ./dmqgcp (517) 05-MAY-1997 21:06:33 ************
    gcp, group control process for group 1 has exited
    
    <<<
    
    If we run dmqivpipc -v  we get this log :
    >>>
    Message Queue Parameters
        MSGMNI = 63
        MSGMAX = 32767
        MSGMNB = 65535
        MSGSSZ * MSGSEG = 655360
        MSGTQL = 40
    
    Semaphore Parameters
        SEMMNI = 15
        SEMMNS = 375
        SEMMSL = 25
        SEMOPM = 10
        SEMUME = 10
    
    Shared Memory Parameters
      * SHMMNI = 0
            parameter is too low
            minimum value is 4
            preferred value is 7
      * SHMSEG = 0
            parameter is too low
            minimum value is 3
            preferred value is 6
        SHMMAX = 4194304
    <<<
    but our IPC parameter as we takes from sysconfigtab are :
    
    >>>
    msg-max = 32767
    msg-mnb = 65535
    msg-mni = 64
    msg-tql = 40
    shm-max = 67108864
    shm-min = 4096
    shm-mni = 256
    shm-seg = 64
    sem-mni = 16
    sem-msl = 25
    sem-opm = 10
    sem-ume = 10
    sem-vmx = 32767
    sem-aem = 16384
    num-of-sems = 60
    max-kernel-ports = 93911
    port-hash-max-num = 4695550
    port-reserved-max-num = 93911
    set-max-num = 24837
    ssm-threshold = 8388608
    ssm-enable-core-dump = 1
    <<<
    
    We have already a system with Unix 3.2c and DMQ 3.2 with same IPC
    parameters and all works fine.
    
    What's the problem ? Customer is waiting for an adequate answer from
    DIGITAL.
    We had to work very hard in convincing one oif the major italian TLC
    customers in adopting DMQ as a robust and usable layered software.
    This nasty situation doesn't help in eventually being successfully with
    DMQ.
    Please, help, urgently.
    Thanks.
    stefano
    

looking at my current system on unix 3.2 the dmqivp looks like it 
reports what is currently available on the active system rather than what
the values are e.g the SHMNI param is lower in the ivp. Did you try 
increasing the values by the margins reported and reconfig the kernel?

hope this helps,

there maybe other notes in this conference that tell what the dmqivpipc 
program does.


Bob 

imsosf.ayo.dec.com> /sbin/sysconfig -q ipc
msg-max = 32767
msg-mnb = 65535
msg-mni = 64
msg-tql = 40
shm-max = 4194304
shm-min = 1
shm-mni = 128
shm-seg = 32
sem-mni = 64
sem-msl = 25
sem-opm = 10
sem-ume = 10
sem-vmx = 32767
sem-aem = 16384
num-of-sems = 60
max-kernel-ports = 22487
port-hash-max-num = 1124350
port-reserved-max-num = 22487
set-max-num = 1029
imsosf.ayo.dec.com> dmqivpipc -v                
Message Queue Parameters
    MSGMNI = 45
    MSGMAX = 32767
    MSGMNB = 65535
    MSGSSZ * MSGSEG = 655360
    MSGTQL = 40

Semaphore Parameters
    SEMMNI = 49
    SEMMNS = 1225
    SEMMSL = 25
    SEMOPM = 10
    SEMUME = 10

Shared Memory Parameters
    SHMMNI = 113
    SHMSEG = 32
    SHMMAX = 4194304

I just done a quick search on dmqivp. You may want to have a look at 
note 2218. 

Bob

    Bob , before to write down note I read every notes more or less related
    to our problem, but no suggestions inside them gave me good results.
    The problem is that kernel parameter values are higher was DMQ
    required, and when we start DMQ no other software is running on the
    system, so no semaphores are used by anybody, and no share memory is
    used . By the way we doubled faulted parametrs but nothing happened.
    We had tried to start a minimum DMQ environment (no init file, 1 bus, 1
    group) directly with dmqgcp procedure, but we obtained the same result.
    
    We have a DEc Unix 3.2 / DMQ 3.2 configuration and all works fine. I
    suspect the problem arises  with DEC Unix 4.0a and DMQ 3.2a or DMQ 3.2
    and may be with our DEC Unix 4.0a configuration.
    So we are trying to start from a clean DEC Unix 4.0a configuration and
    reinstall DMQ on it. Meanwhile the problem is always open and customer
    is discouraged, maybe we should open a QAR or Sw Support escalation
    quickly .
    regards 
    stefano 

re: .0

>    dmqgcp -b 1 -g 1 -f /dev/null -n TEST > log.gcp 

	  You maybe running into a problem attempting to startup using a
	null init file.  Try using the template init file and see if that 
	helps.



	Marty