Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PHP Fatal error: Uncaught mysqli_sql_exception: MySQL server has gone away #525

Open
s-maisch opened this issue Dec 30, 2023 · 3 comments
Open

Comments

@s-maisch
Copy link

Hello,

i have reinstalled the site, and recovered the Database, the site are working , but the encoder ist greyed.

The Log says :

[30-Dec-2023 01:33:22 UTC] PHP Fatal error:  Uncaught mysqli_sql_exception: MySQL server has gone away in /var/www/AVideo/upload/objects/Streamer.php:26
Stack trace:
#0 /var/www/AVideo/upload/objects/Streamer.php(26): mysqli->query()
#1 /var/www/AVideo/upload/objects/Streamer.php(68): Streamer::get()
#2 /var/www/AVideo/upload/objects/Login.php(108): Streamer::createIfNotExists()
#3 /var/www/AVideo/upload/objects/login.json.php(15): Login::run()
#4 {main}
  thrown in /var/www/AVideo/upload/objects/Streamer.php on line 26

The MySQL server log :

2023-12-30T01:33:12.614520Z 777 [ERROR] [MY-013183] [InnoDB] Assertion failure: pars0pars.cc:733:sym_node->table != nullptr thread 140279874106944
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2023-12-30T01:33:12Z UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=73915b0bb061f1c7958738d6bcc1903b5a2e0aac
Thread pointer: 0x7f9508029400
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7f957410ac40 thread_stack 0x100000

what is that :-(

@DanielnetoDotCom
Copy link
Member

Looks like a corrupted table. I have no idea how to recover.

but if the issue is with the encoder, you should just reinstall it from scratch.

@s-maisch
Copy link
Author

I completely reinstalled the encoder. Can I also reinstall the site and use the data from the existing database so that I can take over video files etc.

@s-maisch
Copy link
Author

I found the error, there was a user table in the main database. I downloaded the entire database as SQL. repaired the user table, changed the database name and imported it again. I then changed the database to the new one in the configuration file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants