The installation or repair took too long or failed. Try again?
ls -l@e /var/run/net.tunnelblick.tunnelblick.tunnelblickd.socket
srw-rw-rw- 1 root daemon 0 Dec 7 16:34 /var/run/net.tunnelblick.tunnelblick.tunnelblickd.socket
Il giorno 11 dic 2017, alle ore 15:12, Tunnelblick developer <jkbu...@gmail.com> ha scritto:ls -l@e /var/run/net.tunnelblick.tunnelblick.tunnelblickd.socket
Hello, no .pid file for tunnelblick in that folder.PS: I thought it was a permission issue but I already checked all the permissions in /tmp /private/tmp.PPS: I already uninstalled completely tunnelblick (with your uninstaller script) and tried to install it again (latest beta) but with no luck. Always the same error appears.Thanks in advance.Mattia Trussardi------------------------------------------------------------------------
Mattia Trussardi
<>
Cell. +39 3294158330
------------------------------------------------------------------------
--
You received this message because you are subscribed to a topic in the Google Groups "tunnelblick-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tunnelblick-discuss/fIHQiupUOVE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tunnelblick-dis...@googlegroups.com.
Visit this group at https://groups.google.com/group/tunnelblick-discuss.
For more options, visit https://groups.google.com/d/optout.
sudo /bin/launchctl/launchctl load /Library/LaunchDaemons/net.tunnelblick.tunnelblick.tunnelblickd.plist
ls -l@e /var/run/net.tunnelblick.tunnelblick.tunnelblickd.socket
which launchctl
Il giorno 11 dic 2017, alle ore 17:38, Tunnelblick developer <jkbu...@gmail.com> ha scritto:ls -l@e /var/run/net.tunnelblick.tunnelblick.tunnelblickd.socket
NOTE: Due to bugs in the previous implementation and long-stand-
ing client expectations around those bugs, the load and unload
subcommands will only return a non-zero exit code due to
improper usage. Otherwise, zero is always returned.
launchctl will exit with status 0 if the subcommand succeeded. Otherwise,
it will exit with an error code that can be given to the error subcommand
to be decoded into human-readable form.
Overrides the Disabled key and sets it to false or true for the load and unload subcommands respectively.
ls -l /Library/LaunchDaemons/net.tunnelblick.tunnelblick.tunnelblickd.plist
sudo /bin/launchctl load -w /Library/LaunchDaemons/net.tunnelblick.tunnelblick.tunnelblickd.plist
Il giorno 12 dic 2017, alle ore 02:09, Tunnelblick developer <jkbu...@gmail.com> ha scritto:
Ah -- we're making progress. The installer uses the 'sudo /bin/launchctl load ...' command to load the Tunnelblick launch daemon.
The problem is that launchctl does not return an error result even if it fails! Per the man page:NOTE: Due to bugs in the previous implementation and long-stand-
ing client expectations around those bugs, the load and unload
subcommands will only return a non-zero exit code due to
improper usage. Otherwise, zero is always returned.Apparently launchctl is not loading the .plist because "Service is disabled". But it is returning a status of zero when that happens. Tunnelblick sees the status of zero and assumes that all is well and the .plist was loaded, which is incorrect. I never saw this language when I wrote this code, and relied on the language at the end of the man page that sayslaunchctl will exit with status 0 if the subcommand succeeded. Otherwise,
it will exit with an error code that can be given to the error subcommand
to be decoded into human-readable form.So the questions are:
- Why is the service disabled?
- What can we do if the service is disabled?
#1 Doesn't really matter (although I'm curious). I suppose it is either some "security" software that you are using, or a rogue installer that "disables" stuff by default, or something like that.As to #2, how to deal with this problem, I think there are two approaches.One is to modify the .plist so it includes a "Disabled:No" key.The other is to use launchctl's "-w option, which, according to the launchctl man page:Overrides the Disabled key and sets it to false or true for the load and unload subcommands respectively.Since it isn't clear that adding Disabled:No to the .plist will override whatever disabled it in the first place, I am hoping to use launchctl's "-w" option.Please first check the following:ls -l /Library/LaunchDaemons/net.tunnelblick.tunnelblick.tunnelblickd.plist
to make sure that the .plist is there. I'm hoping that it is there from earlier attempts to and see if it succeeds (you might need to install it yet again, I'm not sure).
(If the .plist isn't there, please try to install TB; it should be there after that, as long as you don't uninstall. If that doesn't work you could copy it from Tunnelblick.app/Contents/Resources/net.tunnelblick.tunnelblick.tunnelblickd.plist to /Library/LaunchDaemons.)Assuming it's there, do:sudo /bin/launchctl load -w /Library/LaunchDaemons/net.tunnelblick.tunnelblick.tunnelblickd.plistIf it succeeds, I think you will be able to use Tunnelblick, and I can easily modify the installer so that it uses the -w option.If it doesn't succeed, I'd be interested in what message launchctl displays.Thanks again for your help on this.On Monday, December 11, 2017 at 7:07:44 PM UTC-5, Mattia Trussardi wrote:Hello.Here the output of the three commands.Thanks in advance.MattiaMacBook-Pro-di-Mattia:~ mattia$ sudo /bin/launchctl load /Library/LaunchDaemons/net.tunnelblick.tunnelblick.tunnelblickd.plist/Library/LaunchDaemons/net.tunnelblick.tunnelblick.tunnelblickd.plist: Service is disabledMacBook-Pro-di-Mattia:~ mattia$ which launchctl/bin/launchctlMacBook-Pro-di-Mattia:~ mattia$ ls -l@e /var/run/net.tunnelblick.tunnelblick.tunnelblickd.socketls: /var/run/net.tunnelblick.tunnelblick.tunnelblickd.socket: No such file or directory