Skip to main content
added 19 characters in body
Source Link
zedmelon
  • 155
  • 10

thanks for reading.

thanks for reading.

deleted 243 characters in body
Source Link
Rui F Ribeiro
  • 58k
  • 28
  • 156
  • 238

...so I know the executable can run, and the databases are at least somewhat valid (the sites all appear normal). Am I missing something dumb?

I tried trimming this post to relevant info--glad to post the entire (cfg|log) where useful.

Thanks for reading

If this post should be moved to another Stack Exchange (ServerFault?) I apologize--and mods feel free to correct it.

...so I know the executable can run, and the databases are at least somewhat valid (the sites all appear normal). Am I missing something dumb?

I tried trimming this post to relevant info--glad to post the entire (cfg|log) where useful.

Thanks for reading

If this post should be moved to another Stack Exchange (ServerFault?) I apologize--and mods feel free to correct it.

...so I know the executable can run, and the databases are at least somewhat valid (the sites all appear normal). Am I missing something?

long post, offering a shortcut to the true answer--anyone bored enough is still welcome to read the entire thing :-)
Source Link
zedmelon
  • 155
  • 10

UPDATE: I now know my issue was database corruption, but discerning it was somewhat tricky--apparmor appeared to be the cause for longer than it should've.

I didn't note when first posting that even after putting mysql in complain mode and sending apparmor both stop and teardown commands my syslog still showed the apparmor message...feeding my irrational fear of the protection layer--still not sure how this happened. I finally got mysql separated from apparmor, but it still couldn't lock its own files. Ergo database corruption--dang. My backups worked fine on a new server.

INITIAL POST:

Mysql server is being blocked by (I think) apparmor, but I'm at wits' end to determine why/how. I'm not overly familiar with apparmor.

Mysql server is being blocked by (I think) apparmor, but I'm at wits' end to determine why/how. I'm not overly familiar with apparmor.

UPDATE: I now know my issue was database corruption, but discerning it was somewhat tricky--apparmor appeared to be the cause for longer than it should've.

I didn't note when first posting that even after putting mysql in complain mode and sending apparmor both stop and teardown commands my syslog still showed the apparmor message...feeding my irrational fear of the protection layer--still not sure how this happened. I finally got mysql separated from apparmor, but it still couldn't lock its own files. Ergo database corruption--dang. My backups worked fine on a new server.

INITIAL POST:

Mysql server is being blocked by (I think) apparmor, but I'm at wits' end to determine why/how. I'm not overly familiar with apparmor.

correcting a hastily-made copy/paste error
Source Link
zedmelon
  • 155
  • 10
Loading
Source Link
zedmelon
  • 155
  • 10
Loading