504 gateway timeout error while accessing tags, categories in discussion forum #563
-
Hi team, SB:Category read <--- Last few GCs ---> [97:0x5da1590] 334500 ms: Mark-sweep 506.4 (521.3) -> 502.5 (521.5) MB, 772.2 / 0.0 ms (average mu = 0.279, current mu = 0.238) allocation failure; scavenge might not succeed <--- JS stacktrace ---> FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
2023-07-03T07:13:15.944Z [4567/108] - warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run
2023-07-03T07:13:15.945Z [4567/108] - warn: [plugins/load] DEPRECATION The hook filter:router.page has been deprecated as of v1.15.3, and slated for removal in v2.1.0. Please use response:router.page instead. The following plugins are still listening for this hook:
Can You pls help to resolve this error? @keshavprasadms , @santhosh-tg |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
@rajeevsathish @vinukumar-vs Can you please get back on this issue |
Beta Was this translation helpful? Give feedback.
-
Discussion forum error is resolved now.
The ideal approach to enable discussions is, first create category in nodebb UI and update form API with PID fetched from category created |
Beta Was this translation helpful? Give feedback.
Discussion forum error is resolved now.
Below are the steps involved in Discussion forum setup on release-4.10.0
Provision nodebb by running build and deploy nodebb jobs from Jenkins and login to https://{{host}}/discussions/login with username and password available in secrets.yaml file
Follow the steps https://github.com/project-sunbird/sunbird-devops/blob/bee2ee6f39baa087eba22646d7919493552b10e1/private_repo/ansible/inventory/dev/Core/secrets.yml#L113 to generate master token and update the value in secrets.yaml file
Redeploy discussionsmw
Login to portal and create groups
While creating groups, we found two errors acceptformAPI and googlerecaptcha from network console, which…