3.1.13 update problem

Discussion in 'General' started by chume, Oct 1, 2018.

  1. chume

    chume Member

    Hello Everyone:
    The System->Server Config links to the multi-servers server configuration pages stopped working after 3.1.13 update.
    Any idea how to fix this problem.

    Thank you.
    Chume
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Which error do you get when you access system > server config?
     
  3. chume

    chume Member

    Good morning Till.
    When I access system > server config, the other servers show up as usual but when I click on a link to go to the server page including the main server, nothing happens. it's stuck on the server config window.

    The other system menus such as system . server services works properly.

    Thank you.
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    any errors in the global apache / nginx error.log file on the control panel server when you access the server config section?
     
  5. chume

    chume Member

    There's no error in the httpd error_log and ispconfig.log files
     
  6. chume

    chume Member

    I tried the system > server config again and found this error in the apache error_log:
     
  7. till

    till Super Moderator Staff Member ISPConfig Developer

    The problem is that the PHP version on your server is too old for the syntax used in that file, this is already listed in the bug tracker.
     
  8. chume

    chume Member

    Thank you Till.
    I appreciate the help.
     
  9. chume

    chume Member

    Hello Till:
    To get ISPConfig to work on Freebsd manually of course, what recommendations/suggestions would you proffer?
    Any rewrite of the classes?
    Thank you Till.
     
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    One way might be to try to trick the installer and mimic a Linux system, choose if you either prefer the Debian or CentOS config layout, then create the files identifydetify the operating system to make the installer believe that he is on that operating system and run it. Before you do that, you probably have to create some directories or symlinks for compatibility, e.g. something like /etc/apache2/sites-enabled/ and sites-available. ISPConfig supports systemd and traditional init.d, to make it possible that ispconfig can restart and reload services, it might be nescessary to mimic the traditional init style system by placing a few small shell scripts for the services (or at least for apache and bind) in /etc/init.d/ directory.
     
  11. chume

    chume Member

    Thank you Till for your insight.
    I remain appreciative of your skills, experience and effort to help others.
     
    till likes this.

Share This Page