[SOLVED] mail and website backup not working Ispconfig 3.1

Discussion in 'General' started by barbarab, Aug 15, 2019 at 6:22 PM.

Tags:
  1. barbarab

    barbarab New Member

    hi, I installed Ispconfig with the "perfect server" guide for lubuntu 18.04 (in a VM).
    Moved the mails, created the accounts (Roundcube works) but the backup doesn't work.
    The path is /home/user/backup/ispconfig.
    The website backup works, but only running manually
    /usr/local/ispconfig/server/cron_debug.php --cronjob=500-backup.inc.php
    I tried both with web user and root user, but the mail backup is always missing.
    Also the logfiles don't refresh and I cannot see the "used space" in mailbox quota.
    Any suggestion?
    Thank you
     
  2. barbarab

    barbarab New Member

    short update:
    running manually
    php /usr/local/ispconfig/server/cron_debug.php --cronjob=500-backup_mail.inc.php
    mail backup works,
    thank you for any help
     
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    Try to run this sql query in the dbispconfig database with phpmyadmin:

    Code:
    update sys_cron set running = 0;
    and then check tomorrow if the backup has been created.
     
  4. barbarab

    barbarab New Member

    Hi Till,
    thank you for reply (and for working even in August!)
    attached the output of the query (sorry for Italian language)
    I went into the sys_cron table and here what I got: attached
    (It seems also quota and log not updating problems have to do with cron...)
    What do you suggest?

    query_output.jpg error-sys_cron.jpg sys_cron_table.jpg
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    Really strange why you got a next_run date in 2020. Maybe the date was not set correctly during initial ispconfig install or when your server uses an image thatw as installed by your isp with ispconfig preinstalled, theny they may have installed it using a wrong date. empty (truncate) the complete sys_cron table. ISPConfig will fill it again on next cron run.
     
  6. barbarab

    barbarab New Member

    I did it, but it kept 2020 as next_run date, yes, really strange

    new_sys_cron_table.png

    I attach also the htf report file
     

    Attached Files:

  7. till

    till Super Moderator Staff Member ISPConfig Developer

    Which exact ISPConfig version do you use?
     
  8. barbarab

    barbarab New Member

    ISPConfig version is 3.1dev
    $sudo grep 'def.*VERS' /usr/local/ispconfig/server/lib/config.inc.php
    define('ISPC_APP_VERSION', '3.1dev');
    p.s. In the meanwile I fixed the bug of phpmyadmin (libraries/sql.lib.php#613)
     
  9. till

    till Super Moderator Staff Member ISPConfig Developer

    There was an issue in the dev releases in the last 2 weeks which has been fixed today, the issue is not present in the stable 3.1.14p2 release, that's why it took some time until we noticed that there must be something wrong due to more reports of similar issues. Update to 'git-stable' branch by using the ispconfig_update.sh command, this will fix the issue.
     
  10. barbarab

    barbarab New Member

    Hi, thank you!
    I made the update to 'git-stable', everything went fine (below the htf_report.txt)
    Then emptied the sys_cron table, which now looks much better
    sys_cron_after_update.png

    I'll have to wait until tomorrow to check the backup.
    ---
    In /var/log/ispconfig/cron.log I get:
    ven 16 ago 2019, 16.53.02, CEST 16.08.2019-16:53 - WARNING - Unable to add a delayed restart for 'postfix'. Service not registered.
    Do I have to worry about? Something to do or to check?
    Thank you!
    ---
    ##### SERVER #####
    IP-address (as per hostname): ***.***.***.***
    [WARN] could not determine server's ip address by ifconfig
    [INFO] ISPConfig is installed.

    ##### ISPCONFIG #####
    ISPConfig version is 3.1dev


    ##### VERSION CHECK #####

    [INFO] php (cli) version is 7.2.19-0ubuntu***.***.***.***

    ##### PORT CHECK #####


    ##### MAIL SERVER CHECK #####


    ##### RUNNING SERVER PROCESSES #####

    [INFO] I found the following web server(s):
    Apache 2 (PID 4956)
    [INFO] I found the following mail server(s):
    Postfix (PID 1545)
    [INFO] I found the following pop3 server(s):
    Dovecot (PID 689)
    [INFO] I found the following imap server(s):
    Dovecot (PID 689)
    [INFO] I found the following ftp server(s):
    PureFTP (PID 1681)

    ##### LISTENING PORTS #####
    (solo ()
    Indirizzo (remoto)
    [localhost]:10026 (1571/amavisd-new)
    [localhost]:10027 (1545/master)
    [anywhere]:587 (1545/master)
    [localhost]:11211 (634/memcached)
    [anywhere]:5900 (1925/x11vnc)
    [anywhere]:110 (689/dovecot)
    [anywhere]:143 (689/dovecot)
    [anywhere]:465 (1545/master)
    [anywhere]:21 (1681/pure-ftpd)
    ***.***.***.***:53 (635/named)
    [localhost]:53 (635/named)
    ***.***.***.***:53 (479/systemd-resolve)
    [anywhere]:22 (670/sshd)
    [localhost]:631 (488/cupsd)
    [anywhere]:25 (1545/master)
    [localhost]:953 (635/named)
    [anywhere]:993 (689/dovecot)
    [anywhere]:995 (689/dovecot)
    [localhost]:10023 (704/postgrey)
    [localhost]:10024 (1571/amavisd-new)
    [localhost]:10025 (1545/master)
    *:*:*:*::*:3306 (808/mysqld)
    *:*:*:*::*:10026 (1571/amavisd-new)
    *:*:*:*::*:587 (1545/master)
    *:*:*:*::*:5900 (1925/x11vnc)
    [localhost]10 (689/dovecot)
    [localhost]43 (689/dovecot)
    *:*:*:*::*:8080 (4956/apache2)
    *:*:*:*::*:80 (4956/apache2)
    *:*:*:*::*:8081 (4956/apache2)
    *:*:*:*::*:465 (1545/master)
    *:*:*:*::*:21 (1681/pure-ftpd)
    *:*:*:*::*:53 (635/named)
    *:*:*:*::*:22 (670/sshd)
    *:*:*:*::*:631 (488/cupsd)
    *:*:*:*::*:25 (1545/master)
    *:*:*:*::*:953 (635/named)
    *:*:*:*::*:443 (4956/apache2)
    *:*:*:*::*:993 (689/dovecot)
    *:*:*:*::*:995 (689/dovecot)
    *:*:*:*::*:10023 (704/postgrey)
    *:*:*:*::*:10024 (1571/amavisd-new)




    ##### IPTABLES #####
    Chain INPUT (policy ACCEPT)
    target prot opt source destination

    Chain FORWARD (policy ACCEPT)
    target prot opt source destination

    Chain OUTPUT (policy ACCEPT)
    target prot opt source destination
     
    Last edited: Aug 16, 2019 at 6:15 PM
  11. till

    till Super Moderator Staff Member ISPConfig Developer

    I'll check that for the next release, but I guess it's harmless.
     
  12. barbarab

    barbarab New Member

    Fine,
    keep you posted about backup,
    many thanks again
     
  13. barbarab

    barbarab New Member

    Hi, now website and mail backup works like a charm!
    (it took a while to understand that the new "backup time" setting (System->Server config) would have been seen only at the next run)
    I'd write "solved", ok?
    Just a minor issue: it doesn't see the "used space" in mailbox quota (roundcube works), but I can live with it.
    Thank you!
     

Share This Page