dzt/shopify-monitor

Errors when running on windows server from mac

Closed this issue · 5 comments

It run's the initial check for each website then it throws this:
I'm running 44 websites and changed the 300000 to 600000 in the config.json

Are you missing a .transacting(trx) call?
at Timeout._onTimeout (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\knex\lib\client.js:287:18)
at ontimeout (timers.js:475:11)
at tryOnTimeout (timers.js:310:5)
at Timer.listOnTimeout (timers.js:270:5) sql: undefined, bindings: undefined }
[Sun Nov 12 2017 15:05:49] [LOG] err { TimeoutError: Knex: Timeout acquiring a connection. The pool is probably full.
Are you missing a .transacting(trx) call?
at Timeout._onTimeout (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\knex\lib\client.js:287:18)
at ontimeout (timers.js:475:11)
at tryOnTimeout (timers.js:310:5)
at Timer.listOnTimeout (timers.js:270:5) sql: undefined, bindings: undefined }
[Sun Nov 12 2017 15:05:49] [LOG] err { TimeoutError: Knex: Timeout acquiring a connection. The pool is probably full.
Are you missing a .transacting(trx) call?
at Timeout._onTimeout (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\knex\lib\client.js:287:18)
at ontimeout (timers.js:475:11)
at tryOnTimeout (timers.js:310:5)
at Timer.listOnTimeout (timers.js:270:5) sql: undefined, bindings: undefined }
[Sun Nov 12 2017 15:05:50] [LOG] err { TimeoutError: Knex: Timeout acquiring a connection. The pool is probably full.
Are you missing a .transacting(trx) call?
at Timeout._onTimeout (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\knex\lib\client.js:287:18)
at ontimeout (timers.js:475:11)
at tryOnTimeout (timers.js:310:5)
at Timer.listOnTimeout (timers.js:270:5) sql: undefined, bindings: undefined }
C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\bluebird\js\release\using.js:12
setTimeout(function(){throw e;}, 0);
^

RangeError: Maximum call stack size exceeded
at Object.log (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\knex\lib\client.js:232:24)
at Pool.log [as _log] (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\generic-pool\lib\generic-p
ool.js:168:19)
at Pool.dispense [as _dispense] (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\generic-pool\lib
\generic-pool.js:300:10)
at Pool._addResourceToAvailableObjects (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\generic-p
ool\lib\generic-pool.js:396:8)
at Pool.release (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\generic-pool\lib\generic-pool.js
:470:8)
at C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\knex\lib\client.js:295:23
at Pool.dispense [as _dispense] (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\generic-pool\lib
\generic-pool.js:310:12)
at Pool._addResourceToAvailableObjects (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\generic-p
ool\lib\generic-pool.js:396:8)
at Pool.release (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\generic-pool\lib\generic-pool.js
:470:8)
at C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\knex\lib\client.js:295:23
at Pool.dispense [as _dispense] (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\generic-pool\lib
\generic-pool.js:310:12)
at Pool._addResourceToAvailableObjects (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\generic-p
ool\lib\generic-pool.js:396:8)
at Pool.release (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\generic-pool\lib\generic-pool.js
:470:8)
at C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\knex\lib\client.js:295:23
at Pool.dispense [as _dispense] (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\generic-pool\lib
\generic-pool.js:310:12)
at Pool._addResourceToAvailableObjects (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\generic-p
ool\lib\generic-pool.js:396:8)
at Pool.release (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\generic-pool\lib\generic-pool.js
:470:8)
at C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\knex\lib\client.js:295:23
at Pool.dispense [as _dispense] (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\generic-pool\lib
\generic-pool.js:310:12)
at Pool._addResourceToAvailableObjects (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\generic-p
ool\lib\generic-pool.js:396:8)
at Pool.release (C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\generic-pool\lib\generic-pool.js
:470:8)
at C:\Users\Administrator\desktop\shopify-monitor-master\node_modules\knex\lib\client.js:295:23
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! shopify-monitor-2@2.0.0 start: babel-node index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the shopify-monitor-2@2.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Administrator\AppData\Roaming\npm-cache_logs\2017-11-12T15_05_51_991Z-debug.log
PS C:\Users\Administrator\desktop\shopify-monitor-master> RangeError: Maximum call stack size exceeded

dzt commented

Do you have the acquireConnectionTimeout field in the database object in the config.json file set to 600000 or higher?

Yes I also changed that to 600000

@XioYang23 here is what you are looking for. It blatantly specifies proxy in the request configuration. I just checked all the codebase and the only place requesting without a proxy is when (A) you are sending discord/slack notification or (B) in the lib/index file, which is not used. Please do not create issues / reply to issues unless it is a real bug. Thank you.

@XioYang23 All issues have been fixed for any proxy problems anyone would be having. If you really need help please DM me on twitter.

Ur welcome