Can´t create Virtual env. creation on Debian Wheezy #1554
Comments
|
It's frustrating that that traceback doesn't actually say what the missing file is. Looks like we'd have to edit If you do |
|
I faced same problem in my Debian Wheezy host |
|
Someone else reported that installing / updating |
|
@pde Do you really mean: Or do you mean:
|
|
I was having the same problem on Debian Wheezy, however I was trying with a user account (not with root) who has sudo capabilities. On my Jessie box that was enough as However here it wasn't enough. But running |
|
I'm having a similar problem (https://github.com/letsencrypt/letsencrypt/issues/2817]). Did anyone find a solution for this one? |
|
What happens if you run EDIT: Also make sure you're using an up to date copy of |
|
I'm using letsencrypt-auto downloaded from git yesterday. Here's what happens with virtualenv: |
|
This is a problem with
My current hypothesis is |
|
Here's what happens with virtualenv: Contents of the directories $TMP/bin and /usr/share/python-virtualenv: |
|
@gbeddow, the relevant output there is: Because of this, where the name of the |
|
Still not working: |
|
After creating one more symlink file the process gets further, but now letsencrypt-auto hangs. First, here's what virtualenv does: Then, getting back to the original issue, here's what happens with letsencrypt-auto cert renewal: At that point it hangs forever. Have to ^C out: Any idea why letsencrypt-auto is hanging? |
|
Oh wow. That's a major step forward. |
|
Just to be clear, I installed letsencrypt back in December, and certificate creation and renewal were working fine in December and January; it's only in the past couple days (as the January + 90 day expiration draws close) that letsencrypt-auto renewal has been failing. Anyway, how long would you expect it to take to renew? The first time I let it run for a half hour before killing it, way longer than any reasonable expectation. The second time is still running as I type this, but it's been 10 or 15 minutes... |
Well we did do a release last week, however, it seems unlikely that any of the changes that were made would cause the problems you are having. One thing you can do to test if the new release is the cause of the problems on your system is to download the previous version of
This is obviously dependent on the system you're running it on, however, the script shouldn't take more than a minute after you see this output: |
|
It finished - successfully - thanks! Took about 30 minutes. Looking at the log files, it seems to spend large amounts of time waiting for responses from the letsencrypt server. Thanks again. Assuming it works, the timing thing shouldn't be an issue since it's normally run from cron. |
|
That's really strange. There is an issue about our connection pooling not being as efficient as possible, but 30 minutes certainly isn't normal. Regardless, I'm glad you were able to renew your certs! Thanks for bearing with me while I suggested different things. |
|
Is this problem still reproducible, or should we close this? |
|
This has been working for me since then. |
|
I got the same error. I have Debian 7.11 and I was following the instructions from here: |
|
Creating the symlink fixed the problem, as @bmw suggested. |
|
For me too, the symlink method mentiond by @bmw worked! |
|
Debian Wheezy has reached its end of life and is no longer supported by Debian. We are no longer trying to maintain support either so I'm closing this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi guys,
i´m running letsencrypt on a Debian Wheezy Server.
No Backports-Repo or something else.
I also removed the directory and done a fresh copy.
Log:
Any solution? :)
Thanks in advance,
The text was updated successfully, but these errors were encountered: