Unable to commit code in SVN repo

[Pothkanoori, Praveen Kumar(HCL) via users]

Hi Team,

 

Please help with any solution to fix the code commit issue in SVN repo. There is no issue in code check out, only it is throwing below error while doing code commits.

 

We tried all the major troubleshooting steps to fix the issue – yet it is not working.

 

Some of selected resources were not committed. RA layer request failed svn: Commit failed (details follow): svn: Unexpected server error 500 'Internal Server Error' on '/repos/dca/!svn/act/593a4397-bae7-704a-a828-6e8f2d1aee63' Additional errors: RA layer request failed svn: Unexpected server error 500 'Internal Server Error' on '/repos/dca/!svn/act/593a4397-bae7-704a-a828-6e8f2d1aee63'

 

Regards,

Praveen Pothkanoori

ECOM Support | India

 

[Daniel Sahlberg]

What version are you running (both server and client)?

Are there any error messages in the server logs?

Kind regards 

Daniel Sahlberg

[Pothkanoori, Praveen Kumar(HCL) via users]

Hi Daniel,

 

Below are the details requested –

 

SVN version

 

$ svn --version svn, version 1.6.11 (r934486)    compiled Aug  4 2015, 09:07:02   Copyright (C) 2000-2009 CollabNet. Subversion is open source software, see http://subversion.tigris.org/ This product includes software developed by CollabNet (http://www.Collab.Net/).   The following repository access (RA) modules are available:   * ra_neon : Module for accessing a repository via WebDAV protocol using Neon.   - handles 'http' scheme   - handles 'https' scheme * ra_svn : Module for accessing a repository using the svn network protocol.   - with Cyrus SASL authentication   - handles 'svn' scheme * ra_local : Module for accessing a repository on local disk.   - handles 'file' scheme

 

Linux version

 

$ lsb_release -a LSB Version:    :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch Distributor ID: RedHatEnterpriseServer Description:    Red Hat Enterprise Linux Server release 6.10 (Santiago) Release:        6.10 Codename:       Santiago

 

Errors:

 

10.1.174.152 - - [07/Jul/2023:07:31:14 -0700] "MKACTIVITY /pvcs/mattel/!svn/act/1ac6f174-a536-ae47-85d4-15f6183c211d HTTP/1.1" 401 487 "-" "SVN/1.9.7 (x64-microsoft-windows) serf/1.3.9 TortoiseSVN-1.9.7.27907" 10.1.174.152 - DUTTAOIS [07/Jul/2023:07:31:26 -0700] "MKACTIVITY /pvcs/mattel/!svn/act/1ac6f174-a536-ae47-85d4-15f6183c211d HTTP/1.1" 500 620 "-" "SVN/1.9.7 (x64-microsoft-windows) serf/1.3.9 TortoiseSVN-1.9.7.27907" 10.1.174.152 - DUTTAOIS [07/Jul/2023:07:31:27 -0700] "DELETE /pvcs/mattel/!svn/act/1ac6f174-a536-ae47-85d4-15f6183c211d HTTP/1.1" 500 620 "-" "SVN/1.9.7 (x64-microsoft-windows) serf/1.3.9 TortoiseSVN-1.9.7.27907"

 

[Sun May 28 03:38:02 2023] [notice] Apache/2.2.15 (Unix) DAV/2 SVN/1.6.11 configured -- resuming normal operations [Wed May 31 01:40:22 2023] [error] [client 10.7.52.182] Could not MERGE resource "/repos/wc/!svn/act/f8303ca6-08cd-854f-b08c-4f1433336a96" into "/repos/wc/onestore/branch/WCSPOD_2020/workspace/CSRStores/WebContent/Widgets/MattelCSRLineItemNotes".  [409, #0] [Wed May 31 01:40:22 2023] [error] [client 10.7.52.182] Commit blocked by pre-commit hook (exit code 1) with output:\n------------------------------------------------------------------------\nCOMMIT VIOLATION:\n    Commit comment must start with Jira issue IDs, like ASDF-0001, OWL-1234, AGCUP-567, or NONE, followed by ":"\n    Revision property "svn:log" did not match regex "^((NONE)|((OWL|AEMECOM|CM|AGDT|ADA|AGDH|TPP|DPS|WCSPB)-[0-9]+,?)+):"\nMore info at http://svn/repos/wc/onestore/admin/rules.html\n  [409, #165001] [Wed May 31 10:52:29 2023] [error] [client 10.7.52.182] Could not MERGE resource "/repos/wc/!svn/act/cab5ba16-3390-6c47-93a3-92ba30ec5780" into "/repos/wc/onestore/tag/QA_latest/workspace/CSRStores".  [409, #0] [Wed May 31 10:52:29 2023] [error] [client 10.7.52.182] Commit blocked by pre-commit hook (exit code 1) with output:\n------------------------------------------------------------------------\nCOMMIT VIOLATION:\n    Commit comment must start with Jira issue IDs, like ASDF-0001, OWL-1234, AGCUP-567, or NONE, followed by ":"\n    Revision property "svn:log" did not match regex "^((NONE)|((OWL|AEMECOM|CM|AGDT|ADA|AGDH|TPP|DPS|WCSPB)-[0-9]+,?)+):"\n------------------------------------------------------------------------\nCOMMIT VIOLATION:\n    Commit comment must have at least 10 characters after the colon\n    Revision property "svn:log" did not match regex ":.{10,}"\nMore info at http://svn/repos/wc/onestore/admin/rules.html\n  [409, #165001] [Wed May 31 13:23:01 2023] [error] [client 10.3.65.26] Directory index forbidden by Options directive: /var/www/html/ [Wed May 31 13:23:20 2023] [error] [client 10.3.65.26] File does not exist: /var/www/html/js [Wed May 31 13:23:20 2023] [error] [client 10.3.65.26] Directory index forbidden by Options directive: /var/www/html/ [Wed May 31 13:23:20 2023] [error] [client 10.3.65.26] File does not exist: /var/www/html/DeviceInformation [Wed May 31 13:23:20 2023] [error] [client 10.3.65.26] File does not exist: /var/www/html/CGI [Wed May 31 13:23:20 2023] [error] [client 10.3.65.26] Directory index forbidden by Options directive: /var/www/html/ [Wed May 31 13:23:20 2023] [error] [client 10.3.65.26] File does not exist: /var/www/html/js [Wed May 31 13:23:20 2023] [error] [client 10.3.65.26] Directory index forbidden by Options directive: /var/www/html/ [Wed May 31 13:23:20 2023] [error] [client 10.3.65.26] File does not exist: /var/www/html/php [Wed May 31 13:23:20 2023] [error] [client 10.3.65.26] File does not exist: /var/www/html/DeviceInformation [Wed May 31 13:23:20 2023] [error] [client 10.3.65.26] File does not exist: /var/www/html/CGI [Wed May 31 13:24:21 2023] [error] [client 10.3.65.26] File does not exist: /var/www/html/selfupdate [Wed May 31 13:24:21 2023] [error] [client 10.3.65.26] Directory index forbidden by Options directive: /var/www/html/ [Wed May 31 13:24:21 2023] [error] [client 10.3.65.26] Directory index forbidden by Options directive: /var/www/html/

 

 

Regards,

Praveen Pothkanoori

 

From: Daniel Sahlberg <daniel.l...@gmail.com>
Sent: Thursday, July 13, 2023 8:49 AM
To: Pothkanoori, Praveen Kumar(HCL) <PraveenKumar...@Mattel.com>
Cc: us...@subversion.apache.org
Subject: Re: Unable to commit code in SVN repo

 

** This email was sent from an external source **

[Nathan Hartman]

On Thu, Jul 13, 2023 at 10:09 AM Pothkanoori, Praveen Kumar(HCL) via
users <us...@subversion.apache.org> wrote:
> [Wed May 31 10:52:29 2023] [error] [client 10.7.52.182] Commit
> blocked by pre-commit hook (exit code 1) with output:\n---------------

> ---------------------------------------------------------\nCOMMIT
> VIOLATION:\n Commit comment must start with Jira issue IDs, like
> ASDF-0001, OWL-1234, AGCUP-567, or NONE, followed by ":"\n Revision
> property "svn:log" did not match regex
> "^((NONE)|((OWL|AEMECOM|CM|AGDT|ADA|AGDH|TPP|DPS|WCSPB)-[0-

> 9]+,?)+):"\n----------------------------------------------------------

> --------------\nCOMMIT VIOLATION:\n Commit comment must have at
> least 10 characters after the colon\n Revision property "svn:log"
> did not match regex ":.{10,}"\nMore info at
> http://svn/repos/wc/onestore/admin/rules.html\n [409, #165001]

Hi,

Your site has what is called a pre-commit hook, which verifies that
certain aspects of your commit match what the administrator has
configured. You can read more about pre-commit hooks at [1].

In this case, according to the error message, your site's pre-commit
hook is looking for a Jira issue ID in the log message. If you believe
that you have included the needed Jira issue ID, then you should
consult your site's administrator to find out why it is not being
accepted by the pre-commit hook.

References:
[1] https://svnbook.red-bean.com/en/1.7/svn.ref.reposhooks.pre-commit.html

Hope this helps,

Nathan

[Daniel Sahlberg]

Hi

I believe the pre commit hook message is unrelated since it is on a completely different date. Anyway you have some information about it in Nathan’s mail.

I’ve searched for MKACTIVITY and error code 500 with very little success but some sources point to incorrect file system rights on the server. You should probably also run svnadmin verify on your repository (see 

https://svnbook.red-bean.com/en/1.7/svn.ref.svnadmin.c.verify.html).

You are running a version of Subversion that is over 10 years old. While I can’t say that this is the cause of your problem, it might be a bug that has been fixed in later versions. There may also be security fixes in later versions so I really encourage you to upgrade to Subversion 1.14.

Kind regards 

Daniel Sahlberg 

[Pothkanoori, Praveen Kumar(HCL) via users]

HI Daniel,

 

Thanks for the inputs.

 

Upon my analysis – I could conclude that pre commit hook error is not causing the issue as we could even see these error while commit was working.

 

Also, this commit issue started only from June 20, 2023 – some 3 weeks ago.

 

I completely understand it is very old version that we are using, but it broke suddenly, and no fix is working.

 

Can we upgrade to latest version with this issue ongoing? And this upgrade doesn’t corrupt the files?

 

Best Regards,

Praveen Pothkanooru

Mattel ECOM Support

HCL Tech | Mattel Inc

[Daniel Sahlberg]

Den tors 13 juli 2023 kl 18:13 skrev Pothkanoori, Praveen Kumar(HCL) <PraveenKumar...@mattel.com>:

HI Daniel,

 

Thanks for the inputs.

 

Upon my analysis – I could conclude that pre commit hook error is not causing the issue as we could even see these error while commit was working.

 

Also, this commit issue started only from June 20, 2023 – some 3 weeks ago.

 

I completely understand it is very old version that we are using, but it broke suddenly, and no fix is working.

 

Can we upgrade to latest version with this issue ongoing? And this upgrade doesn’t corrupt the files?

I would suggest you first run svnadmin verify on the repositories.  Report back if there are any issues!

Please also verify that there is enough disk space available on the server.

You should be able to upgrade the server without making any changes to the repositories (however some releases added new features to the repository format in which case you might want do to a dump/load cycle to access benefit from the new features). Please check the release notes, for example https://subversion.apache.org/docs/release-notes/1.14.html (change the version number in the end of the URL to 1.13, 1.12 etc. for each release down to 1.6).

Before upgrading, make sure you have a backup of the repositories and the server.

Kind regards,

Daniel