6 months ago
@projectId: 91e48b2d-a33c-488b-86a1-30182fe1221a
@projectName: clk_0199097fc80774019e599_12edd7
@service:"svc_0199097fc80774019e599_12edd7" enabled serverless
not access http logs found
mongodb
@service MongoDB-834563117840293888 with ServerLess enabled
if this is a bug of railway,please refund money back!
Pinned Solution
6 months ago
accordingly to the documentation https://docs.railway.com/reference/app-sleeping the activity of the app is based on the outbound packets detection, not inbound traffic. This way, if there is any traffic going out from your service - the service is considered active:
Inactivity is based on the detection of any outbound packets, which could include network requests, database connections, or even NTP. If no packets are sent from the service for over 10 minutes, the service is considered inactive
and
It's important to note that the networking graph in the metrics tab only displays public internet traffic. If you're using a private network to communicate with other services, this traffic won't appear in the metrics tab. However, it's still counted as outbound traffic and will prevent the service from being put to sleep.
especially:
Some things that can prevent a service from being put to sleep -
Keeping active database connections open, such as a database connection pooler.
Making requests to other services in the same project over the private network.
In other words, the Serverless is not about incoming http traffic, it's about the service activity. As you have Mongo DB connected it's very likely that there is background communication goes on between the database and your service even despite no http requests made to the service. This is considered as active by Railway
The same way, as your Mongo service does generate outbound traffic to your service, the Mongo also considered active
3 Replies
6 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
Railway
Hey there! We've found the following might help you get unblocked faster: - [🧵 MongoDB Fail to Authorize](https://station.railway.com/questions/mongo-db-fail-to-authorize-e98857f2) - [🧵 Does Hobby Plan Include Static IPs?](https://station.railway.com/questions/does-hobby-plan-include-static-i-ps-7cf4b6f8) - [🧵 Access Issue: n8n Project "Capable-Compassion" on Railway - Admin Contact Required](https://station.railway.com/questions/access-issue-n8n-project-capable-compa-aaea4a9b) If you find the answer from one of these, please let us know by solving the thread!
6 months ago
not the problem specified
develop
not the problem specified
6 months ago
accordingly to the documentation https://docs.railway.com/reference/app-sleeping the activity of the app is based on the outbound packets detection, not inbound traffic. This way, if there is any traffic going out from your service - the service is considered active:
Inactivity is based on the detection of any outbound packets, which could include network requests, database connections, or even NTP. If no packets are sent from the service for over 10 minutes, the service is considered inactive
and
It's important to note that the networking graph in the metrics tab only displays public internet traffic. If you're using a private network to communicate with other services, this traffic won't appear in the metrics tab. However, it's still counted as outbound traffic and will prevent the service from being put to sleep.
especially:
Some things that can prevent a service from being put to sleep -
Keeping active database connections open, such as a database connection pooler.
Making requests to other services in the same project over the private network.
In other words, the Serverless is not about incoming http traffic, it's about the service activity. As you have Mongo DB connected it's very likely that there is background communication goes on between the database and your service even despite no http requests made to the service. This is considered as active by Railway
The same way, as your Mongo service does generate outbound traffic to your service, the Mongo also considered active
Status changed to Solved jake • 6 months ago
