Posts by DragonZX

    Quote


    BTW:

    • Your apache config was wrong somewhere.
    • The installer doesn't change the SQL root password
    • Your server seem partially broken
    • You can always lets the panel think that plugins are disabled by by using mysql command line tool:


    SQL
    1. # mysql -u -root -p<password>
    2. > use imscp;
    3. > UPDATE plugin SET plugin_status = 'disabled', plugin_error = NULL;


    Thanks.
    - My server was comletely reinstalled under same ip and restored using script, I posted before, because it was compromised (server not mine, it belongs to my customer). So no logs at all was there.
    - MySQL root password situation is not clear for me, as I understand, installer asks about generating SQL pasword for user which own imscp default database? So I'm still under root (for testing purposes) So on...
    - Thank you for the MySQL query. 'Show tables' didnt work I wonder...


    I understood that ;) But in this year there is the third server, I must built up from trash (compomising, memory/hdd crash etc...) we need some script tho make full clear panel backup/restore. I'm trying to learn perl for it, but as for now...


    upd: ohh, finaly done. After reconfiguring with recreation of ssl done. Panel doesn't create /var/log/apache2/%panel domain%/*.log and /var/log/nginx/%panel domain%/*.log

    Уes, but now a have a logic circle
    1. I have no webinterface at all
    2. I have some plugins, which is missing (I've not back up it as I didn't need them in such case(clear install+server crash dump)
    3. Mysql full backup is about 30 GB of data, so I need to make another query to disable plugins (which in my situation ends an error).
    4. So i need some option to disable or delete plugin from the database if the plugin error happens.
    Just an IMHO


    P.S. MySQL root password has been changed to heavy by the installer as I understood?


    Also crashed in the final steps

    Code
    1. -- Logs begin at Thu 2015-05-07 16:20:25 MSK, end at Thu 2015-05-07 16:32:37 MSK. --May 07 16:32:16 server2 apache2[8841]: AH00014: Configuration check failedMay 07 16:32:16 server2 apache2[8841]: Action 'configtest' failed.May 07 16:32:16 server2 apache2[8841]: The Apache error log may have more information.May 07 16:32:16 server2 systemd[1]: apache2.service: control process exited, code=exited status=1May 07 16:32:16 server2 systemd[1]: Failed to start LSB: Apache2 web server.-- Subject: Unit apache2.service has failed-- Defined-By: systemd-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel---- Unit apache2.service has failed.---- The result is failed.May 07 16:32:16 server2 systemd[1]: Unit apache2.service entered failed state.May 07 16:32:37 server2 postfix/pickup[1002]: CD5D5262C6C: uid=0 from=<root>May 07 16:32:37 server2 postfix/cleanup[1005]: warning: hash:/etc/postfix/imscp/aliases is unavailable. open database /etc/postfix/imscp/aliases.db: No such file or directoryMay 07 16:32:37 server2 postfix/cleanup[1005]: warning: hash:/etc/postfix/imscp/aliases lookup error for "[email protected]"May 07 16:32:37 server2 postfix/cleanup[1005]: warning: CD5D5262C6C: virtual_alias_maps map lookup problem for [email protected] -- message not accepted, try again later


    Apache error log:

    Code
    1. [Thu May 07 16:20:35.576837 2015] [suexec:notice] [pid 603:tid 3073640256] AH01232: suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
    2. [Thu May 07 16:20:35.594300 2015] [mpm_worker:notice] [pid 619:tid 3073640256] AH00292: Apache/2.4.10 (Debian) mod_fcgid/2.3.9 OpenSSL/1.0.1k configured -- resuming normal operations
    3. [Thu May 07 16:20:35.594317 2015] [core:notice] [pid 619:tid 3073640256] AH00094: Command line: '/usr/sbin/apache2'
    4. [Thu May 7 16:20:35 2015] [alert] vlogger: unable to connect to MySQL server: Can't connect to MySQL server on '127.0.0.1' (111)
    5. [Thu May 7 16:20:35 2015] [alert] vlogger: Tracker feature turned off
    6. [Thu May 7 16:20:35 2015] [notice] vlogger: started CustomLog Handler -- resuming normal operations
    7. [Thu May 07 16:23:19.854060 2015] [mpm_worker:notice] [pid 619:tid 3073640256] AH00295: caught SIGTERM, shutting down
    8. [Thu May 7 16:23:19 2015] [notice] vlogger: caught TERM, shutting down

    Вообще можно включить в свойствах реселлера и клиента возможность редактировать настройки PHP, тогда основные настройки можно будет редактировать из панели инструментов.