Since Update: All new sites error with 502 code


#1

Here are the error logs:

2019-01-05T03:45:42.040513Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).

2019-01-05T03:45:42.040730Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.23) starting as process 80 …

2019-01-05T03:45:42.054425Z 0 [Note] InnoDB: PUNCH HOLE support available

2019-01-05T03:45:42.054442Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2019-01-05T03:45:42.054445Z 0 [Note] InnoDB: Uses event mutexes

2019-01-05T03:45:42.054448Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier

2019-01-05T03:45:42.054450Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3

2019-01-05T03:45:42.054452Z 0 [Note] InnoDB: Using Linux native AIO

2019-01-05T03:45:42.054594Z 0 [Note] InnoDB: Number of pools: 1

2019-01-05T03:45:42.054721Z 0 [Note] InnoDB: Using CPU crc32 instructions

2019-01-05T03:45:42.055871Z 0 [Note] InnoDB: Initializing buffer pool, total size = 32M, instances = 1, chunk size = 32M

2019-01-05T03:45:42.057327Z 0 [Note] InnoDB: Completed initialization of buffer pool

2019-01-05T03:45:42.062944Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

2019-01-05T03:45:42.070023Z 0 [Note] InnoDB: Highest supported file format is Barracuda.

2019-01-05T03:45:42.070363Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 3381120

2019-01-05T03:45:42.070372Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 3381444

2019-01-05T03:45:42.070481Z 0 [Note] InnoDB: Database was not shutdown normally!

2019-01-05T03:45:42.070486Z 0 [Note] InnoDB: Starting crash recovery.

2019-01-05T03:45:42.088277Z 0 [Note] InnoDB: Starting an apply batch of log records to the database…

InnoDB: Progress in percent: 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99

2019-01-05T03:45:42.089353Z 0 [Note] InnoDB: Apply batch completed

2019-01-05T03:45:42.191646Z 0 [Note] InnoDB: Removed temporary tablespace data file: “ibtmp1”

2019-01-05T03:45:42.191689Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables

2019-01-05T03:45:42.191728Z 0 [Note] InnoDB: Setting file ‘./ibtmp1’ size to 12 MB. Physically writing the file full; Please wait …

2019-01-05T03:45:42.211052Z 0 [Note] InnoDB: File ‘./ibtmp1’ size is now 12 MB.

2019-01-05T03:45:42.211491Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.

2019-01-05T03:45:42.211497Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.

2019-01-05T03:45:42.211815Z 0 [Note] InnoDB: Waiting for purge to start

2019-01-05T03:45:42.263121Z 0 [Note] InnoDB: 5.7.23 started; log sequence number 3381444

2019-01-05T03:45:42.263378Z 0 [Note] Plugin ‘FEDERATED’ is disabled.

2019-01-05T03:45:42.264074Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key

2019-01-05T03:45:42.264083Z 0 [Note] Server hostname (bind-address): ‘*’; port: 3306

2019-01-05T03:45:42.264112Z 0 [Note] IPv6 is available.

2019-01-05T03:45:42.264119Z 0 [Note] - ‘::’ resolves to ‘::’;

2019-01-05T03:45:42.264123Z 0 [Note] Server socket created on IP: ‘::’.

2019-01-05T03:45:42.265376Z 0 [Warning] Insecure configuration for --pid-file: Location ‘/var/run/mysqld’ in the path is accessible to all OS users. Consider choosing a different directory.

2019-01-05T03:45:42.266214Z 0 [Warning] ‘user’ entry ‘root@localhost’ ignored in --skip-name-resolve mode.

2019-01-05T03:45:42.266235Z 0 [Warning] ‘user’ entry ‘mysql.session@localhost’ ignored in --skip-name-resolve mode.

2019-01-05T03:45:42.266241Z 0 [Warning] ‘user’ entry ‘mysql.sys@localhost’ ignored in --skip-name-resolve mode.

2019-01-05T03:45:42.266254Z 0 [Warning] ‘db’ entry ‘performance_schema mysql.session@localhost’ ignored in --skip-name-resolve mode.

2019-01-05T03:45:42.266259Z 0 [Warning] ‘db’ entry ‘sys mysql.sys@localhost’ ignored in --skip-name-resolve mode.

2019-01-05T03:45:42.266266Z 0 [Warning] ‘proxies_priv’ entry ‘@ root@localhost’ ignored in --skip-name-resolve mode.

2019-01-05T03:45:42.267142Z 0 [Warning] ‘tables_priv’ entry ‘user mysql.session@localhost’ ignored in --skip-name-resolve mode.

2019-01-05T03:45:42.267152Z 0 [Warning] ‘tables_priv’ entry ‘sys_config mysql.sys@localhost’ ignored in --skip-name-resolve mode.

2019-01-05T03:45:42.273961Z 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool

2019-01-05T03:45:42.282445Z 0 [Note] InnoDB: Buffer pool(s) load completed at 190105 3:45:42

2019-01-05T03:45:42.282574Z 0 [Note] Event Scheduler: Loaded 0 events

2019-01-05T03:45:42.282869Z 0 [Note] /usr/sbin/mysqld: ready for connections.

Version: ‘5.7.23’ socket: ‘/var/run/mysqld/mysqld.sock’ port: 3306 MySQL Community Server (GPL)

Any insight?


#2

Look guys, I’m willing to pay for support…but a week and no response? What’s going on here? -Rich


#3

I get the same error. Try refreshing the browser several times ,works for me.


#4

Yup, I know the refresh game you’re talking about. This is something different. It never resolves, no matter how many times I refresh. It’s a different error than I’m used to seeing when that trick works.

Logs are above