You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what the bug is.
To Reproduce:
Steps to reproduce the behavior:
Install Strapi
Select the Mongo edition
Wait till install finishes.
Open pod logs, and observe service fails to start.
Observed Results:
Pod fails to start, enters reboot cycle.
Expected Behavior:
Should startup without errors.
Screenshots:
Failure Logs
Starting your app...
[2021-02-02T03:59:44.119Z] debug STRAPI_LOG_LEVEL environment variable is overridden by logger middleware. It only applies outside Strapi's middleware context.
[2021-02-02T03:59:44.253Z] error Bootstrap function in plugin "content-manager" failed
[2021-02-02T03:59:44.254Z] error Error: entry.notFound
at update (/srv/app/node_modules/strapi-connector-mongoose/lib/queries.js:483:19)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at runNextTicks (internal/process/task_queues.js:66:3)
at processImmediate (internal/timers.js:434:9)
at async Object.update (/srv/app/node_modules/strapi-connector-mongoose/lib/queries.js:64:14)
at async Object.update (/srv/app/node_modules/strapi-database/lib/queries/helpers.js:15:18)
at async Object.set (/srv/app/node_modules/strapi/lib/services/core-store.js:96:9)
at async Promise.all (index 1)
at async Object.syncConfigurations (/srv/app/node_modules/strapi-plugin-content-manager/services/configuration.js:67:5)
at async module.exports (/srv/app/node_modules/strapi-plugin-content-manager/config/functions/bootstrap.js:7:3)
at async Promise.all (index 1)
at async Strapi.runBootstrapFunctions (/srv/app/node_modules/strapi/lib/Strapi.js:432:5)
at async Strapi.load (/srv/app/node_modules/strapi/lib/Strapi.js:364:5)
at async Strapi.start (/srv/app/node_modules/strapi/lib/Strapi.js:191:9)
The text was updated successfully, but these errors were encountered:
Summary:
A clear and concise description of what the bug is.
To Reproduce:
Steps to reproduce the behavior:
Observed Results:
Pod fails to start, enters reboot cycle.
Expected Behavior:
Should startup without errors.
Screenshots:
Failure Logs
The text was updated successfully, but these errors were encountered: