We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Commit a712bbe
Steps to reproduce:
greg@gregdev:~/ga/slack/build$ ./slack++
Returned error:
Welcome to slack++ Could not connect. Check your connection and retry.
Troubleshooting performed to date (all returned error above):
--- Verification of token
greg@gregdev:~/ga/slack/build$ echo $SLACK_TOKEN xoxp-317<redacted>244
greg@gregdev:~/ga/slack/build$ ./slack++ SLACK_TOKEN
greg@gregdev:~/ga/slack/build$ ./slack++ xoxp-317<redacted>244
Have also re-issued slack token, as well as tried connecting to a different slack organization entirely. Machine has Same result.
--- Network trace
greg@gregdev:~/ga/slack/build$ strace -f -e trace=network -s 10000 ./slack++ > out.log
output of log:
connect(4, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 4 connect(4, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 5 strace: Process 7590 attached [pid 7590] socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5 [pid 7590] connect(5, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) [pid 7590] socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5 [pid 7590] connect(5, {sa_family=AF_LOCAL, sun_path="/var/run/nscd/socket"}, 110) = -1 ENOENT (No such file or directory) [pid 7590] socket(PF_INET, SOCK_DGRAM|SOCK_NONBLOCK, IPPROTO_IP) = 5 [pid 7590] connect(5, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("127.0.1.1")}, 16) = 0 [pid 7590] sendmmsg(5, {{{msg_name(0)=NULL, msg_iov(1)=[{"\307i\1\0\0\1\0\0\0\0\0\0\5slack\3com\0\0\1\0\1", 27}], msg_controllen=0, msg_flags=MSG_DONTROUTE|MSG_DONTWAIT|MSG_EOR|MSG_WAITALL|MSG_ERRQUEUE|MSG_FASTOPEN|MSG_CMSG_CLOEXEC|0xc8c0010}, 27}, {{msg_name(0)=NULL, msg_iov(1)=[{"\237\277\1\0\0\1\0\0\0\0\0\0\5slack\3com\0\0\34\0\1", 27}], msg_controllen=0, msg_flags=MSG_OOB|MSG_DONTROUTE|MSG_CTRUNC|0x10}, 27}}, 2, MSG_NOSIGNAL) = 2 pid 7590] recvfrom(5, "\307i\201\200\0\1\0\1\0\0\0\0\5slack\3com\0\0\1\0\1\300\f\0\1\0\1\0\0\0\r\0\4\r!i%", 2048, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("127.0.1.1")}, [16]) = 43 [pid 7590] recvfrom(5, "\237\277\201\200\0\1\0\0\0\1\0\0\5slack\3com\0\0\34\0\1\300\f\0\6\0\1\0\0\0017\0F\7ns-1493\tawsdns-58\3org\0\21awsdns-hostmaster\6amazon\300\22\0\0\0\1\0\0\34 \0\0\3\204\0\22u\0\0\0\1,", 65536, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("127.0.1.1")}, [16]) = 109 [pid 7590] +++ exited with 0 +++ Welcome to slack++ socket(PF_INET, SOCK_STREAM, IPPROTO_TCP) = 5 connect(5, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("13.33.105.37")}, 16) = -1 EINPROGRESS (Operation now in progress) getsockopt(5, SOL_SOCKET, SO_ERROR, [0], [4]) = 0 getpeername(5, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("13.33.105.37")}, [16]) = 0 getsockname(5, {sa_family=AF_INET, sin_port=htons(55728), sin_addr=inet_addr("192.168.8.21")}, [16]) = 0
@FedeDP any thoughts?
The text was updated successfully, but these errors were encountered:
That's weird. I can connect, even if after that i'm hit by #3 . Are you connected to a slow/unstable network?
Sorry, something went wrong.
It seems i have fixed #3 (at least on my machine, waiting for input by other users on that issue). Can you please retry?
No branches or pull requests
Commit a712bbe
Steps to reproduce:
Returned error:
Troubleshooting performed to date (all returned error above):
--- Verification of token
Have also re-issued slack token, as well as tried connecting to a different slack organization entirely. Machine has Same result.
--- Network trace
output of log:
@FedeDP any thoughts?
The text was updated successfully, but these errors were encountered: