2005-09-1 18:00:00 AM CEST --> delgadop

Several authentication problems were caused by a expired proxy in /tmp that was used by default (insted of the one stored in myproxy).

When this proxy was removed, the problem was solved and the transfers started again.

The log level was turned back to debug, but the load seems to keep relatively low.

The original load and database problems are not completely understood yet.

2005-08-31 11:00:00 AM CEST --> delgadop

The agents of the three active channels were dead during the night, so no transfer were perfomed. The cause of the death is still to be seen.

We have restarted all the services this morning and keep studying the logs.

2005-08-30 18:00:42 AM CEST --> delgadop

During the day, we stopped the load generator and decreased the log level from debug to warn, and as consequence the load of the machine got down.

Akos also created the missing /etc/grid-security/vomsdir. That eliminated some error messages (although was not cause of real problems).

2005-08-30 11:00:42 AM CEST --> delgadop

High load was detected in lxshare026d, the transfer rate dropped a lot, the "/" partition were the tomcat logs were increased dramatically.

Akos Frohner intervened in lxshare026d to move the logs that were filling up "/" to the larger "/var". This give FTS team time to understand the real cause of the problem. He also restarted tomcat to see it that improved things... To be seen.

These are the details.

    # logs are still under /usr/share/tomcat5/logs
    # increasing priority of
    # https://savannah.cern.ch/bugs/index.php?func=detailitem&item_id=8024
    service tomcat5 stop
    # moving logs to /var
    cd /var/log
    rm tomcat5
    mkdir tomcat5
    chmod 755 tomcat5
    chown tomcat4:tomcat4 tomcat5/
    cd /var/log/tomcat5/
    mv /usr/share/tomcat5/logs/* .
    rmdir /usr/share/tomcat5/logs
    cd /usr/share/tomcat5
    ln -s /var/log/tomcat5 logs
    service tomcat5 start
        Starting tomcat5: process allready running
    # I did not start it?!
    service tomcat5 restart
    # fine.

    # loglevel kept at DEBUG due to
    # https://savannah.cern.ch/bugs/?func=detailitem&item_id=8702

-- JamieShiers - 04 Aug 2005

04-AUG-05 09:11 Please log any interventions, reverse chronological order, name and timestamp pending moving to a more permanent solution: Jamie Shiers

This topic: LCG > WebHome > LCGServiceChallenges > InterventionLogs
Topic revision: r4 - 2005-09-02 - AntonioDelgadoPeris
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback