Okay, thank you for your response. I will check further.

N

nato•10/29/24, 2:35 PM

how can I make 2 different cloudflare workers apps use same D1 db in local dev?

N

nato•10/29/24, 2:35 PM

I see it uses ./wrangler/state/v3/d1 but since both projects are on seperate folders

N

nato•10/29/24, 2:36 PM

is there any way to specify path?

N

nato•10/29/24, 2:37 PM

nvm it was mentioned in docs

npx wrangler dev --persist-to <DIRECTORY>

npx wrangler dev --persist-to <DIRECTORY>

npx wrangler dev --persist-to <DIRECTORY>

npx wrangler dev --persist-to <DIRECTORY>

TTomK Okay, thank you for your response. I will check further.

S

Stan Angeloff•10/29/24, 3:01 PM

I'm another customer that's observing lots of random D1 failures today (and in general a lot more since September, lots of lost connection, internal error, etc.) Just thought I'd chime in so you know you are not alone.

S

sz19•10/29/24, 4:01 PM

It started at 12PM UTC, I've been receiving these errors since then.
D1 storage operation exceeded timeout which caused object to be reset. / Network connection lost. / internal error

Ssz19 It started at 12PM UTC, I've been receiving these errors since then. D1 storage ...

T

TomKOP•10/29/24, 4:38 PM

I also encountered the same issue at the same time.

TTomK I also encountered the same issue at the same time.

S

sz19•10/29/24, 4:49 PM

is your d1 database located somewhere in asia?

Ssz19 is your d1 database located somewhere in asia?

T

TomKOP•10/29/24, 4:57 PM

yes

T

TomKOP•10/29/24, 4:59 PM

I'm not sure if this has anything to do with the maintenance program in the Singapore region?

T

TomKOP•10/29/24, 5:02 PM

TTomK Click to see attachment

F

fry69•10/29/24, 5:09 PM

That is still in the future if I read this correctly (UTC)

F

fry69•10/29/24, 5:10 PM

(should start in <1h)

F

fry69•10/29/24, 5:12 PM

The hiccups could of course be due to preparations for this maintenance or other things.

Ffry69 That is still in the future if I read this correctly (UTC)

T

TomKOP•10/29/24, 5:14 PM

Yes, it was future time, which is a very far-fetched reason indeed, but other than that I can't associate it with any other reason, since the code wasn't updated.:NotLikeThis:

S

sz19•10/29/24, 5:38 PM

Update: errors seems to be gone now on mine

S

sz19•10/29/24, 5:44 PM

There was about a solid 5 mins giving me this error:
Error: D1_ERROR: Internal error while starting up D1 storage caused object to be reset.
, then after that i no longer receive d1 errors. Hopefully it stays like this

R

rubenf•10/29/24, 8:41 PM

Our D1 database has been unavailable for the last 10mins withL:

D1_ERROR: Internal error while starting up D1 storage caused object to be reset.

D1_ERROR: Internal error while starting up D1 storage caused object to be reset.

D1_ERROR: Internal error while starting up D1 storage caused object to be reset.

D1_ERROR: Internal error while starting up D1 storage caused object to be reset.

R

rubenf•10/29/24, 8:42 PM

even the cloud console can't access it

R

rubenf•10/29/24, 8:42 PM

Are D1 databases beta/unfit for prod?

Rrubenf Our D1 database has been unavailable for the last 10mins withL: `D1_ERROR: Inter...

F

fry69•10/29/24, 8:45 PM

Which region/colo?

R

rubenf•10/29/24, 8:46 PM

@fry69 not sure actually, where do I find that info

R

rubenf•10/29/24, 8:46 PM

we have the database id

Rrubenf we have the database id

F

fry69•10/29/24, 8:56 PM

running_in_region

running_in_region

running_in_region

running_in_region via

wrangler d1 info <dbname>

wrangler d1 info <dbname>

wrangler d1 info <dbname>

wrangler d1 info <dbname>

F

fry69•10/29/24, 8:57 PM

R

rubenf•10/29/24, 8:58 PM

  Internal error: failed to get DB size and num_tables [code: 7500]
  
  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/workers-sdk/issues/new/choose

  Internal error: failed to get DB size and num_tables [code: 7500]
  
  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/workers-sdk/issues/new/choose

  Internal error: failed to get DB size and num_tables [code: 7500]
  
  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/workers-sdk/issues/new/choose

  Internal error: failed to get DB size and num_tables [code: 7500]
  
  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/workers-sdk/issues/new/choose

R

rubenf•10/29/24, 8:58 PM

the whole db is completely unavailable

1

1984 Ford Laser•10/29/24, 8:59 PM

syntax error?

Rrubenf ``` Internal error: failed to get DB size and num_tables [code: 7500] If ...

F

fry69•10/29/24, 8:59 PM

Worked for me in region

EEUR

EEUR

EEUR

EEUR (creating a new D1 db and showing the info)

R

rubenf•10/29/24, 8:59 PM

that's using the CLI

R

rubenf•10/29/24, 8:59 PM

We have numerous D1 database, this one is failing, not the others

I

itsmatteomanf•10/29/24, 9:00 PM

Yeah, my best bet is that it's an issue of the specific D1 instance... can we ping somebody in the D1 team or escalate it, @Walshy?

1

1984 Ford Laser•10/29/24, 9:00 PM

https://github.com/cloudflare/workers-sdk/issues/4713
There's this that relates to comments in sql file, maybe relevant?

Rrubenf even the cloud console can't access it

C

Chaika•10/29/24, 9:00 PM

what's the id of the db and your account id?

C

Chaika•10/29/24, 9:00 PM

even if the dash doesn't load, should still let you see it

CChaika even if the dash doesn't load, should still let you see it

I

itsmatteomanf•10/29/24, 9:01 PM

a while back I had a db fail similarly, it wouldn't show it at all

R

rubenf•10/29/24, 9:01 PM

is it ok to share the id publicly ?

C

Chaika•10/29/24, 9:01 PM

yes

R

rubenf•10/29/24, 9:01 PM

cbc9139f-7d2b-494d-b8ca-91875f273dda

I

itsmatteomanf•10/29/24, 9:01 PM

but yeah, db id and account id are fine to share

Iitsmatteomanf a while back I had a db fail similarly, it wouldn't show it at all

C

Chaika•10/29/24, 9:01 PM

must depend on type of failure, when my broke it (way back during the beta) just refused to load details

R

rubenf•10/29/24, 9:02 PM

We have moved everything from RDS to D1, and we're now a little bit concerned to say the least

CChaika must depend on type of failure, when my broke it (way back during the beta) just...

I

itsmatteomanf•10/29/24, 9:02 PM

mine had a storage issue on the node, fully collapsed and didn't show anywhere, it remained in the loading state

Rrubenf We have moved everything from RDS to D1, and we're now a little bit concerned to...

I

itsmatteomanf•10/29/24, 9:02 PM

let me escalate this for you

Rrubenf cbc9139f-7d2b-494d-b8ca-91875f273dda

I

itsmatteomanf•10/29/24, 9:02 PM

Mind giving me the account id, too?

I

itsmatteomanf•10/29/24, 9:02 PM

That's the DB ID, right?

R

rubenf•10/29/24, 9:03 PM

correct, just gotta find out where to get our account id

H

Hugo•10/29/24, 9:03 PM

our account id is f3802b49118373bb0dd68e319c9be207

Iitsmatteomanf Yeah, my best bet is that it's an issue of the specific D1 instance... can we pi...

W

Walshy•10/29/24, 9:03 PM

dealing with a diff inc atm - p3 it pls

WWalshy dealing with a diff inc atm - p3 it pls

I

itsmatteomanf•10/29/24, 9:05 PM

Done!

Okay, thank you for your response. I will check further.

Similar Threads

Similar Threads

Similar Threads