You didn't attach the logs?


On Sun, Nov 06, 2016 at 06:07:13PM -0600, James Nylen wrote:
>    >**I**also tried `SHELL=/bin/bash ./tmux -vvvvv start-server` and same
>    result
>    I meant to say `SHELL=/bin/bash ./tmux -vvvvv new` here.
>    On Sun, Nov 6, 2016 at 6:06 PM, James Nylen <[1][email protected]> wrote:
> 
>      Ah, my mistake.
>      From client:
>      1478476588.612786 sending message 105 to peer 0x2644fa0 (16 bytes)
>      1478476588.612797 sending message 106 to peer 0x2644fa0 (0 bytes)
>      1478476588.612808 sending message 200 to peer 0x2644fa0 (8 bytes)
>      1478476588.612818 client loop enter
>      1478476588.637893 peer 0x2644fa0 message 211
>      1478476588.637942 peer 0x2644fa0 message 211
>      1478476588.637960 peer 0x2644fa0 message 211
>      1478476588.651970 peer 0x2644fa0 message 211
>      1478476588.652000 peer 0x2644fa0 message 203
>      1478476588.652013 client loop exit
>      From server:
>      1478476588.651457 spawn: USER=redacted
>      1478476588.651465 spawn: VISUAL=pico
>      1478476588.651472 spawn: _=./tmux
>      1478476588.651480 spawn:
>      __hook_functions_chpwd=:__hook_chpwd_check_nvmrc:
>      1478476588.651488 spawn: __last_wd=/home/redacted/code/tmux
>      1478476588.651496 spawn: __ps1_hostname=redacted
>      1478476588.651660 session 0 destroyed
>      1478476588.651682 session 0 has 2 references
>      1478476588.651709 sending message 211 to peer 0x26731e0 (8200 bytes)
>      1478476588.651730 server_client_push_stderr: client 0x2672b60, sent 51,
>      left 0
>      1478476588.651741 unref client 0x2672b60 (3 references)
>      1478476588.651753 cmdq_next <0x2672b60>:
>      callback[server_client_command_done] (1), flags 0
>      1478476588.651762 unref client 0x2672b60 (2 references)
>      1478476588.651771 cmdq_next <0x2672b60>: exit (empty)
>      1478476588.651779 cmdq_next <global>: enter
>      1478476588.651788 cmdq_next <global>: callback[notify_callback] (1),
>      flags 0
>      1478476588.651809 session 0 has 1 references
>      1478476588.651820 cmdq_next <global>: exit (empty)
>      1478476588.651829 cmdq_next <0x2672b60>: empty
>      1478476588.651837 cmdq_next <global>: empty
>      1478476588.651845 cmdq_next <0x2672b60>: empty
>      1478476588.651855 sending message 203 to peer 0x26731e0 (4 bytes)
>      1478476588.651875 session 0 freed (0 references)
>      1478476588.651928 cmdq_next <global>: empty
>      1478476588.651941 cmdq_next <0x2672b60>: empty
>      1478476588.652367 lost client 0x2672b60
>      1478476588.652485 remove peer 0x26731e0
>      1478476588.652540 unref client 0x2672b60 (1 references)
>      1478476588.652559 free client 0x2672b60 (0 references)
>      1478476588.652572 cmdq_next <global>: empty
>      1478476588.652582 server loop exit
>      Full logs attached, as before.** You'll note references to
>      /usr/local/cpanel/bin/jailshell, which I can run just fine, but I**also
>      tried `SHELL=/bin/bash ./tmux -vvvvv start-server` and same result.
>      On Sun, Nov 6, 2016 at 2:36 PM, Nicholas Marriott
>      <[2][email protected]> wrote:
> 
>        This log is from you running "tmux start-server", but start-server
>        does
>        not create a session, so tmux will exit since you are not creating one
>        in the config. Please show the log from you running "tmux new".
> 
>        On Sun, Nov 06, 2016 at 01:56:35PM -0600, James Nylen wrote:
>        >** ** Hi all,
>        >** ** I've built tmux on a server (I don't have root access here, so
>        I have to
>        >** ** build and install within my user account).** I followed very
>        close to
>        >** ** these instructions:
>        **[1][3]https://gist.github.com/ryin/3106801
>        >** ** When I run any tmux commands, e.g. `./tmux -vvvvv
>        start-server`, no output
>        >** ** is printed and the process exits immediately.
>        >** ** Here are the last few lines of the server log:
>        >** ** 1478460501.790071 preparing -t state: target none**
>        >** ** 1478460501.790079 preparing -s state: target none**
>        >** ** 1478460501.790092 unref client 0x7850b0 (2 references)
>        >** ** 1478460501.790122 sending message 203 to peer 0x7856b0 (4
>        bytes)
>        >** ** 1478460501.790738 lost client 0x7850b0
>        >** ** 1478460501.790785 remove peer 0x7856b0
>        >** ** 1478460501.790818 unref client 0x7850b0 (1 references)
>        >** ** 1478460501.790835 free client 0x7850b0 (0 references)
>        >** ** 1478460501.790848 server loop exit**
>        >** ** and the client log:
>        >** ** 1478460501.764205 sending message 105 to peer 0x76d040 (22
>        bytes)
>        >** ** 1478460501.764216 sending message 105 to peer 0x76d040 (9
>        bytes)
>        >** ** 1478460501.764226 sending message 105 to peer 0x76d040 (16
>        bytes)
>        >** ** 1478460501.764236 sending message 106 to peer 0x76d040 (0
>        bytes)
>        >** ** 1478460501.764248 sending message 200 to peer 0x76d040 (17
>        bytes)
>        >** ** 1478460501.764258 client loop enter
>        >** ** 1478460501.790307 peer 0x76d040 message 203
>        >** ** 1478460501.790347 client loop exit
>        >** ** I've attached the full logs (with username and hostname changed
>        to
>        >** ** "redacted").** There is also a `tmux-out-5635.log` but it is
>        blank for
>        >** ** this command.
>        >** ** I've tried a few things so far, and nothing helped with this
>        issue:
>        >
>        >** ** ** * Different commands (`./tmux ls`, `./tmux`, `./tmux
>        new-session`)
>        >** ** ** * Removed my ~/.tmux.conf
>        >** ** ** * Different versions of ncurses (5.9, 6.0)
>        >** ** ** * Different versions of libevent (2.0.19 stable, 2.1.6 beta)
>        >** ** ** * Different versions of tmux (`git checkout 2.3`, `git
>        checkout
>        >** ** ** ** origin/master`)
>        >
>        >** ** I also tried to follow the flow of the code but I couldn't
>        figure out what
>        >** ** operation is failing and causing tmux to exit.** How can I
>        continue
>        >** ** debugging this issue?
>        >** ** Thanks,
>        >** ** James
>        >
>        >** ** --
>        >** ** You received this message because you are subscribed to the
>        Google Groups
>        >** ** "tmux-users" group.
>        >** ** To unsubscribe from this group and stop receiving emails from
>        it, send an
>        >** ** email to [2][4][email protected].
>        >** ** To post to this group, send email to
>        [3][5][email protected].
>        >** ** For more options, visit
>        [4][6]https://groups.google.com/d/optout.
>        >
>        > References
>        >
>        >** ** Visible links
>        >** ** 1. [7]https://gist.github.com/ryin/3106801
>        >** ** 2. mailto:[8][email protected]
>        >** ** 3. mailto:[9][email protected]
>        >** ** 4. [10]https://groups.google.com/d/optout
> 
>    --
>    You received this message because you are subscribed to the Google Groups
>    "tmux-users" group.
>    To unsubscribe from this group and stop receiving emails from it, send an
>    email to [11][email protected].
>    To post to this group, send email to [12][email protected].
>    For more options, visit [13]https://groups.google.com/d/optout.
> 
> References
> 
>    Visible links
>    1. mailto:[email protected]
>    2. mailto:[email protected]
>    3. https://gist.github.com/ryin/3106801
>    4. mailto:tmux-users%[email protected]
>    5. mailto:[email protected]
>    6. https://groups.google.com/d/optout
>    7. https://gist.github.com/ryin/3106801
>    8. mailto:tmux-users%[email protected]
>    9. mailto:[email protected]
>   10. https://groups.google.com/d/optout
>   11. mailto:[email protected]
>   12. mailto:[email protected]
>   13. https://groups.google.com/d/optout

-- 
You received this message because you are subscribed to the Google Groups 
"tmux-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to