3. Can't get jsreport to run using jsreport start

Can't get jsreport to run using jsreport start


  • Hi,
    I'm trying to get jsreport running on a new prod server to mirror our dev server (someone else has previously setup jsreport there for us on dev). I've installed it on prod and can access the web interface to see our templates but I'm very confused about one thing I'm hoping someone can explain to me.

    On Dev I just run:
    jsreport init
    jsreport start

    And the app starts up and runs fine.

    On Prod, these commands don't work. If I try to run either I get this error:
    jsreport: command not found

    I can get the app running if I run these commands instead (after some digging online I found these):

    node node_modules/jsreport --init
    npm start

    Why do I have to run these weird commands to make something happen? Why won't "jsreport init" and "jsreport start" work? Why is it saying jsreport command not found?

    So confused =(

    0

  • Hi, you should follow commands described on our download page
    https://jsreport.net/on-prem

    npm install jsreport-cli -g
jsreport init
jsreport configure
jsreport start
    0

  • I forgot to mention, in case it makes a difference somewhere, that i'm trying to keep the version of node.js and jsreport the same on both Dev and Prod. Dev needs to be updated, but it is running stable for the time being so we will upgrade it when things die down. I'm trying to keep things the same because we need to integrate jsreport with an Angular app and I wasn't around when everything was developed on Dev and there was no documentation left as to how the developed did any of this.
    I want to keep the process, code, and commands the same between both environments to hopefully get Prod up and running in a timely manner and in the same way Dev is.

    Right now we're using
    jsreport 1.6.0

    If I try installing fresh using the commands you have above, I get told that node.js is too old and I need to upgrade, which means I would need overhaul the Angular app as well (which we know we will need to do eventually, we just need to get a few things our the door first).
    Dev is older and doesn't cli as far as I know and still uses the "init" and "start" commands, how come they work there and not on Prod?

    0
  • administrators

    hmm

    i will probably try the following:

    run this command jsreport -v in both dev and prod servers and check its output, both version outputs should match, most important the output of your prod server should match with your dev server.

    note: to ensure that you have the same version of cli that the one that gets installed with jsreport 1.6.0 you should do this npm install -g jsreport-cli@1.0.4. (probably you need this in your prod server)

    0

  • If I run that command, I get the same error as before:
    bash: jsreport: command not found

    It's installed, I can access the web interface so I know it's there, but none of the standard commands seem to work. I'm so confused.

    EDIT: I just installed the version of cli suggested in the above comment and now if I try
    jsreport init or jsreport start i just get this message:

    No such file or directory

    0
  • administrators

    hmm so far it seems that it is a problem with you console session and bash, maybe for some reason it does not recognize commands installed with global npm installation, maybe you can fix your bash session by following the steps described here.

    i think you should be able to run the commands (even if your bash session does not found it) if you do node_modules/.bin/jsreport -v or node_modules/.bin/jsreport start

    0

  • I just tried running both of those commands and both times I got "Permission denied"

    I also created a new folder on Prod to start fresh and copied the node_modules folder from Dev to it to ensure I have the exact same versions of the files on each server, and then tried running "jsreport init". Still got the "No such file or directory" error. What does this error mean?

    What exactly happens when we run the install scripts? I find the documentation for this process could be more robust.

    0
  • administrators

    What exactly happens when we run the install scripts? I find the documentation for this process could be more robust.

    the docs about jsreport init contains the following description: Initializes the current working directory to start a jsreport application (creates server.js, jsreport.config.json, package.json and install jsreport if necessary) that is all what it does, do you think that is confusing? if yes, please share how you think it could be improved.

    the errors that you are getting seems to be related with the configuration of your server, maybe you don't have enough permissions, etc or node,npm is not installed right or they required elevated permissions to be executed.

    it will be difficult to add to documentation every possible failure, the error that you are getting is not common, and it is a sign that you have wrong permissions set up in your server. maybe the directory that contains your project requires admin permissions

    I just tried running both of those commands and both times I got "Permission denied"

    this could be a good sign that your problem is the permissions configured in your server, what happens if you try sudo node_modules/.bin/jsreport -v or sudo node_modules/.bin/jsreport start? other alternatives: node node_modules/.bin/jsreport -v or sudo node node_modules/.bin/jsreport -v or node node node_modules/.bin/jsreport start or sudo node node_modules/.bin/jsreport start

    I also created a new folder on Prod to start fresh and copied the node_modules folder from Dev to it to ensure I have the exact same versions of the files on each server, and then tried running "jsreport init". Still got the "No such file or directory" error. What does this error mean?

    before running those commands check if the file [your project path]/node_modules/.bin/jsreport is present in your project after copying, seeing "No such file or directory" makes me think that file was not copied.

    0

  • I tried everything you mentioned and here are my results.
    Note: this is all in my newly created fresh folder mentioned in my last comment.

    First I checked for the [your project path]/node_modules/.bin/jsreport file. It is there. Here is it's content:

    #!/usr/bin/env node
    var path = require('path')
    var semver = require('semver')
    var Liftoff = require('liftoff')
    var commander = require('./lib/commander')
    var init = require('./lib/commands/init')
    var repair = require('./lib/commands/repair')
    var configure = require('./lib/commands/configure')
    var cliPackageJson = require('./package.json')

    var cli = new Liftoff({
    processTitle: 'jsreport',
    moduleName: 'jsreport-cli',
    configName: '.jsreport'
    })

    cli.launch({}, initCLI)

    function initCLI (env) {
    var args = process.argv.slice(2)
    var cwd = process.cwd()
    var localCommander

    if (!env.modulePath) {
    // if no local installation is found,
    // try to detect if some global command was specified
    var globalCliHandler = commander(cwd, {
    builtInCommands: [init, repair, configure],
    ignoreEntryPointCommands: ['init', 'repair', 'configure']
    })

    globalCliHandler.on('started', function (err, info) {
  if (err) {
    console.error(err)
    return process.exit(1)
  }

  if (!info.handled) {
    console.error('Local jsreport-cli not found in:', env.cwd)
    console.error('Try installing jsreport-cli or jsreport package')

    return process.exit(1)
  }

  return
})

globalCliHandler.start(args)

    } else {
    // Check for semver difference between global cli and local installation
    if (semver.gt(cliPackageJson.version, env.modulePackage.version)) {
    console.log('Warning: jsreport-cli version mismatch:')
    console.log('Global jsreport-cli is', cliPackageJson.version)
    console.log('Local jsreport-cli is', env.modulePackage.version)
    }

    localCommander = require(path.join(path.dirname(env.modulePath), 'lib/commander.js'))(cwd)

// start processing
localCommander.start(args)

    }
    }

    [side note, how do I format my code like you do in my posts?]

    0

  • Second I tried running all those commands.. nothing really worked, here are my results:
    For sudo node_modules/.bin/jsreport -v or sudo node_modules/.bin/jsreport start:
    I got this error: sudo: node_modules/.bin/jsreport: command not found

    For command node node_modules/.bin/jsreport -v:
    module.js:478
    throw err;
    ^

    Error: Cannot find module './lib/commander'
    at Function.Module._resolveFilename (module.js:476:15)
    at Function.Module._load (module.js:424:25)
    at Module.require (module.js:504:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> ([project_path]/node_modules/.bin/jsreport:5:17)
    at Module._compile (module.js:577:32)
    at Object.Module._extensions..js (module.js:586:10)
    at Module.load (module.js:494:32)
    at tryModuleLoad (module.js:453:12)
    at Function.Module._load (module.js:445:3)

    For commands
    sudo node node_modules/.bin/jsreport -v
    sudo node node_modules/.bin/jsreport start
    same error as node node_modules/.bin/jsreport -v

    0
  • administrators

    [side note, how do I format my code like you do in my posts?]

    try writing the text in the same way that you see in this screenshoot:

    0_1531244941085_Captura de pantalla 2018-07-10 a las 12.48.05 p.m..png

    0

  • Hurrah! Thanks!
    /node_modules/.bin/jsreport file properly formatted for easier reading:

    #!/usr/bin/env node
var path = require('path')
var semver = require('semver')
var Liftoff = require('liftoff')
var commander = require('./lib/commander')
var init = require('./lib/commands/init')
var repair = require('./lib/commands/repair')
var configure = require('./lib/commands/configure')
var cliPackageJson = require('./package.json')

var cli = new Liftoff({
  processTitle: 'jsreport',
  moduleName: 'jsreport-cli',
  configName: '.jsreport'
})

cli.launch({}, initCLI)

function initCLI (env) {
  var args = process.argv.slice(2)
  var cwd = process.cwd()
  var localCommander

  if (!env.modulePath) {
    // if no local installation is found,
    // try to detect if some global command was specified
    var globalCliHandler = commander(cwd, {
      builtInCommands: [init, repair, configure],
      ignoreEntryPointCommands: ['init', 'repair', 'configure']
    })

    globalCliHandler.on('started', function (err, info) {
      if (err) {
        console.error(err)
        return process.exit(1)
      }

      if (!info.handled) {
        console.error('Local jsreport-cli not found in:', env.cwd)
        console.error('Try installing jsreport-cli or jsreport package')

        return process.exit(1)
      }

      return
    })

    globalCliHandler.start(args)
  } else {
    // Check for semver difference between global cli and local installation
    if (semver.gt(cliPackageJson.version, env.modulePackage.version)) {
      console.log('Warning: jsreport-cli version mismatch:')
      console.log('Global jsreport-cli is', cliPackageJson.version)
      console.log('Local jsreport-cli is', env.modulePackage.version)
    }

    localCommander = require(path.join(path.dirname(env.modulePath), 'lib/commander.js'))(cwd)

    // start processing
    localCommander.start(args)
  }
}
    0
  • administrators

    ok, at this point i'm not sure how you end with all of these errors, so i think the best here will be that somehow i connect to your server and check the error by myself.

    if you are able to share with me a temporal user of your server, i will try to start a ssh session and connect to your server, and try the commands directly and see what i can do about it. you can send me those details at bjrmatos@gmail.com

    0

  • Unfortunately our security won't allow me to let anyone connect to our severs.
    I guess I'll have to stick with using this, even tho I'm not sure why nothing else works.

    node node_modules/jsreport --init
npm start

    I still have to connect this with our Angular app, so let's hope that doesn't cause more weird problems.

    Could you explain a few of the installed installed files to me?
    The docs say that jsreport.config.json is created and loaded, but that dev.config.json or prod.config.json are loaded too depending on the NODE_ENV variable.
    So does that mean BOTH jsreport.config.json AND either dev.config.json or prod.config.json are loaded together, or just one of the 3 depending on what settings are defined? Also where is NODE_ENV defined? What file?

    If I look in package.json, I see a scripts section:

    "scripts": {
    "start": "node server",
    "jsreport": "jsreport"
  },

    Doesn't this mean I should be able to run these as commands like start jsreport and that would actually run node server jsreport? Because if I run node server jsreport it runs but WITHOUT my reconfigured port number (4201 over the current default), but if I run start jsreport, it says no command found?

    0
  • administrators

    If I look in package.json, I see a scripts section:

    "scripts": {
    "start": "node server",
    "jsreport": "jsreport"
  },

    Doesn't this mean I should be able to run these as commands like start jsreport and that would actually run node server jsreport? Because if I run node server jsreport it runs but WITHOUT my reconfigured port number (4201 over the current default), but if I run start jsreport, it says no command found?

    yes, you should be able to start jsreport with just node server.js instead of jsreport start. there is no difference. the reason that you don't have the correct right port probably is because you don't have a dev.config.json file in your project, maybe it is called jsreport.config.json in your case (explanation bellow for why jsreport.config.json is not loaded for your project), you need to rename jsreport.config.json to dev.config.json

    Could you explain a few of the installed installed files to me?

    yes, of course. first of all the docs that you see right now are mostly relevant for jsreport v2, they are updated to reflect latest version of jsreport (v2), we want in future to have a way to inspect docs for older versions (like your case, since you are using jsreport v1), but right now is not possible because it requires some internal work that we are not able to find the right time to do it.

    The docs say that jsreport.config.json is created and loaded, but that dev.config.json or prod.config.json are loaded too depending on the NODE_ENV variable.
    So does that mean BOTH jsreport.config.json AND either dev.config.json or prod.config.json are loaded together, or just one of the 3 depending on what settings are defined?

    just one file is loaded, you can see what file is loaded in first line of the logs of your console, it will be something like this (in case of there is no config file it will print dev.config.json):

    info: Initializing jsreport@1.6.0 in development mode using configuration file dev.config.json

    in your case since you are using old version (jsreport 1.6.0 ), the jsreport.config.json is not supported there (it will never be loaded for your project), so only one of the files (dev.config.json or prod.config.json) will be loaded, by default what is loaded in your case is dev.config.json if present, the prod.config.json is just loaded when the environtment variable NODE_ENV is set to the value production

    Also where is NODE_ENV defined? What file?

    the NODE_ENV is an environtment variable, in linux you can set environtment variables by using the following syntax in your command when starting jsreport: NODE_ENV=production node server.js, for other different OS you can find a lot of answers by searching "how to set environtment variables in ..." (remember that if you don't define the NODE_ENV env var then what is loaded by default is dev.config.json)

    0
  • administrators

    yes, you should be able to start jsreport with just node server.js instead of jsreport start. there is no difference. the reason that you don't have the correct right port probably is because you don't have a dev.config.json file in your project, maybe it is called jsreport.config.json in your case (explanation bellow for why jsreport.config.json is not loaded for your project), you need to rename jsreport.config.json to dev.config.json

    to add more about this, make sure you are not using new config format (what you see in current docs is the format of configuration for v2), since you are using jsreport 1.6.0 then the configuration is a little bit different, keys has other names or different shape, etc. an example of an old configuration for jsreport 1.6.0 is like this:

    {
  "httpPort": 5488,
  "authentication": {
    "cookieSession": {
      "secret": "<your strong secret here>"
    },
    "admin": {
      "username": "admin",
      "password": "password"
    },
    "enabled": false
  },
  "connectionString": {
    "name": "fs"
  },
  "logger": {
    "providerName": "winston"
  },
  "blobStorage": "fileSystem",
  "tasks": {
    "allowedModules": "*",
    "strategy": "http-server",
    "timeout": 10000
  },
  "scripts": {
    "allowedModules": "*",
    "timeout": 40000
  },
  "assets": {
    "allowedFiles": "*.*",
    "searchOnDiskIfNotFoundInStore": true
  },
  "phantom": {
    "allowLocalFilesAccess": true,
    "strategy": "phantom-server",
    "timeout": 40000
  },
  "electron": {
    "allowLocalFilesAccess": true,
    "strategy": "electron-ipc",
    "timeout": 40000
  },
  "sample-template": {
    "createSamples": true
  }
}
    0

  • Thanks for the clarification, that clears a couple things up a bit.
    I'm following the files on Dev as close as possible trying to keep Prod as close to Dev (which works fine) as possible, so I'm following its config format and only deviating when something doesn't work as expected.

    I'm glad that running node server.js works for me, but do you have any ideas as to why trying to run the scripts in the package.json file don't work? Is this the same probable that we've been trying to debug or a different issue? I guess this means I can't write any of my own scripts there either then if it can't seem to find them.

    0
  • administrators

    but do you have any ideas as to why trying to run the scripts in the package.json file don't work?

    reading your old comment, your first script "start": "node server",, should be running with npm start, it will do the same that running node server.js if running npm start does not work then probably it is the same error that we were trying to debug.

    your second script "jsreport": "jsreport" should be running with npm run jsreport, but that probably will give you an error that is related to the same error that we were trying to debug.

    0

  • So running either node server.js or npm start both work and do the same thing... without my customized port. I do have a prod.config.json defined, so if I run npm start --production then it runs with the correct port.

    Running npm run jsreport gives me an error:

    > jsreport-server@ jsreport [project-path]
> jsreport

: No such file or directory

npm ERR! Linux 3.10.0-862.3.2.el7.x86_64
npm ERR! argv "/usr/bin/node" "/bin/npm" "run" "jsreport"
npm ERR! node v6.14.2
npm ERR! npm  v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! jsreport-server@ jsreport: `jsreport`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the jsreport-server@ jsreport script 'jsreport'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the jsreport-server package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     jsreport
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs jsreport-server
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls jsreport-server
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     [project-path]/npm-debug.log

    I'm assuming given what we've assessed so far this is not surprising?

    0
  • administrators

    So running either node server.js or npm start both work and do the same thing... without my customized port. I do have a prod.config.json defined, so if I run npm start --production then it runs with the correct port.

    ok, you can also do node server.js --httpPort 4201 in case you want to use another port but dont want to edit your config file when trying multiple different ports.

    I'm assuming given what we've assessed so far this is not surprising?

    yes, exactly. it is still a mystery for me too

    0
install 1 installation 2 start up 1 commands 1
Log in to reply
 

Looks like your connection to jsreport forum was lost, please wait while we try to reconnect.