Ci-dessous, les différences entre deux révisions de la page.
— |
linux:debug [30-03-2021 11:01] (Version actuelle) edmc73 créée |
||
---|---|---|---|
Ligne 1: | Ligne 1: | ||
+ | ====== Debug ====== | ||
+ | |||
+ | commande pour voir ce qui se passe dans un process | ||
+ | |||
+ | First find the rserver process-id. | ||
+ | |||
+ | ps auxw | grep studio | ||
+ | rstudio-server | ||
+ | |||
+ | Note the second number that appears on the output of a row containing the string rstudio-server/ | ||
+ | |||
+ | Then trace rserver sending the output to a file. The number after -p should be the rserver process-id. The funky -e option is used to cut-down noise from Java's thread management. | ||
+ | |||
+ | sudo strace -f -e ' | ||
+ | |||
+ | Login and wait for the error message to appear. | ||
+ | |||
+ | Stop the tracing by pressing ctrl-c. | ||
+ | |||
+ | Open the file with your favourite editor, and search for the string exit_group. | ||
+ | |||
+ | The lines above it are likely to indicate the error in rsession. In my case it was a symbolic link from .rstudio to a missing directory. | ||
+ | |||
+ | 7529 mkdir("/ | ||
+ | 7529 stat("/ | ||
+ | 7529 write(2, "07 Feb 2015 16:46:53 [rsession-d" | ||
+ | 7529 sendto(3, "< | ||
+ | 7529 exit_group(1) |