Posts by kalmarr

    Hello Nuxwin



    I am sorry for the late reply but I have been very busy in the last few days. I would like to ask if you could possibly deal with the server at the weekend. Thank you for your help in advance.


    I sent PM.


    Robert

    • Ensure that you have not any other script that setup iptable, remove any iptable rule

    I change my iptables:


    #perl /var/www/imscp/engine/tools/imscp-net-traffic-logger -v stop

    Code
    1. [DEBUG] iMSCP::Bootstrapper::boot: Booting backend....[DEBUG] iMSCP::Config::_init: Tying /etc/imscp/imscp.conf file[DEBUG] iMSCP::Execute::execute: iptables -S[DEBUG] main::stop: -P INPUT ACCEPT-P FORWARD ACCEPT-P OUTPUT ACCEPT-A INPUT -i lo -j ACCEPT-A INPUT -m conntrack --ctstate INVALID -j DROP-A INPUT -m conntrack --ctstate ESTABLISHED -j ACCEPT-A OUTPUT -o lo -j ACCEPT-A OUTPUT -j ACCEPT


    • Disable the opendkim plugin manually (search on our forum to know how)

    I disabled all plugins and I uninstalled the opendkim.

    • Rerun the installer

    I got again error same message:


    Code
    1. [ERROR] iMSCP::Stepper::_callback: Could not restart the imscp_traffic service: iMSCP::Provider::Service::Sysvinit::_exec: Job for imscp_traffic.service failed. See 'systemctl status imscp_traffic.service' and 'journalctl -xn' for details. at /usr/local/src/imscp-1.3.3/engine/PerlLib/iMSCP/Service.pm line 206.
    2. autoinstaller::Functions::install: An error occurred while performing installation steps

    Thank you for your answer Nuxwin!


    I stopped this service and I tried upgrade iMSCP again and I got more errors:


    Install panel:


    Code
    1. [ERROR]Error while performing step: Processing setup tasksError was:iMSCP::Stepper::_callback: Could not restart the imscp_traffic service:iMSCP::Provider::Service::Sysvinit::_exec: Job for imscp_traffic.service failed. See 'systemctl status imscp_traffic.service' and 'journalctl -xn' for details. at /usr/local/src/imscp-1.3.3/engine/PerlLib/iMSCP/Service.pm line 206. Please have a look at http://i-mscp.net/forum if you need help.


    shell: new errors



    Code
    1. [ERROR] Servers::named::bind::addCustomDNS: Could not dump projekt-tanacsadas.hu zone: /etc/imscp/bind/working/projekt-tanacsadas.hu.db:27: unknown RR type '60'zone projekt-tanacsadas.hu/IN: loading from master file /etc/imscp/bind/working/projekt-tanacsadas.hu.db failed: unknown class/typezone projekt-tanacsadas.hu/IN: not loaded due to errors.Servers::named::bind::addCustomDNS: Could not dump matrixcbs-server.info zone: /etc/imscp/bind/working/matrixcbs-server.info.db:41: unknown RR type '60'zone matrixcbs-server.info/IN: loading from master file /etc/imscp/bind/working/matrixcbs-server.info.db failed: unknown class/typezone matrixcbs-server.info/IN: not loaded due to errors.Servers::named::bind::addCustomDNS: Could not dump usis.me zone: /etc/imscp/bind/working/usis.me.db:83: unknown RR type '60'zone usis.me/IN: loading from master file /etc/imscp/bind/working/usis.me.db failed: unknown class/typezone usis.me/IN: not loaded due to errors.Servers::named::bind::addCustomDNS: Could not dump m-telesales.hu zone: /etc/imscp/bind/working/m-telesales.hu.db:27: unknown RR type '60'zone m-telesales.hu/IN: loading from master file /etc/imscp/bind/working/m-telesales.hu.db failed: unknown class/typezone m-telesales.hu/IN: not loaded due to errors.iMSCP::Stepper::_callback: Could not restart the imscp_traffic service: iMSCP::Provider::Service::Sysvinit::_exec: Job for imscp_traffic.service failed. See 'systemctl status imscp_traffic.service' and 'journalctl -xn' for details. at /usr/local/src/imscp-1.3.3/engine/PerlLib/iMSCP/Service.pm line 206.autoinstaller::Functions::install: An error occurred while performing installation steps


    Domain error - example (#cat /etc/imscp/bind/working/projekt-tanacsadas.hu.db)




    I didn't change configuration, all origin iMSCP are config files.


    Robert

    Yes, first I tried latest version, but the error was same.



    After I think upgrade step by step the versions, but I couldn't it unfortunately.



    I think the error context “#service imscp_traffic status > Failed to start i-MSCP traffic logger.” will be.

    Hello,



    I tried upgrade iMSCP 1.3.0 -> iMSCP 1.3.1, but I got an error message and the upgrade process stopped:



    ---


    [ERROR]


    │ Error while performing step:


    │ Processing setup tasks


    │ Error was:


    │iMSCP::Stepper::_callback: Could not restart the imscp_traffic service: iMSCP::Provider::Service::Sysvinit::_exec: Job for imscp_traffic.service failed. See


    │ 'systemctl status imscp_traffic.service' and 'journalctl -xn' for details. at /usr/local/src/imscp-1.3.1/engine/PerlLib/iMSCP/Service.pm line 206.


    │ Please have a look at http://i-mscp.net/forum if you need help.


    ---


    I looked the forum. I found a intrest post: https://i-mscp.net/index.php/T…ic-service-i-MSCP-1-2-16/



    I rollback my old system to iMSCP 1.3.0 and I try check on my old server this instruction:





    Code
    1. service imscp_traffic status


    Result:

    Code
    1. ● imscp_traffic.service - i-MSCP traffic logger
    2. Loaded: loaded (/etc/systemd/system/imscp_traffic.service; enabled)
    3. Active: failed (Result: exit-code) since v 2016-09-25 13:14:10 CEST; 11min ago
    4. Process: 463 ExecStart=/usr/bin/perl /var/www/imscp/engine/tools/imscp-net-traffic-logger start (code=exited, status=1/FAILURE)
    5. Main PID: 463 (code=exited, status=1/FAILURE)
    6. szept 25 13:14:09 admin systemd[1]: Starting i-MSCP traffic logger...
    7. szept 25 13:14:10 admin perl[463]: [ERROR] main::start: iptables: Chain already exists.
    8. szept 25 13:14:10 admin systemd[1]: imscp_traffic.service: main process exited, code=exited, status=1/FAILURE
    9. szept 25 13:14:10 admin systemd[1]: Failed to start i-MSCP traffic logger.
    10. szept 25 13:14:10 admin systemd[1]: Unit imscp_traffic.service entered failed state.



    but my iMSCP 1.3.0 server working is perfect. I could upgrade it (iMSCP 1.2.17 > iMSCP 1.3.0) without fail.



    What is the error? How can I fix it, that I can upgrade the system is iMSCP 1.3.3 (latest update)?



    My system is now Debian 8.6



    Thx!



    Robert

    Sziasztok,



    Elkészítem a StartSSL-re is a leírást, mert amit tapasztaltam, hogy megváltozott a How To Install StartSSL And GeoTrust SSL Certificates leírásban szereplő domain címek (nem működnek a letöltések).



    Shell-Script
    1. cd /root && mkdir startssl && cd startssl
    2. wget http://www.startssl.com/certs/ca-sha2.pem
    3. wget https://www.startssl.com/certs/sca.server1.crt
    4. cat sca.server1.crt ca-sha2.pem > bundle.pem


    Szerver kulcs elkészítése a fentiek szerint.



    A StartSSL felülete is változott, ami szerintem felhasználó barátabb lett.


    Azonosítani kell a domain nevet, illetve a domain megadása után kell feltölteni az elkészített .csr filet.
    Elküldés után pár másodperccel már le is tölthető a tanúsítvány .pem kiterjesztéssel (nem .crt,de ugyan az).



    Innentől kezdve a lépések megegyeznek ezzel: Lépések

    Hello,


    I am experiencing the following with the SSL certificate:
    Now I am using the the StartSSL, and I cant decide if that is causing the problem, or if its not an error, but something else.


    I am using the latest version of I-MSCP under Debian 8.


    The admin surface of I-MSCP runs, for example on: https://admin.server.com. This is accepted by the browsers without a problem.
    But, if I would like to use one of my pages' domains in the following way: https://domain.com:4443/webmail/
    then the browser shows an error, and also indicates that https://admin.server.com This Connection is Untrusted.
    In other words, I have to accept the StartSSL certificate as trustworthy.


    I had also corrected the following error in the I-MSCP: https://i-mscp.net/index.php/Thread/11801-problem-with-domain-after-upgrade-to-1-2-17/?postID=42155#post42155


    Robert

    Hát, ha kívánni lehetne akkor nem csak ez a szimpla funkció hiányzik csak :(. Egy költöztetést nem macerának, inkább rémálomnak neveznék. Sajnos az I-MSCP nem tud (eddig nem jöttem rá), úgy biztonsági mentést készíteni, hogy akár egy lépésből vissza tudjam állítani az adatokat egy másik szerveren, ami nagyon jó lenne. Sajnos ilyen eset bárkinek bármikor előfordulhat és kb. 1-2 napos meló.
    Sőt, lehet már az is elég lenne, ha egy közös helyre mentené, esetleg több napi mentéssel, hogy vissza lehessen állítani. Igaz minden megoldható külső scripttel, de azért az jó lenne, ha is benne lenne az I-MSCP.


    Kalmi

    Szia,


    szerintem nem, mivel új ügyfelet hozol létre egy domain név létrehozásakor és ott nincs átjárás. Továbbá szerintem ez nem egy gyakori probléma.


    Egyszerűbb lementened az adatbázist, e-maileket és fileokat és létrehozni az új domain nevet és belemásolni, visszaállítani mindent.


    Üdv.


    Kalmi