Doesn't look like it shows anything new. Did you restart nodebb after adding the console.log?

@baris

I did. Not even sure why this is coming up sinxe that databse and the code was working properly on another server without this particular error.

Could I have missinstalled something?

You can always try running ./nodebb upgrade and try again, but your error is weird because it is coming from the cron dependency and it's complaining about an invalid date being passed to it.

await cron.addJob({
	name: 'notifications:prune',
	cronTime: '*/30 * * * *',
	onTick: Notifications.prune,
});

However the line it points to in our code uses a valid cron string, which works on this forum and my local environment.

What is your nodejs version?

24.14.0 running on Gentoo linux

@CWSmith that log isn't showing enough.

Instead of ./nodebb log can you open the log in something like nano so you can see more?

All I see are just blocks of this error over and over in logs/output.log

NodeBB v4.13.2 Copyright (C) 2013-2026 NodeBB Inc.      This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistrib>For the full license, please visit: http://www.gnu.org/>                                                        Clustering enabled: Spinning up 1 process(es).

2026-07-05T16:37:19.790Z [4567/85498] - ^[[32minfo^[[39>
2026-07-05T16:37:20.749Z [4567/85498] - ^[[33mwarn^[[39>
2026-07-05T16:37:20.921Z [4567/85498] - ^[[32minfo^[[39>
2026-07-05T16:37:20.980Z [4567/85498] - ^[[32minfo^[[39>
2026-07-05T16:37:20.988Z [4567/85498] - ^[[32minfo^[[39>
2026-07-05T16:37:21.013Z [4567/85498] - ^[[31merror^[[3>
    at CronTime.getNextDateFrom (/var/www/community.dar>
    at CronTime.sendAt (/var/www/community.darkscribes.>
    at CronTime.getTimeout (/var/www/community.darkscri>
    at CronJob.start (/var/www/community.darkscribes.co>
    at new CronJob (/var/www/community.darkscribes.com/>
    at exports.addJob (/var/www/community.darkscribes.c>
    at Analytics.init (/var/www/community.darkscribes.c>
    at Object.wrapperCallback [as init] (/var/www/commu>
    at initializeNodeBB (/var/www/community.darkscribes>
    at process.processTicksAndRejections (node:internal>
[cluster] Child Process (85498) has exited (code: 0, si>

NodeBB v4.13.2 Copyright (C) 2013-2026 NodeBB Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistrib>
For the full license, please visit: http://www.gnu.org/>

Clustering enabled: Spinning up 1 process(es)

I am still on Gentoo Linux so if I missed a use flag I can fix it. Just need a use flag.

@cwsmith@community.nodebb.org I would recommend you try to add in the console log that @baris@community.nodebb.org suggested so we can see the cron value being passed in.

Judging by your logs they're not showing anything output

Can you make the edit and let us know what kind of logging you added as well?

Ok, just one question.

Where do I find the console.log you are asking for?

@CWSmith you'll have to edit the actual file and add it in yourself