ISPConfig 2.2.10 released

Discussion in 'General' started by till, Feb 20, 2007.

  1. till

    till Super Moderator Staff Member ISPConfig Developer

    Run /etc/init.d/ispconfig_server start
     
  2. celtic

    celtic New Member

    [email protected]:~# /etc/init.d/ispconfig_server start
    Starting ISPConfig system...
    /root/ispconfig/httpd/bin/apachectl startssl: httpd started
    FreshClam is already running!
    ISPConfig system is now up and running!

    still the problem remains...
     
  3. Ben

    Ben ISPConfig Developer ISPConfig Developer

    fyi, update went fine ;)



    where does this errormessage come from? Seems that you try to access through a proxy?
    if the connection is refused by your machine, what happens with a directy access ( no proxy in between) or if you directly try this on the box locally, e.g. with lynx.
    Does netstat -tap show ispconfig_server listening on port 81?
     
  4. celtic

    celtic New Member

    Never had problems before with this situation. However Ive tried toaccess from an open connection an still have reanched no success.

    Active Internet connections (servers and established)
    Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
    tcp 0 0 *:mysql *:* LISTEN 3956/mysqld
    tcp 0 0 *:10000 *:* LISTEN 4804/perl
    tcp 0 0 *:81 *:* LISTEN 24461/ispconfig_htt
    tcp 0 0 *:ftp *:* LISTEN 24826/proftpd: (acc
    tcp 0 0 jfo.nortenet.pt:domain *:* LISTEN 24811/named
    tcp 0 0 localhost:domain *:* LISTEN 24811/named
    tcp 0 0 localhost:953 *:* LISTEN 24811/named
    tcp 0 0 *:smtp *:* LISTEN 24767/master
    tcp 0 0 jfo.nortenet.pt:mysql jfo.nortenet.pt:38284 ESTABLISHED3956/mysqld
    tcp 0 0 jfo.nortenet.pt:42957 jfo.nortenet.pt:mysql TIME_WAIT -
    tcp 0 0 jfo.nortenet.pt:38284 jfo.nortenet.pt:mysql ESTABLISHED24907/apache2
    tcp6 0 0 *:imaps *:* LISTEN 3830/couriertcpd
    tcp6 0 0 *:pop3s *:* LISTEN 3865/couriertcpd
    tcp6 0 0 *:pop3 *:* LISTEN 3845/couriertcpd
    tcp6 0 0 *:imap2 *:* LISTEN 3810/couriertcpd
    tcp6 0 0 *:www *:* LISTEN 24675/apache2
    tcp6 0 0 *:ssh *:* LISTEN 4130/sshd
    tcp6 0 0 ip6-localhost:953 *:* LISTEN 24811/named
    tcp6 0 0 *:smtp *:* LISTEN 24767/master
    tcp6 0 0 *:https *:* LISTEN 24675/apache2
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4544 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4545 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4546 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4547 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4510 TIME_WAIT -
    tcp6 0 1748 jfo.nortenet.pt:ssh ADSL-F49-S200-jfo:14859 ESTABLISHED29617/0
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4520 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4521 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4522 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4523 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4524 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4525 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4526 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4527 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4513 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4514 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4515 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4516 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4517 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4518 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4519 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4536 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4537 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4538 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4539 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4540 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4541 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4542 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4543 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4528 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4529 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4532 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4533 TIME_WAIT -
    tcp6 0 0 jfo.nortenet.pt:www ::ffff:85.138.54.1:4535 TIME_WAIT -
     
  5. rbartz

    rbartz Member HowtoForge Supporter

    CLAMAV not scanning with 2.2.10 install

    This may be URGENT for some users with clients expecting virus protection:

    There is a problem with CLAMAV 0.90 and Clamassassin 1.2.3 that needs to be addressed in the ISPconfig installation right away as mail MAY NOT be being scanned on some systems.

    On my FC3 and FC4 installations the CLAMAV was failing on mail scans as the clamassassin --mbox option fails. I do not know about other installations.

    [​IMG]

    By removing the --mbox from the clamassassin options in /home/admispconfig/ispconfig/tools/clamav/bin/clamassassin the errors are fixed:

    # Configure options passed to clamscanner
    # CLAMSCANOPT="--no-summary --stdout --mbox"
    CLAMSCANOPT="--no-summary --stdout"

    [​IMG]

    There is some information about it on various other forums of other products, but I assume it is pretty general on installations where clamassassin calls clamscan rather than using clamd.

    Cheers,

    Richard
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

  7. mbunal

    mbunal New Member

    co-domain doesnt work and...

    hi all

    i upgraded from 2.2.6 t0 2.2.10 on ubuntu dapper amd64.

    webmail.domain.com doesnt work anymore.

    ispconfig_server doesnt run at server startup.

    what can i do?

    cheers

    baris.
    ________
    GODDESSZAIRA LIVE
     
    Last edited: Sep 8, 2011
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    This is not a default feature of ISPConfig, so you might do the same changes to get this working as you did for ISPConfig 2.2.6

    That is not touched by the update, so I guess your 2.2.6 relaese has not started at boot time too. Please run:

    update-rc.d ispconfig_server defaults
     
  9. celtic

    celtic New Member

    Does any one guess why I cannot access https://212.13.41.2:81 after my last post?

    I am glad that the upgrade went fine but I cannot use ISP Config until this issue is solved.

    I kindly thank any help in advance.
     
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    Looks like your SSL certificate is corrupted. Please create a new one as described here:

    http://www.howtoforge.com/forums/showthread.php?t=121
     
  11. celtic

    celtic New Member

    Should i go that way even if my sites work fine and mail clients that request SSL dont have any kind of problem?
     
  12. till

    till Super Moderator Staff Member ISPConfig Developer

    This has nothing to do with your clients SSL certifictaes or sites. The SSL certificate of the controlpanel is corrupted, if you dont fix it you wont be able to login to the controlpanel anymore.
     
  13. celtic

    celtic New Member

    Problem Solved!

    ISPCOnfig rev 10 is now up and running!

    I dont catch much of linux but with a backup team like this I am getting dangerously fearless!

    Thank you!
     
  14. brent.stephens

    brent.stephens New Member

    This is pretty huge for me, thanks a bunch!

    If I may be so bold...is it possible to consider having a setting for a "global" MX to be set for all locally exchanged domains? I have a reverse DNS setup for my main domain, and I always go back and set that domain as the primary MX for any domains that I add to ISPC. Does this request make sense?
     
  15. nenad

    nenad ISPConfig Developer ISPConfig Developer

    I just installed ISPConfig with Debian 4.0 (etch).

    So far so good.
    it seems that only little modifications are necessary comparing to how-to for sarge.
     
  16. rhc

    rhc New Member

    When updating from ISPconfig 2.2.6 to 2.2.10 I receive this error
    ./setup2: line 860: ispconfig_tmp/php/bin/php: Datei oder Verzeichnis nicht gefunden
    ERROR: Das mitgelieferte PHP-Binary funktioniert auf Ihrem System nicht! Die Installation bricht hier ab!
    and the old installation of ISPconfig is lost.
    My system is a Fedora Core 5 on an AMD64 System.
    Any solutions?

    Best regards

    rhc

    BTW: mysql-devel is installed...
     
    Last edited: Mar 3, 2007
  17. falko

    falko Super Moderator ISPConfig Developer

    You should find backups of the old system in /tmp.
    What's the output of
    Code:
    df -h
    ?
     
  18. rhc

    rhc New Member

    Furtunately the backup was no problem :)
    The output of df -h is
    /dev/md1 2,0G 342M 1,6G 19% /
    /dev/md0 99M 15M 80M 16% /boot
    /dev/shm 501M 0 501M 0% /dev/shm
    /dev/mapper/LogVol02 1,9G 1,5G 322M 83% /home
    /dev/mapper/LogVol04 29G 5,1G 22G 19% /opt
    /dev/mapper/LogVol03 1,4G 717M 636M 53% /tmp
    /dev/mapper/LogVol00 7,6G 2,8G 4,5G 39% /usr
    /dev/mapper/LogVol01 25G 6,7G 17G 30% /var
    I think there should be enough disk space for a new installation...

    rhc
     
  19. till

    till Super Moderator Staff Member ISPConfig Developer

    There must be a error in the compilation output before this line. Please post this error here.
     
  20. rhc

    rhc New Member

    Yes, there was a lot of errors. The last ones as example:
    mv: Aufruf von stat für âuudeviewâ nicht möglich: Datei oder Verzeichnis nicht gefunden
    tar: clamav.tar.gz: Kann open nicht ausführen.: Datei oder Verzeichnis nicht gefunden
    tar: Nicht behebbarer Fehler: Programmabbruch.
    tar: Child returned status 2
    tar: Fehler beim Beenden, verursacht durch vorhergehende Fehler.
    mv: Aufruf von stat für âclamavâ nicht möglich: Datei oder Verzeichnis nicht gefunden
    tar: aps.tar.gz: Kann open nicht ausführen.: Datei oder Verzeichnis nicht gefunden
    tar: Nicht behebbarer Fehler: Programmabbruch.
    tar: Child returned status 2
    tar: Fehler beim Beenden, verursacht durch vorhergehende Fehler.
    ./setup2: line 860: ispconfig_tmp/php/bin/php: Datei oder Verzeichnis nicht gefunden
    ERROR: Das mitgelieferte PHP-Binary funktioniert auf Ihrem System nicht! Die Installation bricht hier ab!​
     

Share This Page