-
Notifications
You must be signed in to change notification settings - Fork 849
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
==> default: /tmp/vagrant-shell: line 138: /etc/postfix/main.cf: No such file or directory #628
Comments
It also hits error for me (Win 8 host). |
@hubdotcom @af7 Does software gets installed automatically in the virtual machine for you while doing provisioning? I am also getting this error and for me software aren't getting installed. |
Are there other errors during provisioning? I've provisioned from scratch a few times recently and haven't had any trouble, though it's possible that this error displays. Can you paste the entire provisioning log into a gist or pastebin? It may be helpful to see all of those details. |
Can you tell me how to copy the provisioning log from git bash? |
Depending on the terminal in use, you may be able to configure how many lines of scrollback are available. In OSX or Linux, you can pipe the results like Have you tried starting over with |
I have already tried @jeremyfelt: Here is the log of doing |
Ahh, it looks like this may be key:
I'm going to try a fresh |
Ok, everything worked fine during a fresh Are you behind a proxy at all? Note - this is unrelated to the error in the original title of this issue. I do get that, but it's more of an informational error—though we should find a way to fix it. |
Yes this indeed is the key. After I removed the nginx mainline signing key and custom sources added by vvv from the vm and installed the stable nginx(1.4.6) manually, it seems to be working. But, I am still unsure that everything is as stable as before.
No, I am not behind a proxy. |
I'm still seeing this postfix error during provisioning. Just updating with a note that this line may be it - https://github.com/Varying-Vagrant-Vagrants/VVV/blob/master/provision/provision.sh#L195-L196 |
In #420, we added a line to provisioning that attempts to set "ipv4" as the only allowed protocol for postfix due to issues in how network connections managed the ipv6 connection. Because the config file does not yet exist during initial provisioning, that caused an error message saying as much. See #628. It turns out that this line hasn't been doing anything. :) I first went down the path of using `debconf-set-selections` to set the protocol value. This works, but then disables ipv6 entirely as a valid protocol. Since we haven't heard of any other issues besides the original in #420, I think it's safe to not make any change here and then watch for any problems. I have a feeling that postfix has gotten better about this. In the documentation for the `inet_protocols` config, it's mentioned that "versions before 2.8 attempt to connect via IPv6 before attempting to use IPv4." http://www.postfix.org/postconf.5.html#inet_protocols Now that we're past 2.8, it's entirely possible that the protocol detection has gotten better. If we do run into an issue, there is a newer `smtp_address_preference` config that allows us to specify which protocol should be attempted first. http://www.postfix.org/postconf.5.html#smtp_address_preference In that case, we may need to create our own custom config file as it's not entirely obvious that `debconf-set-selections` will work for this value. See #420. Fixes #628.
In Varying-Vagrant-Vagrants#420, we added a line to provisioning that attempts to set "ipv4" as the only allowed protocol for postfix due to issues in how network connections managed the ipv6 connection. Because the config file does not yet exist during initial provisioning, that caused an error message saying as much. See Varying-Vagrant-Vagrants#628. It turns out that this line hasn't been doing anything. :) I first went down the path of using `debconf-set-selections` to set the protocol value. This works, but then disables ipv6 entirely as a valid protocol. Since we haven't heard of any other issues besides the original in Varying-Vagrant-Vagrants#420, I think it's safe to not make any change here and then watch for any problems. I have a feeling that postfix has gotten better about this. In the documentation for the `inet_protocols` config, it's mentioned that "versions before 2.8 attempt to connect via IPv6 before attempting to use IPv4." http://www.postfix.org/postconf.5.html#inet_protocols Now that we're past 2.8, it's entirely possible that the protocol detection has gotten better. If we do run into an issue, there is a newer `smtp_address_preference` config that allows us to specify which protocol should be attempted first. http://www.postfix.org/postconf.5.html#smtp_address_preference In that case, we may need to create our own custom config file as it's not entirely obvious that `debconf-set-selections` will work for this value. See Varying-Vagrant-Vagrants#420. Fixes Varying-Vagrant-Vagrants#628.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
https://github.com/Varying-Vagrant-Vagrants/VVV/blob/master/provision/provision.sh#L138
The text was updated successfully, but these errors were encountered: