- 전체
- 게임 일반 (make game basics)
- 모바일 기획 및 디자인
- GameMaker Studio
- Unity3D
- Cocos2D
- 3D Engine OGRE
- 3D Engine irrlicht
- copperCube
- corona SDK
- Windows Basic Game
- BaaS (Mobile Backend)
- phnegap & cordova
- ionic & anguler
- parse (backend)
- firebase (backend)
- Game Backend Server / Opt
- web assembly
- Smart Makers
- pyGame & Ren'Py
- 머드(MUD) 게임 만들기
- Xamarin(자마린)
- flutter (플루터 앱 개발)
- construct 2 / 3
- pocketbase
- RPG Maker 시리즈
- godot engine
- playmaker(unity)
- react native
Minecraft : multicaft server 로그인시 500 database 에러시
| delete /opt/bitnami/mysql/data/tc.log |
I'm using the Bitnami Multicraft pre-built virtual machine image on Microsoft Azure. Recently after a server shutdown/restart, I can no longer login to the Multicraft dashboard.
The error is:
Error 500
Failed to connect to the panel database.
The error message is: CDbConnection failed to open the DB connection.
Please run the control panel installer to fix this issue.
When I slick the link for "run the control panel installer" it simply returns me to the login screen. I'm pretty unhappy about this as Azure is billed by time, so I'm paying for a server that I cannot use. Please advise.
-
created
May 30 -
last reply
May 30 - 4
replies
- 323
views
- 2
users
- 1
like
- 2
links
-
Hi @rich_h,
I am so sorry to hear that. Your issue is related to the fact that your database server is not running. For some reason, it was not properly initiated after your server restart. Could you please access over SSH to your VM and execute the following command?
sudo /opt/bitnami/ctlscript.sh restart mysql
The following document will help you accessing through SSH in case you are not sure about how to proceed:
https://docs.bitnami.com/azure/faq/#how-to-connect-to-the-server-through-ssh
If you the script above fails, please, execute:
sudo cat opt/bitnami/mysql/data/mysqld.log
and look for errors.
We’ll be looking forward to receiving your reply.
Best regards,
David González
Thanks for getting back to me. I tried to execute the command in your reply, and it failed with:
/opt/bitnami/mysql/scripts/ctl.sh : mysql could not be started
Here is the full log from the point where the command was executed:
170530 08:41:48 mysqld_safe Starting mysqld daemon with databases from /opt/bitnami/mysql/data
2017-05-30 8:41:49 140560746391488 [Note] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 10.1.21-MariaDB) starting as process 1493 ...
2017-05-30 8:41:49 140560746391488 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-30 8:41:49 140560746391488 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-30 8:41:49 140560746391488 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-05-30 8:41:49 140560746391488 [Note] InnoDB: GCC builtin _syncsynchronize() is used for memory barrier
2017-05-30 8:41:49 140560746391488 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-30 8:41:49 140560746391488 [Note] InnoDB: Using Linux native AIO
2017-05-30 8:41:49 140560746391488 [Note] InnoDB: Using SSE crc32 instructions
2017-05-30 8:41:49 140560746391488 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2017-05-30 8:41:49 140560746391488 [Note] InnoDB: Completed initialization of buffer pool
2017-05-30 8:41:49 140560746391488 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-30 8:41:50 140560746391488 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-30 8:41:50 140560746391488 [Note] InnoDB: Waiting for purge to start
2017-05-30 8:41:50 140560746391488 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 32270319
2017-05-30 8:41:50 140559775663872 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-05-30 8:41:50 140560746391488 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-30 8:41:50 140560746391488 [Note] Recovering after a crash using tc.log
2017-05-30 8:41:50 140560746391488 [ERROR] Can't init tc log
2017-05-30 8:41:50 140560746391488 [ERROR] Aborting
170530 08:41:53 mysqld_safe mysqld from pid file /opt/bitnami/mysql/data/mysqld.pid ended
170530 08:44:15 mysqld_safe Starting mysqld daemon with databases from /opt/bitnami/mysql/data
2017-05-30 8:44:15 140538338940864 [Note] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 10.1.21-MariaDB) starting as process 2574 ...
2017-05-30 8:44:15 140538338940864 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-30 8:44:15 140538338940864 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-30 8:44:15 140538338940864 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-05-30 8:44:15 140538338940864 [Note] InnoDB: GCC builtin _syncsynchronize() is used for memory barrier
2017-05-30 8:44:15 140538338940864 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-30 8:44:15 140538338940864 [Note] InnoDB: Using Linux native AIO
2017-05-30 8:44:15 140538338940864 [Note] InnoDB: Using SSE crc32 instructions
2017-05-30 8:44:15 140538338940864 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2017-05-30 8:44:15 140538338940864 [Note] InnoDB: Completed initialization of buffer pool
2017-05-30 8:44:15 140538338940864 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-30 8:44:15 140538338940864 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-30 8:44:15 140538338940864 [Note] InnoDB: Waiting for purge to start
2017-05-30 8:44:15 140538338940864 [Note] InnoDB: Percona XtraDB (edited) 5.6.34-79.1 started; log sequence number 32270329
2017-05-30 8:44:15 140538338940864 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-30 8:44:15 140538338940864 [Note] Recovering after a crash using tc.log
2017-05-30 8:44:15 140538338940864 [ERROR] Can't init tc log
2017-05-30 8:44:15 140538338940864 [ERROR] Aborting
170530 08:44:18 mysqld_safe mysqld from pid file /opt/bitnami/mysql/data/mysqld.pid ended
170530 08:44:32 mysqld_safe Starting mysqld daemon with databases from /opt/bitnami/mysql/data
2017-05-30 8:44:33 140458972809152 [Note] /opt/bitnami/mysql/bin/mysqld.bin (mysqld 10.1.21-MariaDB) starting as process 2811 ...
2017-05-30 8:44:33 140458972809152 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-05-30 8:44:33 140458972809152 [Note] InnoDB: The InnoDB memory heap is disabled
2017-05-30 8:44:33 140458972809152 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-05-30 8:44:33 140458972809152 [Note] InnoDB: GCC builtin _syncsynchronize() is used for memory barrier
2017-05-30 8:44:33 140458972809152 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-05-30 8:44:33 140458972809152 [Note] InnoDB: Using Linux native AIO
2017-05-30 8:44:33 140458972809152 [Note] InnoDB: Using SSE crc32 instructions
2017-05-30 8:44:33 140458972809152 [Note] InnoDB: Initializing buffer pool, size = 256.0M
2017-05-30 8:44:33 140458972809152 [Note] InnoDB: Completed initialization of buffer pool
2017-05-30 8:44:33 140458972809152 [Note] InnoDB: Highest supported file format is Barracuda.
2017-05-30 8:44:33 140458972809152 [Note] InnoDB: 128 rollback segment(s) are active.
2017-05-30 8:44:33 140458972809152 [Note] InnoDB: Waiting for purge to start
2017-05-30 8:44:33 140458972809152 [Note] InnoDB: Percona XtraDB (edited) 5.6.34-79.1 started; log sequence number 32270355
2017-05-30 8:44:33 140458972809152 [Note] Plugin 'FEEDBACK' is disabled.
2017-05-30 8:44:33 140458972809152 [Note] Recovering after a crash using tc.log
2017-05-30 8:44:33 140458972809152 [ERROR] Can't init tc log
2017-05-30 8:44:33 140458972809152 [ERROR] Aborting
So, after some googling it appears that if you delete /opt/bitnami/mysql/data/tc.log it solves the issue.
I renamed it, and restarted mysql as suggested in the first reply. The control panel is working again.
Thanks for your help. It got me to the right place.
Hi again @rich_h!
Thank you for posting the solution! The tc.log file sometimes gets corrupted when the machine is not properly shut down, so mysql is unable to get back up unless such corruption is deleted. We'll see how can we improve that.
If you even run into any other issue, please, do not hesitate to come back for help. We'll be more than glad to help you!
Best regards,
David González
[출처] https://community.bitnami.com/t/multicraft-error-500/49543광고 클릭에서 발생하는 수익금은 모두 웹사이트 서버의 유지 및 관리, 그리고 기술 콘텐츠 향상을 위해 쓰여집니다.