-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to register at portmap: portmap service not available #48
Comments
Do we just remove this line? irods_client_nfsrods/irods-vfs-impl/src/main/java/org/irods/nfsrods/vfs/ServerMain.java Line 80 in 1575255
|
It should probably remain, but configurable, and possibly default off.
|
this may have been resolved. is anyone still seeing this message following recent releases? |
I thought I had seen it with 1.0.0... do you not? |
it didn't show up in my last test of nfsrods. i need to verify that though. |
confirmed with
|
Installing the |
Hi 👋 We are trying to deploy this NFS client on our iRODS zone (currently my local test environment). All our services run in Docker containers, so I tried to run the Docker image as explained in the When I start the container, here are the logs:
After searching for a bit, I found the present issue and this commit. It seems that the modifications from this commit are not in the current repository. I thus proceeded to add
When I try to mount on another host/container using:
Do you have any idea why this does not work? Is there a reason why these lines are not included in the sources anymore? |
The reason the changes in that commit for rpcbind aren't included is because of #155. We bumped the OS image to Ubuntu 22.04 for NFSRODS v2.2.0. In all of my testing, the message about portmap never appeared to affect NFSRODS' operation. We aren't sure what causes that message yet. For now, it has remained a low priority item since there's no evidence of it having a negative impact on usage. As for the mount error, please explain your setup between computers, containers, and where the mount command is being run. |
Thanks for the link to #155. Since it evicted NFSRODS from the list of the suspects for the mounting error, I investigated other mounts inside containers. It turns out mounting from within a container requires additional privileges. Adding the Sorry for bringing this issue back to life. |
Glad you got it working. |
If NFSRODS is not meant to be able to register at portmap in the container, then it should be configured to not attempt to register at portmap. Otherwise, this WARN is noise that might lead an admin to believe something is wrong.
The text was updated successfully, but these errors were encountered: