3 months ago
there is an issue in MYsql databse in the service in railway it wont connect , please whats the problem ? my application is in production
16 Replies
3 months ago
have you tried redeploying?
nah , this is a nightmare for me , so i wont touch anything unless u gys tell me
3 months ago
could you try redeploying then? it's possible the incident placed it in a weird state and redeploying might fix it
3 months ago
Hey Mod, same issue here:
Command "messenger:consume async --sleep=10 --memory-limit=512M --no-interaction" exited with code "1"
SQLSTATE[HY000] [2002] Connection timed out
In DoctrineReceiver.php line 59:
An exception occurred in the driver: SQLSTATE[HY000] [2002] Connection time
d out
In PDOConnect.php line 22:
In ExceptionConverter.php line 91:
An exception occurred in the driver: SQLSTATE[HY000] [2002] Connection time
SQLSTATE[HY000] [2002] Connection timed out
d out
In Exception.php line 24:
messenger:consume [-l|--limit LIMIT] [-f|--failure-limit FAILURE-LIMIT] [-m|--memory-limit MEMORY-LIMIT] [-t|--time-limit TIME-LIMIT] [--sleep SLEEP] [-b|--bus BUS] [--queues QUEUES] [--no-reset] [--all] [--keepalive [KEEPALIVE]] [--] [<receivers>...]
// Quit the worker with CONTROL-C.
User Deprecated: Support for MySQL < 8 is deprecated and will be removed in DBAL 5 (AbstractMySQLDriver.php:75 called by AbstractDriverMiddleware.php:32, https://github.com/doctrine/dbal/pull/6343, package doctrine/dbal)
[OK] Consuming messages from transport "async".
// Re-run the command with a -vv option to see logs about consumed messages.
// The worker will automatically exit once it has exceeded 512M of memory or
// received a stop signal via the messenger:stop-workers command.
I restarted a couple of times but crashing again. IT was working great I did change nothing.
3 months ago
it happens after like 15-20 minutes. I restarted again, let's see.
3 months ago
Nope it crashed again pfff.
3 months ago
Update: Looks like MySQL services are not running.
Is there anyone out there who have any idea what is going on?
3 months ago
MODS this is a huge problem that comes this morning
3 months ago
Sorry guys, from what I can tell this is still related to the original incident, a fix has been rolled out but I've been told the fleet is taking a bit to stabilize
fragly is it going to take much ? , and please what is the original incident ?
3 months ago
the original incident is here: https://status.railway.com/cmj89j6z2000qodpsfs4nc2gb
and I'm not sure how long it'll take to stabilize, hopefully not long
To be clear, the incident has never been solved, its still ongoing
3 months ago
okay i will keep the ticket opened in case something happened , hope the fix comes fast