We are using SE_DPM_MYSQL and MON in the same node for quiet some time
and suddenly dropping support for such a combination is a completely
wrong approach. We dealt with port conflict by moving the srm_v1 port
and so far nothing broke. The issue is mentioned in a savannah bug which
I cannot locate right now, I dont remember the explanation why there was
this conflict with the well known for quiet some time tomcat port, but
it did not seem sufficient.
I don't see this important change into established behaviour mentioned
in the release notes or known issues, perhaps someone can point it out
to me or add it.
Adam Padee wrote:
> Hi Pawel,
> Have you EVER managed to combine SE_DPM_MYSQL with MON ?? This seems
> very strange to me, as there is port conflict between SRM_V1 and Secure
> [root@mon root]# netstat -apn --inet |grep LISTEN |grep 8443
> tcp 0 0 0.0.0.0:8443
> 0.0.0.0:* LISTEN 7609/java
> [root@mon root]#
> [root@se root]# netstat -apn --inet |grep LISTEN|grep 8443
> tcp 0 0 0.0.0.0:8443
> 0.0.0.0:* LISTEN 5128/srmv1
> [root@se root]#
> This issue has been there since the switch to Secure R-GMA, which was
> done at the end of 2005 as I remember. There has been a discussion about
> this on the list, so you can search the archives. It is possible to
> change the port number used by SRM_V1 (recipe is given in man page of
> srmv1, of course you need to publish the new port in BDII), but I don't
> know if some experiment-specific software does not rely on hard-coded
> value 8443. Maybe some expert would help?
> It is also possible to reconfigure tomcat to use some other port (
> http://tomcat.apache.org/tomcat-4.0-doc/ssl-howto.html ), but again, I
> don't know how this will affect the central services.
> I had exactly the same problem when moving to authenticated R-GMA, but I
> decided separate MON and SE to avoid non-standard setup problems. Can't
> you move your MON box to another machine?
> Best regards,
> Pawel Dziekonski wrote:
>> after last update I get this on our SE:
>> # /opt/glite/yaim/scripts/configure_node /usr/local/egee/site-info.def SE_dpm_mysql MON
>> INFO: Configuration root : /usr/local/egee
>> INFO: Global configuration in: /usr/local/egee/site-info.def
>> ERROR: the node combination MON SE is not permitted
>> i have not seen any info about this in any documentation, nor release
>> notes. we can't move MON to any other machine.. any ideas what to do
>> now besides downgrading ????
>> thanks in advance, P
GridAUTH Operations Centre @ Aristotle University of Thessaloniki , Greece
Tel: +302310998223 Fax: +302310994309