Service with Storage Start Failed
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.
Solution:Jump to solution
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?
35 Replies
Project ID:
100de0d1-4433-49c2-acb0-1463b57b3e59Do you mean storage asn a database?
I mean the new Persist Storage / Volume, sorry that info is missing.
what is your mount point for the volume?
/app/uploads
do you already have a pre existing folder in that location?
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.
sounds good, I'll be around
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 @Brody
let's see it
Any news on this topic ☺️? Thanks 🙏
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
I thought you look directly in then project … ah sorry I didn’t know. Who can help on this infrastructure bug?
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?
Yea… how can I link an internal supporter?
Yes it crash’s because of timeout
I would flag the team for you once I am sure that this is an issue with the platform
After a the publishing time in the logs, are nothing
It’s failed after 1 hour timeout as a crash
can you try mounting the volume to
/app/1234 and let me know if that deploys successfullyOk, I will try. Iam on the road, after I arrive the office I answer here
👍
it's late for me, so I'd probably end up getting back to your answer in the morning
No problem, thanks four your support ❤️
hmm same error with /app/1234
now the status is failed and after 1 houre is crashed
no real error just a timeout?
nope
no error
and you don't happen to have a folder named 1234 do you lol
yes same like /app/uploads
if i unmount the volume, the service run
you do have a folder named 1234 in your project??
no
i had two more project with the same stack, no error
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
yes for sure!
thanks!
Flagging this thread. A team member will be with you shortly.
Looks like the service is in a funky state due to the folder originally existing on the same path.
Solution
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?
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
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?