Bug report on SVN 1.8.3 Cannot allocate Memory
440 views
Skip to first unread message
Nguyen, Quyen
Dec 12, 2013, 5:12:45 PM12/12/13
to us...@subversion.apache.org, Vornbrock, Beth
Hi,
We had subversion 1.8.3 installed on our test server.
svn, version 1.8.3 (r1516576)
compiled Aug 30 2013, 17:19:00 on x86_64-unknown-linux-gnu
The OS on this server is OS Red Hat Enterprise Linux Server release 6.3 (Santiago) .
Initially, testing 1.8.3 on this test server looks good but then we ran into this showstopper a few weeks ago.
svn rm URL -m "Remove test dir"
svn: E165002: Failed to start '/../../../hooks/start-commit' hook
Looking into the subversion error_log and it appears it point to the memory
[Mon Nov 18 17:28:53 2013] [error] [client 10.20.36.51] Can't start process '/data00////start-commit': Cannot allocate memory [500, #12]
Our Linux System Admin had applied different memory cache setting to the server but thus far we have no luck resolving this error.
If you could please provide any insights on why and ho we could correct this issue, I’m truly appreciated your help/
Thanks in advance for your help
Quyen Nguyen
Quality Assurance Engineer
Epsilon Targeting
2550 Crescent Drive, Lafayette, CO 80026
This e-mail and files transmitted with it are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you are not one of the named recipient(s) or otherwise have reason to believe that you received this message in error, please immediately notify sender by e-mail, and destroy the original message. Thank You.
Ben Reser
Dec 12, 2013, 5:36:54 PM12/12/13
to Nguyen, Quyen, us...@subversion.apache.org, Vornbrock, Beth
On 12/12/13 2:12 PM, Nguyen, Quyen wrote:
> Looking into the subversion error_log and it appears it point to the memory
>
> [Mon Nov 18 17:28:53 2013] [error] [client 10.20.36.51] Can't start process
> '/data00////start-commit': Cannot allocate memory [500, #12]
That is an OS error. Subversion is providing you the "Cannot allocate memory"
> Looking into the subversion error_log and it appears it point to the memory
>
> [Mon Nov 18 17:28:53 2013] [error] [client 10.20.36.51] Can't start process
> '/data00////start-commit': Cannot allocate memory [500, #12]
message as a convenience, it's not producing the error.
Looking at the code I'd bet that fork() is returning ENOMEM on your system.
> Our Linux System Admin had applied different memory cache setting to the
> server but thus far we have no luck resolving this error.
>
> If you could please provide any insights on why and ho we could correct this
Add more memory to the system or figure out why the kernel doesn't think it has
enough memory. Might want to check your configured ulimits as well.
Nguyen, Quyen
Dec 12, 2013, 5:39:54 PM12/12/13
to Ben Reser, us...@subversion.apache.org, Vornbrock, Beth
Thank you for your input Ben.
We will get with our System Admin and see what is going there.
Quyen Nguyen
-----Original Message-----
From: Ben Reser [mailto:b...@reser.org]
Sent: Thursday, December 12, 2013 3:37 PM
To: Nguyen, Quyen; us...@subversion.apache.org
Cc: Vornbrock, Beth
Subject: Re: Bug report on SVN 1.8.3 Cannot allocate Memory
On 12/12/13 2:12 PM, Nguyen, Quyen wrote:
> Looking into the subversion error_log and it appears it point to the
> memory
>
> [Mon Nov 18 17:28:53 2013] [error] [client 10.20.36.51] Can't start
> process
> '/data00////start-commit': Cannot allocate memory [500, #12]
That is an OS error. Subversion is providing you the "Cannot allocate memory"
message as a convenience, it's not producing the error.
Looking at the code I'd bet that fork() is returning ENOMEM on your system.
> Our Linux System Admin had applied different memory cache setting to
> the server but thus far we have no luck resolving this error.
>
> If you could please provide any insights on why and ho we could
> correct this issue, I'm truly appreciated your help/
Add more memory to the system or figure out why the kernel doesn't think it has enough memory. Might want to check your configured ulimits as well.
We will get with our System Admin and see what is going there.
Quyen Nguyen
-----Original Message-----
From: Ben Reser [mailto:b...@reser.org]
Sent: Thursday, December 12, 2013 3:37 PM
To: Nguyen, Quyen; us...@subversion.apache.org
Cc: Vornbrock, Beth
Subject: Re: Bug report on SVN 1.8.3 Cannot allocate Memory
On 12/12/13 2:12 PM, Nguyen, Quyen wrote:
> Looking into the subversion error_log and it appears it point to the
> memory
>
> [Mon Nov 18 17:28:53 2013] [error] [client 10.20.36.51] Can't start
> process
> '/data00////start-commit': Cannot allocate memory [500, #12]
That is an OS error. Subversion is providing you the "Cannot allocate memory"
message as a convenience, it's not producing the error.
Looking at the code I'd bet that fork() is returning ENOMEM on your system.
> Our Linux System Admin had applied different memory cache setting to
> the server but thus far we have no luck resolving this error.
>
> If you could please provide any insights on why and ho we could
Add more memory to the system or figure out why the kernel doesn't think it has enough memory. Might want to check your configured ulimits as well.
Thorsten Schöning
Dec 13, 2013, 1:37:06 AM12/13/13
to us...@subversion.apache.org
Guten Tag Nguyen, Quyen,
am Donnerstag, 12. Dezember 2013 um 23:12 schrieben Sie:
> svn: E165002: Failed to start '/../../../hooks/start-commit' hook
It may help to provide your hook's source to the list, just in case
there's an error in it like a wrong shebang, wrong line endings or
stuff like that which may prevent fork from working as expected.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten....@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
am Donnerstag, 12. Dezember 2013 um 23:12 schrieben Sie:
> svn: E165002: Failed to start '/../../../hooks/start-commit' hook
there's an error in it like a wrong shebang, wrong line endings or
stuff like that which may prevent fork from working as expected.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten....@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Henrik Carlqvist
Dec 13, 2013, 1:54:41 AM12/13/13
to us...@subversion.apache.org
> We will get with our System Admin and see what is going there.
The command "dmesg" might also give a clue on Linux systems.
regards Henrik
Nguyen, Quyen
Feb 13, 2014, 6:37:07 PM2/13/14
to Ben Reser, us...@subversion.apache.org, Vornbrock, Beth, Besaw, Jeffrey
Hi Ben
I just posted my questions on http://post.gmane.org
I'm not sure if it is posted on the mailing list yet. Anyway, I also decide to send it directly to you guys.
If this is not the right way to approach, please pardon me and let me know. Here is my comments that I posted on http://post.gmane.org
The Linux VM test machine showed it is the OOM error.
Below is the error when I run the command dmesg
Out of memory: Kill process 4353 (httpd) score 134 or sacrifice child
Killed process 4353, UID 41000, (httpd) total-vm:2850244kB, anon-rss:690052kB, file-rss:28kB
This Linux VM machine has Apache/2.2.25 (Unix) mod_ssl/2.2.25 OpenSSL/0.9.8y DAV/2 SVN/1.8.5 configured.
From this error message, the httpd process was killed which seem to me it either has something to do with the Apache server or SVN 1.8 itself ??
We download this release of subversion from Collabnet. It bundles subversion and apache together so we don't modify the apache configuration to have the correc modules.
Have anyone ran into this OOM issue with subversion 1.8 and Apache 2.2.25 configuration?
Could you please help to shed some light on this? Let me know if you need any additional information.
-----Original Message-----
From: Ben Reser [mailto:b...@reser.org]
Sent: Thursday, December 12, 2013 3:37 PM
To: Nguyen, Quyen; us...@subversion.apache.org
Cc: Vornbrock, Beth
Subject: Re: Bug report on SVN 1.8.3 Cannot allocate Memory
Add more memory to the system or figure out why the kernel doesn't think it has enough memory. Might want to check your configured ulimits as well.
I just posted my questions on http://post.gmane.org
I'm not sure if it is posted on the mailing list yet. Anyway, I also decide to send it directly to you guys.
If this is not the right way to approach, please pardon me and let me know. Here is my comments that I posted on http://post.gmane.org
The Linux VM test machine showed it is the OOM error.
Below is the error when I run the command dmesg
Out of memory: Kill process 4353 (httpd) score 134 or sacrifice child
Killed process 4353, UID 41000, (httpd) total-vm:2850244kB, anon-rss:690052kB, file-rss:28kB
This Linux VM machine has Apache/2.2.25 (Unix) mod_ssl/2.2.25 OpenSSL/0.9.8y DAV/2 SVN/1.8.5 configured.
From this error message, the httpd process was killed which seem to me it either has something to do with the Apache server or SVN 1.8 itself ??
We download this release of subversion from Collabnet. It bundles subversion and apache together so we don't modify the apache configuration to have the correc modules.
Have anyone ran into this OOM issue with subversion 1.8 and Apache 2.2.25 configuration?
Could you please help to shed some light on this? Let me know if you need any additional information.
-----Original Message-----
From: Ben Reser [mailto:b...@reser.org]
Sent: Thursday, December 12, 2013 3:37 PM
To: Nguyen, Quyen; us...@subversion.apache.org
Cc: Vornbrock, Beth
Subject: Re: Bug report on SVN 1.8.3 Cannot allocate Memory
On 12/12/13 2:12 PM, Nguyen, Quyen wrote:
> Looking into the subversion error_log and it appears it point to the
> memory
>
> [Mon Nov 18 17:28:53 2013] [error] [client 10.20.36.51] Can't start
> process
> '/data00////start-commit': Cannot allocate memory [500, #12]
That is an OS error. Subversion is providing you the "Cannot allocate memory"
message as a convenience, it's not producing the error.
Looking at the code I'd bet that fork() is returning ENOMEM on your system.
> Our Linux System Admin had applied different memory cache setting to
> the server but thus far we have no luck resolving this error.
>
> If you could please provide any insights on why and ho we could
> correct this issue, I'm truly appreciated your help/
> Looking into the subversion error_log and it appears it point to the
> memory
>
> [Mon Nov 18 17:28:53 2013] [error] [client 10.20.36.51] Can't start
> process
> '/data00////start-commit': Cannot allocate memory [500, #12]
That is an OS error. Subversion is providing you the "Cannot allocate memory"
message as a convenience, it's not producing the error.
Looking at the code I'd bet that fork() is returning ENOMEM on your system.
> Our Linux System Admin had applied different memory cache setting to
> the server but thus far we have no luck resolving this error.
>
> If you could please provide any insights on why and ho we could
Add more memory to the system or figure out why the kernel doesn't think it has enough memory. Might want to check your configured ulimits as well.
Reply all
Reply to author
Forward
0 new messages