Unable to start DB if -Mn*-Ma > 1024

[Mike45]

Hi,
we have to increase the number of users in our db. Version 10.2B08 Enterprise. But if parameter -Mn*-Ma is greater than 1024 the start canceled with error (793)
Any Idea?

 

[Patrice Perrot]

Hi ,
I have no issue with "-Mn 42 -Mpb 40 -Ma 40" .

proserve dbnewdb -N TCP -S 4.... -n 1606 -Mn 42 -Mpb 40 -Ma 40 -Mi 5
OpenEdge Release 10.2B0830 as of Mon Feb 16 03:35:45 EST 2015
09:26:47 BROKER The startup of this database requires 70Mb of shared memory. Maximum segment size is 1024Mb.
09:26:47 BROKER 0: D▒but de la session Multi-Utilisateurs. (333)
09:26:47 BROKER 0: Avant l'initialisation du journal d'image dans le bloc 405 avec un d▒calage 2703. (15321)
09:26:47 BROKER 0: Connexion de l'utilisateur openbase ▒ /dev/pts/1. (452)
09:26:47 BROKER 0: D▒marrage de 49175 en utilisant TCP IPV4 address 0.0.0.0, pid 13500766. (5644)

Could you give us your command line ?

patrice

 

[jdpjamesp]

Is this 32 bit of 64 bit? Are you absolutely sure of your version? It looks like this bug: Progress KB - Database experiences a forced shutdown with error 793 and 744

 

[jdpjamesp]

Also, what OS is this?

 

[Mike45]

Hi ,
I have no issue with "-Mn 42 -Mpb 40 -Ma 40" .

proserve dbnewdb -N TCP -S 4.... -n 1606 -Mn 42 -Mpb 40 -Ma 40 -Mi 5
OpenEdge Release 10.2B0830 as of Mon Feb 16 03:35:45 EST 2015
09:26:47 BROKER The startup of this database requires 70Mb of shared memory. Maximum segment size is 1024Mb.
09:26:47 BROKER 0: D▒but de la session Multi-Utilisateurs. (333)
09:26:47 BROKER 0: Avant l'initialisation du journal d'image dans le bloc 405 avec un d▒calage 2703. (15321)
09:26:47 BROKER 0: Connexion de l'utilisateur openbase ▒ /dev/pts/1. (452)
09:26:47 BROKER 0: D▒marrage de 49175 en utilisant TCP IPV4 address 0.0.0.0, pid 13500766. (5644)

Could you give us your command line ?

patrice

Hi Patrice,
thanks for your answer. Now i tried your commandline.
proserve dbpavxx -N TCP -S 13000 -n 1606 -Mn 42 -Mpb 40 -Ma 32 -Mi 5 : not working
proserve dbpavxx -N TCP -S 13000 -n 1606 -Mn 32 -Mpb 40 -Ma 32 -Mi 5 : not working
proserve dbpavxx -N TCP -S 13000 -n 1606 -Mn 31 -Mpb 40 -Ma 32 -Mi 5 : working

we use Suse Sles 10 as OS. Which OS do you use?

Mike

 

[Mike45]

Also, what OS is this?

proadsv -query
OpenEdge Release 10.2B0874 as of Wed Jun 14 00:25:40 EDT 2017

OS:
SUSE Linux Enterprise Server 10 (x86_64)
VERSION = 10
PATCHLEVEL = 3

I knew the kb-article and also called support@progress. But they sad that this bug is patched in openedge 10.2B nothing else. But we have this error.

[2021/12/17@10:23:11.977+0100] P-10722 T-47535665463280 I BROKER 0: (10471) Database connections have been enabled.
[2021/12/17@10:23:11.978+0100] P-10722 T-47535665463280 I BROKER 0: (793) Select returned -1 , errno=22.
[2021/12/17@10:23:11.978+0100] P-10722 T-47535665463280 I BROKER 0: (744) Forcing shutdown, reason 15.
[2021/12/17@10:23:11.978+0100] P-10722 T-47535665463280 I BROKER 0: (15193) The normal shutdown of the database will continue for 10 Min 0

 

[Rob Fitzpatrick]

proserve dbpavxx -N TCP -S 13000 -n 1606 -Mn 42 -Mpb 40 -Ma 32 -Mi 5 : not working
proserve dbpavxx -N TCP -S 13000 -n 1606 -Mn 32 -Mpb 40 -Ma 32 -Mi 5 : not working
proserve dbpavxx -N TCP -S 13000 -n 1606 -Mn 31 -Mpb 40 -Ma 32 -Mi 5 : working

I don't understand why you would try settings like these. You should never have -Mpb for one broker higher than -Mn on the primary broker. -Mn determines the number of secondary brokers and remote servers you can have, for both server types, database-wide. -Mpb determines the maximum number of servers you can spawn for a particular connection broker.

The value of -Mn should be at least the sum of all broker -Mpb values plus the number of secondary brokers.

proserve sports -S 13000 -n 1606 -Mn 42 -Mpb 40 -Ma 32 -Mi 5 works for me in 10.2B08 on Linux.

Your original screenshot doesn't actually show your client/server parameters, aside from -Mpb and -minport/-maxport. Can you please post your entire set of client/server-related parameters for all brokers for your database?

 

[Patrice Perrot]

Hi

I have some issue with high -n on older release of Progress when the "-shmsegsize " was too small.
Could you try to start your db with the line below
proserve sports -S 13000 -n 1606 -Mn 42 -Mpb 40 -Ma 32 -Mi 5 -shmsegsize 2G -minport 18500 -maxport 22000

 

[Mike45]

Hi

I have some issue with high -n on older release of Progress when the "-shmsegsize " was too small.
Could you try to start your db with the line below
proserve sports -S 13000 -n 1606 -Mn 42 -Mpb 40 -Ma 32 -Mi 5 -shmsegsize 2G -minport 18500 -maxport 22000

Ok,
i tried proserve pavar -S 13000 -n 1606 -Mn 42 -Mpb 40 -Ma 32 -Mi 5 -shmsegsize 2G -minport 18500 -maxport 22000. It did not work. Logfile attached.