Transactions and permissions
Email notifications
You may tailor the notifications you get by going to:
https://VOMRSserver:8443/vo/VOName/vomrs?path=/RootNode/Subscribtion&action=execute
Examples:
DTEAM
CERN Test VO
If you have email filters to put messages in folders, this is, most probably the only "Subject" that will require action from you as VO Admins:
Subject: Member has requested the addition of a new certificate - approval required
Actions when VO member's certificate changes
Installation and configuration help on the GOC wiki
User unknown to this VO
How to check if a user is in the CERN ORGDB view (LHC Experiment VOs only)
Login as root on the test vom(r)s installation tbed0152.cern.ch:
cd /opt/lcg_check_registration/bin
run
./check_user.sh <last_name>
e.g
./check_user.sh dimou
will return:
WARN [main] Could not find ch.cern.lcg.registration.configdir in system properties. - configuration.Configuration
INFO [main] Resource dir /opt/lcg/etc/registration added to source path - utilities.Resource
INFO [main] log4j.properties loaded from classpath - utilities.Resource
INFO [main] lcg-registration.database.properties loaded from classpath - utilities.Resource
INFO [main] Booting user information interface for LCG registration - configuration.Configuration
INFO [main] Loaded JDBC driver oracle.jdbc.driver.OracleDriver - database.ConnectionPool
INFO [main] Created query pool - database.QueryPool
INFO [main] Created new query connection: connection #1 in query pool - database.QueryPool
Name DIMOU
First name MARIA
Email Maria.Dimou@cern.ch
Physical Email dimou@mail.cern.ch
Experiment CMS
LHC Experiment VO user registration failed in vomrs
lcg registration database configuration file /opt/vomrs-1.3/var/etc/vomrs_
/lcg-registration.database.properties should belongs to tomcat
e.g.
cd /opt/vomrs-1.3/var/etc/vomrs_cms
chown tomcat4:tomcat4 lcg-registration.database.properties
Otherwise, user will encounter the following error when registratering Phase I
java.lang.NoClassDefFoundError
ch.cern.lcg.registration.Experiment.matchMembers(Experiment.java:292)
ch.cern.lcg.registration.Experiment.matchMember(Experiment.java:340)
fnal.vox.vomrs.lcg.LCG.fill(Unknown Source)
fnal.vox.vomrs.tables.PersonalInfos.addInternalPI(Unknown Source)
fnal.vox.vomrs.database.RegisterMember.doActionImpl(Unknown Source)
fnal.vox.vomrs.tables.DBTablesBase.doAction(Unknown Source)
fnal.vox.vomrs.database.ServiceBroker.executeService(Unknown Source)
fnal.vox.vomrs.services.VOMRSSoapBindingImpl.execute(Unknown Source)
fnal.vox.vomrs.services.VOMRSSoapBindingImpl.registerMember(Unknown Source)
fnal.vox.vomrs.webui.MemberPhaseIRegistration.register(Unknown Source)
fnal.vox.vomrs.webui.MemberPhaseIRegistration.execute(Unknown Source)
fnal.vox.vomrs.webui.PageGenerator.print_content(Unknown Source)
fnal.vox.vomrs.webui.PageGenerator.generate_page(Unknown Source)
fnal.vox.vomrs.webui.PageGenerator.doGetPost(Unknown Source)
fnal.vox.vomrs.webui.PageGenerator.doPost(Unknown Source)
javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
VOMRS host certificate DN change
Such a change make synchronisation with VOMS fail, because, in order to allow VOMRS to synchronise with VOMS, we added a global acl entry which grants administrator rigths to the host certificate of VOMRs (lcg-voms.cern.ch).
So, in this case, you have to modify the ACL entry in order to replace the VOMRS host DN (and maybe its CA) with the new one. To do that, there are several ways :
- Use VOMS-Admin : 'Administer the VO' -> 'Global ACL', and modify the corresponding entry for all VOs.
- Or, if you can't access this page, but have the DB password, you can use the Perl script 'fix-vomrs_host_dn.pl' which is attached to this page. (See at the bottom)
-- Main.dimou - 07 Jun 2006