github-starred/acebase-server
2
0
Fork 0
mirror of https://github.com/appy-one/acebase-server.git synced 2026-05-24 22:01:28 -06:00
Code Issues 7 Projects Packages Wiki Activity Actions

[GH-ISSUE #27] Running Into Issue Creating Server. Am I Missing Something? #13

New issue
Closed
opened 2026-05-23 08:38:25 -06:00 by gitea-mirror · 6 comments
gitea-mirror commented 2026-05-23 08:38:25 -06:00
Owner
Copy link

Originally created by @flancast90 on GitHub (Jul 21, 2022).
Original GitHub issue: https://github.com/appy-one/acebase-server/issues/27

Hi,
I've begun migrating my project to AceBase, and while the regular AceBase library works fine, as soon as I attempt to integrate with AceBase-Server, I get an error (see bottom of issue). Mainly, I'm confused as to how the code should look (e.g. do I need both an AceBase and AceBase-server instance)?

The issue is probably just an issue with how I've imported everything, so I'd appreciate some guidance on how to fix :)

My Code:

import { AceBase } from 'acebase'
const db = new AceBase('db');

import { AceBaseServer } from 'acebase-server';
const server = new AceBaseServer('db', { host: 'localhost', port: 5757 });

Error Message:

[db] DEBUG THIS: getNodeInfo error Error: Not enough bytes read from file at index 131072, expected 128 but got 0
    at NodeReader.readHeader (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:3051:49)
    at async start (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2649:17)
    at async NodeReader.getChildInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2956:9)
    at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1725:33)
    at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34)
    at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34)
    at async AceBaseStorage.getNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1587:30)
    at async AceBaseStorage.transactNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage.js:1274:26)
    at async LocalApi.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\api-local.js:133:24)
    at async DataReference.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase-core\dist\cjs\data-reference.js:293:28)
[db] DEBUG THIS: getNodeInfo error Error: Not enough bytes read from file at index 131072, expected 128 but got 0
    at NodeReader.readHeader (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:3051:49)
    at async start (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2649:17)
    at async NodeReader.getChildInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2956:9)
    at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1725:33)
    at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34)
    at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34)
    at async AceBaseStorage.getNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1587:30)
    at async AceBaseStorage.transactNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage.js:1274:26)
    at async LocalApi.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\api-local.js:133:24)
    at async DataReference.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase-core\dist\cjs\data-reference.js:293:28)
[db] DEBUG THIS: getNodeInfo error Error: Not enough bytes read from file at index 131072, expected 128 but got 0      
    at NodeReader.readHeader (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:3051:49)
    at async start (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2649:17)
    at async NodeReader.getChildInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2956:9)
    at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1725:33)
    at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34)
    at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34)
    at async AceBaseStorage.getNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1587:30)
    at async AceBaseStorage.transactNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage.js:1274:26)
    at async LocalApi.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\api-local.js:133:24)
    at async DataReference.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase-core\dist\cjs\data-reference.js:293:28)
[db] DEBUG THIS: getNode error: Error: Not enough bytes read from file at index 131072, expected 128 but got 0
    at NodeReader.readHeader (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:3051:49)
    at async start (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2649:17)
    at async NodeReader.getChildInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2956:9)
    at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1725:33)
    at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34)
    at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34)
    at async AceBaseStorage.getNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1587:30)
    at async AceBaseStorage.transactNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage.js:1274:26)
    at async LocalApi.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\api-local.js:133:24)
    at async DataReference.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase-core\dist\cjs\data-reference.js:293:28)
node:internal/process/promises:279
            triggerUncaughtException(err, true /* fromPromise */);
            ^

Error: Not enough bytes read from file at index 131072, expected 128 but got 0
    at NodeReader.readHeader (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:3051:49)
    at async start (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2649:17)
    at async NodeReader.getChildInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2956:9)
    at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1725:33)
    at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34)
    at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34)
    at async AceBaseStorage.getNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1587:30)
    at async AceBaseStorage.transactNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage.js:1274:26)
    at async LocalApi.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\api-local.js:133:24)
    at async DataReference.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase-core\dist\cjs\data-reference.js:293:28)
Originally created by @flancast90 on GitHub (Jul 21, 2022). Original GitHub issue: https://github.com/appy-one/acebase-server/issues/27 Hi, I've begun migrating my project to AceBase, and while the regular AceBase library works fine, as soon as I attempt to integrate with AceBase-Server, I get an error (see bottom of issue). Mainly, I'm confused as to how the code should look (e.g. do I need both an AceBase and AceBase-server instance)? The issue is probably just an issue with how I've imported everything, so I'd appreciate some guidance on how to fix :) My Code: ```js import { AceBase } from 'acebase' const db = new AceBase('db'); import { AceBaseServer } from 'acebase-server'; const server = new AceBaseServer('db', { host: 'localhost', port: 5757 }); ``` Error Message: ``` [db] DEBUG THIS: getNodeInfo error Error: Not enough bytes read from file at index 131072, expected 128 but got 0 at NodeReader.readHeader (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:3051:49) at async start (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2649:17) at async NodeReader.getChildInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2956:9) at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1725:33) at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34) at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34) at async AceBaseStorage.getNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1587:30) at async AceBaseStorage.transactNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage.js:1274:26) at async LocalApi.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\api-local.js:133:24) at async DataReference.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase-core\dist\cjs\data-reference.js:293:28) [db] DEBUG THIS: getNodeInfo error Error: Not enough bytes read from file at index 131072, expected 128 but got 0 at NodeReader.readHeader (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:3051:49) at async start (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2649:17) at async NodeReader.getChildInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2956:9) at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1725:33) at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34) at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34) at async AceBaseStorage.getNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1587:30) at async AceBaseStorage.transactNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage.js:1274:26) at async LocalApi.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\api-local.js:133:24) at async DataReference.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase-core\dist\cjs\data-reference.js:293:28) [db] DEBUG THIS: getNodeInfo error Error: Not enough bytes read from file at index 131072, expected 128 but got 0 at NodeReader.readHeader (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:3051:49) at async start (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2649:17) at async NodeReader.getChildInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2956:9) at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1725:33) at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34) at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34) at async AceBaseStorage.getNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1587:30) at async AceBaseStorage.transactNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage.js:1274:26) at async LocalApi.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\api-local.js:133:24) at async DataReference.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase-core\dist\cjs\data-reference.js:293:28) [db] DEBUG THIS: getNode error: Error: Not enough bytes read from file at index 131072, expected 128 but got 0 at NodeReader.readHeader (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:3051:49) at async start (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2649:17) at async NodeReader.getChildInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2956:9) at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1725:33) at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34) at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34) at async AceBaseStorage.getNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1587:30) at async AceBaseStorage.transactNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage.js:1274:26) at async LocalApi.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\api-local.js:133:24) at async DataReference.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase-core\dist\cjs\data-reference.js:293:28) node:internal/process/promises:279 triggerUncaughtException(err, true /* fromPromise */); ^ Error: Not enough bytes read from file at index 131072, expected 128 but got 0 at NodeReader.readHeader (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:3051:49) at async start (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2649:17) at async NodeReader.getChildInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:2956:9) at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1725:33) at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34) at async AceBaseStorage.getNodeInfo (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1701:34) at async AceBaseStorage.getNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage-acebase.js:1587:30) at async AceBaseStorage.transactNode (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\storage.js:1274:26) at async LocalApi.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase\src\api-local.js:133:24) at async DataReference.transaction (C:\Users\Finn Lancaster\Desktop\Finned-Backend\node_modules\acebase-core\dist\cjs\data-reference.js:293:28) ```
gitea-mirror commented 2026-05-23 08:38:28 -06:00
Author
Owner
Copy link

@donl commented on GitHub (Jul 26, 2022):

Try removing

const db = new AceBase('db');

Otherwise you are creating/accessing the same database named 'db' on disk multiple times simultaneously, which requires special coordination.

<!-- gh-comment-id:1194885548 --> @donl commented on GitHub (Jul 26, 2022): Try removing ``` js const db = new AceBase('db'); ``` Otherwise you are creating/accessing the same database named 'db' on disk multiple times simultaneously, which requires special coordination.
gitea-mirror commented 2026-05-23 08:38:29 -06:00
Author
Owner
Copy link

@flancast90 commented on GitHub (Jul 26, 2022):

I tried both with and without that line, and got the same issue either way.
Any other ideas?

On Mon, Jul 25, 2022 at 10:03 PM Don @.***> wrote:

Try removing

const db = new AceBase('db');

Otherwise you are creating/accessing the same database named 'db' on disk
multiple times simultaneously, which requires special coordination.

—
Reply to this email directly, view it on GitHub
https://github.com/appy-one/acebase-server/issues/27#issuecomment-1194885548,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR2EVEEBIWLEL3BLGP4IOQLVV5BNNANCNFSM54FYQGJQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:1194901275 --> @flancast90 commented on GitHub (Jul 26, 2022): I tried both with and without that line, and got the same issue either way. Any other ideas? On Mon, Jul 25, 2022 at 10:03 PM Don ***@***.***> wrote: > Try removing > > const db = new AceBase('db'); > > Otherwise you are creating/accessing the same database named 'db' on disk > multiple times simultaneously, which requires special coordination. > > — > Reply to this email directly, view it on GitHub > <https://github.com/appy-one/acebase-server/issues/27#issuecomment-1194885548>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AR2EVEEBIWLEL3BLGP4IOQLVV5BNNANCNFSM54FYQGJQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
gitea-mirror commented 2026-05-23 08:38:30 -06:00
Author
Owner
Copy link

@appy-one commented on GitHub (Jul 26, 2022):

It looks like you may have corrupted the database file by accessing (writing to) it from both an AceBaseServer and local AceBase db instance, I posted about this a while ago in the discussion "How to protect your database from corruption".

If the data you stored in the db is important, I might be able to help you recover the data. If it only has dev/test data, I recommend removing it and starting over with a fresh db. Make sure you only let a single AceBaseServer instance access the database files, or configure an acebase-ipc-server to setup a cluster.

<!-- gh-comment-id:1195879825 --> @appy-one commented on GitHub (Jul 26, 2022): It looks like you may have corrupted the database file by accessing (writing to) it from both an `AceBaseServer` and local `AceBase` db instance, I posted about this a while ago in the discussion ["How to protect your database from corruption"](https://github.com/appy-one/acebase/discussions/48). If the data you stored in the db is important, I might be able to help you recover the data. If it only has dev/test data, I recommend removing it and starting over with a fresh db. Make sure you only let a single `AceBaseServer` instance access the database files, or configure an [acebase-ipc-server](https://github.com/appy-one/acebase-ipc-server) to setup a cluster.
gitea-mirror commented 2026-05-23 08:38:31 -06:00
Author
Owner
Copy link

@flancast90 commented on GitHub (Jul 29, 2022):

I tried using only one of the instances and deleting the existing db to
allow it to create a fresh one, with the same issue. In terms of recovery,
I never actually got it to work, so there was no data in it.

On Tue, Jul 26, 2022 at 3:14 PM Ewout Stortenbeker @.***>
wrote:

It looks like you may have corrupted the database file by accessing
(writing to) it from both an AceBaseServer and local AceBase db instance,
I posted about this a while ago in the discussion "How to protect your
database from corruption"
https://github.com/appy-one/acebase/discussions/48.

If the data you stored in the db is important, I might be able to help you
recover the data. If it only has dev/test data, I recommend removing it and
starting over with a fresh db. Make sure you only let a single
AceBaseServer instance access the database files, or configure an
acebase-ipc-server https://github.com/appy-one/acebase-ipc-server to
setup a cluster.

—
Reply to this email directly, view it on GitHub
https://github.com/appy-one/acebase-server/issues/27#issuecomment-1195879825,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR2EVEARWLLBNI46GDX3LHDVWA2IVANCNFSM54FYQGJQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:1199896698 --> @flancast90 commented on GitHub (Jul 29, 2022): I tried using only one of the instances and deleting the existing db to allow it to create a fresh one, with the same issue. In terms of recovery, I never actually got it to work, so there was no data in it. On Tue, Jul 26, 2022 at 3:14 PM Ewout Stortenbeker ***@***.***> wrote: > It looks like you may have corrupted the database file by accessing > (writing to) it from both an AceBaseServer and local AceBase db instance, > I posted about this a while ago in the discussion "How to protect your > database from corruption" > <https://github.com/appy-one/acebase/discussions/48>. > > If the data you stored in the db is important, I might be able to help you > recover the data. If it only has dev/test data, I recommend removing it and > starting over with a fresh db. Make sure you only let a single > AceBaseServer instance access the database files, or configure an > acebase-ipc-server <https://github.com/appy-one/acebase-ipc-server> to > setup a cluster. > > — > Reply to this email directly, view it on GitHub > <https://github.com/appy-one/acebase-server/issues/27#issuecomment-1195879825>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AR2EVEARWLLBNI46GDX3LHDVWA2IVANCNFSM54FYQGJQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
gitea-mirror commented 2026-05-23 08:38:32 -06:00
Author
Owner
Copy link

@appy-one commented on GitHub (Jul 30, 2022):

Alright, you'll have to provide more code to reproduce this then. Only importing AceBaseServer and instantiating it with a new db does not cause any issues in my tests?

<!-- gh-comment-id:1200280828 --> @appy-one commented on GitHub (Jul 30, 2022): Alright, you'll have to provide more code to reproduce this then. Only importing `AceBaseServer` and instantiating it with a new db does not cause any issues in my tests?
gitea-mirror commented 2026-05-23 08:38:32 -06:00
Author
Owner
Copy link

@appy-one commented on GitHub (Aug 19, 2022):

I'm closing this issue for now. If you have more info about how to reproduce this, feel free to reopen!

<!-- gh-comment-id:1221049310 --> @appy-one commented on GitHub (Aug 19, 2022): I'm closing this issue for now. If you have more info about how to reproduce this, feel free to reopen!
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
dependabot/npm_and_yarn/socket.io-4.6.2
dependabot/npm_and_yarn/braces-3.0.3
dependabot/npm_and_yarn/express-4.19.2
dependencies/acebase-1.24.2/acebase-core-1.22.3
dependencies/acebase
fix/tsc-node-16-module-resolution
v1.19.0
v1.18.2
v1.18.0
v1.17.0
v1.16.2
v1.16.1
v1.16.0
v1.15.2
v1.15.1
v1.15.0
v1.14.0
v1.13.3
v1.13.2
v1.13.1
v1.13.0
v1.12.0
v1.11.0
v1.10.1
Labels
Clear labels   
bug

   
enhancement

   
feature request

   
pull-request

Mirrored from GitHub Pull Request

  
types
No labels
bug
enhancement
feature request
pull-request
types
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/acebase-server#13
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?