You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've found a bug in the init script for the GridFTP server in current versions of the globus-gridftp-server-progs RPM for RHEL 6. Not sure if that's been fixed in your fork, but I wanted to make you aware in case.
Whenever this script is run with the status option (/etc/init.d/globus-gridftp server status) the status is correctly reported, but the return code is always 0. This isn't a problem until someone tries to use Pacemaker to manage GridFTP services. The incorrect return code causes Pacemaker to always think the GridFTP service is running, so it never gets started.
The following hack makes the script return an exit value correctly when the status parameter is passed.
I've found a bug in the init script for the GridFTP server in current versions of the globus-gridftp-server-progs RPM for RHEL 6. Not sure if that's been fixed in your fork, but I wanted to make you aware in case.
Whenever this script is run with the status option (/etc/init.d/globus-gridftp server status) the status is correctly reported, but the return code is always 0. This isn't a problem until someone tries to use Pacemaker to manage GridFTP services. The incorrect return code causes Pacemaker to always think the GridFTP service is running, so it never gets started.
The following hack makes the script return an exit value correctly when the status parameter is passed.
The text was updated successfully, but these errors were encountered: