search

WASdev / ci.docker.websphere-traditional

Dockerfiles for WebSphere Application Server traditional
Apache License 2.0
170 stars 190 forks source link

LogViewer not able to write logViewer.pos file #192

Closed donbourne closed 4 years ago

donbourne commented 4 years ago

In 9.0.5.2 Docker images we're seeing the problem below, where the logViewer fails to start:

Configure logging mode
WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[/work/config-ibm/webContainer.props]"
HPEL is enabled
Starting logViewer ................
Starting server ...................

logViewer cannot write resume file at /logViewer.pos.
ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server server1 open for e-business; process id is 624
Starting logViewer ................

logViewer cannot write resume file at /logViewer.pos.
Starting logViewer ................

logViewer cannot write resume file at /logViewer.pos.
Starting logViewer ................

(repeats)

This is impeding the tWAS Docker image from sending logs to stdout.

gmarcy commented 4 years ago

Fixed by #191