When logging in to Enterprise Server, the following error can sometimes appear:
Database error (S1004)
This can have different causes, each with their own solution.
Scenario 1: The issue occurred after some videos got interrupted
Restarting the database server has been known to resolve this.
Scenario 2: MYSQL was not sufficiently optimized for productivity and memory usage
The following settings of the my.cnf file have been known to resolve the issue:
Note: The system on which this was implemented had 25Gb of physical RAM.
key_buffer_size=256M max_allowed_packet=4M innodb_buffer_pool_size=2048M innodb_log_file_size=250M innodb_log_buffer_size=16M innodb_additional_mem_pool_size=200M tmp_table_size=256M innodb_flush_log_at_trx_commit=0 table_cache=1024 thread_cache_size=16 thread_concurrency=8 myisam_sort_buffer_size=64M
Do you have corrections or additional information about this article? Leave a comment! Do you have a question about what is described in this article? Please contact Support.
Please sign in to leave a comment.