> Hi,
> I've played a little bit with my dCache admin node.
> Unless I've missed something blatantly obvious (in which case
> thanks in advance for pointing it out) the there seems to be
> no straightforward way of disabling gsidcap and dcap on admin
> nodes.
In terms of the dcache-opt service there is no difference between an "admin" node and a "pool" node. So install_doors.sh should work just fine for disabling gsidcap on the admin node.
>
> Running /opt/d-cache/install/install_doors.sh with gsidcap
> disabled on the admin node resulted in *all* doors being
> down, not just the selected ones. After a few hours of trying to
> fix this, I decided to reinstall... I wouldn't recommend running
> this script on your admin nodes.
How were you determining that the doors were down? If you've just installed the dcache-opt rpm on the admin node then the doors will be SRM,Dcap-GSI and GFTP. If you've run the install_doors script they'll be SRM-<host>, Dcap-GSI-<host> and GFTP-<host> and won't show as up on the web interface. If you want them too, you can edit the bottom of /opt/d-cache/config/httpd.batch and then restart the httpd service with
/opt/d-cache/jobs/httpd stop;/opt/d-cache/jobs/httpd -logfile=/opt/d-cache/log/http.log start
What I suspect happened is that you had the dcache-opt service running when you ran the install_doors script. The install_doors script changes the /etc/init.d script, so it was probably trying to stop services that weren't started and the ones that were started got lost.
>
> OK, here's how I've disabled dcap and gsidcap on my admin node. The
> bad news is that is is a hack, the good news is that you can reverse
> the process should you wish to re-enable the doors.
>
> Disabling dcap
> ~~~~~~~~~~~~~~
> In /opt/d-cache/config/door.batch
> I've commented out the following bunch of lines (70--82
> counting the first line as 1, not 0).
>
Or you could comment out the 2 lines that start and stop the door service in /etc/init.d/dcache-core
> Then I brutally restarted the entire dCache using my
> last-resort dCache
> script as restarting only -opt/-core wouldn't help (doors kept
> reapearing after I killed them or/and restarted).
Each java process is started by a script, if the script see its child java process end, it'll start another, kill the scripts first:
# ps aux | grep srm
root 19909 0.0 0.0 4348 1228 ? S May29 0:00 /bin/sh /opt/d-cache/jobs/srm-dcache -logfile=/opt/d-cache/log/srm-dcache.log start
root 19910 22.0 19.6 631948 404012 ? S May29 461:39 /usr/java/j2sdk1.4.2_08/bin/java -server -Xmx384m -XX:MaxDirectMemorySize=384m -Dorg.globus.tcp.port.range=50000,52000 dmg.cells.services.Domain srm-dcacheDomain -param setupFile=/opt/d-cache/config/srm-dcacheSetup ourHomeDir=/opt/d-cache ourName=srm-dcache
Derek
|