Announcement

Collapse
No announcement yet.

Commit Failure

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    here is another one ...
    I added a new folder to the repo ... for a new project.
    Now I am trying to add and commit 3 new files to this empty folder ...... but this is the error i am getting consistently ...
    Code:
    Commit
    E:\workspace\ECI6DS\ECI6_USART_PROTOCOL.odt
    E:\workspace\ECI6DS\ECI6_USART_PROTOCOL.pdf
    E:\workspace\ECI6DS\README_INCASE_OF_DEBUGGER_ERROR.txt
    E:\workspace\ECI6DS\ECI6_USART_PROTOCOL.odt
    Commit failed (details follow):
    At least one property change failed; repository is unchanged
    '/svn/ec/!svn/wrk/75582974-e28b-ff47-a2ca-fd2b2410d28c/ECI6DS/ECI6_USART_PROTOCOL.odt'
    path not found
    I tried doing the commit again and again ... and suddenly after some number of tries , i was successfully able to commit these files .... without doing any modifications to my "steps to follow" ....except that i removed the README_INCASE_OF_DEBUGGER_ERROR.txt from the commit list .
    Last edited by rajeshdgsb; 04-16-2012, 01:13 PM.

    Comment


    • #17
      Here is an excerpt from the error log on the server side of this transaction:

      [Mon Apr 16 15:12:07 2012] [error] [client 10.22.10.126] A failure occurred while driving the update report editor [404, #160013]
      [Mon Apr 16 15:12:07 2012] [error] [client 10.22.10.126] Working copy path 'README_INCASE_OF_DEBUGGER_ERROR.txt' does not exist in repository [404, #160013]
      [Mon Apr 16 15:19:05 2012] [error] [client 10.22.10.126] A failure occurred while driving the update report editor [404, #160013]
      [Mon Apr 16 15:19:05 2012] [error] [client 10.22.10.126] Working copy path 'README_INCASE_OF_DEBUGGER_ERROR.txt' does not exist in repository [404, #160013]
      [Mon Apr 16 15:19:42 2012] [error] [client 10.22.10.126] A failure occurred while driving the update report editor [404, #160013]
      [Mon Apr 16 15:19:42 2012] [error] [client 10.22.10.126] Working copy path 'README_INCASE_OF_DEBUGGER_ERROR.txt' does not exist in repository [404, #160013]
      [Mon Apr 16 15:19:54 2012] [error] [client 10.22.10.126] A failure occurred while driving the update report editor [404, #160013]
      [Mon Apr 16 15:19:54 2012] [error] [client 10.22.10.126] Working copy path 'README_INCASE_OF_DEBUGGER_ERROR.txt' does not exist in repository [404, #160013]


      As far as I can see, it looks like Rajesh's client machine thinks there is a file "README_INCASE_OF_DEBUGGER_ERROR.txt" in the "ECI6DS" directory, but it does not actually exist on the subversion server. Looking at the "access.log" for the server, it seems that the file was deleted a little earlier:


      10.22.10.126 - rajesh [16/Apr/2012:15:19:24 +0200] "OPTIONS /svn/ec/ECI6DS HTTP/1.1" 200 142 "-" "SVN/1.6.17 (r1128011)/TortoiseSVN-1.6.16.21511 neon/0.29.6"
      10.22.10.126 - rajesh [16/Apr/2012:15:19:25 +0200] "PROPFIND /svn/ec/ECI6DS HTTP/1.1" 207 355 "-" "SVN/1.6.17 (r1128011)/TortoiseSVN-1.6.16.21511 neon/0.29.6"
      10.22.10.126 - rajesh [16/Apr/2012:15:19:25 +0200] "MKACTIVITY /svn/ec/!svn/act/b55e7a45-2dec-df41-ab46-c35ba030675e HTTP/1.1" 201 300 "-" "SVN/1.6.17 (r1128011)/TortoiseSVN-1.6.16.21511 neon/0.29.6"
      10.22.10.126 - rajesh [16/Apr/2012:15:19:26 +0200] "CHECKOUT /svn/ec/!svn/vcc/default HTTP/1.1" 201 310
      "-" "SVN/1.6.17 (r1128011)/TortoiseSVN-1.6.16.21511 neon/0.29.6"
      10.22.10.126 - rajesh [16/Apr/2012:15:19:26 +0200] "PROPPATCH /svn/ec/!svn/wbl/b55e7a45-2dec-df41-ab46-c35ba030675e/598 HTTP/1.1" 207 265 "-" "SVN/1.6.17 (r1128011)/TortoiseSVN-1.6.16.21511 neon/0.29.6"
      10.22.10.126 - rajesh [16/Apr/2012:15:19:27 +0200] "PROPFIND /svn/ec/ECI6DS HTTP/1.1" 207 244 "-" "SVN/1.6.17 (r1128011)/TortoiseSVN-1.6.16.21511 neon/0.29.6"
      10.22.10.126 - rajesh [16/Apr/2012:15:19:28 +0200] "CHECKOUT /svn/ec/!svn/ver/596/ECI6DS HTTP/1.1" 201 312 "-" "SVN/1.6.17 (r1128011)/TortoiseSVN-1.6.16.21511 neon/0.29.6"
      10.22.10.126 - rajesh [16/Apr/2012:15:19:28 +0200] "DELETE /svn/ec/!svn/wrk/b55e7a45-2dec-df41-ab46-c35ba030675e/ECI6DS/README_INCASE_OF_DEBUGGER_ERROR.txt HTTP/1.1" 404 354 "-" "SVN/1.6.17 (r1128011)/TortoiseSVN-1.6.16.21511 neon/0.29.6"
      10.22.10.126 - rajesh [16/Apr/2012:15:19:28 +0200] "DELETE /svn/ec/!svn/act/b55e7a45-2dec-df41-ab46-c35ba030675e HTTP/1.1" 204 - "-" "SVN/1.6.17 (r1128011)/TortoiseSVN-1.6.16.21511 neon/0.29.6"
      10.22.10.126 - - [16/Apr/2012:15:19:37 +0200] "OPTIONS /svn/ec/ECI6DS HTTP/1.1" 401 392 "-" "SVN/1.6.17
      (r1128011)/TortoiseSVN-1.6.16.21511 neon/0.29.6"



      This looks to me like some corruption in the local .svn metadata on Rajesh's machine. But it is odd that he has had problems on other machines too. Rajesh - can you check out the "ECI6DS" directory in a fresh directory, and see if it works okay now?

      Comment


      • #18
        Hi David ,

        The problem is that .. I tried checking in the single README_INCASE_OF_DEBUGGER_ERROR.txt , An i get a success message that says
        Code:
        Commit
        E:\workspace\ECI6DS\README_INCASE_OF_DEBUGGER_ERROR.txt
        E:\workspace\ECI6DS\README_INCASE_OF_DEBUGGER_ERROR.txt
        At revision: 599
        Now . I expect that this file has reached the svn server and now a copy of it resides in the repo ECI6DS.
        But , apart from the new revision number ... i cant see any thing new in the repo .... I cant see the file that i just committed successfully .
        when I try to do a svn update on my working copy ... i get this error

        Code:
        Update
        Working copy path 'README_INCASE_OF_DEBUGGER_ERROR.txt' does not exist in repository
        which means that ... even after the successful commit .... the file has not been added to the svn server !!!
        This has been a major problem !!!
        Infact if u see the logs @ the server side ... u will find that i have successfully commited this file 2-3 times .... but i still cant find on the server.

        Comment


        • #19
          Hi David,
          A suggestion ...rather .... a very lame one ..... can u search the server for the file README_INCASE_OF_DEBUGGER_ERROR.txt . I am skeptic if somehow the file is ending up @ some other location in the server . Though I have rechecked the commit path .....and its fine. But since we are getting a new revision number ....and when i say show log .. it shows me log until the revision number 296 only .that being the rev no when i commited the 2 previous files .. that i can see now on the repo. After that revision ....until now .. i have done 3 commits for the same file README_INCASE_OF_DEBUGGER_ERROR.txt . but i cant see it in repo ... nor can i see the rev no in the show log .That is the reason ...I am thinking may bee the file is getting added to some other folder(project) ... probably thats why the show log (for my project) does not show the rev no or the file !!!!

          Comment


          • #20
            May be this info could be of some help .....
            This is regarding the problem where i do a successful commit and get a new rev number. But when i do a svn update ..it says "file does not exist in the repo".

            in the .svn folder we have 4 other folders
            - prop-base
            - props
            - text-base
            - tmp

            Now after i do a commit and get a new rev number .....
            The text-base folder has all the files that i have checked in . But the prop-base folder do not have the files that i just commited . So i try to do a svn update ... and that is when it throws the error "file does not exist in the repo".

            Comment


            • #21
              You could try doing an update before the commit to try and resolve some of the conflicts.

              To be honest, I think you're going to continue to have problems until you bring things up to date (the working copy format has changed considerably since 1.4 and the current earliest supported version is 1.6). You'd need to update the server version and the repository format using 'svnadmin upgrade'.

              Failing that you could try downgrading the client to a 1.4 version, this may help reduce some of the problems.
              Mand Beckett
              WANdisco

              Read the WANdisco blog for Subversion, uberSVN and SmartSVN tips and tricks | Find me on Twitter

              Comment


              • #22
                Originally posted by Mand View Post
                You could try doing an update before the commit to try and resolve some of the conflicts.

                To be honest, I think you're going to continue to have problems until you bring things up to date (the working copy format has changed considerably since 1.4 and the current earliest supported version is 1.6). You'd need to update the server version and the repository format using 'svnadmin upgrade'.

                Failing that you could try downgrading the client to a 1.4 version, this may help reduce some of the problems.
                Hi Mand,
                I tried wht u said ... I tried using svn 1.4.8 on client side ...
                that now allows me at least the single file commits without error .... but still .. if i commit multiple files .. i cant find my changes .

                Comment


                • #23
                  Do you still get the same errors in the logs?
                  Mand Beckett
                  WANdisco

                  Read the WANdisco blog for Subversion, uberSVN and SmartSVN tips and tricks | Find me on Twitter

                  Comment


                  • #24
                    Originally posted by Mand View Post
                    Do you still get the same errors in the logs?
                    not sure abt the server side logs ... caus my server admin is not available for next week. But I still get the same "general svn error from server" , "Path does not exist in repo"
                    kind of errors on client side.

                    I really dont understand .... When I am creating a new file , adding and then commiting ... Obviously .. the repo will not be having that file ... because i am commiting it for the first time !!! So why does it throw the error "Path not found" ....?

                    Comment


                    • #25
                      It sames like that you are the only person got this problem, haha. why don't you go to some ask and answer sites to get your problem solved, many professional guys are there.

                      Comment


                      • #26
                        I should probably have posted this long ago when we resolved the problem, but forgot since the thread was so old. But in case anyone else reads it, we found the problem. The old version of subversion that we had on the server had a bug that could cause errors when accessed by http through a redirecting proxy. Since Rajesh (and others) accessed the server that way, there were a few corruptions in the svn database. The solution was to build a new subversion server using a newer version (which does not have that bug).

                        Comment

                        Working...
                        X