Hi Guys,
I have no idea. But the same tmux-server is back now.
On Wed, Dec 19, 2012 at 8:42 PM, Guang-Nan Cheng <chen...@gmail.com> wrote:
> No the server did not recover.
>
> Here is some addition info that I found. It seems that tmux lost it's TTY?
>
> 9655 *?* Ss 101:03 tmux
>
>
> I tried the tip
> here<http://unix.stackexchange.com/questions/40928/tmux-session-lost-in-unknown-pts-cause-and-possible-solution>
> but doesn't resolve my problem.
>
> killall -s SIGUSR1 tmux
>
>
> Here is the lsof -n -p 9655
>
> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> tmux 9655 root cwd DIR 253,1 4096 25690113 /root
> tmux 9655 root rtd DIR 253,1 4096 2 /
> tmux 9655 root txt REG 253,1 359328 2885247
> /usr/bin/tmux
> tmux 9655 root mem REG 253,1 62464 2884171
> /usr/lib64/libnss_files-2.15.so
> tmux 9655 root mem REG 253,1 141264 2884179
> /usr/lib64/libpthread-2.15.so
> tmux 9655 root mem REG 253,1 19552 2884159
> /usr/lib64/libdl-2.15.so
> tmux 9655 root mem REG 253,1 2062152 2884153
> /usr/lib64/libc-2.15.so
> tmux 9655 root mem REG 253,1 106632 2884181
> /usr/lib64/libresolv-2.15.so
> tmux 9655 root mem REG 253,1 44320 2884183
> /usr/lib64/librt-2.15.so
> tmux 9655 root mem REG 253,1 287944 2883599
> /usr/lib64/libevent-2.0.so.5.1.6
> tmux 9655 root mem REG 253,1 167608 2884216
> /usr/lib64/libtinfo.so.5.9
> tmux 9655 root mem REG 253,1 147096 2884206
> /usr/lib64/libncurses.so.5.9
> tmux 9655 root mem REG 253,1 14648 2884187
> /usr/lib64/libutil-2.15.so
> tmux 9655 root mem REG 253,1 156160 2884146
> /usr/lib64/ld-2.15.so
> tmux 9655 root 0u CHR 1,3 0t0 1028
> /dev/null
> tmux 9655 root 1u CHR 1,3 0t0 1028
> /dev/null
> tmux 9655 root 2u CHR 1,3 0t0 1028
> /dev/null
> tmux 9655 root 3u 0000 0,9 0 5608
> anon_inode
> tmux 9655 root 4u unix 0xffff88090d3a16c0 0t0 40187 socket
> tmux 9655 root 5u unix 0xffff88090d3a1a00 0t0 40188 socket
> tmux 9655 root 6u unix 0xffff88090ed4db00 0t0 27332 socket
> tmux 9655 root 7u unix 0xffff88090d3a6800 0t0 40189
> /tmp//tmux-0/default
> tmux 9655 root 8u CHR 5,2 0t0 1158
> /dev/ptmx
> tmux 9655 root 9u CHR 5,2 0t0 1158
> /dev/ptmx
> tmux 9655 root 10u unix 0xffff881017c75480 0t0 11670475
> /tmp//tmux-0/default
> tmux 9655 root 11u CHR 5,2 0t0 1158
> /dev/ptmx
> tmux 9655 root 12u CHR 5,2 0t0 1158
> /dev/ptmx
> tmux 9655 root 13u CHR 5,2 0t0 1158
> /dev/ptmx
> tmux 9655 root 14u CHR 5,2 0t0 1158
> /dev/ptmx
> tmux 9655 root 15u CHR 5,2 0t0 1158
> /dev/ptmx
> tmux 9655 root 16u CHR 5,2 0t0 1158
> /dev/ptmx
> tmux 9655 root 17u unix 0xffff88090d3a5140 0t0 11522912
> /tmp//tmux-0/default
> tmux 9655 root 18u CHR 5,2 0t0 1158
> /dev/ptmx
> tmux 9655 root 19u CHR 136,6 0t0 9
> /dev/pts/6
> tmux 9655 root 20u CHR 136,0 0t0 3
> /dev/pts/0
> tmux 9655 root 21u CHR 136,0 0t0 3
> /dev/pts/0
> tmux 9655 root 22u CHR 136,0 0t0 3
> /dev/pts/0
> tmux 9655 root 23u CHR 136,0 0t0 3
> /dev/pts/0
> tmux 9655 root 24u CHR 136,6 0t0 9
> /dev/pts/6
> tmux 9655 root 25u CHR 136,6 0t0 9
> /dev/pts/6
> tmux 9655 root 26u CHR 5,2 0t0 1158
> /dev/ptmx
> tmux 9655 root 27u CHR 136,6 0t0 9
> /dev/pts/6
>
>
>
> On Wed, Dec 19, 2012 at 8:13 PM, Nicholas Marriott <
> nicholas.marri...@gmail.com> wrote:
>
>> What happens if you kill the tmux client or close the terminal it is in?
>> Does the server recover?
>>
>>
>>
>> On Wed, Dec 19, 2012 at 07:54:28PM +0800, Guang-Nan Cheng wrote:
>> > Okay, PID 578 is the hanging attaching tmux clients. Here is the
>> backtrace
>> > for the original tmux server.
>> > (gdb) bt
>> > #0 **0x00007f8696181950 in __write_nocancel () at
>> > ../sysdeps/unix/syscall-template.S:82
>> > #1 **0x000000000042d1c0 in tty_stop_tty (tty=tty@entry=0xe12c68) at
>> > tty.c:242
>> > #2 **0x000000000042d35c in tty_close (tty=tty@entry=0xe12c68) at
>> tty.c:272
>> > #3 **0x0000000000423490 in server_client_msg_dispatch (c=0xe02b60) at
>> > server-client.c:776
>> > #4 **0x000000000042372d in server_client_callback (fd=22, events=2,
>> > data=0x7) at server-client.c:213
>> > #5 **0x00007f86968850c2 in event_process_active_single_queue
>> > (activeq=<optimized out>, base=<optimized out>) at event.c:1340
>> > #6 **event_process_active (base=<optimized out>) at event.c:1407
>> > #7 **event_base_loop (base=<optimized out>, flags=flags@entry=1) at
>> > event.c:1604
>> > #8 **0x00007f8696886131 in event_loop (flags=flags@entry=1) at
>> > event.c:1518
>> > #9 **0x0000000000424f2a in server_loop () at server.c:210
>> > #10 0x000000000042549f in server_start () at server.c:201
>> > #11 0x0000000000404829 in client_connect (path=0x66fc80
>> > "/tmp//tmux-0/default", start_server=1) at client.c:80
>> > #12 0x0000000000404ca9 in client_main (argc=argc@entry=0,
>> > argv=argv@entry=0x7fff03c09050, flags=flags@entry=1) at client.c:152
>> > #13 0x0000000000403537 in main (argc=0, argv=0x7fff03c09050) at
>> tmux.c:406
>> > On Wed, Dec 19, 2012 at 7:39 PM, Guang-Nan Cheng <[1]
>> chen...@gmail.com>
>> > wrote:
>> >
>> > Thanks for the tip. It seems**related**with epoll_wait. I have no
>> idea
>> > what it is.
>> > > strace -p 578
>> > Process 578 attached
>> > epoll_wait(3,**
>> > > gdb
>> > Missing separate debuginfos, use: debuginfo-install
>> > tmux-1.6-1.fc17.x86_64
>> > (gdb) bt
>> > #0 **0x00007f18e7b9dc53 in __epoll_wait_nocancel () from
>> > /lib64/libc.so.6
>> > #1 **0x00007f18e82a8223 in ?? () from /lib64/libevent-2.0.so.5
>> > #2 **0x00007f18e8293e00 in event_base_loop () from
>> > /lib64/libevent-2.0.so.5
>> > #3 **0x0000000000404d20 in ?? ()
>> > #4 **0x0000000000403537 in ?? ()
>> > #5 **0x00007f18e7acd735 in __libc_start_main () from
>> /lib64/libc.so.6
>> > #6 **0x000000000040374d in ?? ()
>> > #7 **0x00007fff70392898 in ?? ()
>> > #8 **0x000000000000001c in ?? ()
>> > #9 **0x0000000000000002 in ?? ()
>> > #10 0x00007fff70393bd2 in ?? ()
>> > #11 0x00007fff70393bd7 in ?? ()
>> > #12 0x0000000000000000 in ?? ()
>> > On Wed, Dec 19, 2012 at 12:59 AM, Thomas Adam <[2]
>> tho...@xteddy.org>
>> > wrote:
>> >
>> > On 18 December 2012 16:11, Guang-Nan Cheng <[3]chen...@gmail.com
>> >
>> > wrote:
>> > > It happend again. This time, I don't even have a .tmux.conf
>> file.
>> > >
>> > > Is there any trick so that I can send a signal to the PID and
>> tmux
>> > will
>> > > print the stack so we know why it hangs?
>> >
>> > Attach strace to the server pid of tmux. **Or better yet, gdb,
>> and
>> > issue "bt" to see if that helps any.
>> > -- Thomas Adam
>> >
>> > References
>> >
>> > Visible links
>> > 1. mailto:chen...@gmail.com
>> > 2. mailto:tho...@xteddy.org
>> > 3. mailto:chen...@gmail.com
>>
>
>
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users
