kicked out of the program and gives an error
Uncaught ConnectionManager_Exception: Cannot connect to database: Connection refused in /var/www/boxbeehappyodua/web1/web/packages/ConnectionManager/ConnectionManager_MySQLi...
Probably running out of disk space
-------------------------------------------------- -------------------------------------------------- ---
We have space on our server. What happened to 1box?
Original question is available on version: ru
Probably running out of disk space
-------------------------------------------------- -------------------------------------------------- ---
We have space on our server. What happened to 1box?
Answers:
Good evening.
On 11/22/2020 at 21:40 the server was overloaded:
Nov 22 21:40:01 box systemd: Started Session 144834 of user root.
Nov 22 21:44:54 box journal: Runtime journal is using 8.0M (max allowed 72.0M, trying to leave 108.0M free of 712.1M available → current limit 72.0M).
Nov 22 21:44:54 box kernel: Initializing cgroup subsys cpuset
Nov 22 21:44:54 box kernel: Initializing cgroup subsys cpu
...
After the reboot, the database did not rise, errors appeared:
Nov 22 21:45:19 box mysqld: 2020-11-22 21:45:19 140501749160128 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
There may be a problem with the hardware of the server.
On 11/22/2020 at 21:40 the server was overloaded:
Nov 22 21:40:01 box systemd: Started Session 144834 of user root.
Nov 22 21:44:54 box journal: Runtime journal is using 8.0M (max allowed 72.0M, trying to leave 108.0M free of 712.1M available → current limit 72.0M).
Nov 22 21:44:54 box kernel: Initializing cgroup subsys cpuset
Nov 22 21:44:54 box kernel: Initializing cgroup subsys cpu
...
After the reboot, the database did not rise, errors appeared:
Nov 22 21:45:19 box mysqld: 2020-11-22 21:45:19 140501749160128 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
There may be a problem with the hardware of the server.
25.11.2020, 22:10
Original comment available on version: ru
Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter.
Log in and comment
Copyright © OneBox 2024
