Do have problems with nginx configuration

  • Try this:


    Log in as root and stop the mysql daemon. Now lets start up the mysql daemon and skip the grant tables which store the passwords.
    sudo /etc/init.d/mysql stop
    mysqld_safe --skip-grant-tables
    You should see mysqld start up successfully. If not, well you have bigger issues. Now you should be able to connect to mysql without a password.
    mysql --user=root mysql

    Code
    update user set Password=PASSWORD('new-password') where user='root';
    flush privileges;
    exit


    Then restart it normally. You should be good to go.

  • Well I did uninstall seafile; but before I start the new installation I like to understand if I should create a new folder or should I place it under /root/seafile? I also belive that I don't need to make a new configuration for mysql? What else should I think about before doing the installation. Don't get me wrong I'm not lazy but I feel that I should discuss those steps before I go ahead again.


    I do not know how you did the first install of seafile. If you created a seafile user and re going to follow the new guide, you should delete the old seafile user first :


    Code
    userdel seafile


    @baldman
    And please not: there is a step missing in the new tutorial in part 4 between step 6 and 7:


    6b restart seafile to make it recognize the new settings

    Code
    /etc/init.d/seafile-server stop
    /etc/init.d/seafile-server start
  • @Zoki, Restarting either Seafile the way you said above or restarting Nginx did not work for me in a fresh new VM. The only thing that worked was to reboot the server. I original had a step there saying to reboot but someone asked me to remove that step saying I was not necessary. For now I will have to put it back in or people will complain about bad gateways. I'll do some more testing later, we might need to restart it another way.

  • Sorry, but what should happen here?


    Code
    Stopping MySQL database server: mysqld.
    root@NAS:~# mysqld_safe --skip-grant-tables
    160617 16:55:20 mysqld_safe Logging to syslog.
    160617 16:55:20 mysqld_safe Starting mysqld daemon with databases from /media/4fcfda30-31ac-49ad-8d8c-d84723cbe1af/MYSQL-DATA/
  • You need to login to mysql to execute that command. Starting mysql in safe mode allows you to do that with no password. As root,
    execute: mysql then enter the update user sql command. Don't forgot the semi-colon at the end.

    omv 5.5.17-3 usul | 64 bit | 5.4 proxmox kernel | omvextrasorg 5.4.2
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Not sure what I do wrong...


    root@NAS:~# sudo /etc/init.d/mysql stop
    Stopping MySQL database server: mysqld.
    root@NAS:~# mysqld_safe --skip-grant-tables
    160617 19:34:48 mysqld_safe Logging to syslog.
    160617 19:34:48 mysqld_safe Starting mysqld daemon with databases from /media/4fcfda30-31ac-49ad-8d8c-d84723cbe1af/MYSQL-DATA/


    How do I see that mysql starts automatically
    Should I see


    root@nas again or?

  • Something looks wrong to me:


    Code
    Stopping MySQL database server: mysqld.
    root@NAS:~# mysqld_safe --skip-grant-tables
    160617 20:05:24 mysqld_safe Logging to syslog.
    160617 20:05:24 mysqld_safe Starting mysqld daemon with databases from /media/4fcfda30-31ac-49ad-8d8c-d84723cbe1af/MYSQL-DATA/
    mysql --user=root mysql
    update user set Password=PASSWORD('xxxxx9999') where user='root';
    flush privileges;
    sudo /etc/init.d/mysql start
  • I also see that I do have a seafile db file, do I need to delete that one?


Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!