-
Notifications
You must be signed in to change notification settings - Fork 15
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
No logging info from DSI #29
Comments
Any log on the client side? Unfortunately, if the DSI crashes for any cause, the logs are not flushed to the stdout. |
Hi @bnordgren : I was also at times experiencing similar problems with nothing logged. I think this tends to happen when the dlopen of the iRODS DSI fails. With iRODS 4.x, the DSI shared-object has dependencies on the iRODS libraries ... and my only way around it was to LD_PRELOAD these dependencies into the GridFTP server (that's now in the documentation). I'd suggest you check the LD_PRELOAD is there and is working correctly... Cheers, |
Hi @vladimir-mencl-eresearch , @muccix The
My specific problem is fixed, but I'll leave this open due to the topic being the lack of logging output. |
I built the DSI against irods 4.2.0 on centos 7 (see Docker build env). I believe this container to be set up to log to
/var/log/gridftp.log
at the INFO logging level. I have also tried the "ALL" logging level, with no difference.I'm attempting a directory listing of my home directory with
globus-url-copy
. It fails. But all that is logged to/var/log/gridftp.log
is:[6] Sat Dec 23 19:04:47 2017 :: Child process 21 ended with rc = 11
This ticket isn't so much about my actual error as it is about the fact that no useful information is logged even at the "ALL" level.
Note you can't directly run a container from an image generated from the docker build above. The intent is that you use the image above in the FROM line of an environment-specific Dockerfile, where you make the
irods
service account authenticate as therods
user in your zone, and perform other configurations specific to your deployment. However, the above build environment has everything related to this ticket.The text was updated successfully, but these errors were encountered: