PHP Fatal error: Uncaught Error: Undefined constant "ISPC_APP_VERSION"

Discussion in 'ISPConfig 3 Priority Support' started by Stelios, Jun 21, 2024.

  1. till

    till Super Moderator Staff Member ISPConfig Developer

    It may indeed take a while, but 2 hours is a bit long. Most likely, the node is not connected to the master anymore. Did you choose to reconfigure permissions in master database during update?
     
  2. Stelios

    Stelios Active Member HowtoForge Supporter

    Yes I did and finished without an error at all.
    I reboot all servers and is nearly a day now and still shows the old version.
     
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    Run:

    /usr/local/ispconfig/server/server.sh --debug

    on the affected server and post the output.
     
  4. Stelios

    Stelios Active Member HowtoForge Supporter

    root@email3:~# /usr/local/ispconfig/server/server.sh --debug
    Set Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
    27.06.2024-11:59 - DEBUG [server:224] - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
    finished server.php.

    root@email3:~# rm /usr/local/ispconfig/server/temp/.ispconfig_lock
    rm: cannot remove '/usr/local/ispconfig/server/temp/.ispconfig_lock': No such file or directory
    root@email3:~#
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    Ok, so there is no connection issue to the master.

    A lock file exists while the script is running. Therefore, you can not delete it afterward, as the script has removed it already.

    Possible reasons for the issue are: you might have selected the wrong server_id in config.inc.php or one of the cronjobs in sys_cron table of in dbispconfig of the slave is stuck in status running.
     
  6. Stelios

    Stelios Active Member HowtoForge Supporter

    The server id should be the correct as I found it also in the master db where users are listed.
    How can I fix the issue with the sys_cron that you are talking as it might be that
     
  7. till

    till Super Moderator Staff Member ISPConfig Developer

    Check their status with phpmyadmin
     
  8. Stelios

    Stelios Active Member HowtoForge Supporter

    The sys_cron table that is on the email server that I have the issue or on the master?
     
  9. Stelios

    Stelios Active Member HowtoForge Supporter

    This is from within the email server which has the issue:

    Code:
    MariaDB [dbispconfig]> select * from sys_cron;
    +-----------------------------------+---------------------+---------------------+---------+
    | name                              | last_run            | next_run            | running |
    +-----------------------------------+---------------------+---------------------+---------+
    | cronjob_awstats                   | 2024-06-27 00:00:02 | 2024-06-28 00:00:00 |       0 |
    | cronjob_backup                    | 2024-06-26 12:35:12 | 2024-06-27 00:00:00 |       1 |
    | cronjob_backup_mail               | 2024-06-27 00:00:02 | 2024-06-28 00:00:00 |       0 |
    | cronjob_bind_dnssec               | 2024-06-27 03:30:01 | 2024-06-28 03:30:00 |       0 |
    | cronjob_cleanup                   | 2024-06-27 12:20:02 | 2024-06-27 12:25:00 |       0 |
    | cronjob_clean_mailboxes           | 2024-06-26 22:00:01 | 2024-06-27 22:00:00 |       0 |
    | cronjob_file_cleanup              | 2024-06-27 12:21:01 | 2024-06-27 12:22:00 |       0 |
    | cronjob_ftplogfiles               | 2024-06-27 00:00:02 | 2024-06-28 00:00:00 |       0 |
    | cronjob_goaccess                  | 2024-06-27 00:00:02 | 2024-06-28 00:00:00 |       0 |
    | cronjob_jailkit_maintenance       | 2024-06-27 12:20:02 | 2024-06-27 12:25:00 |       0 |
    | cronjob_letsencrypt               | 2024-06-27 03:00:01 | 2024-06-28 03:00:00 |       0 |
    | cronjob_logfiles                  | 2024-06-27 00:00:02 | 2024-06-28 00:00:00 |       0 |
    | cronjob_mailbox_stats             | 2024-06-27 00:00:01 | 2024-06-28 00:00:00 |       0 |
    | cronjob_mailbox_stats_hourly      | 2024-06-27 12:00:01 | 2024-06-27 13:00:00 |       0 |
    | cronjob_monitor_backup            | 2024-06-27 12:20:01 | 2024-06-27 12:25:00 |       0 |
    | cronjob_monitor_clamav_log        | 2024-06-27 12:20:01 | 2024-06-27 12:25:00 |       0 |
    | cronjob_monitor_cpu               | 2024-06-27 12:20:01 | 2024-06-27 12:25:00 |       0 |
    | cronjob_monitor_database_size     | 2024-06-27 12:20:01 | 2024-06-27 12:25:00 |       0 |
    | cronjob_monitor_disk_usage        | 2024-06-27 12:20:01 | 2024-06-27 12:25:00 |       0 |
    | cronjob_monitor_email_quota       | 2024-06-27 12:15:01 | 2024-06-27 12:30:00 |       0 |
    | cronjob_monitor_fail2ban          | 2024-06-27 12:20:01 | 2024-06-27 12:25:00 |       0 |
    | cronjob_monitor_hd_quota          | 2024-06-27 12:20:01 | 2024-06-27 12:25:00 |       0 |
    | cronjob_monitor_iptables          | 2024-06-27 12:20:01 | 2024-06-27 12:25:00 |       0 |
    | cronjob_monitor_ispconfig_log     | 2024-06-27 12:20:01 | 2024-06-27 12:25:00 |       0 |
    | cronjob_monitor_ispconfig_version | 2024-06-27 12:20:01 | 2024-06-27 12:25:00 |       0 |
    | cronjob_monitor_kernel_version    | 2024-06-27 12:20:01 | 2024-06-27 12:25:00 |       0 |
    | cronjob_monitor_letsencrypt_log   | 2024-06-27 12:20:01 | 2024-06-27 12:25:00 |       0 |
    | cronjob_monitor_mail_log          | 2024-06-27 12:20:01 | 2024-06-27 12:25:00 |       0 |
    | cronjob_monitor_mail_queue        | 2024-06-27 12:20:02 | 2024-06-27 12:25:00 |       0 |
    | cronjob_monitor_mem_usage         | 2024-06-27 12:20:02 | 2024-06-27 12:25:00 |       0 |
    | cronjob_monitor_openvz            | 2024-06-27 12:21:01 | 2024-06-27 12:25:00 |       0 |
    | cronjob_monitor_os_version        | 2024-06-26 12:21:11 | 2024-06-26 12:25:00 |       1 |
    | cronjob_monitor_raid              | 2024-06-26 12:22:12 | 2024-06-26 12:25:00 |       1 |
    | cronjob_monitor_rkhunter          | 2024-06-26 12:23:11 | 2024-06-27 00:00:00 |       1 |
    | cronjob_monitor_server            | 2024-06-26 12:31:11 | 2024-06-26 12:35:00 |       1 |
    | cronjob_monitor_services          | 2024-06-26 12:32:11 | 2024-06-26 12:35:00 |       1 |
    | cronjob_monitor_syslog            | 2024-06-26 12:33:12 | 2024-06-26 12:35:00 |       1 |
    | cronjob_monitor_system_update     | 2024-06-26 12:34:11 | 2024-06-26 13:00:00 |       1 |
    | cronjob_openvz                    | 2024-06-27 00:00:02 | 2024-06-28 00:00:00 |       0 |
    | cronjob_purge_mailboxes           | 2024-06-26 23:30:01 | 2024-06-27 23:30:00 |       0 |
    | cronjob_quota_notify              | 2024-06-27 00:00:02 | 2024-06-28 00:00:00 |       0 |
    | cronjob_webalizer                 | 2024-06-27 00:00:02 | 2024-06-28 00:00:00 |       0 |
    +-----------------------------------+---------------------+---------------------+---------+
    42 rows in set (0.003 sec)
     
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    Set running to 0 for all cronjobs:

    Code:
    UPDATE sys_cron SET running = 0;
     
  11. till

    till Super Moderator Staff Member ISPConfig Developer

    On the mail server.
     
  12. Stelios

    Stelios Active Member HowtoForge Supporter

    Thanks that worked.
     
    till likes this.

Share This Page