Is there a way to find out why tmux crashed












11














I am trying to shift from using VNC to tmux. My tmux keeps crashing at least once in a week and I am clueless why this happens. VNC rarely crashed and this weekly crash is a strong detrimental for me to completely switch.



Is there a way I can find out the reason tmux crashes ? My .tmux.conf is pretty simple 



 #Don't show the green ribbon below

 set -g status off                                                                                                                                                                                           

 #Select panes by mouse click                                                                                                                                                                                

 set -g mouse-select-pane on                                                                                                                                                                                 

 #enable scrolling by mouse in tmux                                                                                                                                                                          

 set-window-option -g mode-mouse on                                                                                                                                                                          

 #enable resize of pane by mouse                                                                                                                                                                             

 set -g mouse-resize-pane on


I use iterm2 with terminal mode set to 256 color and heavily use vim plugins and colorschemes(Lid, nerdtree, tagbar, indentLine, molokai etc.,). To adjust terminal color I had following setting in my .vimrc but I am not sure if these are in any way related to tmux crash



set t_ut=

set t_Co=256


Also, I have enabled mouse in my vim set mouse=a



Is there a way to find why my tmux session is crashing ?



EDIT: Attaching the final logs from my tmux-server



found key 0x1001: ""

input_parse: ' ground

input_c0_dispatch: '

input_parse: ' ' ground

input_parse: ' ground

input_c0_dispatch: '

keys are 1 ()

complete key  0x1001

writing key 0x1001

found key 0x1001: ""

input_parse: ' ground

input_c0_dispatch: '

input_parse: ' ' ground

input_parse: ' ground

input_c0_dispatch: '

keys are 1 ()

complete key  0x1001

writing key 0x1001

found key 0x1001: ""

input_parse: ' ground

input_c0_dispatch: '

input_parse: ' ' ground

input_parse: ' ground

input_c0_dispatch: '

keys are 1 ()

complete key  0x1001

writing key 0x1001

found key 0x1001: ""

input_parse: '' ground

input_c0_dispatch: '

got 5 from client 6

writing 4 to client 6

got 13 from client 6





tmux







share|improve this question




















  • 7




    Can you start tmux using tmux -vvvv ? It will give you a logfile in the same directory called tmux-[...].log. Try to reproduce the crash and as soon as it crashes, post the last X lines of your error log here :)!
    – polym
    Jul 24 '14 at 0:19












  • @polym I have started tmux as follows tmux -vvv -S default new-session -s $USER I will paste the log during the next crash
    – user881300
    Jul 24 '14 at 1:02












  • @polym Here is the output of tmux server after it crashed. user@server> tail tmux-server-33131.log input_parse: ' ' ground keys are 1 () complete key 0x2 keys are 1 (d) complete key d 0x64 cmdq 0x12c4460: detach-client (client 8) writing 1 to client 8 got 5 from client 8 writing 4 to client 8 lost client 8 user@server>
    – user881300
    Jul 24 '14 at 18:14












  • can you edit your question and put more of the logs (server and client) e.g. tail -n200 ?
    – polym
    Jul 24 '14 at 20:04










  • @polym I have attached the logs to the question after tmux has crashed
    – user881300
    Jul 28 '14 at 22:22
















11














I am trying to shift from using VNC to tmux. My tmux keeps crashing at least once in a week and I am clueless why this happens. VNC rarely crashed and this weekly crash is a strong detrimental for me to completely switch.



Is there a way I can find out the reason tmux crashes ? My .tmux.conf is pretty simple 



 #Don't show the green ribbon below

 set -g status off                                                                                                                                                                                           

 #Select panes by mouse click                                                                                                                                                                                

 set -g mouse-select-pane on                                                                                                                                                                                 

 #enable scrolling by mouse in tmux                                                                                                                                                                          

 set-window-option -g mode-mouse on                                                                                                                                                                          

 #enable resize of pane by mouse                                                                                                                                                                             

 set -g mouse-resize-pane on


I use iterm2 with terminal mode set to 256 color and heavily use vim plugins and colorschemes(Lid, nerdtree, tagbar, indentLine, molokai etc.,). To adjust terminal color I had following setting in my .vimrc but I am not sure if these are in any way related to tmux crash



set t_ut=

set t_Co=256


Also, I have enabled mouse in my vim set mouse=a



Is there a way to find why my tmux session is crashing ?



EDIT: Attaching the final logs from my tmux-server



found key 0x1001: ""

input_parse: ' ground

input_c0_dispatch: '

input_parse: ' ' ground

input_parse: ' ground

input_c0_dispatch: '

keys are 1 ()

complete key  0x1001

writing key 0x1001

found key 0x1001: ""

input_parse: ' ground

input_c0_dispatch: '

input_parse: ' ' ground

input_parse: ' ground

input_c0_dispatch: '

keys are 1 ()

complete key  0x1001

writing key 0x1001

found key 0x1001: ""

input_parse: ' ground

input_c0_dispatch: '

input_parse: ' ' ground

input_parse: ' ground

input_c0_dispatch: '

keys are 1 ()

complete key  0x1001

writing key 0x1001

found key 0x1001: ""

input_parse: '' ground

input_c0_dispatch: '

got 5 from client 6

writing 4 to client 6

got 13 from client 6





tmux







share|improve this question




















  • 7




    Can you start tmux using tmux -vvvv ? It will give you a logfile in the same directory called tmux-[...].log. Try to reproduce the crash and as soon as it crashes, post the last X lines of your error log here :)!
    – polym
    Jul 24 '14 at 0:19












  • @polym I have started tmux as follows tmux -vvv -S default new-session -s $USER I will paste the log during the next crash
    – user881300
    Jul 24 '14 at 1:02












  • @polym Here is the output of tmux server after it crashed. user@server> tail tmux-server-33131.log input_parse: ' ' ground keys are 1 () complete key 0x2 keys are 1 (d) complete key d 0x64 cmdq 0x12c4460: detach-client (client 8) writing 1 to client 8 got 5 from client 8 writing 4 to client 8 lost client 8 user@server>
    – user881300
    Jul 24 '14 at 18:14












  • can you edit your question and put more of the logs (server and client) e.g. tail -n200 ?
    – polym
    Jul 24 '14 at 20:04










  • @polym I have attached the logs to the question after tmux has crashed
    – user881300
    Jul 28 '14 at 22:22














11












11








11


2





I am trying to shift from using VNC to tmux. My tmux keeps crashing at least once in a week and I am clueless why this happens. VNC rarely crashed and this weekly crash is a strong detrimental for me to completely switch.



Is there a way I can find out the reason tmux crashes ? My .tmux.conf is pretty simple 



 #Don't show the green ribbon below

 set -g status off                                                                                                                                                                                           

 #Select panes by mouse click                                                                                                                                                                                

 set -g mouse-select-pane on                                                                                                                                                                                 

 #enable scrolling by mouse in tmux                                                                                                                                                                          

 set-window-option -g mode-mouse on                                                                                                                                                                          

 #enable resize of pane by mouse                                                                                                                                                                             

 set -g mouse-resize-pane on


I use iterm2 with terminal mode set to 256 color and heavily use vim plugins and colorschemes(Lid, nerdtree, tagbar, indentLine, molokai etc.,). To adjust terminal color I had following setting in my .vimrc but I am not sure if these are in any way related to tmux crash



set t_ut=

set t_Co=256


Also, I have enabled mouse in my vim set mouse=a



Is there a way to find why my tmux session is crashing ?



EDIT: Attaching the final logs from my tmux-server



found key 0x1001: ""

input_parse: ' ground

input_c0_dispatch: '

input_parse: ' ' ground

input_parse: ' ground

input_c0_dispatch: '

keys are 1 ()

complete key  0x1001

writing key 0x1001

found key 0x1001: ""

input_parse: ' ground

input_c0_dispatch: '

input_parse: ' ' ground

input_parse: ' ground

input_c0_dispatch: '

keys are 1 ()

complete key  0x1001

writing key 0x1001

found key 0x1001: ""

input_parse: ' ground

input_c0_dispatch: '

input_parse: ' ' ground

input_parse: ' ground

input_c0_dispatch: '

keys are 1 ()

complete key  0x1001

writing key 0x1001

found key 0x1001: ""

input_parse: '' ground

input_c0_dispatch: '

got 5 from client 6

writing 4 to client 6

got 13 from client 6





tmux







share|improve this question















I am trying to shift from using VNC to tmux. My tmux keeps crashing at least once in a week and I am clueless why this happens. VNC rarely crashed and this weekly crash is a strong detrimental for me to completely switch.



Is there a way I can find out the reason tmux crashes ? My .tmux.conf is pretty simple 



 #Don't show the green ribbon below

 set -g status off                                                                                                                                                                                           

 #Select panes by mouse click                                                                                                                                                                                

 set -g mouse-select-pane on                                                                                                                                                                                 

 #enable scrolling by mouse in tmux                                                                                                                                                                          

 set-window-option -g mode-mouse on                                                                                                                                                                          

 #enable resize of pane by mouse                                                                                                                                                                             

 set -g mouse-resize-pane on


I use iterm2 with terminal mode set to 256 color and heavily use vim plugins and colorschemes(Lid, nerdtree, tagbar, indentLine, molokai etc.,). To adjust terminal color I had following setting in my .vimrc but I am not sure if these are in any way related to tmux crash



set t_ut=

set t_Co=256


Also, I have enabled mouse in my vim set mouse=a



Is there a way to find why my tmux session is crashing ?



EDIT: Attaching the final logs from my tmux-server



found key 0x1001: ""

input_parse: ' ground

input_c0_dispatch: '

input_parse: ' ' ground

input_parse: ' ground

input_c0_dispatch: '

keys are 1 ()

complete key  0x1001

writing key 0x1001

found key 0x1001: ""

input_parse: ' ground

input_c0_dispatch: '

input_parse: ' ' ground

input_parse: ' ground

input_c0_dispatch: '

keys are 1 ()

complete key  0x1001

writing key 0x1001

found key 0x1001: ""

input_parse: ' ground

input_c0_dispatch: '

input_parse: ' ' ground

input_parse: ' ground

input_c0_dispatch: '

keys are 1 ()

complete key  0x1001

writing key 0x1001

found key 0x1001: ""

input_parse: '' ground

input_c0_dispatch: '

got 5 from client 6

writing 4 to client 6

got 13 from client 6





tmux




tmux






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 28 '14 at 22:12







user881300

















asked Jul 23 '14 at 22:35









user881300user881300

5192714




5192714








  • 7




    Can you start tmux using tmux -vvvv ? It will give you a logfile in the same directory called tmux-[...].log. Try to reproduce the crash and as soon as it crashes, post the last X lines of your error log here :)!
    – polym
    Jul 24 '14 at 0:19












  • @polym I have started tmux as follows tmux -vvv -S default new-session -s $USER I will paste the log during the next crash
    – user881300
    Jul 24 '14 at 1:02












  • @polym Here is the output of tmux server after it crashed. user@server> tail tmux-server-33131.log input_parse: ' ' ground keys are 1 () complete key 0x2 keys are 1 (d) complete key d 0x64 cmdq 0x12c4460: detach-client (client 8) writing 1 to client 8 got 5 from client 8 writing 4 to client 8 lost client 8 user@server>
    – user881300
    Jul 24 '14 at 18:14












  • can you edit your question and put more of the logs (server and client) e.g. tail -n200 ?
    – polym
    Jul 24 '14 at 20:04










  • @polym I have attached the logs to the question after tmux has crashed
    – user881300
    Jul 28 '14 at 22:22














  • 7




    Can you start tmux using tmux -vvvv ? It will give you a logfile in the same directory called tmux-[...].log. Try to reproduce the crash and as soon as it crashes, post the last X lines of your error log here :)!
    – polym
    Jul 24 '14 at 0:19












  • @polym I have started tmux as follows tmux -vvv -S default new-session -s $USER I will paste the log during the next crash
    – user881300
    Jul 24 '14 at 1:02












  • @polym Here is the output of tmux server after it crashed. user@server> tail tmux-server-33131.log input_parse: ' ' ground keys are 1 () complete key 0x2 keys are 1 (d) complete key d 0x64 cmdq 0x12c4460: detach-client (client 8) writing 1 to client 8 got 5 from client 8 writing 4 to client 8 lost client 8 user@server>
    – user881300
    Jul 24 '14 at 18:14












  • can you edit your question and put more of the logs (server and client) e.g. tail -n200 ?
    – polym
    Jul 24 '14 at 20:04










  • @polym I have attached the logs to the question after tmux has crashed
    – user881300
    Jul 28 '14 at 22:22








7




7




Can you start tmux using tmux -vvvv ? It will give you a logfile in the same directory called tmux-[...].log. Try to reproduce the crash and as soon as it crashes, post the last X lines of your error log here :)!
– polym
Jul 24 '14 at 0:19






Can you start tmux using tmux -vvvv ? It will give you a logfile in the same directory called tmux-[...].log. Try to reproduce the crash and as soon as it crashes, post the last X lines of your error log here :)!
– polym
Jul 24 '14 at 0:19














@polym I have started tmux as follows tmux -vvv -S default new-session -s $USER I will paste the log during the next crash
– user881300
Jul 24 '14 at 1:02






@polym I have started tmux as follows tmux -vvv -S default new-session -s $USER I will paste the log during the next crash
– user881300
Jul 24 '14 at 1:02














@polym Here is the output of tmux server after it crashed. user@server> tail tmux-server-33131.log input_parse: ' ' ground keys are 1 () complete key 0x2 keys are 1 (d) complete key d 0x64 cmdq 0x12c4460: detach-client (client 8) writing 1 to client 8 got 5 from client 8 writing 4 to client 8 lost client 8 user@server>
– user881300
Jul 24 '14 at 18:14






@polym Here is the output of tmux server after it crashed. user@server> tail tmux-server-33131.log input_parse: ' ' ground keys are 1 () complete key 0x2 keys are 1 (d) complete key d 0x64 cmdq 0x12c4460: detach-client (client 8) writing 1 to client 8 got 5 from client 8 writing 4 to client 8 lost client 8 user@server>
– user881300
Jul 24 '14 at 18:14














can you edit your question and put more of the logs (server and client) e.g. tail -n200 ?
– polym
Jul 24 '14 at 20:04




can you edit your question and put more of the logs (server and client) e.g. tail -n200 ?
– polym
Jul 24 '14 at 20:04












@polym I have attached the logs to the question after tmux has crashed
– user881300
Jul 28 '14 at 22:22




@polym I have attached the logs to the question after tmux has crashed
– user881300
Jul 28 '14 at 22:22










2 Answers
2






active

oldest

votes


















1














This may/will depend on the distro you're using, and whether or not debug/dev packages for tmux are installed, and whether or not it would dump core (if the OS settings permit it to). If it dumps core, and you have a debug version, you should be able to narrow the reason for the failure down quite nicely.






share|improve this answer





























    0














    I found this in the readme on the tmux github page.



    "For debugging, running tmux with -v or -vv will generate server and client log
    files in the current directory."



    In other words, unless you explicitly told it to log, it won't.






    share|improve this answer








    New contributor




    Robert Baker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.


















      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "106"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f146228%2fis-there-a-way-to-find-out-why-tmux-crashed%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      1














      This may/will depend on the distro you're using, and whether or not debug/dev packages for tmux are installed, and whether or not it would dump core (if the OS settings permit it to). If it dumps core, and you have a debug version, you should be able to narrow the reason for the failure down quite nicely.






      share|improve this answer


























        1














        This may/will depend on the distro you're using, and whether or not debug/dev packages for tmux are installed, and whether or not it would dump core (if the OS settings permit it to). If it dumps core, and you have a debug version, you should be able to narrow the reason for the failure down quite nicely.






        share|improve this answer
























          1












          1








          1






          This may/will depend on the distro you're using, and whether or not debug/dev packages for tmux are installed, and whether or not it would dump core (if the OS settings permit it to). If it dumps core, and you have a debug version, you should be able to narrow the reason for the failure down quite nicely.






          share|improve this answer












          This may/will depend on the distro you're using, and whether or not debug/dev packages for tmux are installed, and whether or not it would dump core (if the OS settings permit it to). If it dumps core, and you have a debug version, you should be able to narrow the reason for the failure down quite nicely.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jul 23 '14 at 22:52









          tinktink

          4,16211219




          4,16211219

























              0














              I found this in the readme on the tmux github page.



              "For debugging, running tmux with -v or -vv will generate server and client log
              files in the current directory."



              In other words, unless you explicitly told it to log, it won't.






              share|improve this answer








              New contributor




              Robert Baker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.























                0














                I found this in the readme on the tmux github page.



                "For debugging, running tmux with -v or -vv will generate server and client log
                files in the current directory."



                In other words, unless you explicitly told it to log, it won't.






                share|improve this answer








                New contributor




                Robert Baker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.





















                  0












                  0








                  0






                  I found this in the readme on the tmux github page.



                  "For debugging, running tmux with -v or -vv will generate server and client log
                  files in the current directory."



                  In other words, unless you explicitly told it to log, it won't.






                  share|improve this answer








                  New contributor




                  Robert Baker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  I found this in the readme on the tmux github page.



                  "For debugging, running tmux with -v or -vv will generate server and client log
                  files in the current directory."



                  In other words, unless you explicitly told it to log, it won't.







                  share|improve this answer








                  New contributor




                  Robert Baker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  share|improve this answer



                  share|improve this answer






                  New contributor




                  Robert Baker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  answered 3 hours ago









                  Robert BakerRobert Baker

                  12




                  12




                  New contributor




                  Robert Baker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.





                  New contributor





                  Robert Baker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






                  Robert Baker is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Unix & Linux Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid …



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid …



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f146228%2fis-there-a-way-to-find-out-why-tmux-crashed%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      -

                      Popular posts from this blog

                      Accessing regular linux commands in Huawei's Dopra Linux

                      Image
                      4 Backstory: I have a Huawei HG8245 router in my house and I want to change the default username/password. I've tried following this guide but the config file always gets reset. My ISP isn't helping either so I'm looking for other ways to accomplish this. The router has telnet access so this seems like a way to change the credentials. The first shell I gain access to looks like this: WAP> Pressing "?" gives me a list of available commands which I've pasted here, the two interesting ones are "su" and "shell". I can't seem to get su access, even after logging in as root (challenge password prompt, and then nothing happens), but shell gives me a proper linux shell. WAP>shell BusyBox v1.18.4 (2017-12-26 17:06:34 CST) built-in shell (ash) Enter 'hel...
                      Read more

                      Can't connect RFCOMM socket: Host is down

                      Image
                      up vote 3 down vote favorite I have bluez 5.4.3 and I am attempting to communicate with a ble device through minicom. These two deceives (my computer and a bluno nano) are alreadt paired and this has been my method so far. #bluetoothctl # pair xx:xx:xx:xx:xx:xx # exit Everything is working well so far then... #sudo rfcomm connect /dev/rfcomm0 xx:xx:xx:xx:xx:xx 1 & [1] 3665 Can't connect RFCOMM socket: Host is down Does anyone know how to resolve this issue? Any help would be very much appreciated. bluetooth bluez share | improve this question asked Feb 9 '17 at 18:46 Brandon Knape 46 2 ...
                      Read more

                      Kernel panic - not syncing: Fatal Exception in Interrupt

                      Image
                      0 Every day this error occured on my pc, kernel panic error on interrupt, what will be the problem? linux-mint share asked 6 mins ago Vinod Selvin Vinod Selvin 1 1 New contributor Vinod Selvin is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment ...
                      Read more