vncserver dies immediately upon start











up vote
0
down vote

favorite












I'm trying to configure VNC server for remote logins on a fresh install of CentOS 7, but I just can't seem to get it working right.



I've followed the install steps here including the firewall-cmd steps, but when I run systemctl status vncserver@:1.service, I see:



Loaded: loaded (/etc/systemd/system/vncserver@:1.service; enabled; vendor preset: disabled)
Active: inactive (dead) since <~4 seconds after start time>
Main PID: 1462 (code=exited, status=0/SUCCESS)

<start time> localhost.localdomain systemd[1]: Starting Remote desktop service (VNC)...
<start time+3> localhost.localdomaind systemd[1]: Started Remote desktop service (VNC).


When I instead try to run vncserver manually (as su - remote-user), the log output (in /home/remote-user/.vnc/localhost.localdomain:1.log) is:



  vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5901
vncext: created VNC server for screen 0
Killing Xvnc process ID 17085


Other thing that may be causing or contributing to the issue:



In /etc/systemd/system/vncserver@:1.service, the line:



PIDFile=/home/remote-user/.vnc/%H%i.pid


Doesn't appear to generate any .pid files. /home/remote-user/.vnc contains no files ending in .pid; this may be because the vnc process doesn't live long enough to create them, but I'm not sure.










share|improve this question









New contributor




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
























    up vote
    0
    down vote

    favorite












    I'm trying to configure VNC server for remote logins on a fresh install of CentOS 7, but I just can't seem to get it working right.



    I've followed the install steps here including the firewall-cmd steps, but when I run systemctl status vncserver@:1.service, I see:



    Loaded: loaded (/etc/systemd/system/vncserver@:1.service; enabled; vendor preset: disabled)
    Active: inactive (dead) since <~4 seconds after start time>
    Main PID: 1462 (code=exited, status=0/SUCCESS)

    <start time> localhost.localdomain systemd[1]: Starting Remote desktop service (VNC)...
    <start time+3> localhost.localdomaind systemd[1]: Started Remote desktop service (VNC).


    When I instead try to run vncserver manually (as su - remote-user), the log output (in /home/remote-user/.vnc/localhost.localdomain:1.log) is:



      vncext: VNC extension running!
    vncext: Listening for VNC connections on all interface(s), port 5901
    vncext: created VNC server for screen 0
    Killing Xvnc process ID 17085


    Other thing that may be causing or contributing to the issue:



    In /etc/systemd/system/vncserver@:1.service, the line:



    PIDFile=/home/remote-user/.vnc/%H%i.pid


    Doesn't appear to generate any .pid files. /home/remote-user/.vnc contains no files ending in .pid; this may be because the vnc process doesn't live long enough to create them, but I'm not sure.










    share|improve this question









    New contributor




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






















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I'm trying to configure VNC server for remote logins on a fresh install of CentOS 7, but I just can't seem to get it working right.



      I've followed the install steps here including the firewall-cmd steps, but when I run systemctl status vncserver@:1.service, I see:



      Loaded: loaded (/etc/systemd/system/vncserver@:1.service; enabled; vendor preset: disabled)
      Active: inactive (dead) since <~4 seconds after start time>
      Main PID: 1462 (code=exited, status=0/SUCCESS)

      <start time> localhost.localdomain systemd[1]: Starting Remote desktop service (VNC)...
      <start time+3> localhost.localdomaind systemd[1]: Started Remote desktop service (VNC).


      When I instead try to run vncserver manually (as su - remote-user), the log output (in /home/remote-user/.vnc/localhost.localdomain:1.log) is:



        vncext: VNC extension running!
      vncext: Listening for VNC connections on all interface(s), port 5901
      vncext: created VNC server for screen 0
      Killing Xvnc process ID 17085


      Other thing that may be causing or contributing to the issue:



      In /etc/systemd/system/vncserver@:1.service, the line:



      PIDFile=/home/remote-user/.vnc/%H%i.pid


      Doesn't appear to generate any .pid files. /home/remote-user/.vnc contains no files ending in .pid; this may be because the vnc process doesn't live long enough to create them, but I'm not sure.










      share|improve this question









      New contributor




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











      I'm trying to configure VNC server for remote logins on a fresh install of CentOS 7, but I just can't seem to get it working right.



      I've followed the install steps here including the firewall-cmd steps, but when I run systemctl status vncserver@:1.service, I see:



      Loaded: loaded (/etc/systemd/system/vncserver@:1.service; enabled; vendor preset: disabled)
      Active: inactive (dead) since <~4 seconds after start time>
      Main PID: 1462 (code=exited, status=0/SUCCESS)

      <start time> localhost.localdomain systemd[1]: Starting Remote desktop service (VNC)...
      <start time+3> localhost.localdomaind systemd[1]: Started Remote desktop service (VNC).


      When I instead try to run vncserver manually (as su - remote-user), the log output (in /home/remote-user/.vnc/localhost.localdomain:1.log) is:



        vncext: VNC extension running!
      vncext: Listening for VNC connections on all interface(s), port 5901
      vncext: created VNC server for screen 0
      Killing Xvnc process ID 17085


      Other thing that may be causing or contributing to the issue:



      In /etc/systemd/system/vncserver@:1.service, the line:



      PIDFile=/home/remote-user/.vnc/%H%i.pid


      Doesn't appear to generate any .pid files. /home/remote-user/.vnc contains no files ending in .pid; this may be because the vnc process doesn't live long enough to create them, but I'm not sure.







      centos vnc






      share|improve this question









      New contributor




      Chris B 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 question









      New contributor




      Chris B 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 question




      share|improve this question








      edited 2 days ago









      Rui F Ribeiro

      38.5k1479128




      38.5k1479128






      New contributor




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









      asked 2 days ago









      Chris B

      1




      1




      New contributor




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





      New contributor





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






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



























          active

          oldest

          votes











          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',
          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
          });


          }
          });






          Chris B is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f487422%2fvncserver-dies-immediately-upon-start%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          Chris B is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          Chris B is a new contributor. Be nice, and check out our Code of Conduct.













          Chris B is a new contributor. Be nice, and check out our Code of Conduct.












          Chris B is a new contributor. Be nice, and check out our Code of Conduct.
















          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%2f487422%2fvncserver-dies-immediately-upon-start%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

          Entries order in /etc/network/interfaces

          新発田市

          Grub takes very long (several minutes) to open Menu (in Multi-Boot-System)