I am using pm2 to run my nodejs(express server) app. As i know pm2 will restart the app if the app crashed. But i don't know why the process is automatically deleted(dissapear) after i found out that the website is "503 error" and i try to type "pm2 monit" the process is dissapear.
Here are some info:
the app is hosted on sharedhosting with ssh access.
after installed pm2 globally, i start the app using the default command: "pm2 start [path_to_server_from_public_html].js"
inside pm2.log:
2019-08-02T11:05:35: PM2 log: ===============================================================================
2019-08-02T11:05:35: PM2 log: --- New PM2 Daemon started ----------------------------------------------------
2019-08-02T11:05:35: PM2 log: Time : Fri Aug 02 2019 11:05:35 GMT+0700
2019-08-02T11:05:35: PM2 log: PM2 version : 3.5.1
2019-08-02T11:05:35: PM2 log: Node.js version : 12.6.0
2019-08-02T11:05:35: PM2 log: Current arch : x64
2019-08-02T11:05:35: PM2 log: PM2 home : /home/u1971755/.pm2
2019-08-02T11:05:35: PM2 log: PM2 PID file : /home/u1971755/.pm2/pm2.pid
2019-08-02T11:05:35: PM2 log: RPC socket file : /home/u1971755/.pm2/rpc.sock
2019-08-02T11:05:35: PM2 log: BUS socket file : /home/u1971755/.pm2/pub.sock
2019-08-02T11:05:35: PM2 log: Application log path : /home/u1971755/.pm2/logs
2019-08-02T11:05:35: PM2 log: Process dump file : /home/u1971755/.pm2/dump.pm2
2019-08-02T11:05:35: PM2 log: Concurrent actions : 2
2019-08-02T11:05:35: PM2 log: SIGTERM timeout : 1600
2019-08-02T11:05:35: PM2 log: ===============================================================================
2019-08-02T11:05:35: PM2 log: App [server:0] starting in -fork mode-
2019-08-02T11:05:35: PM2 log: App [server:0] online
2019-08-02T11:18:35: PM2 log: App [server:0] exited with code [0] via signal [SIGTERM]
2019-08-02T11:18:35: PM2 log: App [server:0] starting in -fork mode-
2019-08-02T11:18:35: PM2 log: App [server:0] online
2019-08-02T11:19:09: PM2 error: 1 : id unknown
2019-08-02T11:19:13: PM2 log: Stopping app:server id:0
2019-08-02T11:19:13: PM2 log: App [server:0] exited with code [0] via signal [SIGINT]
2019-08-02T11:19:13: PM2 log: pid=31251 msg=process killed
2019-08-02T11:19:28: PM2 log: App [server:0] starting in -fork mode-
2019-08-02T11:19:28: PM2 log: App [server:0] online
2019-08-02T11:19:51: PM2 error: 1 : id unknown
2019-08-02T11:22:18: PM2 log: App [server:0] exited with code [0] via signal [SIGTERM]
2019-08-02T11:22:18: PM2 log: App [server:0] starting in -fork mode-
2019-08-02T11:22:18: PM2 log: App [server:0] online
2019-08-02T11:22:21: PM2 log: App [server:0] exited with code [0] via signal [SIGTERM]
2019-08-02T11:22:21: PM2 log: App [server:0] starting in -fork mode-
2019-08-02T11:22:21: PM2 log: App [server:0] online
2019-08-02T11:23:11: PM2 error: 1 : id unknown
2019-08-20T10:18:42: PM2 log: Stopping app:server id:0
2019-08-20T10:18:43: PM2 log: App [server:0] exited with code [0] via signal [SIGINT]
2019-08-20T10:18:43: PM2 log: pid=5965 msg=process killed
2019-08-20T10:18:43: PM2 log: App [server:0] starting in -fork mode-
2019-08-20T10:18:43: PM2 log: App [server:0] online
2019-08-21T11:33:39: PM2 log: App [server:0] exited with code [0] via signal [SIGTERM]
2019-08-21T11:33:39: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:33:39: PM2 log: App [server:0] online
2019-08-21T11:34:42: PM2 log: Stopping app:server id:0
2019-08-21T11:34:42: PM2 log: App [server:0] exited with code [0] via signal [SIGINT]
2019-08-21T11:34:42: PM2 log: pid=9888 msg=process killed
2019-08-21T11:34:42: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:34:42: PM2 log: App [server:0] online
2019-08-21T11:41:25: PM2 log: Stopping app:server id:0
2019-08-21T11:41:25: PM2 log: App [server:0] exited with code [0] via signal [SIGINT]
2019-08-21T11:41:25: PM2 log: pid=15091 msg=process killed
2019-08-21T11:41:25: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:25: PM2 log: App [server:0] online
2019-08-21T11:41:26: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:26: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:26: PM2 log: App [server:0] online
2019-08-21T11:41:26: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:26: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:26: PM2 log: App [server:0] online
2019-08-21T11:41:26: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:26: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:26: PM2 log: App [server:0] online
2019-08-21T11:41:26: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:26: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:26: PM2 log: App [server:0] online
2019-08-21T11:41:26: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:26: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:26: PM2 log: App [server:0] online
2019-08-21T11:41:27: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:27: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:27: PM2 log: App [server:0] online
2019-08-21T11:41:27: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:27: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:27: PM2 log: App [server:0] online
2019-08-21T11:41:27: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:27: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:27: PM2 log: App [server:0] online
2019-08-21T11:41:27: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:27: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:27: PM2 log: App [server:0] online
2019-08-21T11:41:27: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:27: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:27: PM2 log: App [server:0] online
2019-08-21T11:41:28: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:28: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:28: PM2 log: App [server:0] online
2019-08-21T11:41:28: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:28: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:28: PM2 log: App [server:0] online
2019-08-21T11:41:28: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:28: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:28: PM2 log: App [server:0] online
2019-08-21T11:41:28: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:28: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:28: PM2 log: App [server:0] online
2019-08-21T11:41:28: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:28: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:28: PM2 log: App [server:0] online
2019-08-21T11:41:28: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:28: PM2 log: Script /home/u1971755/public_html/service/build/server/server.js had too many unstable restarts (16). Stopped. "errored"
2019-08-21T11:41:43: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:43: PM2 log: App [server:0] online
2019-08-21T11:41:43: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:43: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:43: PM2 log: App [server:0] online
2019-08-21T11:41:44: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:44: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:44: PM2 log: App [server:0] online
2019-08-21T11:41:44: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:44: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:44: PM2 log: App [server:0] online
2019-08-21T11:41:44: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:44: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:44: PM2 log: App [server:0] online
2019-08-21T11:41:44: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:44: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:44: PM2 log: App [server:0] online
2019-08-21T11:41:44: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:44: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:44: PM2 log: App [server:0] online
2019-08-21T11:41:44: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:44: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:44: PM2 log: App [server:0] online
2019-08-21T11:41:45: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:45: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:45: PM2 log: App [server:0] online
2019-08-21T11:41:45: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:45: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:45: PM2 log: App [server:0] online
2019-08-21T11:41:45: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:45: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:45: PM2 log: App [server:0] online
2019-08-21T11:41:45: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:45: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:45: PM2 log: App [server:0] online
2019-08-21T11:41:45: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:45: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:45: PM2 log: App [server:0] online
2019-08-21T11:41:45: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:45: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:45: PM2 log: App [server:0] online
2019-08-21T11:41:46: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:46: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:46: PM2 log: App [server:0] online
2019-08-21T11:41:46: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:46: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:41:46: PM2 log: App [server:0] online
2019-08-21T11:41:46: PM2 log: App [server:0] exited with code [1] via signal [SIGINT]
2019-08-21T11:41:46: PM2 log: Script /home/u1971755/public_html/service/build/server/server.js had too many unstable restarts (16). Stopped. "errored"
2019-08-21T11:42:36: PM2 log: Stopping app:server id:0
2019-08-21T11:42:36: PM2 error: app=server id=0 does not have a pid
2019-08-21T11:43:36: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:43:36: PM2 log: App [server:0] online
2019-08-21T11:43:55: PM2 log: Stopping app:server id:0
2019-08-21T11:43:55: PM2 log: App [server:0] exited with code [0] via signal [SIGINT]
2019-08-21T11:43:55: PM2 log: pid=20025 msg=process killed
2019-08-21T11:43:55: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:43:55: PM2 log: App [server:0] online
2019-08-21T11:45:02: PM2 log: Stopping app:server id:0
2019-08-21T11:45:02: PM2 log: App [server:0] exited with code [0] via signal [SIGINT]
2019-08-21T11:45:02: PM2 log: pid=21490 msg=process killed
2019-08-21T11:45:02: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T11:45:02: PM2 log: App [server:0] online
2019-08-21T11:47:54: PM2 log: Stopping app:server id:0
2019-08-21T11:47:54: PM2 log: App [server:0] exited with code [0] via signal [SIGINT]
2019-08-21T11:47:54: PM2 log: pid=27614 msg=process killed
2019-08-21T12:08:06: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T12:08:06: PM2 log: App [server:0] online
2019-08-21T12:12:23: PM2 log: Stopping app:server id:0
2019-08-21T12:12:23: PM2 log: App [server:0] exited with code [0] via signal [SIGINT]
2019-08-21T12:12:23: PM2 log: pid=24151 msg=process killed
2019-08-21T12:38:26: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T12:38:26: PM2 log: App [server:0] online
2019-08-21T12:39:41: PM2 log: Stopping app:server id:0
2019-08-21T12:39:41: PM2 log: App [server:0] exited with code [0] via signal [SIGINT]
2019-08-21T12:39:41: PM2 log: pid=10351 msg=process killed
2019-08-21T12:39:41: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T12:39:41: PM2 log: App [server:0] online
2019-08-21T12:44:09: PM2 log: App [server:0] exited with code [0] via signal [SIGTERM]
2019-08-21T12:44:09: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T12:44:09: PM2 log: App [server:0] online
2019-08-21T12:44:33: PM2 log: App [server:0] exited with code [0] via signal [SIGTERM]
2019-08-21T12:44:33: PM2 log: App [server:0] starting in -fork mode-
2019-08-21T12:44:33: PM2 log: App [server:0] online
2019-09-14T12:44:52: PM2 log: ===============================================================================
2019-09-14T12:44:52: PM2 log: --- New PM2 Daemon started ----------------------------------------------------
2019-09-14T12:44:52: PM2 log: Time : Sat Sep 14 2019 12:44:52 GMT+0700
2019-09-14T12:44:52: PM2 log: PM2 version : 3.5.1
2019-09-14T12:44:52: PM2 log: Node.js version : 12.6.0
2019-09-14T12:44:52: PM2 log: Current arch : x64
2019-09-14T12:44:52: PM2 log: PM2 home : /home/u1971755/.pm2
2019-09-14T12:44:52: PM2 log: PM2 PID file : /home/u1971755/.pm2/pm2.pid
2019-09-14T12:44:52: PM2 log: RPC socket file : /home/u1971755/.pm2/rpc.sock
2019-09-14T12:44:52: PM2 log: BUS socket file : /home/u1971755/.pm2/pub.sock
2019-09-14T12:44:52: PM2 log: Application log path : /home/u1971755/.pm2/logs
2019-09-14T12:44:52: PM2 log: Process dump file : /home/u1971755/.pm2/dump.pm2
2019-09-14T12:44:52: PM2 log: Concurrent actions : 2
2019-09-14T12:44:52: PM2 log: SIGTERM timeout : 1600
2019-09-14T12:44:52: PM2 log: ===============================================================================
2019-09-14T12:46:02: PM2 log: App [server:0] starting in -fork mode-
2019-09-14T12:46:02: PM2 log: App [server:0] online
NOTE:
app first start date: (2019-08-02T11:05:35)
last log before today(PM2 log: App [server:0] online)): (2019-08-21T12:44:33)
app process suddenly dissapear date: (2019-09-14T12)
As you could see that the app or pm2 should work just fine right?. btw i just restarted the app manually today(2019-09-14T12:44:52) after i found out the app process no longer exist using: "pm2 start [path_to_server_from_public_html].js".
Please help me, it is so annoying if i need to restart the app manually after 1 month. Thank you very much guys...
Related
I am trying to install MySQL 8.0 Community Edition on Fedora 34. I installed the repo rom from https://dev.mysql.com/downloads/repo/yum/
After running sudo dnf install mysql-community-server I am getting the below error output:
MySQL 8.0 Community Server 0.0 B/s | 0 B 12:42
Errors during downloading metadata for repository 'mysql80-community':
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30020 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/x86_64/repodata/c55e90c7ab0dc694323139988d5868a381c441ff-primary.xml.gz [Resolving timed out after 30096 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/x86_64/repodata/c55e90c7ab0dc694323139988d5868a381c441ff-primary.xml.gz [Resolving timed out after 30000 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/x86_64/repodata/c55e90c7ab0dc694323139988d5868a381c441ff-primary.xml.gz [Resolving timed out after 30001 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30001 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/x86_64/repodata/5920395724110a6f03637c4f6187bfa801f8a70b-filelists.xml.gz [Resolving timed out after 30096 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30004 milliseconds]
Error: Failed to download metadata for repo 'mysql80-community': Yum repo downloading error: Downloading error(s): repodata/c55e90c7ab0dc694323139988d5868a381c441ff-primary.xml.gz - Cannot download, all mirrors were already tried without success; repodata/5920395724110a6f03637c4f6187bfa801f8a70b-filelists.xml.gz - Cannot download, all mirrors were already tried without success
MySQL Connectors Community 0.0 B/s | 0 B 08:39
Errors during downloading metadata for repository 'mysql-connectors-community':
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-connectors-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30026 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-connectors-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30001 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-connectors-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30023 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-connectors-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30006 milliseconds]
Error: Failed to download metadata for repo 'mysql-connectors-community': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
MySQL Tools Community 0.0 B/s | 0 B 08:38
Errors during downloading metadata for repository 'mysql-tools-community':
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30053 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30007 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30000 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-community/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30101 milliseconds]
Error: Failed to download metadata for repo 'mysql-tools-community': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
MySQL Tools Preview 0.0 B/s | 0 B 08:17
Errors during downloading metadata for repository 'mysql-tools-preview':
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-preview/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30004 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-preview/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30000 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-preview/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30027 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-preview/fc/34/x86_64/repodata/repomd.xml [Resolving timed out after 30031 milliseconds]
Error: Failed to download metadata for repo 'mysql-tools-preview': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
MySQL 8.0 Community Server - Source 0.0 B/s | 0 B 08:28
Errors during downloading metadata for repository 'mysql80-community-source':
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30125 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-8.0-community/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30000 milliseconds]
Error: Failed to download metadata for repo 'mysql80-community-source': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
MySQL Connectors Community - Source 0.0 B/s | 0 B 08:44
Errors during downloading metadata for repository 'mysql-connectors-community-source':
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-connectors-community/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30000 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-connectors-community/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30002 milliseconds]
Error: Failed to download metadata for repo 'mysql-connectors-community-source': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
MySQL Tools Community - Source 0.0 B/s | 0 B 08:45
Errors during downloading metadata for repository 'mysql-tools-community-source':
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-community/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30029 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-community/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30084 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-community/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30000 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-community/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30001 milliseconds]
Error: Failed to download metadata for repo 'mysql-tools-community-source': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
MySQL Tools Preview - Source 0.0 B/s | 0 B 08:36
Errors during downloading metadata for repository 'mysql-tools-preview-source':
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-preview/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30007 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-preview/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 32320 milliseconds]
- Curl error (28): Timeout was reached for http://repo.mysql.com/yum/mysql-tools-preview/fc/34/SRPMS/repodata/repomd.xml [Resolving timed out after 30001 milliseconds]
Error: Failed to download metadata for repo 'mysql-tools-preview-source': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
Ignoring repositories: mysql80-community, mysql-connectors-community, mysql-tools-community, mysql-tools-preview, mysql80-community-source, mysql-connectors-community-source, mysql-tools-community-source, mysql-tools-preview-source
Last metadata expiration check: 0:31:20 ago on Sunday 11 July 2021 10:46:17 AM.
No match for argument: mysql-community-server
Error: Unable to find a match: mysql-community-server
[root#fedora ~]#
Installed Repo Package:
[rajiv#fedora yum.repos.d]$ dnf list installed | grep mysql
mysql80-community-release.noarch fc34-1 ##commandline
[rajiv#fedora yum.repos.d]$
RepoList:
[rajiv#fedora ~]$ sudo dnf repolist
[sudo] password for rajiv:
repo id repo name
fedora Fedora 34 - x86_64
fedora-cisco-openh264 Fedora 34 openh264 (From Cisco) - x86_64
fedora-modular Fedora Modular 34 - x86_64
google-chrome google-chrome
mysql-connectors-community MySQL Connectors Community
mysql-connectors-community-source MySQL Connectors Community - Source
mysql-tools-community MySQL Tools Community
mysql-tools-community-source MySQL Tools Community - Source
mysql-tools-preview MySQL Tools Preview
mysql-tools-preview-source MySQL Tools Preview - Source
mysql80-community MySQL 8.0 Community Server
mysql80-community-source MySQL 8.0 Community Server - Source
updates Fedora 34 - x86_64 - Updates
updates-modular Fedora Modular 34 - x86_64 - Updates
Contents of Repo:
[rajiv#fedora yum.repos.d]$ pwd
/etc/yum.repos.d
[rajiv#fedora yum.repos.d]$ ls
_copr_phracek-PyCharm.repo fedora.repo fedora-updates-testing-modular.repo mysql-community.repo rpmfusion-nonfree-steam.repo
fedora-cisco-openh264.repo fedora-updates-modular.repo fedora-updates-testing.repo mysql-community-source.repo
fedora-modular.repo fedora-updates.repo google-chrome.repo rpmfusion-nonfree-nvidia-driver.repo
[rajiv#fedora yum.repos.d]$ tac mysql-community.repo
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
gpgcheck=1
enabled=1
baseurl=http://repo.mysql.com/yum/mysql-tools-preview/fc/$releasever/$basearch/
name=MySQL Tools Preview
[mysql-tools-preview]
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
gpgcheck=1
enabled=1
baseurl=http://repo.mysql.com/yum/mysql-tools-community/fc/$releasever/$basearch/
name=MySQL Tools Community
[mysql-tools-community]
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
gpgcheck=1
enabled=1
baseurl=http://repo.mysql.com/yum/mysql-connectors-community/fc/$releasever/$basearch/
name=MySQL Connectors Community
[mysql-connectors-community]
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
gpgcheck=1
enabled=1
baseurl=http://repo.mysql.com/yum/mysql-8.0-community/fc/$releasever/$basearch/
name=MySQL 8.0 Community Server
[mysql80-community]
[rajiv#fedora yum.repos.d]$ tac mysql-community-source.repo
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
gpgcheck=1
enabled=1
baseurl=http://repo.mysql.com/yum/mysql-tools-preview/fc/$releasever/SRPMS
name=MySQL Tools Preview - Source
[mysql-tools-preview-source]
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
gpgcheck=1
enabled=1
baseurl=http://repo.mysql.com/yum/mysql-tools-community/fc/$releasever/SRPMS
name=MySQL Tools Community - Source
[mysql-tools-community-source]
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
gpgcheck=1
enabled=1
baseurl=http://repo.mysql.com/yum/mysql-connectors-community/fc/$releasever/SRPMS
name=MySQL Connectors Community - Source
[mysql-connectors-community-source]
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-mysql
gpgcheck=1
enabled=1
baseurl=http://repo.mysql.com/yum/mysql-8.0-community/fc/$releasever/SRPMS
name=MySQL 8.0 Community Server - Source
[mysql80-community-source]
[rajiv#fedora yum.repos.d]$
I tried reinstalling the repo package, but it still the same issue. Please advice. Thanks!
After a bit of troubleshooting, following steps has enabled to get the installation right: -
Installation Steps: [Component]-[FileNameReference]
Configuration - mysql-community-common
Client Plugins - mysql-community-client
Shared Library - mysql-community-libs
Development Libraries - mysql-community-devel
Client Utilties - mysql-community-client
MySQL Server - mysql-community-server
Workbench - mysql-community-workbench
I am dealing with the project deposition made on FastAPI to a remote ubuntu server. I'll try to run the project from terminal (using SSH connection) by the command
gunicorn -k uvicorn.workers.UvicornWorker main:app
The output is
gunicorn -k uvicorn.workers.UvicornWorker main:app
[2020-07-14 15:24:28 +0000] [23102] [INFO] Starting gunicorn 20.0.4
[2020-07-14 15:24:28 +0000] [23102] [INFO] Listening at: http://127.0.0.1:8000 (23102)
[2020-07-14 15:24:28 +0000] [23102] [INFO] Using worker: uvicorn.workers.UvicornWorker
[2020-07-14 15:24:28 +0000] [23104] [INFO] Booting worker with pid: 23104
[2020-07-14 15:24:28 +0000] [23104] [INFO] Started server process [23104]
[2020-07-14 15:24:28 +0000] [23104] [INFO] Waiting for application startup.
[2020-07-14 15:24:28 +0000] [23104] [INFO] Application startup complete.
But I need the project to be available at the IP address of the server. If I try smth like
uvicorn main:app --host 66.226.247.55 --port 8000
I get
INFO: Started server process [23308]
INFO: Waiting for application startup.
INFO: Connected to database postgresql://recognition:********#localhost:5432/reco
INFO: Application startup complete.
ERROR: [Errno 99] error while attempting to bind on address ('66.226.247.55', 8000): cannot assign requested address
INFO: Waiting for application shutdown.
INFO: Disconnected from database postgresql://recognition:********#localhost:5432/reco
INFO: Application shutdown complete.
Where 66.226.247.55 - external IP adress from google cloud platform instances
How do I start a project so that it can be accessed via IP?
The --host should be the local address of your GCP server.
uvicorn main:app --host 0.0.0.0 --port 8000
and now access the application by http://66.226.247.55:8000
Note: You should open your 8000 port of GCP server.
If you're using nginx server
create a file in /etc/nginx/sites-enabled/
create file touch fastapi_nginx
copy code into file and adjust accordingly
server{
listen 80;
server_name "your public ip";
location / {
proxy_pass http://127.0.0.1:8000; #localhost
}
}
This should reroute to your public ip
You cannot launch your fast api app on your local to your remote server in GCP.
You must deploy your app to GCP. In other words you need to run that command on a remote server not your localhost.
The app stops and I can't figure out why.
I start the command like this CMD ["pm2-runtime", "main.bundle.js", "--cron", "0 */16 * * *"] (should mean to restar the app every 16 hours)
Then I see the app starting:
15:35:02
2020-01-09T15:35:02: PM2 log: Launching in no daemon mode
15:35:03
2020-01-09T15:35:03: PM2 log: App [main.bundle:0] starting in -fork mode-
15:35:03
2020-01-09T15:35:03: PM2 log: App [main.bundle:0] online
And after half an hour I see that it's stopping the app.
16:05:32
2020-01-09T16:05:32: PM2 log: Stopping app:main.bundle id:0
16:05:32
2020-01-09T16:05:32: PM2 log: App [main.bundle:0] exited with code [0] via signal [SIGINT]
16:05:32
2020-01-09T16:05:32: PM2 log: pid=30 msg=process killed
16:05:32
2020-01-09T16:05:32: PM2 log: PM2 successfully stopped
I see no errors in my app and I can't understnad why it stops.
Another end log:
06:11:52
2020-01-11T06:11:52: PM2 log: Stopping app:main.bundle id:0
06:11:52
2020-01-11T06:11:52: PM2 log: App [main.bundle:0] exited with code [0] via signal [SIGINT]
06:11:52
2020-01-11T06:11:52: PM2 log: pid=16 msg=process killed
06:11:52
2020-01-11T06:11:52: PM2 log: PM2 successfully stopped
I'm deploying my Java8 SpringBoot App to a Google Compute Engine instance and trying to connect it to a Debian9 CloudSQL instance. I'm trying to get the instance to run with my startup-script.sh, but when it tries to boot up the SpringBoot Application, according to the daemon.log, when the .war is ran by "java -jar order-routing-0.0.1-SNAPSHOT.war" the startup fails with a "Unable to obtain connection from database: Communications link failure", with SQL State:08S01 and error code 0.
I mapped the GCE instance to a static external IP, as well as whitelisting that IP on the CloudSQL instance's connections configs. I also verify that the war file runs locally with "java -jar order-routing.war".
Here is my startup script.sh:
#!/usr/bin/env bash
# This script is passed to the GCE instance by the setup script. It is run on the instance when it is spun up.
# Derived from GCE Tutorial at https://cloud.google.com/java/docs/tutorials/bookshelf-on-compute-engine
# [START script]
set -e
set -v
# Talk to the metadata server to get the project id
PROJECTID=$(curl -s "http://metadata.google.internal/computeMetadata/v1/project/project-id" -H "Metadata-Flavor: Google")
BUCKET=$(curl -s "http://metadata.google.internal/computeMetadata/v1/instance/attributes/BUCKET" -H "Metadata-Flavor: Google")
echo "Project ID: ${PROJECTID}"
# get our file(s)
gsutil cp "gs://order-routing-install/gce/"** .
# Install dependencies from apt
apt-get update
apt-get install mysql-client -y
wget https://dl.google.com/cloudsql/cloud_sql_proxy.linux.amd64
mv cloud_sql_proxy.linux.amd64 cloud_sql_proxy
chmod +x cloud_sql_proxy
./cloud_sql_proxy -instances=instance-qa1:us-central1:instance-qa1-cloudsql-0=tcp:3307 &
apt-get install -yq default-jre
apt-get install -yq default-jdk
java -jar order-routing-0.0.1-SNAPSHOT.war
# [END script]
Here is the failing error log from the daemon.log:
ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'flywayInitializer' defined in class path resource [org/springframework/boot/autoconfigure/flyway/FlywayAutoConfiguration$FlywayConfiguration.class]: Invocation of init method failed; nested exception is org.flywaydb.core.internal.exception.FlywaySqlException:
Jul 29 03:39:30 order-routing-group-hk66 startup-script: INFO startup-script: Unable to obtain connection from database: Communications link failure
Jul 29 03:39:30 order-routing-group-hk66 startup-script: INFO startup-script: 2019-07-29 03:39:30.435 INFO 9051 --- [ main] ConditionEvaluationReportLoggingListener :
Jul 29 03:39:30 order-routing-group-hk66 startup-script: INFO startup-script:n from database: Communications link failure
Jul 29 03:39:30 order-routing-group-hk66 startup-script: INFO startup-script: The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
Jul 29 03:39:30 order-routing-group-hk66 startup-script: INFO startup-script: SQL State : 08S01
Jul 29 03:39:30 order-routing-group-hk66 startup-script: INFO startup-script: Error Code : 0
Jul 29 03:39:30 order-routing-group-hk66 startup-script: INFO startup-script: Message : Communications link failure
Expected Result:
The GCE instance starts up the war file successfully and I can access my app using the external IP.
Actual Result:
Getting CommunicationsLinkFailures upon starting up Spring Boot Java app.
I am getting the error:
"org.openqa.selenium.WebDriverException: Timed out waiting for driver server to start"
when I am running the test suite on the Bamboo server. The code is working fine locally when I run the suite via Eclipse - Maven or cucumber runner.
I have configured my Virtual desktop as my local remote agent for bamboo.
please find more information below:
JDK - jdk1.8.0_161
Chrome : tried both 71.0.3578.80 & 74.0.3729.131
Chrome Driver: tried with v2.46 and v74
Selenium-java: 3.14
Driver Initialization:
System.setProperty("webdriver.chrome.driver","src/test/resources/Drivers/chromedriver.exe");
WebDriver driver= new ChromeDriver();
Bamboo Log excerpt:
error 08-May-2019 08:11:14 Starting ChromeDriver 2.46.628402 (536cd7adbad73a3783fdc2cab92ab2ba7ec361e1) on port 5501
error 08-May-2019 08:11:14 Only local connections are allowed.
error 08-May-2019 08:11:14 Please protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code.
error 08-May-2019 08:11:16 May 08, 2019 2:11:16 PM org.openqa.selenium.remote.DesiredCapabilities chrome
error 08-May-2019 08:11:16 INFO: Using new ChromeOptions() is preferred to DesiredCapabilities.chrome()
error 08-May-2019 08:11:19 Starting ChromeDriver 71.0.3578.137 (86ee722808adfe9e3c92e6e8ea746ade08423c7e) on port 3798
error 08-May-2019 08:11:19 Only local connections are allowed.
error 08-May-2019 08:11:19 Please protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code.
error 08-May-2019 08:11:19 Failed to redirect stderr to log file.
error 08-May-2019 08:11:19 Unable to initialize logging. Exiting...
error 08-May-2019 08:11:37 May 08, 2019 2:11:37 PM org.openqa.selenium.os.OsProcess checkForError
error 08-May-2019 08:11:37 SEVERE: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
build 08-May-2019 08:11:37 Failure in before hook:Hooks.BrowserInit(Scenario)
build 08-May-2019 08:11:37 Message: org.openqa.selenium.WebDriverException: Timed out waiting for driver server to start.
build 08-May-2019 08:11:37 Build info: version: '3.14.0', revision: 'aacccce0', time: '2018-08-02T20:19:58.91Z'
build 08-May-2019 08:11:37 System info: host: 'XXXXXX', ip: 'Machine IP', os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.8.0_161'
build 08-May-2019 08:11:37 Driver info: driver.version: ChromeDriver
build 08-May-2019 08:11:37 at org.openqa.selenium.remote.service.DriverService.waitUntilAvailable(DriverService.java:193)
build 08-May-2019 08:11:37 at org.openqa.selenium.remote.service.DriverService.start(DriverService.java:179)
build 08-May-2019 08:11:37 at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:79)
build 08-May-2019 08:11:37 at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:548)
build 08-May-2019 08:11:37 at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:212)
build 08-May-2019 08:11:37 at org.openqa.selenium.remote.RemoteWebDriver.(RemoteWebDriver.java:130)
build 08-May-2019 08:11:37 at org.openqa.selenium.chrome.ChromeDriver.(ChromeDriver.java:181)
build 08-May-2019 08:11:37 at org.openqa.selenium.chrome.ChromeDriver.(ChromeDriver.java:168)
build 08-May-2019 08:11:37 at org.openqa.selenium.chrome.ChromeDriver.(ChromeDriver.java:123)
I have already checked this solution and its all correct in my case.