You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by JP Slavinsky <jp...@gmail.com> on 2008/08/21 23:02:46 UTC
"Commit failed" / "Invalid UTF-8 sequence" messages when doing a commit in SVN 1.5.1
Howdy,
My problem: every time I commit to the repository, I get a "Commit failed"
message talking about an "invalid UTF-8 sequence". While the message says
that the commit failed, the commit is actually always successful in the
repository. However, on the client-side (both command line and Subclipse),
the working copy isn't up-to-date and calls to update seem to produce lots
of issues (conflicts, etc).
My setup: yesterday, I upgraded from from SVN 1.4.4 to SVN 1.5.1. I built
1.5.1 from source, as I did for 1.4.4. I access my repositories over HTTP
using Apache 2.0.59. The SVN server is on RedHat 4. Things in 1.4.4 used to
work fine, both from a linux command line and from Eclipse/Subclipse on
Windows. Now, both the command line and subclipse attempts at committing
give the error message described above and in the example below.
My fellow users recently experiencing similar (if not exactly the same)
problems
http://svn.haxx.se/users/archive-2008-08/0444.shtml
http://svn.haxx.se/users/archive-2008-08/0725.shtml
(For the life of me I couldn't figure out how to add to their threads -
sorry about that).
Any thoughts on why this error is being presented and how to get rid of it?
Below, I have pasted a log of the steps I take to reproduce the problem. I
create a repository, check it out, add a file, do a commit (which gives the
nasty error message), show that my client doesn't believe the commit worked,
then show that the repository has indeed been updated.
--------------------------------------------------
[root@cutlass v1.5]$ svnadmin create sandbox
[root@cutlass v1.5]$ chown -R apache:apache sandbox
[root@cutlass v1.5]$ exit
[slavinsk@cutlass v1.5]$ cd ~/temp/workspace/
[slavinsk@cutlass workspace]$ svn co http://localhost/svn/sandbox
Authentication realm: <http://localhost:80> Sandbox SVN Repository (v1.5)
Password for 'slavinsk':
Checked out revision 0.
[slavinsk@cutlass workspace]$ cd sandbox/
[slavinsk@cutlass sandbox]$ touch test.txt
[slavinsk@cutlass sandbox]$ svn add test.txt
A test.txt
[slavinsk@cutlass sandbox]$ svn commit -m "Committing a dummy file"
Adding test.txt
Transmitting file data .svn: Commit failed (details follow):
svn: Valid UTF-8 data
(hex: 1c)
followed by invalid UTF-8 sequence
(hex: a4 01)
[slavinsk@cutlass sandbox]$ svn status
A test.txt
[slavinsk@cutlass sandbox]$ svnlook tree /svn/v1.5/sandbox
/
test.txt
--------------------------------------------------
Re: "Commit failed" / "Invalid UTF-8 sequence" messages when doing a
commit in SVN 1.5.1
Posted by Steve Whitson <st...@gmail.com>.
JP Slavinsky wrote:
> Howdy,
>
> My problem: every time I commit to the repository, I get a "Commit
> failed" message talking about an "invalid UTF-8 sequence". While the
> message says that the commit failed, the commit is actually always
> successful in the repository. However, on the client-side (both
> command line and Subclipse), the working copy isn't up-to-date and
> calls to update seem to produce lots of issues (conflicts, etc).
>
> My setup: yesterday, I upgraded from from SVN 1.4.4 to SVN 1.5.1.
> <http://1.5.1.> I built 1.5.1 from source, as I did for 1.4.4.
> <http://1.4.4.> I access my repositories over HTTP using Apache
> 2.0.59. <http://2.0.59.> The SVN server is on RedHat 4. Things in
> 1.4.4 used to work fine, both from a linux command line and from
> Eclipse/Subclipse on Windows. Now, both the command line and
> subclipse attempts at committing give the error message described
> above and in the example below.
>
> My fellow users recently experiencing similar (if not exactly the
> same) problems
> http://svn.haxx.se/users/archive-2008-08/0444.shtml
> http://svn.haxx.se/users/archive-2008-08/0725.shtml
> (For the life of me I couldn't figure out how to add to their threads
> - sorry about that).
>
> Any thoughts on why this error is being presented and how to get rid
> of it?
>
> Below, I have pasted a log of the steps I take to reproduce the
> problem. I create a repository, check it out, add a file, do a commit
> (which gives the nasty error message), show that my client doesn't
> believe the commit worked, then show that the repository has indeed
> been updated.
>
> --------------------------------------------------
> [root@cutlass v1.5]$ svnadmin create sandbox
> [root@cutlass v1.5]$ chown -R apache:apache sandbox
> [root@cutlass v1.5]$ exit
> [slavinsk@cutlass v1.5]$ cd ~/temp/workspace/
> [slavinsk@cutlass workspace]$ svn co http://localhost/svn/sandbox
> Authentication realm: <http://localhost:80> Sandbox SVN Repository (v1.5)
> Password for 'slavinsk':
> Checked out revision 0.
> [slavinsk@cutlass workspace]$ cd sandbox/
> [slavinsk@cutlass sandbox]$ touch test.txt
> [slavinsk@cutlass sandbox]$ svn add test.txt
> A test.txt
> [slavinsk@cutlass sandbox]$ svn commit -m "Committing a dummy file"
> Adding test.txt
> Transmitting file data .svn: Commit failed (details follow):
> svn: Valid UTF-8 data
> (hex: 1c)
> followed by invalid UTF-8 sequence
> (hex: a4 01)
> [slavinsk@cutlass sandbox]$ svn status
> A test.txt
> [slavinsk@cutlass sandbox]$ svnlook tree /svn/v1.5/sandbox
> /
> test.txt
> --------------------------------------------------
I don't have any solution but this looks like the same problem I've been
experiencing (noted in two different message threads - my two different
threads differ with regard to the error message seen corresponding to
different apache version).
one message thread is subject: Can't convert string from native
encoding to 'UTF-8' - subversion 1.5.1 with apache 2.03 on linux
the other message thread is subject: Valid UTF-8 data ... followed
by invalid UTF-8 sequence (*this one notes the identical error JP
Slavinsky has)
Re: "Commit failed" / "Invalid UTF-8 sequence" messages when doing
a commit in SVN 1.5.1
Posted by Steve Whitson <st...@gmail.com>.
Steve Whitson wrote:
> Anthony Cagle wrote:
>>> Below I've include a sample of the apache error log. Is anyone else having
>>> problems with SVN 1.5.1 and Apache 2
>>>
>>
>> Yes, I'm having the same problem. I have no solution.
>>
>>
> As previously noted, I too am having the same problem with no solution.
>
> Interesting thing I found, after grabbing the latest subversion source
> (from trunk) it states the apr version in my 2.0.63 apache is too
> old. I suspected that this might be the case. I wasn't able to get
> apache 2.0.63 to build with apr & apr-util 1.2+ (I believe they aren't
> compatible, but haven't exactly substantiated this with
> documentation). I also cannot get subversion 1.5.1 to build against
> apr & apr-util 0.9.7 or 0.9.12.
>
> I do see that according to the subversion 1.5.1 INSTALL document that
> subversion is suppose to be compatible with apr 0.9.7.
Submitted bug (after figuring out how) 3273
<http://subversion.tigris.org/issues/show_bug.cgi?id=3273>
Re: "Commit failed" / "Invalid UTF-8 sequence" messages when doing
a commit in SVN 1.5.1
Posted by Steve Whitson <st...@gmail.com>.
Anthony Cagle wrote:
>> Below I've include a sample of the apache error log. Is anyone else having
>> problems with SVN 1.5.1 and Apache 2
>>
>
> Yes, I'm having the same problem. I have no solution.
>
>
As previously noted, I too am having the same problem with no solution.
Interesting thing I found, after grabbing the latest subversion source
(from trunk) it states the apr version in my 2.0.63 apache is too old.
I suspected that this might be the case. I wasn't able to get apache
2.0.63 to build with apr & apr-util 1.2+ (I believe they aren't
compatible, but haven't exactly substantiated this with documentation).
I also cannot get subversion 1.5.1 to build against apr & apr-util 0.9.7
or 0.9.12.
I do see that according to the subversion 1.5.1 INSTALL document that
subversion is suppose to be compatible with apr 0.9.7.
Re: "Commit failed" / "Invalid UTF-8 sequence" messages when doing a commit in SVN 1.5.1
Posted by Anthony Cagle <da...@gmail.com>.
> Below I've include a sample of the apache error log. Is anyone else having
> problems with SVN 1.5.1 and Apache 2.0.x?
Yes, I'm having the same problem. I have no solution.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: "Commit failed" / "Invalid UTF-8 sequence" messages when doing a commit in SVN 1.5.1
Posted by JP Slavinsky <jp...@gmail.com>.
On Fri, Aug 22, 2008 at 6:07 AM, Daniel Shahaf <d....@daniel.shahaf.name>wrote:
> JP Slavinsky wrote on Thu, 21 Aug 2008 at 16:02 -0700:
> > Howdy,
> >
> > My problem: every time I commit to the repository, I get a "Commit
> failed"
> > message talking about an "invalid UTF-8 sequence". While the message
> says
> > that the commit failed, the commit is actually always successful in the
> > repository. However, on the client-side (both command line and
> Subclipse),
> > the working copy isn't up-to-date and calls to update seem to produce
> lots
> > of issues (conflicts, etc).
> >
> > My setup: yesterday, I upgraded from from SVN 1.4.4 to SVN 1.5.1. I
> built
> > 1.5.1 from source, as I did for 1.4.4. I access my repositories over
> HTTP
> > using Apache 2.0.59. The SVN server is on RedHat 4. Things in 1.4.4
> used to
> > work fine, both from a linux command line and from Eclipse/Subclipse on
> > Windows. Now, both the command line and subclipse attempts at committing
> > give the error message described above and in the example below.
> >
> > My fellow users recently experiencing similar (if not exactly the same)
> > problems
> > http://svn.haxx.se/users/archive-2008-08/0444.shtml
> > http://svn.haxx.se/users/archive-2008-08/0725.shtml
> > (For the life of me I couldn't figure out how to add to their threads -
> > sorry about that).
> >
> > Any thoughts on why this error is being presented and how to get rid of
> it?
> >
> > Below, I have pasted a log of the steps I take to reproduce the problem.
> I
> > create a repository, check it out, add a file, do a commit (which gives
> the
> > nasty error message), show that my client doesn't believe the commit
> worked,
> > then show that the repository has indeed been updated.
> >
>
> Thanks for the transcript, very helpful (and saves a bunch of questions).
>
> > --------------------------------------------------
> > [root@cutlass v1.5]$ svnadmin create sandbox
>
> Does the error go away if you create a BDB repository instead?
>
> > [root@cutlass v1.5]$ chown -R apache:apache sandbox
> > [root@cutlass v1.5]$ exit
> > [slavinsk@cutlass v1.5]$ cd ~/temp/workspace/
> > [slavinsk@cutlass workspace]$ svn co http://localhost/svn/sandbox
> > Authentication realm: <http://localhost:80> Sandbox SVN Repository
> (v1.5)
> > Password for 'slavinsk':
> > Checked out revision 0.
> > [slavinsk@cutlass workspace]$ cd sandbox/
> > [slavinsk@cutlass sandbox]$ touch test.txt
> > [slavinsk@cutlass sandbox]$ svn add test.txt
> > A test.txt
> > [slavinsk@cutlass sandbox]$ svn commit -m "Committing a dummy file"
> > Adding test.txt
> > Transmitting file data .svn: Commit failed (details follow):
> > svn: Valid UTF-8 data
> > (hex: 1c)
> > followed by invalid UTF-8 sequence
> > (hex: a4 01)
>
> All reports of this error have "a4 01" as the non-UTF-8 sequence.
>
> > [slavinsk@cutlass sandbox]$ svn status
> > A test.txt
> > [slavinsk@cutlass sandbox]$ svnlook tree /svn/v1.5/sandbox
> > /
> > test.txt
> > --------------------------------------------------
> >
>
Daniel -- thanks for the response. I don't believe that have the Berkeley
DB option available, so I don't know if there is a problem when using it.
For me, all reports of the invalid UTF-8 sequence do have "a4 01".
Below I've include a sample of the apache error log. Is anyone else having
problems with SVN 1.5.1 and Apache 2.0.x?
[...] Could not MERGE resource
"/svn/sandbox/!svn/act/026bfc8d-63e8-4f49-91c5-75958fdd7e1b" into
"/svn/sandbox/trunk". [409, #0]
[...] An error occurred while committing the transaction. [409, #22]
[...] Valid UTF-8 data\n(hex: 1c)\nfollowed by invalid UTF-8 sequence\n(hex:
a4 01) [409, #22]
[...] Could not DELETE
/svn/sandbox/!svn/act/026bfc8d-63e8-4f49-91c5-75958fdd7e1b. [500, #0]
[...] could not open transaction. [500, #2]
[...] Can't open file '/svn/v1.5/sandbox/db/transactions/1-1.txn/props': No
such file or directory [500, #2]
[...] Could not MERGE resource
"/svn/sandbox/!svn/act/181a52d4-37fe-443d-82f9-2cfb1109c5bf" into
"/svn/sandbox/trunk". [409, #0]
[...] An error occurred while committing the transaction. [409, #22]
[...] Valid UTF-8 data\n(hex: 1c)\nfollowed by invalid UTF-8 sequence\n(hex:
a4 01) [409, #22]
[...] Could not DELETE
/svn/sandbox/!svn/act/181a52d4-37fe-443d-82f9-2cfb1109c5bf. [500, #0]
[...] could not open transaction. [500, #2]
[...] Can't open file '/svn/v1.5/sandbox/db/transactions/2-2.txn/props': No
such file or directory [500, #2]
[...] Could not CHECKOUT resource /svn/sandbox/!svn/ver/2/trunk/test.txt.
[409, #0]
[...] resource out of date; try updating [409, #160024]
[...] Could not DELETE
/svn/sandbox/!svn/act/1f07b546-b721-474f-9c82-8c41de1c10e9. [500, #0]
[...] could not abort transaction. [500, #22]
[...] Transaction cleanup failed [500, #22]
[...] Valid UTF-8 data\n(hex: 1c)\nfollowed by invalid UTF-8 sequence\n(hex:
a4 01) [500, #22]
[...] Could not MERGE resource
"/svn/sandbox/!svn/act/10990bbe-b92d-41a7-acca-c752915a8dca" into
"/svn/sandbox/trunk". [409, #0]
where "[...]" is "[TimeStamp] [error] [client 127.0.0.1]"
Thanks, JP
Re: "Commit failed" / "Invalid UTF-8 sequence" messages when doing
a commit in SVN 1.5.1
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
JP Slavinsky wrote on Thu, 21 Aug 2008 at 16:02 -0700:
> Howdy,
>
> My problem: every time I commit to the repository, I get a "Commit failed"
> message talking about an "invalid UTF-8 sequence". While the message says
> that the commit failed, the commit is actually always successful in the
> repository. However, on the client-side (both command line and Subclipse),
> the working copy isn't up-to-date and calls to update seem to produce lots
> of issues (conflicts, etc).
>
> My setup: yesterday, I upgraded from from SVN 1.4.4 to SVN 1.5.1. I built
> 1.5.1 from source, as I did for 1.4.4. I access my repositories over HTTP
> using Apache 2.0.59. The SVN server is on RedHat 4. Things in 1.4.4 used to
> work fine, both from a linux command line and from Eclipse/Subclipse on
> Windows. Now, both the command line and subclipse attempts at committing
> give the error message described above and in the example below.
>
> My fellow users recently experiencing similar (if not exactly the same)
> problems
> http://svn.haxx.se/users/archive-2008-08/0444.shtml
> http://svn.haxx.se/users/archive-2008-08/0725.shtml
> (For the life of me I couldn't figure out how to add to their threads -
> sorry about that).
>
> Any thoughts on why this error is being presented and how to get rid of it?
>
> Below, I have pasted a log of the steps I take to reproduce the problem. I
> create a repository, check it out, add a file, do a commit (which gives the
> nasty error message), show that my client doesn't believe the commit worked,
> then show that the repository has indeed been updated.
>
Thanks for the transcript, very helpful (and saves a bunch of questions).
> --------------------------------------------------
> [root@cutlass v1.5]$ svnadmin create sandbox
Does the error go away if you create a BDB repository instead?
> [root@cutlass v1.5]$ chown -R apache:apache sandbox
> [root@cutlass v1.5]$ exit
> [slavinsk@cutlass v1.5]$ cd ~/temp/workspace/
> [slavinsk@cutlass workspace]$ svn co http://localhost/svn/sandbox
> Authentication realm: <http://localhost:80> Sandbox SVN Repository (v1.5)
> Password for 'slavinsk':
> Checked out revision 0.
> [slavinsk@cutlass workspace]$ cd sandbox/
> [slavinsk@cutlass sandbox]$ touch test.txt
> [slavinsk@cutlass sandbox]$ svn add test.txt
> A test.txt
> [slavinsk@cutlass sandbox]$ svn commit -m "Committing a dummy file"
> Adding test.txt
> Transmitting file data .svn: Commit failed (details follow):
> svn: Valid UTF-8 data
> (hex: 1c)
> followed by invalid UTF-8 sequence
> (hex: a4 01)
All reports of this error have "a4 01" as the non-UTF-8 sequence.
> [slavinsk@cutlass sandbox]$ svn status
> A test.txt
> [slavinsk@cutlass sandbox]$ svnlook tree /svn/v1.5/sandbox
> /
> test.txt
> --------------------------------------------------
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org