Hi,
the problem is an auto-updating of the field "creationTime" when any other
field of the same table is updated.
The creamdb is scratched by yaim only under well defined conditions.
In the Daniela's scenario, the creamdb is not scratched.
Please, see https://ggus.eu/tech/ticket_show.php?ticket=85970
Cheers,
E r i c.
On Mon, 10 Sep 2012 15:50:52 +0200, Andreas Haupt wrote
> Hi Daniela,
>
> On Fri, 2012-09-07 at 15:35 +0100, Daniela Bauer wrote:
> > Also, not to rain on anyone's parade, but we've had several instances
> > were rerunning yaim on an EMI2 CREAMCE scraped the creamdb and we
> > haven't gotten to the bottom of it yet.
>
> this is probably the reason:
>
> [root@nero-vm4 ~]# rpm -qf /etc/glite-ce-cream/populate_creamdb_mysql.sql
> glite-ce-cream-1.14.0-4.sl6.noarch
> [root@nero-vm4 ~]# head -n 8 /etc/glite-ce-cream/populate_creamdb_mysql.sql
> /************ Drop: Database ***************/
> DROP DATABASE IF EXISTS creamdb;
>
> /************ Create: Database ***************/
> CREATE DATABASE creamdb;
>
> /************ Use: Database ***************/
> USE creamdb;
>
> This script is called by /opt/glite/yaim/functions/config_cream_db
> everytime yaim runs ...
>
> I wonder if someone documented that rerunning yaim is now connected with
> a (longer) downtime of the service. This wasn't the case in gLite times.
> But now it seems scripts have been developed with exactly this
> deficit in mind :-(
>
> Cheers,
> Andreas
> --
> | Andreas Haupt | E-Mail: [log in to unmask]
> | DESY Zeuthen | WWW: http://www-zeuthen.desy.de/~ahaupt
> | Platanenallee 6 | Phone: +49/33762/7-7359
> | D-15738 Zeuthen | Fax: +49/33762/7-7216
|