StefVDM

Untitled

Oct 22nd, 2019
194
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.17 KB | None | 0 0
  1.  
  2. Save New Duplicate & Edit Just Text Twitter
  3. 1
  4. 2
  5. 3
  6. 4
  7. 5
  8. 6
  9. 7
  10. 8
  11. 9
  12. 10
  13. 11
  14. 12
  15. 13
  16. 14
  17. 15
  18. 16
  19. 17
  20. 18
  21. 19
  22. 20
  23. 21
  24. 22
  25. 23
  26. 24
  27. 25
  28. 26
  29. 27
  30. 28
  31. 29
  32. 30
  33. 31
  34. 32
  35. 33
  36. 34
  37. 35
  38. 36
  39. 37
  40. 38
  41. 39
  42. 40
  43. 41
  44. 42
  45. 43
  46. 44
  47. 45
  48. 46
  49. 47
  50. 48
  51. 49
  52. 50
  53. 51
  54. 52
  55. 53
  56. 54
  57. 55
  58. 56
  59. 57
  60. 58
  61.  
  62. Wqrld08-04-2019
  63. You could check your deamon logs
  64. npm run diagnostics
  65.  
  66. Stef08-04-2019
  67. 0 info it worked if it ends with ok
  68. 1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'diagnostics' ]
  69. 2 info using [email protected]
  70. 3 info using [email protected]
  71. 4 verbose config Skipping project config: /root/.npmrc. (matches userconfig)
  72. 5 verbose stack Error: ENOENT: no such file or directory, open '/root/package.json'
  73. 6 verbose cwd /root
  74. 7 verbose Linux 4.4.0-141-generic
  75. 8 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "diagnostics"
  76. 9 verbose node v10.15.0
  77. 10 verbose npm v6.4.1
  78. 11 error path /root/package.json
  79. 12 error code ENOENT
  80. 13 error errno -2
  81. 14 error syscall open
  82. 15 error enoent ENOENT: no such file or directory, open '/root/package.json'
  83. 16 error enoent This is related to npm not being able to find a file.
  84. 17 verbose exit [ -2, true ]
  85.  
  86. This came out as result
  87. Found it in /root/.npm/_logs/2019-04-08T18_59_04_285Z-debug.log
  88.  
  89. Wqrld08-04-2019
  90. cd /srv/daemon first
  91.  
  92. Stef08-04-2019
  93. node scripts/diagnostics.js
  94.  
  95. ? Do you want to include Endpoints (i.e. the FQDN/IP of your Panel) (Y
  96. /n)
  97. npm ERR! cb() never called!
  98.  
  99. npm ERR! This is an error with npm itself. Please report this error at:
  100. npm ERR! https://npm.community/
  101.  
  102. npm ERR! A complete log of this run can be found in:
  103. npm ERR! /root/.npm/_logs/2019-04-08T19_03_32_873Z-debug.log
  104. root@ns3084514:/srv/daemon#
  105. moet ik die file erbij halen?
  106.  
  107. Wqrld08-04-2019
  108. I will login real quick
  109. 02:28:42.384Z WARN wings: Server has triggered automatic kill due to excessive data output. Potential DoS attack. (server=3fab34a5-ce60-4e0f-8c11-f3bafe300123)
  110. Do you get a lot of errors?
  111.  
  112. Stef08-04-2019
  113. No not a lot sometimes just a few plugin ones.
  114.  
  115. Wqrld08-04-2019
  116. I destroyed that system which was causing it.
  117. It will not survive a panel update but it will solve the issue
  118. Just don't forget to remind me when updating the panel next time.
Advertisement
Add Comment
Please, Sign In to add comment