#Service with Storage Start Failed

49 messages · Page 1 of 1 (latest)

celest fern
#

Hello, unfortunately my service 100de0d1-4433-49c2-acb0-1463b57b3e59 does not start when I have a storage enabled for it. As soon as I remove the storage, it starts without error. In the logs it just doesn't continue after Publish time: 13.84 seconds and then I guess a timeout occurs.

I have two other projects that are identical in construction that run without problems.

mild birchBOT
#

Project ID: 100de0d1-4433-49c2-acb0-1463b57b3e59

thorny surgeBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

novel anchor
#

Do you mean storage asn a database?

celest fern
#

I mean the new Persist Storage / Volume, sorry that info is missing.

snow temple
#

what is your mount point for the volume?

celest fern
#

/app/uploads

snow temple
#

do you already have a pre existing folder in that location?

celest fern
#

earlier yes, but I had deleted this on the part of github - because I also thought at first, the error comes from this, but was unfortunately still not solved. what happens if there is a folder already via github? this should be theoretically also possible.

#

don't be surprised, i have now removed the volume from the service for the time being, because i need it now for work - so everything is running again now. will add the volume again tonight after work, so that you can see the error again.

snow temple
#

sounds good, I'll be around

celest fern
#

I am now done with my work and have now hooked the volume back up to the service. The error is available again. If you have time, feel free to take a look. Thanks @snow temple

snow temple
#

let's see it

celest fern
#

Any news on this topic ☺️? Thanks 🙏

snow temple
#

I mean you never showed me any errors?

#

there may be some confusion here because I'm just a community member and I have no access to your project what so ever

celest fern
#

I thought you look directly in then project … ah sorry I didn’t know. Who can help on this infrastructure bug?

snow temple
#

I wish I could, but that's a huge security risk if community members could look into your project like that

#

is there any visual error to begin with?

celest fern
#

Yea… how can I link an internal supporter?

#

Yes it crash’s because of timeout

snow temple
#

I would flag the team for you once I am sure that this is an issue with the platform

celest fern
#

After a the publishing time in the logs, are nothing

#

It’s failed after 1 hour timeout as a crash

snow temple
#

can you try mounting the volume to /app/1234 and let me know if that deploys successfully

celest fern
#

Ok, I will try. Iam on the road, after I arrive the office I answer here

snow temple
#

👍

#

it's late for me, so I'd probably end up getting back to your answer in the morning

celest fern
#

No problem, thanks four your support ❤️

celest fern
#

hmm same error with /app/1234

#

now the status is failed and after 1 houre is crashed

snow temple
#

no real error just a timeout?

celest fern
#

nope

#

no error

snow temple
#

and you don't happen to have a folder named 1234 do you lol

celest fern
#

yes same like /app/uploads

#

if i unmount the volume, the service run

snow temple
#

you do have a folder named 1234 in your project??

celest fern
#

no

#

i had two more project with the same stack, no error

snow temple
#

ah gotcha, okay I'm plenty confident enough that this isn't user error, I hope you understand that I had to be sure before flagging the team

celest fern
#

yes for sure!

#

thanks!

mild birchBOT
#

Flagging this thread. A team member will be with you shortly.

merry kayak
#

Looks like the service is in a funky state due to the folder originally existing on the same path.

#

Would you be okay with deleting the service and just setting up a new one? Or have you already tried doing that and the error keeps showing up with this repo?

celest fern
#

The service can be deleted, the database need to be stay - i can try. but the /app/uplods dir is not existing in the git repo. does this mean that a volume folder must never already exist via the github repo? here again an error message would be important when trying to create this

celest fern
#

Perfect, to recreate the service solved the error - but i am confused how can it be happend. maybe there is a chance to invastigate the problem to prevent same problems in the future on prodcution env's?