Menu

Failed to create new MetaData cache

Help
2005-03-18
2013-04-02
  • Leandro de Almeida

    When I access the cvsmonitor.pl for the first time, and set admin password, cache and static directories, I've got the errors:

    Failed to create new MetaData cache
    Could not determine the CVS version

    I set the cache directory as /www/cache, and I took a look at that, and I found out that it's created a directory /www/cache/CVSMonitor_MetaData_0_6, but it's empty. And webserver user has full access on it.

    This is a bug? Does somebody can help me in that?

    Thanks a lot.

     
    • William McKee

      William McKee - 2005-03-18

      This looks like it may be a problem with your CVS install. What does 'cvs -v' return?

       
    • Leandro de Almeida

      I'm using CVSNT, and I'm installing cvsmonitor at the same server.

      the command 'cvs -v' has the output:

      [root@web root]# cvs -v

      Concurrent Versions System (CVSNT) 2.0.58d (client/server)

      Copyright (c) 1989-2001 Brian Berliner, david d `zoo' zuhn,
                              Jeff Polk, and other authors
      CVSNT version (Nov  1 2004) Copyright (c) 1999-2004 Tony Hoyle and others
      see http://www.cvsnt.org

      Commercial support and training provided by March Hare Software Ltd.
      see http://www.cvsnt.com

      CVS may be copied only under the terms of the GNU General Public License,
      a copy of which can be found with the CVS distribution kit.

      SSH connectivity provided by PuTTY:
        PuTTY is copyright 1997-2001 Simon Tatham.
        Portions copyright Robert de Bath, Joris van Rantwijk, Delian
        Delchev, Andreas Schultz, Jeroen Massar, Wez Furlong, Nicolas Barry,
        Justin Bradford, and CORE SDI S.A.
        see http://www.chiark.greenend.org.uk/~sgtatham/putty/

      Specify the --help option for further information about CVS

      Can I change the script to get the right parameter?^
      Did you know if I can use cvsmonitor with CVSNT?

      Thanks a lot.

      Leandro

       
      • William McKee

        William McKee - 2005-03-18

        You must have missed the line in the requirements[1] which states that the module does not work under Windows. If you want to try debugging it, I suspect the script is having problems parsing the output from cvsnt.

        Good luck,
        William

        [1] http://ali.as/devel/cvsmonitor/requirements.html

         
    • Leandro de Almeida

      But I'm running the cvsmonitor on a RedHat linux. I'm using CVSNT for linux.
      Do you know if I can use cvsmonitor and cvsnt (in linux) together?

      Thanks,

      Leandro.

       
      • William McKee

        William McKee - 2005-03-18

        Oh, I thought that cvsnt meant cvs for WinNT. I have no idea if cvsmonitor can work with cvsnt. From your experience, I'd say it doesn't. You could probably patch it if you know enough Perl. I'd suspect it is misreading the output of cvs -v or something.

         
    • David Wimsey

      David Wimsey - 2005-03-20

      Here are the respective -v differences.  CVSNT is cvs with some nice additions, namely encrypted connections, moves, renaming, ect.  Its been around for some time, its considered a drop in replacement for CVS as it respects all the cvs commandline options and as far as I know is backwards compatible with the standard cvs client.  Probably just the 2.0.5 version number is tripping something up.  This is effecting me too unfortunately.

      dwimsey@gearloose (~)% /usr/bin/cvs -v

      Concurrent Versions System (CVS) 1.11.17-FreeBSD (client/server)

      Copyright (c) 1989-2004 Brian Berliner, david d `zoo' zuhn,
                              Jeff Polk, and other authors

      CVS may be copied only under the terms of the GNU General Public License,
      a copy of which can be found with the CVS distribution kit.

      Specify the --help option for further information about CVS

      dwimsey@gearloose (~)% /usr/local/bin/cvs -v

      Concurrent Versions System (CVSNT) 2.0.58d (client/server)

      Copyright (c) 1989-2001 Brian Berliner, david d `zoo' zuhn,
                              Jeff Polk, and other authors
      CVSNT version (Mar 11 2005) Copyright (c) 1999-2004 Tony Hoyle and others
      see http://www.cvsnt.org

      Commercial support and training provided by March Hare Software Ltd.
      see http://www.cvsnt.com

      CVS may be copied only under the terms of the GNU General Public License,
      a copy of which can be found with the CVS distribution kit.

      SSH connectivity provided by PuTTY:
        PuTTY is copyright 1997-2001 Simon Tatham.
        Portions copyright Robert de Bath, Joris van Rantwijk, Delian
        Delchev, Andreas Schultz, Jeroen Massar, Wez Furlong, Nicolas Barry,
        Justin Bradford, and CORE SDI S.A.
        see http://www.chiark.greenend.org.uk/~sgtatham/putty/

      Specify the --help option for further information about CVS

      dwimsey@gearloose (~)% uname -a
      FreeBSD gearloose.rtsz.com 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #0: Thu Mar 10 06:49:09 UTC 2005     dwimsey@gearloose.rtsz.com:/usr/obj/usr/src/sys/GENERIC  i386

       
    • David Wimsey

      David Wimsey - 2005-03-20

      If you just temporarly put normal cvs in the path rather than cvsnt during the setup stage, cvs monitor will continue with no problems, after setup is complete you can move cvsnt back into path as normal and cvs monitor will continue to function.

      It seems to work fine for me after works, using CVSNT 2.0.58d, I did notice these options in the PServer config file however that may be note worthy should you notice any problems

      # Compatibility levels - currently:
      # 0 = Legacy cvs (cvshome.org cvs, eclipse)
      # 1 = cvsnt (cvsnt client, wincvs, tortoisecvs, etc.)

      #
      # Compat<n>_OldVersion  Pretend to be a Unix CVS version (1.11.1).  Keeps some
      #                       picky frontends happy (eg. Eclipse)
      #Compat0_OldVersion=1

      #
      # Compat<n>_HideStatus  Hide extended stats/log information (mergepoints, commi$
      #
      #Compat0_HideStatus=0

      #
      # Compat<n>_OldCheckout Implement the old '-n update' behaviour
      #
      #Compat0_OldCheckout=0

       
    • Leandro de Almeida

      I found a work around to this problem, as David wrote before.

      I changed the functions 'cvs location' and 'cvs version' in modules/CVSMonitor/MetaData.pm, to point to a 'normal' cvs in an absolute path, and it's works fine.

      The functions are like this:

      # Find the installed location of CVS.
      # Returns the location of CVS on success.
      # Returns undef if CVS not found.
      sub cvslocation {
              my $self = shift;
              #my @location = `which cvs`;
              my @location = `ls /www/cvsmonitor/cvs`;
              scalar @location
                      ? chomp($location[0])
                      : undef;
      }

      # Get the version of the CVS client.
      # Returns the version if we can find it.
      # Returns undef if cannot find version.
      sub cvsversion {
              my $self = shift;
              my @output = `/www/cvsmonitor/cvs -v`;
              chomp(@output);
              if ( $output[1] =~ /\b(1\.[\d\.p]+)/ ) {
                      return $1;
              } else {
                      return undef;
              }
      }

      I changed on @location and @output. in my case, the cvs alternate program are located at the same diretory of the cvsmonitor files.

      Thanks you guys for the help.

      Leandro.

       

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.