Posts by hempelr

    ups sorry, forgot it to copy...
    Here is it:
    ----
    ERROR]


    iMSCP::Net::getAddrDevice: Unknown IP: 127.0.0.1
    Package::FrontEnd::start: Unable to start nginx service
    iMSCP::Execute::getExitCode: External command died with signal 2, without
    coredump
    main::setupRestartServices: Unable to restart FRONTEND service
    iMSCP::Debug::END: Exit code: 1
    ----
    Hope it helps to get an idea


    Ruben

    An actual made update went well until it would configure nginx. I did never ever use nginx, but it seems that with the last git-update (stable branch) came the fact, that i-mscp wants to use nginx for his own frontend.
    Now I don'n know whats newly has been changed and what can I do to get a running system.
    System: Debian wheezy 7.6 / Maria-DB 5.5.28 / vServer at S4Y


    It is strange that the updates have been always works without problems until today...
    Also the script did neither ask for the db-system (in the past it did) nor for the php-version or usability (fpm / fast-cgi) what ist also did in the past.


    Thanks for help in advance


    Ruben

    First, sorry for the late answer, the problem occured on a server which wasn't important, meanwhile my boss did kill that server (it was a virtual machine on a esxi-server with fibrechannel-storagelibrary and he killed the storage...)


    But I think the problem is solved, I did updates on my other servers, and always after the second run of the updatescript it went well without any error. Sometimes things regulate almost self ;-)


    Once more thanks for the good work of the team of imscp - it is really great how to work here and how well everything works.

    Thanks nuxwin,
    is the pinning not right? I actually toufght, that there's no big problems with pinning, because I only install some tools from testing.
    But ok, I know that some packages should not be on a server....


    Well, I did the changings but now the error as following:
    [ERROR] │
    │ │
    │ Error while performing step: │
    │ │
    │ Installing all Debian packages for i-MSCP │
    │ │
    │ Error was: │
    │ │
    │ autoinstaller::Adapter::Debian::installPackages: Reading package lists... │
    │ Building dependency tree... │
    │ Reading state information... │
    │ apache2 is already the newest version. │
    │ apache2-mpm-worker is already the newest version. │
    │ apache2-suexec-custom is already the newest version. │
    │ at is already the newest version. │
    │ bash is already the newest version.


    Some new hints? It does not love the newest versions?
    Thanks in advice.
    Ruben

    Distro: Debian Wheezy


    resolv.conf:
    # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
    # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
    nameserver 8.8.8.8


    /etc/apt/preferences:
    Package: *
    Pin:release n=wheezy
    Pin-Priority: 500
    Package: *
    Pin: release a=testing
    Pin-Priority: 50


    /etc/apt/preferences.d/imscp:
    Package: mariadb-client-10.0 mariadb-server-10.0 mariadb-common libmysqlclient18
    Pin: origin mirror.netcologne.de
    Pin-Priority: 1001


    /etc/apt/sources.list:
    deb-src http://debian.intergenia.de/debian/ wheezy main non-free contrib
    deb http://security.debian.org/ wheezy/updates main contrib non-free
    deb-src http://security.debian.org/ wheezy/updates main contrib non-free
    # wheezy-updates, previously known as 'volatile'
    deb http://debian.intergenia.de/debian/ wheezy-updates main contrib non-free
    deb-src http://debian.intergenia.de/debian/ wheezy-updates main contrib non-free
    deb http://mirror.netcologne.de/mariadb/repo/10.0/debian wheezy main


    /etc/apt/sources.list.d/backports.list:
    # wheezy backports
    deb http://ftp.debian.org/debian/ wheezy-backports main contrib non-free


    /etc/apt/sources.list.d/monitorix.list:
    # wget http://apt.izzysoft.de/izzysoft.asc
    # apt-key add izzysoft.asc
    deb http://apt.izzysoft.de/ubuntu generic universe


    /etc/apt/sources.list.d/debtesting.list:
    deb http://ftp.us.debian.org/debian/ testing main


    /etc/apt/sources.list.d# cat whiskermenu.list:
    # wget http://download.opensuse.org/r…de/Debian_7.0/Release.key
    # sudo apt-key add - < Release.ke
    deb http://download.opensuse.org/r…home:gottcode/Debian_7.0/ /


    /etc/apt/sources.list.d# cat x2go.list:
    #apt-key adv --recv-keys --keyserver keys.gnupg.net E1F958385BFE2B6E
    # X2Go Repository (release builds)
    deb http://packages.x2go.org/debian wheezy main
    # X2Go Repository (sources of release builds)
    deb-src http://packages.x2go.org/debian wheezy main


    apt-get install -f
    Paketlisten werden gelesen... Fertig
    Abhängigkeitsbaum wird aufgebaut.
    Statusinformationen werden eingelesen.... Fertig
    0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.


    Hope that there's no failure in the lists, but apt-get update works without any worry ;-)
    Thanks for any hint.

    I've tried to update a local installation per update-script of the wiki (changed to the stable-trunk) - it's a development environment and groupware plattform on my workoffice where I'm employed.
    The dpkg did went well, no errors. But after synchronize the git and begin of the update of i-mscp after the downloads the following error-message appeared:
    ---begin errormessage
    Error was:

    autoinstaller::Adapter::Debian::installPackages: Reading package lists...
    Building dependency tree...
    Reading state information...
    Reinstallation of libdbi-perl is not possible, it cannot be downloaded.
    Reinstallation of libc6-dev is not possible, it cannot be downloaded.
    Reinstallation of perl-base is not possible, it cannot be downloaded.
    Reinstallation of libberkeleydb-perl is not possible, it cannot be
    downloaded.
    ---end errormessage
    and the installation / update interrupted.
    I-Mscp apparently works, the domains seems to be all reachable - but what where going wrong? How to download the missing packages or what is to do that the update runs troug?
    Thanks for hints - I'm looking tomorrow here again in, now I have closing time... ;-)

    I`ve read some arguments pro an contra .lan-tld-domains - and I will do some corrections in my LAN to get no conflicts and use one of my own domains btw. a subdomain for internal use. It speaks more again so called pseudodomains than for. But the "bad thing" is that it needs more "brain-work" to use no pseudodomains... ;-)
    Thanks and greetings


    hempelr

    I want to install I-MSCP in a LAN with the domain-name webdev.lan.
    It's not possible, because the install-routine meenst, that server1.webdev.lan would be not a valid full qualified tld.
    The problem is, that I can of some given reasons only take .lan as root-zone.
    No other virtual unixoides system did there sometimes complain. How is the trick to get i-mscp work with this root-zone?
    Neither Bind9 nor dnsmasq in a standalone installation does do any smallest problem with this .lan-root-zone - why does it i-mscp?
    It would be nice, if someone can tell me how is this bahavior to disable or to workaround.


    Greetings hempelr

    Thanks Nuxwin, it runs....
    It was a little lektion to search in forum, to learn in linux-debian and in reading error- and statusmessages ;-)
    Thank the top work of the i-mscp-team btw. I think of your work every failure has a plausible error message, so that I could correct all by hand step by step....
    What I've done:
    - first Dist-Update from squeeze to wheeze (it went relative smoot till some problems with the boomanager and the partitons in fstab, but it was relative easy to clear...)
    - in webmin the faulty domain-entry under bind9 deletet (this which is meanwhile transferred to another server)
    - so often startet the install-script and manual deletet the faulty database-entrys in the imscp-db (its still ispcp named in my system, because the server is rather old and in former times runed ispcp on it) till it went without error to the end
    - then the only problem was a error with starting apache, because there was no httpd.conf, what was expectet in the newly createt apache2.conf
    Now all thinks are fine, and one more the fazit, that i-mscp is a top panelsystem.
    Thank you and the team for the good work.


    Greetings from the ore mountains in germany


    hempelr

    Hi Nuxwin,


    ist on a Debian 6.0.9...
    I can imagine myself, that a user / domain, which have been transferred to another server / IP / Provider and is not been deletet in imscp on that machine does make some of the problems.


    How is ist possible to delete a domain and its mailaccounts / Aliases on the cli (because nothing is running nor phpmysql nor webftp nor webmail) ?
    Webmin is running on the server, it could also be possible to do some thinks with those help.
    Thanks for your help.
    BTW - because on the server some customer-domains it would be a bit time-critical to get the system running...