ghidra: RepositoryServerHandle.isReadOnly() throws java.io.IOException

Stood up ghidra as a server and set up PKI auth. Looks like I’m able to authenticate but then this error occurs before the login process finishes. I’m guessing the issue is file/folder permissions. The user that is running the ghidra server is the owner of both the ghidra home and the ghidra project repository folders so I’m kind of at a lost.

An error occured on the server (<redacted>:13100).
Method is not Remote: interface ghidra.framework.remote.RepositoryServerHandle::public abstract boolean ghidra.framework.remote.RepositoryServerHandle.isReadOnly() throws java.io.IOException
java.rmi.RemoteException: Method is not Remote: interface ghidra.framework.remote.RepositoryServerHandle::public abstract boolean ghidra.framework.remote.RepositoryServerHandle.isReadOnly() throws java.io.IOException
	at java.rmi/java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:214)
	at java.rmi/java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:162)
	at com.sun.proxy.$Proxy22.isReadOnly(Unknown Source)
	at ghidra.framework.client.ServerConnectTask.getRepositoryServerHandle(ServerConnectTask.java:290)
	at ghidra.framework.client.ServerConnectTask.run(ServerConnectTask.java:72)
	at ghidra.util.task.Task.monitoredRun(Task.java:126)
	at ghidra.util.task.TaskRunner.lambda$startTaskThread$1(TaskRunner.java:94)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:830)

---------------------------------------------------
Build Date: 2019-Dec-18 1306 EST
Ghidra Version: 9.1.1
Java Home: /Library/Java/JavaVirtualMachines/jdk-13.0.2.jdk/Contents/Home
JVM Version: Oracle Corporation 13.0.2
OS: Mac OS X <redacted>
Workstation: <redacted>

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 4
Comments: 17 (3 by maintainers)

Most upvoted comments

The fix for this should be rolling out soon. FYI, the jdk major version number isn’t the issue, but the minor numbers would be a better indicator, as it was a change in the RMI logic that was committed in the jdk source tree just a few months ago (in October). I’m guessing that change was then incorporated into the different major number builds (11, 12, 13, etc) as one of the minor-ver-number updates.

dev747368 on Feb 4, 2020