gmccall13

Members
  • Posts

    4
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

gmccall13's Achievements

Noob

Noob (1/14)

1

Reputation

  1. I'm also experiencing the same 503 error after my docker container auto-updated.
  2. Edit: I fixed the issue by deleting the mariaDB appdata directory and re-installing. Good evening, I'm having a bit of an issue with my new docker install of mariaDB. I just set the password and then started the docker container, and when I send the command: mysql -uroot -p and then type in my password all I get back is: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES) Within the docker container logs this is what I am seeing: _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30_config: executing... [cont-init.d] 30_config: exited 0. [cont-init.d] 40-initialise-db: executing... [cont-init.d] 40-initialise-db: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 181004 19:03:40 mysqld_safe Logging to syslog. 181004 19:03:40 mysqld_safe Starting mysqld daemon with databases from /config/databases I noticed that the advice to one poster was to view the first post and perform the steps there and as I don't have a backup because this is a new install I just performed the following: docker exec -it mariadb bash mv /config/log/ /config/log-old/ exit docker restart mariadb However I am still getting the same results. I have copied and pasted the password directly from the docker editing page, typed it in manually and still I get the same message. Am I missing something really simple here? Thank you in advance for your help
  3. Wow, I should have know. Thank you for your help! I will start there now.
  4. Good evening all, I received this massage from my unRAID server yesterday and I'm not honestly sure what to make of it: Your server has issued one or more call traces. This could be caused by a Kernel Issue, Bad Memory, etc. You should post your diagnostics and ask for assistance on the unRaid forums. So that's what I'm doing here I hope that you fine people will be able to assist me, I have attached my diagnostics as well. I should also probably note that I found this while I was combing through the syslog: Several of these: unRAID kernel: BTRFS critical (device md4): corrupt node, bad key order: block=132448256, root=1, slot=1 and a couple of these: unRAID kernel: BTRFS critical (device md4): corrupt leaf, slot offset bad: block=119128064, root=1, slot=0 I have a sneaking suspicion that this is what is causing the call traces issue but, I'm not sure how to figure out what device is "md4" or what I should do when I figure out which device it is. Thank you for all of your help in advance! unraid-diagnostics-20170413-1844.zip