[p4] cvs2p4: troubleshooting [signed]

[Gabor Maghera]

The error log indicates that it may be running the Perforce server (p4d)
which is failing, possibly due to bad metadata generated with genmetadata.

This line:
*/usr/bin/p4d -r . -jr dbmeta
*attempts to start p4d and restore metadata from checkpoint and/or journal.

I would test the install of p4d separately from running the cvs2p4 script,
to make sure it is OK.  The fact that the test conversion provided with the
script is failing is an indication of a configuration/environment issue.

Cheers,
Gabor
*
*On Nov 14, 2007 2:25 AM, Mamadou Cisse [c] <mcisse at acquisinc.com> wrote:

> Yes, I did!
>
> Gabor Maghera wrote:
> > Have you recompiled RCS 5.7 to create the patched/modified version of
> rlog?
> >
> > Gabor
> >
> > On Nov 13, 2007 9:02 AM, Mamadou Cisse [c] <mcisse at acquisinc.com> wrote:
> >
> >> I'm trying to use cvs2p4 to migrate a cvsNT repository to Perforce on a
> >> Ubuntu Dapper box.
> >> I couldn't get the test/runtest script to run properly. It always came
> >> back with a "bad results" from the bin/genmetadata script.
> >> Being unable to find out why, I've decided to try my luck with the
> >> bin/cvs2p4 script. This one is throwing the error:
> >> [[
> >> Journal file 'dbmeta' replay failed at line <num>!
> >> Word too big fo a number!
> >> ]]
> >> I've been scouring the web for answers for the last week or so and
> >> couldn't find any clear understanding of the causes or the remedies.
> >>
> >> Can anybody help with some sample?
> >>
> >>
> >> ========== change group 1
> >> dochanges> cd /tmp/cvs2p4-3.0b6/p4root && /usr/bin/p4d -r . -jr dbmeta
> >> Perforce db files in '.' will be created if missing...
> >> Recovering from dbmeta...
> >> dochanges: *** "cd /tmp/cvs2p4-3.0b6/p4root && /usr/bin/p4d -r . -jr
> >> dbmeta" exited with signal 0 status 255
> >> dochanges: "/usr/bin/p4d -r . -jr dbmeta" failed.
> >> *** dochanges  FAILED
> >>
> >>
> >> Best Regards,
> >> mcisse.
> >>
> >>
> > _______________________________________________
> > perforce-user mailing list  -  perforce-user at perforce.com
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
> >
> >
> >
>
>
> --
> --------------------- [ SECURITY NOTICE ] ---------------------
> To: perforce-user at perforce.com.
> For your security, mcisse at acquisinc.com
> digitally signed this message on 14 November 2007 at 10:23:47 UTC.
> Verify this digital signature at http://www.ciphire.com/verify.
> ---------------- [ CIPHIRE DIGITAL SIGNATURE ] ----------------
> Q2lwaGlyZSBTaWcuAjhwZXJmb3JjZS11c2VyQHBlcmZvcmNlLmNvbQBtY2lzc2VA
> YWNxdWlzaW5jLmNvbQBlbWFpbCBib2R5AK4EAAB8AHwAAAABAAAAs8w6R64EAAAv
> AwACAAIAAgAgcT1B7ulrTbhgQFnPbu4QFcLOLXgm/ESnUgjBntK1lDcBAB96H8yw
> x1/YImyCYuRnwVi/WOzx5APTVBtika+ZsH9PD+4Yoja3gcvlnZW7Qor72rUZBCmW
> PqbAUS+shxV9QlNyU2lnRW5k
> ------------------ [ END DIGITAL SIGNATURE ] ------------------
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>