pijul_org / pijul

#172 Cloning Issues on FreeBSD

Opened by 319, on September 6, 2017
Bug
Closed
319 commented on September 6, 2017

Cloning and other network related do not work in pijul and seem to stall it. Any ways I can get some DEBUG flags set to analyze the problem further?

319 commented on September 6, 2017

To add a bit more info to my problem:

  • Task: cloning pijul

  • Results:

  1. .pijul is created
  2. id file is created
  3. patches directory created but empty
  4. pristine created with db and db.lock (empty)
  5. version is created
  6. then it stalls and does not continue
pmeunier commented on September 6, 2017

Hi! Thanks for reporting. At the moment, the network operations involved in clone/pull/push are not well optimised, so cloning Pijul itself might take a while.

You can set the environment variable RUST_LOG to pijul=debug to diagnose the problem.

Other things to try:

  • Can you clone locally?
  • Can you clone a very small repository from the Nest (for instance /pmeunier/user)?
319 commented on September 6, 2017

Thanks for the answer. Trying that right now, but still seems stuck.

  1. local clone from a small test repository to another works perfectly without errors.

  2. cloning small repository from nests just creates the empty user directory, but stucks otherwise. DEBUG env variable is not very useful. Any ideas?

319 commented on September 6, 2017

I get the following DEBUG messages:

> pijul clone https://nest.pijul.com/pijul_org/pijul
DEBUG:pijul::commands::clone: Params { from: Uri { uri: "https://nest.pijul.com/pijul_org/pijul" }, from_branch: "master", to: Local { path: "pijul" }, to_branch: "master" }

or

> pijul clone me@nest.pijul.com/pijul_org/pijul
DEBUG:pijul::commands::clone: Params { from: Local { path: "me@nest.pijul.com/pijul_org/pijul" }, from_branch: "master", to: Local { path: "pijul" }, to_branch: "master" }
DEBUG:pijul::commands::clone: remote init
DEBUG:pijul::commands::clone: pushable?
DEBUG:pijul::commands::remote: source: "me@nest.pijul.com/pijul_org/pijul"
error: IO error: No such file or directory (os error 2)
lthms commented on September 18, 2017

Since you have announced pijul on FreeBSD is a thing, does it mean this issue is gone?

319 commented on September 20, 2017

No, unfortunately, this is quite a blocker on FreeBSD. Not sure where it stems from, could it come from the SSH implementation? Any hints on how to debug that would be appreciated.

pmeunier commented on September 21, 2017

So, I've changed a number of things lately in the SSH implementation. Could you try to set RUST_LOG="thrussh=debug,pijul=debug"?

319 commented on October 5, 2017

All I get is:

> setenv RUST_LOG "thrussh=debug,pijul=debug"
> pijul clone https://nest.pijul.com/pijul_org/pijul
DEBUG:pijul::commands::clone: Params { from: Uri { uri: "https://nest.pijul.com/pijul_org/pijul" }, from_branch: "master", to: Local { path: "pijul" }, to_branch: "master" }


pmeunier commented on November 15, 2017

So, I installed FreeBSD on a virtual machine, and it worked fine, I could clone from the Nest using Pijul 0.8.3, installed via cargo. Can you give us more detail about your system? For instance, which version of FreeBSD is it?

One issue I've had is that ~/.ssh/known_hosts was not created, but that's probably also the case on other platforms.

lthms closed this discussion on April 28, 2018