Stuck on Barrier is Starting Mac OS

Budoman commented 2 years ago

What happened?

I downloaded and Installed the current build (2.4.0-release-3e0d758b) to my i9 iMac running Catalina 10.15.7 and my new MacBook Pro (16-inch, 2021) M1 Max running Monterey 12.0.1. I can launch and run either machine as a server and they recognize one another when other is set to client. However, when the server prompts me to choose position of the client, it opens the same prompt window twice and creates two client instances. Over on the client node, it stays in the state "Barrier is Starting" regardless of which machine is set as Server/Client.

Version

v2.3.3

Git commit hash (if applicable)

3e0d758b

If applicable, where did you install Barrier from?

download the .dmg from Github.

What OSes are you seeing the problem on? (Check all that apply)

macOS

What OS versions are you using?

Core i9 iMac (2020) running Catalina 10.15.7 new MacBook Pro (16-inch, 2021) M1 Max running Monterey 12.0.1

Relevant log output

No response

Any other information

No response

mainTAP commented 2 years ago

I have a similar issue on High Sierra after upgrading from 2.3.3 :


[2021-11-02T09:34:22] INFO: config file: /private/var/folders/cp/210tpxmj1klfj_hkxypfv6gc0000gq/T/Barrier.xuKuyh
[2021-11-02T09:34:22] INFO: log level: INFO
[2021-11-02T09:34:22] INFO: drag and drop enabled
[2021-11-02T09:34:22] NOTE: started client
[2021-11-02T09:34:22] NOTE: connecting to '
[2021-11-02T09:34:22] INFO: OpenSSL 3.0.0 7 sep 2021
2021-11-02 09:34:22.423 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.439 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.439 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.439 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.439 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.440 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.441 barrierc[659:37801] pid(659)/euid(503) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!
2021-11-02 09:34:22.442 barrierc[659:37793] starting cocoa loop
dyld: lazy symbol binding failed: Symbol not found: ____chkstk_darwin
  Referenced from: /Applications/Barrier.app/Contents/MacOS/barrierc
  Expected in: /usr/lib/libSystem.B.dylib
dyld: Symbol not found: ____chkstk_darwin
  Referenced from: /Applications/Barrier.app/Contents/MacOS/barrierc
  Expected in: /usr/lib/libSystem.B.dylib
[2021-11-02T09:34:22] ERROR: process exited with error code: 6
[2021-11-02T09:34:22] INFO: detected process not running, auto restarting
[2021-11-02T09:34:23] INFO: stopping barrier desktop process```

Ps: it looks like the same happens in 2.3.4

p12tic commented 2 years ago

@mainTAP Just to confirm, 2.3.3 works, 2.3.4 doesn't, right?

mainTAP commented 2 years ago

@mainTAP Just to confirm, 2.3.3 works, 2.3.4 doesn't, right?

Yes, going back to 2.3.3 works

shymega commented 2 years ago

OK, this is probably related to the CI builds included in the release notes.

The link is below - it's from a CI build of 2.4.0.

https://dev.azure.com/debauchee/Barrier/_build/results?buildId=618&view=artifacts&pathAsName=false&type=publishedArtifacts

You should be able to see the page, I don't think it's protected, but there are separate builds for different macOS versions. The 'symbol not found' would indicate a linking issue on a newer/older macOS version.

And the link below is from a CI build of 2.3.4:

https://dev.azure.com/debauchee/Barrier/_build/results?buildId=617&view=artifacts&pathAsName=false&type=publishedArtifacts

So, my suggestion is to attempt using one artefact from either link that matches your macOS version - and let me know, if that's the case, we can update the release on GitHub.

Thanks =)

On Tue, Nov 2, 2021, at 11:19 AM, mainTAP wrote:

@mainTAP https://github.com/mainTAP Just to confirm, 2.3.3 works, 2.3.4 doesn't, right?

Yes, going back to 2.3.3 works

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/debauchee/barrier/issues/1364#issuecomment-957346712, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKF2QHIE5T2GNBAGLTGAI3UJ7CLFANCNFSM5HFRTZFA.

-- Kind regards,

Dom Rodriguez (also known as shymega)

p12tic commented 2 years ago

Indeed, the issue is obvious. I've just deleted a comment asking the user to do bisection.

p12tic commented 2 years ago

Reformatting the logs should have been the first thing I do.

mainTAP commented 2 years ago

OK, this is probably related to the CI builds included in the release notes. The link is below - it's from a CI build of 2.4.0. https://dev.azure.com/debauchee/Barrier/_build/results?buildId=618&view=artifacts&pathAsName=false&type=publishedArtifacts You should be able to see the page, I don't think it's protected, but there are separate builds for different macOS versions. The 'symbol not found' would indicate a linking issue on a newer/older macOS version. And the link below is from a CI build of 2.3.4: https://dev.azure.com/debauchee/Barrier/_build/results?buildId=617&view=artifacts&pathAsName=false&type=publishedArtifacts So, my suggestion is to attempt using one artefact from either link that matches your macOS version - and let me know, if that's the case, we can update the release on GitHub. Thanks =)

Thank you, I'm running macOS 10.13.6 but the one from 10.14 worked

shymega commented 2 years ago

Righto. Azure doesn't support macOS 10.13 build agents, but if macOS 10.14 works for you - that's great!

On Tue, Nov 2, 2021, at 4:20 PM, mainTAP wrote:

OK, this is probably related to the CI builds included in the release notes. The link is below - it's from a CI build of 2.4.0. https://dev.azure.com/debauchee/Barrier/_build/results?buildId=618&view=artifacts&pathAsName=false&type=publishedArtifacts You should be able to see the page, I don't think it's protected, but there are separate builds for different macOS versions. The 'symbol not found' would indicate a linking issue on a newer/older macOS version. And the link below is from a CI build of 2.3.4: https://dev.azure.com/debauchee/Barrier/_build/results?buildId=617&view=artifacts&pathAsName=false&type=publishedArtifacts So, my suggestion is to attempt using one artefact from either link that matches your macOS version - and let me know, if that's the case, we can update the release on GitHub. Thanks =)

Thank you, I'm running macOS 10.13.6 but the one from 10.14 worked

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/debauchee/barrier/issues/1364#issuecomment-957910998, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKF2QAZUWJVAMHJXPDQMOTUKAFVLANCNFSM5HFRTZFA.

-- Kind regards,

Dom Rodriguez (also known as shymega)

fakezeta commented 2 years ago

Righto. Azure doesn't support macOS 10.13 build agents, but if macOS 10.14 works for you - that's great! … On Tue, Nov 2, 2021, at 4:20 PM, mainTAP wrote: > OK, this is probably related to the CI builds included in the release notes. The link is below - it's from a CI build of 2.4.0. https://dev.azure.com/debauchee/Barrier/_build/results?buildId=618&view=artifacts&pathAsName=false&type=publishedArtifacts You should be able to see the page, I don't think it's protected, but there are separate builds for different macOS versions. The 'symbol not found' would indicate a linking issue on a newer/older macOS version. And the link below is from a CI build of 2.3.4: https://dev.azure.com/debauchee/Barrier/_build/results?buildId=617&view=artifacts&pathAsName=false&type=publishedArtifacts So, my suggestion is to attempt using one artefact from either link that matches your macOS version - and let me know, if that's the case, we can update the release on GitHub. Thanks =) > Thank you, I'm running macOS 10.13.6 but the one from 10.14 worked — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1364 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKF2QAZUWJVAMHJXPDQMOTUKAFVLANCNFSM5HFRTZFA. -- Kind regards, -- Dom Rodriguez (also known as shymega)

Just to confirm the same issue with 2.4.0 on macOS 10.13.6. Solved with 10.14 artifact.

Thank you

sderose commented 2 years ago

I just installed 2.4.0-release on a MacBook Pro running Big Sur (11.6) with a 4K external monitor, and a client MacBook Air M1 running 11.6.1. When I try to start them up, both get stuck at "Barrier is starting". Have tried autoconfig and giving the client the server's IP address; no difference.

klutzak commented 2 years ago

I just installed 2.4.0-release on a MacBook Pro running Big Sur (11.6) with a 4K external monitor, and a client MacBook Air M1 running 11.6.1. When I try to start them up, both get stuck at "Barrier is starting". Have tried autoconfig and giving the client the server's IP address; no difference.

I have the same issue; running the server on a Win11 PC and the client on a MacBook Pro M1 - MacOS 12.1. Windows server autodetects and allows me to select the Mac client - but the Mac client is stuck on 'starting'.

robolmos commented 2 years ago

The CI links are blank for me. Is the 10.14 artifact able to be linked to the appropriate github releases please?

Also using 10.13.6 for one of the computers. 2.3.3 works, 2.3.4 and 2.4.0 do not, haven't tried the 10.14 artifact yet. Looks like Azure is removing the 10.14 image in the near future.

shymega commented 2 years ago

I'm no longer involved in the Barrier project, and I no longer have access to the CI infrastructure.

PeterIPROOV commented 2 years ago

I am having the same issues, is there an easy step-by-step to sort this?

alexmill commented 1 year ago

Running this set of commands on both of my machines seems to resolve this issue for me:

cd  /Users/username/Library/Application\ Support/barrier/SSL/
mkdir -p Fingerprints
openssl req -x509 -nodes -days 365 -subj /CN=barrier -newkey rsa:4096 -keyout Barrier.pem -out Barrier.pem
openssl x509 -fingerprint -sha1 -noout -in Barrier.pem > Fingerprints/Local.txt
sed -e "s/.*=//" Fingerprints/Local.txt

From this SO answer: https://stackoverflow.com/a/67343805/2628402

frogcrush commented 3 weeks ago

In my case, turning off SSL on both the client and server resolved my issue.

debauchee / barrier