SQLITE_BUSY: database is locked PORT 3000 (Rammerhead port being annoying)

[QuiteAFancyEmerald]

Reported to me via discord. Putting this here so I do not forget.

"I keep getting port in use now after a couple restarts:"

0|HolyUBLTS  | Error: listen EADDRINUSE: address already in use 0.0.0.0:3000
0|HolyUBLTS  |     at Server.setupListenHandle [as _listen2] (node:net:1898:16)
0|HolyUBLTS  |     at listenInCluster (node:net:1946:12)
0|HolyUBLTS  |     at doListen (node:net:2116:7)
0|HolyUBLTS  |     at processTicksAndRejections (node:internal/process/task_queues:83:21) {
0|HolyUBLTS  |   code: 'EADDRINUSE',
0|HolyUBLTS  |   errno: -98,
0|HolyUBLTS  |   syscall: 'listen',
0|HolyUBLTS  |   address: '0.0.0.0',
0|HolyUBLTS  |   port: 3000
0|HolyUBLTS  | }
0|HolyUBLTS  | [Error: SQLITE_BUSY: database is locked] {
0|HolyUBLTS  |   errno: 5,
0|HolyUBLTS  |   code: 'SQLITE_BUSY'
0|HolyUBLTS  | }

Happens after a few restarts. Confirmed other processes are not running in the background using the same port.
Solution: pkill node / npm run kill

[QuiteAFancyEmerald]

Fix:

Holy-Unblocker/lib/rammerhead/holy-config.js

Line 9 in 8f6dcfe

port: process.env.PORT || 3000,

Edit this respective line to a different port. The error above is caused when you set Holy Unblocker to port 3000 as well. Naturally this will not work. A fix will be implemented later for this rogue port.