Question

PRPC-8.2.2-354 - Operator:Unauthenticated or not available

New Installation of PRPC-8.2.2-354 using tomcat/docker. Unable to login to Pega platform using administrator@pega.com.

Error:
There has been an issue; please consult your system administrator
Status:fail
Operator:Unauthenticated or not available
Node:No ID available

On Startup - see attachment for details
On Page reload - see attachment for details
com.pega.pegarules.pub.PRRuntimeException: Error including section 'pyChangePassword' on page 'pyOperPage' of class 'Data-Admin-Operator-ID'.
Caused by: java.lang.NoClassDefFoundError: java.awt.Toolkit

***Moderator Edit-Vidyaranjan: Updated Platform Capability***

Correct Answer
October 8, 2019 - 9:18pm

Very strange indeed, could be the OS is missing some libraries, but we have been using this image without any issues, check this link (the last answer) - maybe you can give it try by installing missing libraries in your docker image: https://askubuntu.com/questions/674579/libawt-xawt-so-libxext-so-6-cannot-open-shared-object-file-no-such-file-or-di

Also, can you try this image which already has prweb.war baked in: https://hub.docker.com/r/pegasystems/pega

Comments

Keep up to date on this post and subscribe to comments

October 7, 2019 - 10:45am

looks like your base tomcat image has some issues linking awt library, can you try this from pega: https://hub.docker.com/r/pegasystems/tomcat

October 7, 2019 - 12:51pm

Updated compose file with pegasystems/tomcat. Fired up a new instance on a new database install. Same result.On reload the page turns blank and the browser header says "Change Password". Logs attached.

 

version: '3.5'
services:
  pega:
    container_name: pega
    #image: tomcat:latest
    image: pegasystems/tomcat:latest
...
...

 

# docker image ls -a
REPOSITORY           TAG                 IMAGE ID            CREATED             SIZE
pegasystems/tomcat   latest              fecdc4fdc13f        3 months ago        221MB

 

October 7, 2019 - 7:00pm
Response to EdwinH62

Interesting, if you only specify -DNodeType=WebUser, would the system come up fine? 

October 8, 2019 - 9:32am
Response to KevinZheng_GCS

Unfortunately, I am getting the same result even with "-DNodeType=WebUser" specified. The prweb.war file I am using is from the 116404_Pega_822.zip media.

  1. # ps -ef | grep [N]odeType
  2. root 1 0 99 13:24 ? 00:25:01 /opt/java/openjdk/bin/java -Djava.util.logging.config.file=/usr/local/tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.awt.headless=true -Xms4096m -Xmx8192m -Djava.security.egd=file:///dev/urandom -DNodeType=WebUser -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -Dignore.endorsed.dirs= -classpath /usr/local/tomcat/bin/bootstrap.jar:/usr/local/tomcat/bin/tomcat-juli.jar -Dcatalina.base=/usr/local/tomcat -Dcatalina.home=/usr/local/tomcat -Djava.io.tmpdir=/usr/local/tomcat/temp org.apache.catalina.startup.Bootstrap start

For the other system if I startup pega on tomcat (non-docker), connect to the database I can login and change the password. Thereafter when I startup pega docker again I can login and see dev studio. However, if I switch to admin studio I get the following error:

There has been an issue; please consult your system administrator
Status:fail
Operator:Unauthenticated or not available
Node:No ID available

October 8, 2019 - 9:18pm
Response to EdwinH62

Very strange indeed, could be the OS is missing some libraries, but we have been using this image without any issues, check this link (the last answer) - maybe you can give it try by installing missing libraries in your docker image: https://askubuntu.com/questions/674579/libawt-xawt-so-libxext-so-6-cannot-open-shared-object-file-no-such-file-or-di

Also, can you try this image which already has prweb.war baked in: https://hub.docker.com/r/pegasystems/pega

October 7, 2019 - 1:53pm
  1. # curl -s http://$(hostname -i):8080/prweb/PRRestService/monitor/pingservice/ping | python -m json.tool
  2. {
  3. "health": [
  4. {
  5. "last_reported_time": "2019-10-07T17:51:51.900Z",
  6. "status": "success",
  7. "test_name": "HTML-Stream-Check"
  8. },
  9. {
  10. "last_reported_time": "2019-10-07T17:51:51.900Z",
  11. "status": "success",
  12. "test_name": "Streamservice-Check"
  13. }
  14. ],
  15. "node_id": "xxxxxxxxxxxxxxxxxxxxxxxxxxx",
  16. "node_type": [
  17. "WebUser",
  18. "BackgroundProcessing",
  19. "Search",
  20. "Stream"
  21. ],
  22. "state": "healthy"
  23. }

 

October 9, 2019 - 11:17am

Kevin,
The pega docker container (below) seemed to work where the tomcat one had issues. Thank you very much for checking back on this thread. 

https://hub.docker.com/r/pegasystems/pega