Got an error while trying to get a shell: "Cannot make/remove an entry for the specified session" about wetty HOT 17 CLOSED

I am using docker 1.2.0 and it works fine for me. Can you check with latest docker?

from wetty.

@zoobab shall I close the bug?

from wetty.

Will try on docker 1.2.0 and give you my feedback.

from wetty.

I still have this issue. Docker version 1.5.0, build a8a31ef, on Linux Mint 13.

from wetty.

@nathanleclaire did you ever hit this problem?

from wetty.

I haven't- @j-bennet @zoobab which image(s) and commands are you running which give you get this result? What is your host setup like? Any VPN or firewall? nathanleclaire/wetty with a similar command works for me. Tested on Mac/Windows with a VM running boot2docker.

from wetty.

I am using the dockerized version and the following command:
sudo docker run --rm --name term -p 3000 -it nathanleclaire/wetty

This is my Docker version:
Docker version 1.5.0, build a8a31ef

I am on Linux Mint 13, using VPN. Here is my ifconfig output:

docker0 Link encap:Ethernet HWaddr 56:84:7a:fe:97:99
inet addr:172.17.42.1 Bcast:0.0.0.0 Mask:255.255.0.0
inet6 addr: fe80::5484:7aff:fefe:9799/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:391 errors:0 dropped:0 overruns:0 frame:0
TX packets:459 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1492059 (1.4 MB) TX bytes:48292 (48.2 KB)

eth0 Link encap:Ethernet HWaddr 5c:f9:dd:6e:8a:e4
inet addr:192.168.0.111 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::5ef9:ddff:fe6e:8ae4/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13651833 errors:0 dropped:0 overruns:0 frame:0
TX packets:13156118 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7790327375 (7.7 GB) TX bytes:11043568767 (11.0 GB)
Interrupt:20 Memory:dcb00000-dcb20000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:407257 errors:0 dropped:0 overruns:0 frame:0
TX packets:407257 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:168320811 (168.3 MB) TX bytes:168320811 (168.3 MB)

tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:172.20.7.36 P-t-P:172.20.7.36 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1300 Metric:1
RX packets:133 errors:0 dropped:0 overruns:0 frame:0
TX packets:180 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:21762 (21.7 KB) TX bytes:16048 (16.0 KB)

veth2850e0b Link encap:Ethernet HWaddr 3a:d3:c6:bc:01:89
inet6 addr: fe80::38d3:c6ff:febc:189/64 Scope:Link
UP BROADCAST RUNNING MTU:1500 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:398 (398.0 B) TX bytes:1632 (1.6 KB)

from wetty.

@j-bennet Hm... that command works for me on boot2docker VM. If you run wetty natively with node app.js -p 3000 from the source does it work?

Also, please try docker rmi nathanleclaire/wetty and run the docker command you mentioned again.

from wetty.

@nathanleclaire I tried and I can't run it natively. This is what I did:

git clone [email protected]:krishnasrinivas/wetty.git
cd ./wetty
npm install
openssl req -x509 -newkey rsa:2048 -keyout key.pem -out cert.pem -days 30000 -nodes
node app.js --sslkey key.pem --sslcert cert.pem -p 3000

And this is the error I get:

from wetty.

@j-bennet it's giving 'connection refused' as you are not running ssh-server at port 22 on your localhost. Can you try @nathanleclaire's other suggestion of doing 'rmi' and re-running?

from wetty.

@krishnasrinivas Yes, I actually tried that suggestion first. I got the same "Cannot make/remove an entry..." error as before.

from wetty.

@j-bennet still having this issue?

from wetty.

I just tried the docker image again, this time on Mac with docker-machine. I don't have the same error. However, when I browse to {docker container IP}:3000, Firefox says "Connecting...", never connects, then spits out a "The connection has timed out" page.

from wetty.

Anyone have solution of this?
I got same error on it.

from wetty.

Can anyone help me?

On Ubuntu, it's working fine, but in CentOs7 after proving credentials it displayed: "Cannot make/remove an entry for the specified session"

from wetty.

Not sure if applicable to present code base running on CentOS7, however, prior to Oct 22, 2017 when app.js was still present and executed by the node entry point, this issue could be resolved by modifying the following line in /etc/pam.d/login
session required pam_loginuid.so
to
session optional pam_loginuid.so

from wetty.

closing issue due to lack of recent activity.
if this is still an issue please reopen, and if @heatmiser suggestion works please feel free to open a pr documenting this

from wetty.