search

kannan-raveendran-nair / pega-pe-docker

Pega Personal Edition made docker deployable
14 stars 17 forks source link

Trouble with Docker on Mac OSX #2

Open AmardeepShinganagutti opened 4 years ago

AmardeepShinganagutti commented 4 years ago

Hi Kannan,

Thanks for starting this up. I am trying to use dockers to solve a long standing issue with Pega-PE. i.e. to run on my Mac. I followed your instructions and got to a point where Postgres runs and restores fine. But Pega deployment creates a lot of issues and eventually craches. For ex Postgress gets errors like below as soon as I start to bring the pega-pe

postgresql-pega | 2020-01-21 18:07:49.871 UTC [1] LOG: database system is ready to accept connections ^[[A^[[Bpostgresql-pega | 2020-01-21 19:06:43.254 UTC [320] ERROR: duplicate key value violates unique constraint "pr_sys_ruleset_index_pk" postgresql-pega | 2020-01-21 19:06:43.254 UTC [320] DETAIL: Key (pzinskey)=(SYSTEM-RULESET-INDEX 40F628069536946EAD2C8BD0F3595138!PEGA-PROCESSCOMMANDER) already exists. postgresql-pega | 2020-01-21 19:06:43.254 UTC [320] STATEMENT: INSERT INTO rules.pr_sys_ruleset_index (pzInsKey , pxCommitDateTime , "pxcreatedatetime" , "pxcreateopname" , "pxcreatesystemid" , "pxinsname" , "pxobjclass" , "pxsavedatetime" , "pyrulesetversion" , "pzrulesetindex" , "pzrulesetlisthash" , "pzrulesetname" , "pzrulesetversionmajor" , "pzrulesetversionminor" , "pzrulesetversionminorpatch" , "pzrulesetversionpatch") VALUES ($1 , CURRENT_TIMESTAMP , $2 , $3 , $4 , $5 , $6 , $7 , $8 , $9 , $10 , $11 , $12 , $13 , $14 , $15) postgresql-pega | 2020-01-21 19:07:08.534 UTC [319] ERROR: duplicate key value violates unique constraint "pr_sys_ruleset_index_pk"

postgresql-pega | 2020-01-21 19:08:14.789 UTC [277] ERROR: duplicate key value violates unique constraint "pr_sys_ruleset_index_pk" postgresql-pega | 2020-01-21 19:08:14.789 UTC [277] DETAIL: Key (pzinskey)=(SYSTEM-RULESET-INDEX A64C1765C619BA11420691487B2762CE!PEGA-RULES) already exists. postgresql-pega | 2020-01-21 19:08:14.789 UTC [277] STATEMENT: INSERT INTO rules.pr_sys_ruleset_index (pzInsKey , pxCommitDateTime , "pxcreatedatetime" , "pxcreateopname" , "pxcreatesystemid" , "pxinsname" , "pxobjclass" , "pxsavedatetime" , "pyrulesetversion" , "pzrulesetindex" , "pzrulesetlisthash" , "pzrulesetname" , "pzrulesetversionmajor" , "pzrulesetversionminor" , "pzrulesetversionminorpatch" , "pzrulesetversionpatch") VALUES ($1 , CURRENT_TIMESTAMP , $2 , $3 , $4 , $5 , $6 , $7 , $8 , $9 , $10 , $11 , $12 , $13 , $14 , $15) postgresql-pega | 2020-01-21 19:14:19.097 UTC [276] ERROR: duplicate key value violates unique constraint "pr_sys_locks_pk" postgresql-pega | 2020-01-21 19:14:19.097 UTC [276] DETAIL: Key (pzinskey)=(PRE-STARTUP: DataFlowServiceStartOperation_RunMigrationLock) already exists. postgresql-pega | 2020-01-21 19:14:19.097 UTC [276] STATEMENT: insert into data.pr_sys_locks ( pxCreateDateTime, pxCreateOpName, pxCreateOperator, pxCreateSystemID, pxExpireDateTime, pxLockHandle, pxObjClass, pxOwnerId, pxSystemName, pxSystemNode, pxUpdateDateTime, pxUpdateOpName, pxUpdateOperator, pxUpdateSystemID, pxUserHost, pyLabel, pzInsKey) values ($1, $2, $3, $4, $5, $6, 'System-Locks', $7, $8, $9, $10, $11, $12, $13, $14, '', $15) postgresql-pega | 2020-01-21 19:14:53.293 UTC [320] ERROR: duplicate key value violates unique constraint "pr_data_stream_nodes_pk" postgresql-pega | 2020-01-21 19:14:53.293 UTC [320] DETAIL: Key (pynodeid)=(/) already exists. postgresql-pega | 2020-01-21 19:14:53.293 UTC [320] STATEMENT: INSERT INTO data.pr_data_stream_nodes ( pyNodeId , pyParentId , pyVersion , pyChildVersion , pyMode , pySession , pyCreateDateTime , pyUpdateDateTime ) VALUES ( $1 ,$2 ,$3 ,$4 ,$5 ,$6 ,$7 ,$8 ) postgresql-pega | 2020-01-21 19:16:47.623 UTC [319] ERROR: duplicate key value violates unique constraint "pr_data_stream_nodes_pk" postgresql-pega | 2020-01-21 19:16:47.623 UTC [319] DETAIL: Key (pynodeid)=(/) already exists. postgresql-pega | 2020-01-21 19:16:47.623 UTC [319] STATEMENT: INSERT INTO data.pr_data_stream_nodes ( pyNodeId , pyParentId , pyVersion , pyChildVersion , pyMode , pySession , pyCreateDateTime , pyUpdateDateTime ) VALUES ( $1 ,$2 ,$3 ,$4 ,$5 ,$6 ,$7 ,$8 ) postgresql-pega | 2020-01-21 19:16:48.542 UTC [319] ERROR: duplicate key value violates unique constraint "pr_data_stream_nodes_pk" postgresql-pega | 2020-01-21 19:16:48.542 UTC [319] DETAIL: Key (pynodeid)=(/prpc_brokers) already exists. postgresql-pega | 2020-01-21 19:16:48.542 UTC [319] STATEMENT: INSERT INTO data.pr_data_stream_nodes ( pyNodeId , pyParentId , pyVersion , pyChildVersion , pyMode , pySession , pyCreateDateTime , pyUpdateDateTime ) VALUES ( $1 ,$2 ,$3 ,$4 ,$5 ,$6 ,$7 ,$8 ) postgresql-pega | 2020-01-21 19:19:59.850 UTC [277] LOG: could not send data to client: Broken pipe postgresql-pega | 2020-01-21 19:19:59.850 UTC [277] STATEMENT: select pzPVStream , pxCommitDateTime from rules.pr4_rule where pzInsKey like $1 order by "pyruleset" , "pyrulesetversion" desc , pzInsKey postgresql-pega | 2020-01-21 19:19:59.851 UTC [277] FATAL: connection to client lost postgresql-pega | 2020-01-21 19:19:59.851 UTC [277] STATEMENT: select pzPVStream , pxCommitDateTime from rules.pr4_rule where pzInsKey like $1 order by "pyruleset" , "pyrulesetversion" desc , pzInsKey

AmardeepShinganagutti commented 4 years ago

Eventually Pega PE gets the below error and crashes pega | 2020-01-21 19:16:59,331 [ervice-registry-task] [ STANDARD] [ ] [ ] (.tasks.TopologyChangedDetector) INFO - Services topology has changed. Current topology: pega | This node ==> Aggregation.Default b12284472faf 172.18.0.3 NORMAL
pega | This node ==> DataFlow.BackgroundProcessing b12284472faf 172.18.0.3 NORMAL
pega | This node ==> DataFlow.Search b12284472faf 172.18.0.3 NORMAL
pega | This node ==> StreamServer.Default b12284472faf 172.18.0.3 NORMAL (was JOINING) pega | This node ==> pega b12284472faf 172.18.0.3 startingUp
pega | pega | 2020-01-21 19:17:18,468 [ b12284472faf] [ STANDARD] [ ] [ ] (ternal.async.PassivationDaemon) INFO - PegaRULES Passivation Daemon initialized in web-tier. pega | 2020-01-21 19:17:22,571 [ b12284472faf] [ STANDARD] [ ] [ ] (base.PassivationStorageManager) INFO - Passivation data will be written to database. pega | 2020-01-21 19:17:23,540 [egaRULES-MasterAgent] [ ] [ ] [ ] ( internal.async.Agent) INFO - System date: Tue Jan 21 19:17:23 GMT 2020 Total memory: 2,861,039,616 Free memory: 2,012,736,456 Requestor Count: 32 Shared Pages memory usage: 0% Current number of threads: 93 pega | 2020-01-21 19:18:59,726 [til LISTENER_STARTUP] [ STANDARD] [ ] [ ] (nc.startup.ListenerStartupTask) INFO - Initializing all listeners.. starting pega | 21-Jan-2020 19:18:59.576 WARNING [PegaRULES-MasterAgent] org.apache.tomcat.jdbc.pool.PooledConnection.clearWarnings Unable to clear Warnings, connection will be closed. pega | org.postgresql.util.PSQLException: This connection has been closed. pega | at org.postgresql.jdbc.PgConnection.checkClosed(PgConnection.java:857) pega

kannan-raveendran-nair commented 4 years ago

Hi, Which version of PE do you use? duplicate key value violates unique constraint - this is something I see all the time, and PE still works fine for me. But postgres other errors I haven't noticed before. I'm not really sure if mac os docker needs any special setup. I will check my logs too to see if the exceptions you see are thrown for me as well.

On Tue., Jan. 21, 2020, 2:33 p.m. AmardeepShinganagutti, < notifications@github.com> wrote:

Eventually Pega PE gets the below error and crashes pega | 2020-01-21 19:16:59,331 [ervice-registry-task] [ STANDARD] [ ] [ ] (.tasks.TopologyChangedDetector) INFO - Services topology has changed. Current topology: pega | This node ==> Aggregation.Default b12284472faf 172.18.0.3 NORMAL pega | This node ==> DataFlow.BackgroundProcessing b12284472faf 172.18.0.3 NORMAL pega | This node ==> DataFlow.Search b12284472faf 172.18.0.3 NORMAL pega | This node ==> StreamServer.Default b12284472faf 172.18.0.3 NORMAL (was JOINING) pega | This node ==> pega b12284472faf 172.18.0.3 startingUp pega | pega | 2020-01-21 19:17:18,468 [ b12284472faf] [ STANDARD] [ ] [ ] (ternal.async.PassivationDaemon) INFO - PegaRULES Passivation Daemon initialized in web-tier. pega | 2020-01-21 19:17:22,571 [ b12284472faf] [ STANDARD] [ ] [ ] (base.PassivationStorageManager) INFO - Passivation data will be written to database. pega | 2020-01-21 19:17:23,540 [egaRULES-MasterAgent] [ ] [ ] [ ] ( internal.async.Agent) INFO - System date: Tue Jan 21 19:17:23 GMT 2020 Total memory: 2,861,039,616 Free memory: 2,012,736,456 Requestor Count: 32 Shared Pages memory usage: 0% Current number of threads: 93 pega | 2020-01-21 19:18:59,726 [til LISTENER_STARTUP] [ STANDARD] [ ] [ ] (nc.startup.ListenerStartupTask) INFO - Initializing all listeners.. starting pega | 21-Jan-2020 19:18:59.576 WARNING [PegaRULES-MasterAgent] org.apache.tomcat.jdbc.pool.PooledConnection.clearWarnings Unable to clear Warnings, connection will be closed. pega | org.postgresql.util.PSQLException: This connection has been closed. pega | at org.postgresql.jdbc.PgConnection.checkClosed(PgConnection.java:857) pega

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kannan-raveendran-nair/pega-pe-docker/issues/2?email_source=notifications&email_token=AL2FXT4GNHTW4RJEJCISUIDQ65EW5A5CNFSM4KJY24CKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJQ62HY#issuecomment-576843039, or unsubscribe https://github.com/notifications/unsubscribe-auth/AL2FXTYOUXHM7BT5ACDKUWTQ65EW5ANCNFSM4KJY24CA .

AmardeepShinganagutti commented 4 years ago

Hi Kannan,

I am using Pega PE 8.3. I was thinking that the duplicate key viloations isnt letting PE perform as expected and eventually leading to a crash. But if it is working for you even with the errors, then issue lies somewhere else. Need to check the context.xml for DB connectivity settings.