Service Unavailable after update

Support
21

Hi Sam,
Sorry to say, this hasn’t worked for me.
The frontend seems to work fine on a brand new site, I can get to the admin login, but then I encounter 502 afterwards.

If I manually input the admin url:
http://localhost:10004/wp-admin/about.php
I can get to this screen, however, any other screens such as plugin.php, or appearance.php all return 502.

error.log (3.1 KB)
local-lightning.log (254.7 KB)

The contents of local-lightning.log are littered with the following errors:

{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2022-12-12T11:32:03.392463Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35","timestamp":"2022-12-12T11:32:04.399Z"}
{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2022-12-12T11:32:04.392618Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 35","timestamp":"2022-12-12T11:32:04.399Z"}
{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2022-12-12T11:32:04.394805Z 1 [ERROR] [MY-012592] [InnoDB] Operating system error number 35 in a file operation.","timestamp":"2022-12-12T11:32:04.703Z"}
{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2022-12-12T11:32:04.394837Z 1 [ERROR] [MY-012596] [InnoDB] Error number 35 means 'Resource temporarily unavailable'","timestamp":"2022-12-12T11:32:04.704Z"}
{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2022-12-12T11:32:04.394868Z 1 [ERROR] [MY-012215] [InnoDB] Cannot open datafile './ibdata1'","timestamp":"2022-12-12T11:32:04.704Z"}
{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2022-12-12T11:32:04.394908Z 1 [ERROR] [MY-012959] [InnoDB] Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!","timestamp":"2022-12-12T11:32:04.706Z"}
{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2022-12-12T11:32:04.394931Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Cannot open a file.","timestamp":"2022-12-12T11:32:04.706Z"}
{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2022-12-12T11:32:04.701323Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine","timestamp":"2022-12-12T11:32:04.707Z"}
{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2022-12-12T11:32:04.701545Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.","timestamp":"2022-12-12T11:32:04.707Z"}
{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2022-12-12T11:32:04.702975Z 0 [ERROR] [MY-010119] [Server] Aborting","timestamp":"2022-12-12T11:32:04.709Z"}
{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2022-12-12T11:32:04.705708Z 0 [System] [MY-010910] [Server] %%resourcesPath%%/lightning-services/mysql-8.0.16+6/bin/darwin/bin/mysqld: Shutdown complete (mysqld 8.0.16)  MySQL Community Server - GPL.","timestamp":"2022-12-12T11:32:04.710Z"}
{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2022-12-12T11:32:05.372233Z 0 [System] [MY-010116] [Server] %%resourcesPath%%/lightning-services/mysql-8.0.16+6/bin/darwin/bin/mysqld (mysqld 8.0.16) starting as process 4092","timestamp":"2022-12-12T11:33:05.545Z"}
{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2022-12-12T11:32:05.376132Z 0 [Warning] [MY-013243] [Server] --character-set-server: The character set UTF8MB3 is deprecated and will be removed in a future release. Please consider using UTF8MB4 instead.","timestamp":"2022-12-12T11:33:05.545Z"}
{"thread":"main","class":"Process","process":"mysql","level":"warn","message":"2022-12-12T11:32:05.377052Z 0 [Warning] [MY-010159] [Server] Setting lower_case_table_names=2 because file system for %%site.runData%%/mysql/data/ is case insensitive","timestamp":"2022-12-12T11:33:05.546Z"}
22

this is a true mess.
no idea or logic to it.
the updates simple dont work and the only way i can use the sites is using php7.3.5
bad bad work and shoddy app updates
very sad cant use anymore

23

Same issue here!
This community is full of threads like this but nothing happened.
I think it’s better not to work with this app. What a pity.

24

@meisterleise What OS version are you on? For @bomakalu and others in this thread, the issue is likely related to OS versions that have reached their end of life. Because of this newer PHP versions won’t work in Local past 7.3.5 if your OS is Mojave or further back. More details below here:

You can find older Local releases here: Releases - Local

You can find out if your MacOS has reached it’s end of life here: Apple macOS | endoflife.date

25

I’m on macOS X.14.6. local 6.4.2 works fine. local 6.6.1 is corrupt.

26

Hi @meisterleise Thanks for confirming. Per my details above, your OS will fall under those that will run into this issue. At a future point if you’re able to update your OS you should be able to resume normal Local updates and utilize the latest versions of PHP. For now, you’ll have to rely on that older release.

1 Like
27

Yes, it seems so. Sadly I lost all my WP installations with this update. I’d recommend to communicate system requirements for LOCAL. I couldn’t find any.

28

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.