Prev
Next
Forums Infor / Lawson Platforms Lawson Landmark

Landmark Re-install fails on gridinstaller error

 5 Replies
 0 Subscribed to this topic
 32 Subscribed to this forum
Sort:
Author
Messages
Keith Barth
Basic Member Send Private Message
Posts: 6
Basic Member
1/29/2016 8:45 PM

Here is the error we are encountering on the reload of Landmark via the LANDMARK.jar process:

@@ run /prod/prod-LM/env/bin/gridinstaller java.lang.reflect.InvocationTargetException Error: java.lang.reflect.InvocationTargetException         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Error:  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) Error:  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56) Error:  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)         at java.lang.reflect.Method.invoke(Method.java:620) Error:  at java.lang.reflect.Method.invoke(Method.java:620)         at com.lawson.rdtech.command.main.Main.exec(Main.java:352) Error:  at com.lawson.rdtech.command.main.Main.exec(Main.java:352)         at com.lawson.rdtech.command.main.Main.main(Main.java:46) Error:  at com.lawson.rdtech.command.main.Main.main(Main.java:46) Caused by: java.lang.NullPointerException Error: Caused by: java.lang.NullPointerException         at com.lawson.grid.util.misc.FileSystemUtils.deleteRecursiveImpl(FileSystemUtils.java:28) Error:  at com.lawson.grid.util.misc.FileSystemUtils.deleteRecursiveImpl(FileSystemUtils.java:28)         at com.lawson.grid.util.misc.FileSystemUtils.deleteRecursive(FileSystemUtils.java:21) Error:  at com.lawson.grid.util.misc.FileSystemUtils.deleteRecursive(FileSystemUtils.java:21)         at com.lawson.grid.util.misc.FileSystemUtils.deleteRecursive(FileSystemUtils.java:16) Error:  at com.lawson.grid.util.misc.FileSystemUtils.deleteRecursive(FileSystemUtils.java:16)         at com.lawson.rdtech.gridadapter.installer.GridInstaller.packGar(GridInstaller.java:760) Error:  at com.lawson.rdtech.gridadapter.installer.GridInstaller.packGar(GridInstaller.java:760)         at com.lawson.rdtech.gridadapter.installer.GridInstaller.main(GridInstaller.java:279) Error:  at com.lawson.rdtech.gridadapter.installer.GridInstaller.main(GridInstaller.java:279)         ... 6 more Error:  ... 6 more Fatal: [install-grid.pl] exit status 1 Error: Fatal: [install-grid.pl] exit status 1 Error: Activating Lawson Grid Runtime Adapter failed. **** 2016.01.29 14.38.59 RESTART Failed. showErrorAndStop called

Any thoughts on this issue would be appreciated.

Peter O
Veteran Member Send Private Message
Posts: 69
Veteran Member
2/1/2016 12:29 PM
""Caused by: java.lang.NullPointerException Error: Caused by: java.lang.NullPointerException java.lang.reflect.InvocationTargetException "" What's your Landmark version, and grid version? Null pointer exception -> someone didn't properly code to handle a null-case. InvocationTargetException -> perhaps something in the arguments passed to the grid installer weren't correct or parts were missing. It would make sense that you're missing some piece (argument to the installer, or configuration missing) if you're hitting both a null pointer and target invocation exception. Double check your configs. Read up on arguments passed to grid installer - rip apart the install-grid.pl and find out what causes an exit status of 1.
Keith Barth
Basic Member Send Private Message
Posts: 6
Basic Member
2/1/2016 4:07 PM
Digging in to that script further, we found what might be the source of this problem. The installer is grabbing the hostname of the server and populating it to the install.cfg and other files. The problem with this is that we are building it on a HA cluster and in order for it to work it has to take the name of the cluster we have defined. We have engaged Infor about this, but have not heard back on any resolution. Has anyone installed Landmark on a HA cluster? If so, how did you get around this issue?
Frank Dusek
Basic Member Send Private Message
Posts: 13
Basic Member
2/1/2016 4:27 PM
I believe we changed the 'real' hostname on the unix lpar to match the 'clustername/servicename' for the install.  Then set it back to the 'real' name.  I hope this helps.
Keith Barth
Basic Member Send Private Message
Posts: 6
Basic Member
2/2/2016 5:46 PM
I tried the changing of the hostname. The grid itself had no problem with it, but when I tried to run the reload of the Landmark application via the LANDMARK.jar, we encountered the same error as noted before (see above). So it would seem this is failing before any aspect of the failover is configured.
Keith Barth
Basic Member Send Private Message
Posts: 6
Basic Member
2/4/2016 12:51 PM
Our solution was to walk through the gridinstaller portion of the reload by hand and manually run the lines of code. It appears that the loader had problems with relative paths in the reload mode. Once we manually ran the steps, we commented the lines out of the grid-install.pl file and restarted the process. We were then able to get the reload to complete without further errors.