darcs repository web UI and hosting app. This is the main darcsden trunk, which also runs hub.darcs.net. (https://hub.darcs.net)

#51pushing too many/too large patches at once can fail and leave a stray lock

Related to #46.

With a "too large" push, all memory on the server can be consumed, triggering the OOM killer which kills one or more related processes leaving stray processes and their lock file, or just a stray lock file. OOM kills can be seen in kern.log and syslog. amgarching has a test repo which seems to reproduce this.

    • summary changed to "pushing too many/too large patches at once can fail and leave a stray lock"
  • i have the suspicion i hit the same issue, but please have a look at it.

    ---==| ~/p/homegrw_0 |==--- $ date Mon Jun 17 17:31:33 HKT 2013

    ---==| ~/p/homegrw_0 |==--- $ darcs -v 2.8.2 (release)

    ---==| ~/p/homegrw-sinatra |==--- $ darcs push onetom@hub.darcs.net:homegrw HINT: if you want to change the default remote repository to onetom@hub.darcs.net:homegrw, quit now and issue the same command with the --set-default flag. Sun Jun 16 03:38:54 HKT 2013 Tamas Herman hermantamas@gmail.com * Base sinatra app Shall I push this patch? (1/16) [ynW...], or ? for more options: withSignalsHandled: Interrupted!

    ---==| ~/p/homegrw-sinatra |==--- $ darcs push onetom@hub.darcs.net:homegrw --set-default Sun Jun 16 03:38:54 HKT 2013 Tamas Herman hermantamas@gmail.com * Base sinatra app Shall I push this patch? (1/16) [ynW...], or ? for more options: a Apply failed!

    ---==| ~/p/homegrw-sinatra |==--- $ darcs put onetom@hub.darcs.net:homegrw --set-default exec request failed on channel 1

    darcs failed: Couldn't initialize remote repository.

    ---==| ~/p/homegrw-sinatra |==--- $ cd ..

    ---==| ~/p |==--- $ darcs get onetom@hub.darcs.net:homegrw Directory '/Users/onetom/p/homegrw' already exists, creating repository as '/Users/onetom/p/homegrw_0' Copying patches, to get lazy repository hit ctrl-C... Finished getting.

    ---==| ~/p |==--- $ cd homegrw_0/

    ---==| ~/p/homegrw_0 |==--- $ darcs pull ../homegrw- homegrw-arduino/ homegrw-sinatra/

    ---==| ~/p/homegrw_0 |==--- $ darcs pull ../homegrw-sinatra/ HINT: if you want to change the default remote repository to /Users/onetom/p/homegrw-sinatra, quit now and issue the same command with the --set-default flag. Sun Jun 16 03:38:54 HKT 2013 Tamas Herman hermantamas@gmail.com * Base sinatra app Shall I pull this patch? (1/16) [ynW...], or ? for more options: a Finished pulling and applying.

    ---==| ~/p/homegrw_0 |==--- $ darcs push Pushing to "onetom@hub.darcs.net:homegrw"... Sun Jun 16 03:38:54 HKT 2013 Tamas Herman hermantamas@gmail.com * Base sinatra app Shall I push this patch? (1/16) [ynW...], or ? for more options: a Apply failed!

    ---==| ~/p/homegrw_0 |==--- $ darcs push Pushing to "onetom@hub.darcs.net:homegrw"... Sun Jun 16 03:38:54 HKT 2013 Tamas Herman hermantamas@gmail.com * Base sinatra app Shall I push this patch? (1/16) [ynW...], or ? for more options: y Sun Jun 16 03:51:45 HKT 2013 Tamas Herman hermantamas@gmail.com * rspec --init Shall I push this patch? (2/16) [ynW...], or ? for more options: d Finished applying... Push successful.

    ---==| ~/p/homegrw_0 |==--- $ darcs push Pushing to "onetom@hub.darcs.net:homegrw"... Sun Jun 16 03:51:45 HKT 2013 Tamas Herman hermantamas@gmail.com * rspec --init Shall I push this patch? (1/15) [ynW...], or ? for more options: a Apply failed!

    ---==| ~/p/homegrw_0 |==--- $ darcs push Pushing to "onetom@hub.darcs.net:homegrw"... No recorded local changes to push!

    ================================================================== tried again after deleting and re-creating the remote repo

    ---==| ~/p/homegrw_0 |==--- $ darcs push --set-default onetom@hub.darcs.net:homegrw Pushing to "onetom@hub.darcs.net:homegrw"... Sun Jun 16 03:38:54 HKT 2013 Tamas Herman hermantamas@gmail.com * Base sinatra app Shall I push this patch? (1/16) [ynW...], or ? for more options: a Apply failed!

    ---==| ~/p/homegrw_0 |==--- $ darcs push --set-default onetom@hub.darcs.net:homegrw Pushing to "onetom@hub.darcs.net:homegrw"... Sun Jun 16 03:38:54 HKT 2013 Tamas Herman hermantamas@gmail.com * Base sinatra app Shall I push this patch? (1/16) [ynW...], or ? for more options: y Sun Jun 16 03:51:45 HKT 2013 Tamas Herman hermantamas@gmail.com * rspec --init Shall I push this patch? (2/16) [ynW...], or ? for more options: d Apply failed!

    ---==| ~/p/homegrw_0 |==--- $ darcs push --set-default onetom@hub.darcs.net:homegrw Pushing to "onetom@hub.darcs.net:homegrw"... Sun Jun 16 03:51:45 HKT 2013 Tamas Herman hermantamas@gmail.com * rspec --init Shall I push this patch? (1/15) [ynW...], or ? for more options: y Sun Jun 16 04:05:07 HKT 2013 Tamas Herman hermantamas@gmail.com * Remove spec_helper comments Shall I push this patch? (2/15) [ynW...], or ? for more options: d Finished applying... Push successful.

    ---==| ~/p/homegrw_0 |==--- $ darcs push --set-default onetom@hub.darcs.net:homegrw Pushing to "onetom@hub.darcs.net:homegrw"... Sun Jun 16 04:05:07 HKT 2013 Tamas Herman hermantamas@gmail.com * Remove spec_helper comments Shall I push this patch? (1/14) [ynW...], or ? for more options: a Apply failed!

    ---==| ~/p/homegrw_0 |==--- $ darcs push --set-default onetom@hub.darcs.net:homegrw Pushing to "onetom@hub.darcs.net:homegrw"... No recorded local changes to push!

  • oh, is it markdown?

    <pre> some code lines indented

    blah </pre>

  • same problem w the stock 2.5 osx version:

    $ darcs-2.5-OSX-10.6-i386 push onetom@hub.darcs.net:test Note: if you want to change the default remote repository to onetom@hub.darcs.net:test, quit now and issue the same command with the --set-default flag. Sun Jun 16 03:38:54 HKT 2013 Tamas Herman hermantamas@gmail.com * Base sinatra app Shall I push this patch? (1/20) [ynW...], or ? for more options: a Apply failed!

    BUT it worked with the ubuntu 12.04 LTS version, which is 2.7.99.1 (release candidate 1)

  • test
  • The original issue is probably independent from mine and still valid.

    My problem was the lack of support for the Control Master SSH feature. If I turned that off, everything worked perfectly.

    See more at: http://hub.darcs.net/simon/hub.darcs.net-docs/FAQ.md#why-ssh-or-darcs-push-to-hub.darcs.net-can-hang