Need help debugging Community Dashboard 502 Error

Our dashboard and API went down randomly with this error: 

INFO [jobs:scanner] Checking plugins ["mobile","web","desktop","plugins","density","locale","browser","sources","views","enterpriseinfo","logger","systemlogs","errorlogs","populator","reports","crashes","push","star-rating","slipping-away-users","compare","server-stats","dbviewer","assistant","plugin-upload","times-of-day","compliance-hub","video-intelligence-monetization","alerts","onboarding"]
/usr/countly/node_modules/bindings/bindings.js:121
throw e;
^

Error: The module '/usr/countly/node_modules/time/build/Release/time.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 57. This version of Node.js requires
NODE_MODULE_VERSION 79. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
at Object.Module._extensions..node (internal/modules/cjs/loader.js:1041:18)
at Module.load (internal/modules/cjs/loader.js:822:32)
at Function.Module._load (internal/modules/cjs/loader.js:730:14)
at Module.require (internal/modules/cjs/loader.js:864:19)
at require (internal/modules/cjs/helpers.js:74:18)
at bindings (/usr/countly/node_modules/bindings/bindings.js:112:48)
at Object.<anonymous> (/usr/countly/node_modules/time/index.js:8:35)
at Module._compile (internal/modules/cjs/loader.js:971:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1011:10)
at Module.load (internal/modules/cjs/loader.js:822:32)
at Function.Module._load (internal/modules/cjs/loader.js:730:14)
at Module.require (internal/modules/cjs/loader.js:864:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object.<anonymous> (/usr/countly/api/utils/common.js:9:12)
at Module._compile (internal/modules/cjs/loader.js:971:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1011:10)
 
I attempted to reinstall using npm install, however the time module consistently fails to install. I'm on an Ubuntu 18.04 machine. I'm using node version 13.9.0 and countly version 19.08.1. I also get disk-space problems with /snap/amazon-ssm-agent and /snap/core. Any advice? 
 
Thank you!
0

Comments

6 comments
  • Hello
    time module only supports Nodejs 10 and lower
    we will be removing it as dependency in future versions

    0
    Comment actions Permalink
  • Thank you Arturs!

    Would you happen to know how to fix this issue as well? I'm running Countly on a Lightsail machine. 

     

    Encountered problems with disk space:

        Mount point : /snap/amazon-ssm-agent/495

            - Total space : 13M

            - Used space : 13M

            - Free space : 0

            - Used space in percent : 100%

        Mount point : /snap/amazon-ssm-agent/1480

            - Total space : 18M

            - Used space : 18M

            - Free space : 0

            - Used space in percent : 100%

        Mount point : /snap/core/8592

            - Total space : 92M

            - Used space : 92M

            - Free space : 0

            - Used space in percent : 100%

        Mount point : /snap/core/8689

            - Total space : 92M

            - Used space : 92M

            - Free space : 0

            - Used space in percent : 100%

    0
    Comment actions Permalink
  • Hello,
    the only way would be to downgrade nodejs version to 8 or 10 and remove node_modules folder and run npm install to resintall all dependencies

    0
    Comment actions Permalink
  • Hello Arturs,

    Thank you for the response. I've already downgraded node and reinstalled all the dependencies. The dashboard and Count.ly API is back up and running. I was wondering if my previous comment with the disk space error was related to my initial problem? 

    Also, we're having this weird discrepancy with tracking where all metrics have plummeted since Feb 8th, which is inconsistent with our Google analytics results. Could this be related to the disk space error?

     

    Thank you! 

    0
    Comment actions Permalink
  • Hello,
    I am really not sure what that information means, but if there is no disk space, then there is no place to write new data in?

    0
    Comment actions Permalink
  • Hello, 

    After looking into it more, that error is unrelated. The discrepancy has gone away as well, not really sure what happened. Thank you!

    0
    Comment actions Permalink

Please sign in to leave a comment.