GP Crash when ever I tried the set config parameters using

[Rohit Tanwar]

Hi team,

The GP crash and restart again when ever I tried the set the GP parameters but i first attempt it works fine but I tried to update the second parameter it fails and crash but when I hit it again it works.

Pleas help me to sort out this issue.

We are using gpdb 6.15.0 version.

LOGS

gpadmin@ip-10-2-50-31:~$ gpconfig -c statement_mem -v 256MB --masteronly

20210623:11:27:47:012917 gpconfig:ip-10-2-50-31:gpadmin-[INFO]:-completed successfully with parameters '-c statement_mem -v 256MB --masteron

gpadmin@ip-10-2-50-31:~$ gpconfig -c max_connections -v 2500 -m 1500

20210623:11:27:59:012981 gpconfig:ip-10-2-50-31:gpadmin-[ERROR]:-server closed the connection unexpectedly

        This probably means the server terminated abnormally

        before or while processing the request.

20210623:11:27:59:012981 gpconfig:ip-10-2-50-31:gpadmin-[ERROR]:-Failed to connect to database, exiting without action. This script can onlye is up.

Failed to connect to database, exiting without action. This script can only be run when the database is up.

gpadmin@ip-10-2-50-31:~$ gpconfig -c max_connections -v 2500 -m 1500

20210623:11:28:06:013001 gpconfig:ip-10-2-50-31:gpadmin-[INFO]:-completed successfully with parameters '-c max_connections -v 2500 -m 1500'

gpadmin@ip-10-2-50-31:~$

gpadmin@ip-10-2-50-31:~$ gpconfig -c shared_buffers -v 6GB -m 12GB

20210623:11:28:13:013087 gpconfig:ip-10-2-50-31:gpadmin-[ERROR]:-server closed the connection unexpectedly

        This probably means the server terminated abnormally

        before or while processing the request.

20210623:11:28:13:013087 gpconfig:ip-10-2-50-31:gpadmin-[ERROR]:-Failed to connect to database, exiting without action. This script can onlye is up.

Failed to connect to database, exiting without action. This script can only be run when the database is up.

gpadmin@ip-10-2-50-31:~$ gpconfig -c shared_buffers -v 6GB -m 12GB

20210623:11:28:30:013135 gpconfig:ip-10-2-50-31:gpadmin-[INFO]:-completed successfully with parameters '-c shared_buffers -v 6GB -m 12GB'

gpadmin@ip-10-2-50-31:~$ psql cloud

psql: FATAL:  semctl(360507, 9, SETVAL, 0) failed: Invalid argument (pg_sema.c:151)

gpadmin@ip-10-2-50-31:~$

gpadmin@ip-10-2-50-31:~$

gpadmin@ip-10-2-50-31:~$ psql cloud

psql (9.4.24)

Type "help" for help.

cloud=# \q

gpadmin@ip-10-2-50-31:~$

gpadmin@ip-10-2-50-31:~$ gpconfig -c work_mem -v 512MB

20210623:11:28:51:013239 gpconfig:ip-10-2-50-31:gpadmin-[INFO]:-completed successfully with parameters '-c work_mem -v 512MB'

gpadmin@ip-10-2-50-31:~$ psql cloud

psql: FATAL:  semctl(393228, 9, SETVAL, 0) failed: Invalid argument (pg_sema.c:151)

gpadmin@ip-10-2-50-31:~$

gpadmin@ip-10-2-50-31:~$ gpconfig -c maintenance_work_mem -v 512MB

20210623:11:29:05:013339 gpconfig:ip-10-2-50-31:gpadmin-[INFO]:-completed successfully with parameters '-c maintenance_work_mem -v 512MB'

gpadmin@ip-10-2-50-31:~$

gpadmin@ip-10-2-50-31:~$ psql cloud

psql: FATAL:  semctl(393245, 9, SETVAL, 0) failed: Invalid argument (pg_sema.c:151)

gpadmin@ip-10-2-50-31:~$

gpadmin@ip-10-2-50-31:~$ gpconfig -c gp_vmem_protect_limit -v 12288

20210623:11:29:16:013438 gpconfig:ip-10-2-50-31:gpadmin-[INFO]:-completed successfully with parameters '-c gp_vmem_protect_limit -v 12288'

gpadmin@ip-10-2-50-31:~$

gpadmin@ip-10-2-50-31:~$ gpconfig -c effective_cache_size -v 10GB

20210623:11:29:22:013523 gpconfig:ip-10-2-50-31:gpadmin-[ERROR]:-server closed the connection unexpectedly

        This probably means the server terminated abnormally

        before or while processing the request.

20210623:11:29:22:013523 gpconfig:ip-10-2-50-31:gpadmin-[ERROR]:-Failed to connect to database, exiting without action. This script can onlye is up.

Failed to connect to database, exiting without action. This script can only be run when the database is up.

gpadmin@ip-10-2-50-31:~$

20210623:11:29:22:013523 gpconfig:ip-10-2-2-111 -31:gpadmin-[ERROR]:-Failed to connect to database, exiting without action. This script can only be run when the database is up.

Failed to connect to database, exiting without action. This script can only be run when the database is up.

gpadmin@ip-10-2-50-31:~$

gpadmin@ip-10-2-50-31:~$ psql cloud

psql: FATAL:  semctl(393245, 9, SETVAL, 0) failed: Invalid argument (pg_sema.c:151)

gpadmin@ip-10-2-50-31:~$

2021-06-21 08:13:08.004117 UTC,"gpadmin","template1",p3394,th2140056512,"127.0.0.1","7743",2021-06-21 08:13:07 UTC,0,con955,,seg-1,,,,,"FATAL","XX000","semctl(950365, 6, SETVAL, 0) failed: Invalid argument (pg_sema.c:151)",,,,,,,0,,"pg_sema.c",151,"Stack trace:

1    0x55766b3c1eb1 postgres errstart + 0x1f1

2    0x55766ae4757a postgres <symbol not found> + 0x6ae4757a

3    0x55766b1afbf3 postgres <symbol not found> + 0x6b1afbf3

4    0x55766b22d582 postgres InitProcess + 0x2c2

5    0x55766b243db9 postgres PostgresMain + 0x159

6    0x55766ae4b01f postgres <symbol not found> + 0x6ae4b01f

7    0x55766b1c3e48 postgres PostmasterMain + 0x11b8

8    0x55766ae502da postgres main + 0x4aa

9    0x7f0b7ceecbf7 libc.so.6 __libc_start_main + 0xe7

10   0x55766ae5c23a postgres _start + 0x2a

"

[Deepika Pandhi]

Hi Rohit

 

Can you make sure OS parameters are set as per documentation for version in use?(specifically kernel.sem,kernel.shmmax,kernel.shmall)

 

Here is document

https://gpdb.docs.pivotal.io/6-15/install_guide/prep_os.html#topic3

 

Thanks

Deepika Pandhi 

Staff Technical Support Engineer
Tanzu Support  |  Mon-Fri  8:30 am to 5:00 pm PDT

3401 Hillview Avenue, Palo Alto, CA 94304
24x7 Support: 1-877-477-2269

--
You received this message because you are subscribed to the Google Groups "Greenplum Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gpdb-users+...@greenplum.org.
To view this discussion on the web visit https://groups.google.com/a/greenplum.org/d/msgid/gpdb-users/1593955e-7f7b-41a5-8431-0115a01b474dn%40greenplum.org.

[Luis Filipe de Macedo]

Rohit,

 

Max_connections, shared_buffers, work_mem do not have the same guidelines on GP as on PG. Please try the returning the defaults.

 

Also the max_connections is a little high. Not sure about GP6 but older versions did not start with such high number. Also please review max_connections manual page as GP has another GUC that needs to be set with it as GP is a distributed database.

 

Be careful when using your PG knowledge on GP as some aspects are very different.

 

 

Rgds,

 

Luis F R Macedo

Advisory Data Engineer & Business Development for Latam

VMware Tanzu Data

Call Me @ +55 11 98860 8596 (new)

Take care of the customers and the rest takes care of itself

To view this discussion on the web visit https://groups.google.com/a/greenplum.org/d/msgid/gpdb-users/1D410751-C0FA-48F8-B85C-C9F18ED510BA%40vmware.com.