i can get mysql. is anyone able to point me in the right place to get it back working? can i just delete mysql from the panel and reinstall it to get it working? and yes i have backups of the database.
Thanks,
Goat

2020-05-31T05:41:49.604486Z 0 [Warning] option 'max_allowed_packet': unsigned value 107374182400 adjusted to 1073741824
2020-05-31T05:41:49.604637Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2020-05-31T05:41:49.604643Z 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2020-05-31T05:41:49.604675Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2020-05-31T05:41:49.604702Z 0 [Note] /www/server/mysql/bin/mysqld (mysqld 5.7.30-log) starting as process 25649 ...
2020-05-31T05:41:49.616748Z 0 [Note] InnoDB: PUNCH HOLE support available
2020-05-31T05:41:49.616795Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-05-31T05:41:49.616802Z 0 [Note] InnoDB: Uses event mutexes
2020-05-31T05:41:49.616812Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2020-05-31T05:41:49.616818Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-05-31T05:41:49.617266Z 0 [Note] InnoDB: Number of pools: 1
2020-05-31T05:41:49.617409Z 0 [Note] InnoDB: Using CPU crc32 instructions
2020-05-31T05:41:49.618654Z 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2020-05-31T05:41:49.637998Z 0 [Note] InnoDB: Completed initialization of buffer pool
2020-05-31T05:41:49.642126Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-05-31T05:41:49.654131Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2020-05-31T05:41:49.657245Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 254600555560
2020-05-31T05:41:49.657264Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 254600555569
2020-05-31T05:41:49.657272Z 0 [Note] InnoDB: Database was not shutdown normally!
2020-05-31T05:41:49.657278Z 0 [Note] InnoDB: Starting crash recovery.
2020-05-31T05:41:49.668361Z 0 [Note] InnoDB: Last MySQL binlog file position 0 14936281, file name mysql-bin.000328
2020-05-31T05:41:49.785022Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2020-05-31T05:41:49.785053Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-05-31T05:41:49.785110Z 0 [Note] InnoDB: Setting file '/www/server/data/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-05-31T05:41:49.848971Z 0 [Note] InnoDB: File '/www/server/data/ibtmp1' size is now 12 MB.
2020-05-31T05:41:49.849971Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2020-05-31T05:41:49.849987Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2020-05-31T05:41:49.850329Z 0 [Note] InnoDB: Waiting for purge to start
2020-05-31T05:41:49.851124Z 0 [ERROR] InnoDB: Page [page id: space=43, page number=4] log sequence number 254601082931 is in the future! Current system log sequence number 254600555588.
2020-05-31T05:41:49.851147Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2020-05-31T05:41:49.851197Z 0 [ERROR] InnoDB: Page [page id: space=43, page number=3] log sequence number 254601082849 is in the future! Current system log sequence number 254600555588.
2020-05-31T05:41:49.851208Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2020-05-31T05:41:49.851335Z 0 [ERROR] InnoDB: Page [page id: space=14, page number=7] log sequence number 254600571887 is in the future! Current system log sequence number 254600555588.
2020-05-31T05:41:49.851348Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2020-05-31T05:41:49.851496Z 0 [ERROR] InnoDB: Page [page id: space=13, page number=4] log sequence number 254600569214 is in the future! Current system log sequence number 254600555588.
2020-05-31T05:41:49.851509Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2020-05-31T05:41:49.852072Z 0 [ERROR] InnoDB: Page [page id: space=43, page number=2] log sequence number 254601082849 is in the future! Current system log sequence number 254600555588.
2020-05-31T05:41:49.852089Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2020-05-31T05:41:49.852116Z 0 [ERROR] InnoDB: Page [page id: space=43, page number=0] log sequence number 254601082849 is in the future! Current system log sequence number 254600555588.
2020-05-31T05:41:49.852128Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
InnoDB: Dump of the tablespace extent descriptor: len 40; hex 00000000000000020000000000ee0000000001de00000001ffffffffffffffffffffffffffffffff; asc ;2020-05-31T05:41:49.852351Z 0 [ERROR] InnoDB: InnoDB is trying to free page [page id: space=43, page number=601] though it is already marked as free in the tablespace! The tablespace free space info is corrupt. You may need to dump your tables and recreate the whole database!
2020-05-31T05:41:49.852361Z 0 [ERROR] [FATAL] InnoDB: Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2020-05-31 01:41:49 0x2b9f17eed700 InnoDB: Assertion failure in thread 47962301323008 in file ut0ut.cc line 918
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/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
05:41:49 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=67108864
read_buffer_size=1048576
max_used_connections=0
max_threads=500
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1096227 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x2b9f400008c0
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 = 2b9f17eecdd0 thread_stack 0x40000
/www/server/mysql/bin/mysqld(my_print_stacktrace+0x3b)[0xe7e9ab]
/www/server/mysql/bin/mysqld(handle_fatal_signal+0x36f)[0x76623f]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x2b9ef1c64390]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x2b9ef2746428]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x2b9ef274802a]
/www/server/mysql/bin/mysqld[0x73b7eb]
/www/server/mysql/bin/mysqld(ZN2ib5fatalD1Ev+0x61)[0x11274a1]
/www/server/mysql/bin/mysqld[0x11e83b9]
/www/server/mysql/bin/mysqld(Z14fseg_free_pagePhmmbP5mtr_t+0x15b)[0x11e99bb]
/www/server/mysql/bin/mysqld(Z32btr_free_externally_stored_fieldP12dict_index_tPhPKhPKmP14page_zip_des_tmbP5mtr_t+0x40e)[0x114896e]
/www/server/mysql/bin/mysqld[0x108f125]
/www/server/mysql/bin/mysqld(Z14row_purge_stepP9que_thr_t+0xa2e)[0x10900ae]
/www/server/mysql/bin/mysqld(_Z15que_run_threadsP9que_thr_t+0xa35)[0x103df55]
/www/server/mysql/bin/mysqld(srv_worker_thread+0x2d7)[0x10c7df7]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba)[0x2b9ef1c5a6ba]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2b9ef281841d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 0
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.