Forever monitor - Unable to view log file in a distributed file system












1















I have a Nodejs app running using forever monitor. The source code resides in a distributed file system (say /mydir/myapp).



I use a VM to start the nodejs server. If i launch a second VM and open /mydir/myapp , i see the log files forever monitor creates but the size is always 0, if i open the file using any editor it is empty. From the first VM the see the size of the log is non-empty and the content is visible.



Note: As long as the forever monitor is running this problem is present, if the forever monitor is closed then i am able to view logs from both VMs.



VMs are running on x86 machines using RHEL 6.4 (santiago) Gnome 2.28.2



The forever monitor code is as given below.



var child = new (forever.Monitor)('myscript.js', {
max: 100,
silent: false,
args: ,
logFile: '/logs/myapp_forever.log', // Path to log output from forever process (when daemonized)
outFile: '/logs/myapp_stdout.log', // Path to log output from child stdout
errFile: '/logs/myapp_stderr.log', // Path to log output from child stderr
});


Any help here is much appreciated. Thanks !










share|improve this question



























    1















    I have a Nodejs app running using forever monitor. The source code resides in a distributed file system (say /mydir/myapp).



    I use a VM to start the nodejs server. If i launch a second VM and open /mydir/myapp , i see the log files forever monitor creates but the size is always 0, if i open the file using any editor it is empty. From the first VM the see the size of the log is non-empty and the content is visible.



    Note: As long as the forever monitor is running this problem is present, if the forever monitor is closed then i am able to view logs from both VMs.



    VMs are running on x86 machines using RHEL 6.4 (santiago) Gnome 2.28.2



    The forever monitor code is as given below.



    var child = new (forever.Monitor)('myscript.js', {
    max: 100,
    silent: false,
    args: ,
    logFile: '/logs/myapp_forever.log', // Path to log output from forever process (when daemonized)
    outFile: '/logs/myapp_stdout.log', // Path to log output from child stdout
    errFile: '/logs/myapp_stderr.log', // Path to log output from child stderr
    });


    Any help here is much appreciated. Thanks !










    share|improve this question

























      1












      1








      1








      I have a Nodejs app running using forever monitor. The source code resides in a distributed file system (say /mydir/myapp).



      I use a VM to start the nodejs server. If i launch a second VM and open /mydir/myapp , i see the log files forever monitor creates but the size is always 0, if i open the file using any editor it is empty. From the first VM the see the size of the log is non-empty and the content is visible.



      Note: As long as the forever monitor is running this problem is present, if the forever monitor is closed then i am able to view logs from both VMs.



      VMs are running on x86 machines using RHEL 6.4 (santiago) Gnome 2.28.2



      The forever monitor code is as given below.



      var child = new (forever.Monitor)('myscript.js', {
      max: 100,
      silent: false,
      args: ,
      logFile: '/logs/myapp_forever.log', // Path to log output from forever process (when daemonized)
      outFile: '/logs/myapp_stdout.log', // Path to log output from child stdout
      errFile: '/logs/myapp_stderr.log', // Path to log output from child stderr
      });


      Any help here is much appreciated. Thanks !










      share|improve this question














      I have a Nodejs app running using forever monitor. The source code resides in a distributed file system (say /mydir/myapp).



      I use a VM to start the nodejs server. If i launch a second VM and open /mydir/myapp , i see the log files forever monitor creates but the size is always 0, if i open the file using any editor it is empty. From the first VM the see the size of the log is non-empty and the content is visible.



      Note: As long as the forever monitor is running this problem is present, if the forever monitor is closed then i am able to view logs from both VMs.



      VMs are running on x86 machines using RHEL 6.4 (santiago) Gnome 2.28.2



      The forever monitor code is as given below.



      var child = new (forever.Monitor)('myscript.js', {
      max: 100,
      silent: false,
      args: ,
      logFile: '/logs/myapp_forever.log', // Path to log output from forever process (when daemonized)
      outFile: '/logs/myapp_stdout.log', // Path to log output from child stdout
      errFile: '/logs/myapp_stderr.log', // Path to log output from child stderr
      });


      Any help here is much appreciated. Thanks !







      logging node.js






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 1 at 10:19









      ajay krishnanajay krishnan

      61




      61






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          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: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          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%2fsuperuser.com%2fquestions%2f1400940%2fforever-monitor-unable-to-view-log-file-in-a-distributed-file-system%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • 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%2fsuperuser.com%2fquestions%2f1400940%2fforever-monitor-unable-to-view-log-file-in-a-distributed-file-system%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

          flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

          Mangá

          Eduardo VII do Reino Unido