by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Daniel Alexandre Cerqueira Santos
    @alexandre1985
    i need to run forever from .bash_profile. what is the proper way of doing this because i only get the output text from forever but when i do forever list it shows no process
    Daniel Alexandre Cerqueira Santos
    @alexandre1985
    i'm running forever from a android box
    sustained
    @sustained
    lol, spam on gitter?
    the one place where no one is dumb enough to click your link?
    sure! okay!
    jsmirrors-limited
    @tectronics
    rtd gen dr mason de victor
    Sam Roquitte
    @samr28
    So I'm trying to get this to work and run a hubot forever. Using this: forever start "bin/hubot" HUBOT_SLACK_TOKEN=myslacktokenhere--adapter slack -n agenda It runs fine but when I check forever list it says stopped in the uptime spot.
    tengers17
    @tengers17
    hi guys, i am new with forever, i have a node js application that i need to deploy in windows server 2012. i did an npm install -g (global) on forever and when i start the server.js file it complains that "forever is not a recognized as an internal or external command" .... i encountered a similar issue when i installed in my local machine with Windows 7 but i fixed it by installing 0.10.5. I used the same version in Windows Server 2012 but it did not work either
    Jibin Mathews
    @jazzyarchitects
    Did anyone figure out how to get the current terminal cols and rows count inside the forever process?
    Farhan Khwaja
    @Farhan_Khwaja_twitter
    hi everyone, I am trying to install forever on EC2, but i am getting errors. My Node and NPM version are v6.10.1 & 5.4.2 respectively
    John Rodney
    @JohnRodney
    Hey I can't find an article on the correct way to do this. I made a dev-server that runs from the script "dev-server": "forever -w ./dist/src/index.js node ./dist/src/index.js",. A babel script watches files then compiles and forever picks up the change and restarts. What I was hoping is some info on how to properly restart the node proccess so that you don't get the error: restarting script because change changed error: Forever detected script was killed by signal: SIGKILL error: Script restart attempt #7. I would like to keep the terminal with the server clean for only errors that occur within the script and not forever's logging.
    it is not possible to catch a SIGKILL as it is meant to kill so is there another leading indicator event that I can catch and process.exitbefore forever kills it with a SIGKILL?
    sakopqiu
    @sakopqiu

    Hi, I have a very simple question, I dont see anything from stdout when executing the following command

    forever start backend/app.js

    I tried to append "-f" but it also does not work

    it seems that forever swallows and suppresses everything from STDOUT
    oh, I found out the reason ,forever start makes the process a daemon one
    kchrs
    @kchrs
    Hello guys, Please can someone help how can I run this "node --harmony index.js -p 8080-d C:\somedir" with forever? If I type "forever start --harmony index.js -p 8080 -d C:\somedir" I get an error.
    jakkabbi
    @jakkabbi
    Hi
    jakkabbi
    @jakkabbi
    Stupid question, I'm running an angular app using node run dev (or prod) depending on which I am using. how do I run my app using forever?
    Or should I only need to run the node server using forever?
    mattyicce
    @mattyicce
    Anyone ever hear of error: Forever detected script exited with code: 3221225477
    xsh
    @cankeall
    hi
    Eugene Serkin
    @jeserkin
    Hello. Have a question about one specific error. I have a forever running inside docker container and whenever I start it, then at first it gives me
    info:    Forever processing file: server.js
    error:   Cannot find forever process: 0
    Dri Torres
    @thedrean
    Hello, am I using -c wrong?
    #! /bin/bash
    
    # Copy configuration in place
    cp /src/api/config/config_${NODE_ENV}.js /src/api/config.js
    node /src/api/scripts/create_db_json.js > /src/database.json
    
    forever start -f --spinSleepTime 10 -c "node --max_old_space_size=${NODE_OLD_SPACE} --max_semi_space_size=${NODE_SEMI_SPACE}" /src/api/server.js -p 3000 &
    forever start -f --spinSleepTime 10 -c "node --max_old_space_size=${NODE_OLD_SPACE} --max_semi_space_size=${NODE_SEMI_SPACE}" /src/api/server.js -p 3001 &
    nginx -g 'daemon off;'
    Justin
    @Justindmo
    No one seems to answer questions here.
    Don't waste your time here, just visit Stack Overflow and go from there.
    YSC
    @TechnoSayge
    @Justindmo seems to be the case on gitter.
    matthew
    @clifton_gitlab
    hi i need help!!
    ??
    matthew
    @clifton_gitlab
    hello
    hellp
    hello
    hello
    enyone here
    anyone here
    Peter Delvaux
    @pjetr
    Hi guys, quick question, is there a way to run forever stop dist/server.js without errors, when it is not running?
    it's for an automated script, where I want to stop the server, overwrite the loaded server.js and start again
    But I don't want to create a script that kills all processes, nor do I want to parse the output of forever list to see if my app is already running...
    Igor Savin
    @kibertoad
    @pjetr What happens now when you try to stop something that is not running?
    Nikos
    @QuantumInformation

    Hi, I tried changing this:

    "debug": "node --inspect node_modules/@google-cloud/functions-framework --target=api",
    to this
    "debug": "forever --inspect node_modules/@google-cloud/functions-framework --target=api",

    but it doesn't work, what am I missing?

    I get
    
    help:    usage: forever [action] [options] SCRIPT [script-options]
    help:
    help:    Monitors the script specified in the current process or as a daemon
    Paul Wareham
    @paulwareham
    i was wondering if there is any way to setup forever to send an alert via email when a chosen process has STOPPED - for example due to an error preventing the code from running? I recently had this problem of a missing module which caused the process to stop and not be able to restart due to a module dependency that had somehow changed.
    Ashwanth Madhav
    @kmaswanth_gitlab
    error: Forever detected script was killed by signal: SIGKILL. Why this error occured in Linux system ?
    Cubox-
    @Lightningcash-dev

    root@iZao2fhw9hznl5Z:~# sudo npm install forever -g
    npm WARN deprecated path-is-absolute@2.0.0: This package is no longer relevant as Node.js 0.12 is unmaintained.
    npm ERR! Linux 4.15.0-72-generic
    npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "forever" "-g"
    npm ERR! node v8.10.0
    npm ERR! npm v3.5.2
    npm ERR! code EMISSINGARG

    npm ERR! typeerror Error: Missing required argument #1
    npm ERR! typeerror at andLogAndFinish (/usr/share/npm/lib/fetch-package-metadata.js:31:3)
    npm ERR! typeerror at fetchPackageMetadata (/usr/share/npm/lib/fetch-package-metadata.js:51:22)
    npm ERR! typeerror at resolveWithNewModule (/usr/share/npm/lib/install/deps.js:456:12)
    npm ERR! typeerror at /usr/share/npm/lib/install/deps.js:457:7
    npm ERR! typeerror at /usr/share/npm/node_modules/iferr/index.js:13:50
    npm ERR! typeerror at /usr/share/npm/lib/fetch-package-metadata.js:37:12
    npm ERR! typeerror at addRequestedAndFinish (/usr/share/npm/lib/fetch-package-metadata.js:82:5)
    npm ERR! typeerror at returnAndAddMetadata (/usr/share/npm/lib/fetch-package-metadata.js:117:7)
    npm ERR! typeerror at pickVersionFromRegistryDocument (/usr/share/npm/lib/fetch-package-metadata.js:134:20)
    npm ERR! typeerror at /usr/share/npm/node_modules/iferr/index.js:13:50
    npm ERR! typeerror This is an error with npm itself. Please report this error at:
    npm ERR! typeerror http://github.com/npm/npm/issues

    npm ERR! Please include the following file with any support request:
    npm ERR! /root/npm-debug.log

    Andy Jang
    @RiinRiin
    After installing globally I am getting "zsh: command not found: forever". Any idea how to fix it? I tried exporting path to it on .zshrc file but still not working.
    Alex Rojo
    @arojoal

    root@iZao2fhw9hznl5Z:~# sudo npm install forever -g
    npm WARN deprecated path-is-absolute@2.0.0: This package is no longer relevant as Node.js 0.12 is unmaintained.
    npm ERR! Linux 4.15.0-72-generic
    npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "forever" "-g"
    npm ERR! node v8.10.0
    npm ERR! npm v3.5.2
    npm ERR! code EMISSINGARG

    npm ERR! typeerror Error: Missing required argument #1
    npm ERR! typeerror at andLogAndFinish (/usr/share/npm/lib/fetch-package-metadata.js:31:3)
    npm ERR! typeerror at fetchPackageMetadata (/usr/share/npm/lib/fetch-package-metadata.js:51:22)
    npm ERR! typeerror at resolveWithNewModule (/usr/share/npm/lib/install/deps.js:456:12)
    npm ERR! typeerror at /usr/share/npm/lib/install/deps.js:457:7
    npm ERR! typeerror at /usr/share/npm/node_modules/iferr/index.js:13:50
    npm ERR! typeerror at /usr/share/npm/lib/fetch-package-metadata.js:37:12
    npm ERR! typeerror at addRequestedAndFinish (/usr/share/npm/lib/fetch-package-metadata.js:82:5)
    npm ERR! typeerror at returnAndAddMetadata (/usr/share/npm/lib/fetch-package-metadata.js:117:7)
    npm ERR! typeerror at pickVersionFromRegistryDocument (/usr/share/npm/lib/fetch-package-metadata.js:134:20)
    npm ERR! typeerror at /usr/share/npm/node_modules/iferr/index.js:13:50
    npm ERR! typeerror This is an error with npm itself. Please report this error at:
    npm ERR! typeerror http://github.com/npm/npm/issues

    npm ERR! Please include the following file with any support request:
    npm ERR! /root/npm-debug.log

    I've got the same error. Anyone can help on how to solve it?

    Edward Pasenidis
    @pasenidis
    hello guys, is forever deprecated?
    I cannot get it installed on my Ubuntu machine...
    Igor Savin
    @kibertoad
    Not quire deprecated, just not super actively supported.
    What is the error that you are getting?
    @pasenidis