Nodeagent or Instance Does Not Start if its Log File Size Exceeds 2 GB
Last updated on JULY 12, 2017
Applies to:Oracle GlassFish Server - Version 8.2 to 8.2 [Release 8.2]
Oracle GlassFish Server - Version 8.1u2 and later
Information in this document applies to any platform.
The following versions of Sun Java Application server 8.x will fail to start if the server.log exceeds two gigabytes in size:
- 8.1 UR2 Patch 24
- 8.2 Patch 7
There is very little information logged in the server.log when this situation occurs.
For example, the node-agent will not start up even if it does not start its instances, the command will time out after a few minutes and no node-agent process is found using the Unix ps command:
# asadmin start-node-agent --user admin --startinstances=false
Timeout waiting for Node Agent to go to starting state.
The key symptoms to look for are:
- A core file is generated in the node-agent's config directory generated each time a startup is attempted:
# ls agent/config/core
# pstack agent/config/core
core '../config/core' of 6819: /work2/as8102p11/lib/appservAgent testna
fefa4210 fileno (0, 0, 440d4, 227e8, fefe8298, fefecb44) + 54
0001124c main (0, fefec7cc, 44998, 10, 226cc, 10) + 4f0
00010d34 _start (0, 0, 0, 0, 0, 0) + 108
- The server.log has a file size exceeding 2 GB in size:
# ls -l server.log
-rwxrwxrwx+ 1 xxxxx staff 2349929078 Feb 21 11:24 server.log
- The node-agent log file, that is its server.log file, does not show anything at the current default logging level.
The default log rotation limit of 2Mb was either increased beyond 2Gb, or was removed completely.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms