Jump to content

coresplinter

Members
  • Posts

    3
  • Joined

  • Last visited

Posts posted by coresplinter

  1. 8 hours ago, saarg said:

    You haven't said what the problem is, just that it's similar and you get the error message when you try to connect.

     

    You can't access nextxloud?

     

    If you remove and install the container you will still have the database as the appdata folder is not deleted when removing a container. If you want to set up a new database using the same settings you did for the current one, just stop mariadb and delete the appdata folder for mariadb and start the container again. That will get you a clean database.

    If you do this, you will have to set up nextxloud again also as the settings and users are stored in the database. The files are still in /data, so you will still have them, but you need to add the users again and then scan for new files manually.

     

     

    Hi Saarg, sorry for the delay! Yeah, I'm unable to access NextCloud and the Web UI of that just says Internal Server Error. 

    I am trying your suggestion and it seems I'm unable to remake/add users with the same username. As I'm unfamiliar with how to get around that, I've just opted to wipe both containers & the share then re-install and resync everything again! 

    Since I'm doing a (nearly) fresh install, everything should work properly! Thank you for looking into this for me. 

     

  2. 39 minutes ago, saarg said:

    Sorry, I don't know how to fix that problem. You are inside the mariadb container when executing the command?


    Yep! I'm running it in the mariadb container via the unraid GUI which is why I am confused. (I believe I followed the Spaceinvader video) (Clicking on the MariaDB docker icon and clicking console). 

    My Nextcloud instance was working fine the past month so I'm 99% certain the command should have been accessible back then. 
    But all of a sudden I'm getting an error now. 

    Do you happen to know if I would lose everything in my NextCloud if I uninstall and reinstall the container? (I'm leaning towards it would screw everything up because it would be basically deleting the NextCloud file database..)

  3. On 4/20/2021 at 1:21 AM, saarg said:

    When have you seen us post anything support related with that account? It's only used to start the support thread, which we now stopped doing and will not do anymore as we want support to happen on our platforms.

     

    There are nobody else reporting any chrashes using our container, so it's a local issue. The container is receiving a signal to stop, so you will have to figure out what does that.



    Hey Saarg! So uh.. I may be encountering  a similar error as well :D
    I'm using Mariadb for my nextcloud only and am trying to figure it out as I'm  not 100% familiar with this topic. 

    Thank you for releasing this Docker Container though!

    I suspected my issue with nextcloud was related to a password expiring or something but I haven't figured out how to reset or access the database as I'm getting "ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)" when I entered my password using "mysql -uroot -p". 

    EDIT: Would you happen to have any advise on how I can fix/get pass this error? 
     

    cat: /var/run/mysqld/mysqld.pid: No such file or directory
    [cont-finish.d] executing container finish scripts...
    [cont-finish.d] done.
    [s6-finish] waiting for services.
    [s6-finish] sending all processes the TERM signal.
    [s6-finish] sending all processes the KILL signal and exiting.
    
    [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
    [s6-init] ensuring user provided files have correct perms...exited 0.
    [fix-attrs.d] applying ownership & permissions fixes...
    [fix-attrs.d] done.
    [cont-init.d] executing container initialization scripts...
    [cont-init.d] 01-envfile: executing...
    [cont-init.d] 01-envfile: exited 0.
    [cont-init.d] 10-adduser: executing...
    usermod: no changes
    
    -------------------------------------
    _ ()
    | | ___ _ __
    | | / __| | | / \
    | | \__ \ | | | () |
    |_| |___/ |_| \__/
    
    
    Brought to you by linuxserver.io
    -------------------------------------
    
    To support LSIO projects visit:
    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] 90-warning: executing...
    
    
    ******************************************************
    ******************************************************
    * *
    * *
    * This image will soon be rebased *
    * from ubuntu to alpine. *
    * Please be aware, this may cause issues *
    * It is strongly recommended to make backups *
    * of your config and databases before *
    * updating your image to the alpine base. *
    * *
    * *
    ******************************************************
    ******************************************************
    [cont-init.d] 90-warning: exited 0.
    
    [cont-init.d] 99-custom-scripts: executing...
    [custom-init] no custom files found exiting...
    [cont-init.d] 99-custom-scripts: exited 0.
    [cont-init.d] done.
    [services.d] starting services
    [services.d] done.
    210430 15:51:31 mysqld_safe Logging to syslog.
    210430 15:51:31 mysqld_safe Starting mysqld daemon with databases from /config/databases
    210430 15:51:33 mysqld_safe Logging to syslog.
    210430 15:51:33 mysqld_safe Starting mysqld daemon with databases from /config/databases
    210430 15:51:35 mysqld_safe Logging to syslog.
    210430 15:51:35 mysqld_safe Starting mysqld daemon with databases from /config/databases
    210430 15:51:37 mysqld_safe Logging to syslog.



     

×
×
  • Create New...