Server stuck on 3.2.12p1

Discussion in 'General' started by lccwill, Jun 25, 2025.

  1. lccwill

    lccwill New Member

    Master server is 3.3.0p2. All slave servers are 3.3.0p2, except for one that is 3.2.12p1. When I run
    Code:
    ispconfig_update.sh
    to update that specific slave server, it says
    .

    Do I have to use the --force parameter to make this slave server show the correct version?
    Do I just need to restart the specific slave server?
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    What you describe does not indicate an update problem; it is a communication problem between the slave and master server. If the slave can not write data to the master anymore, then you keep seeing the old version number. Another possibility is the ISPConfig cron and server.sh cronjobs are not running anymore on that slave node, maybe you commented them out in the root crontab.
     
  3. lccwill

    lccwill New Member

    Ah ok. That makes more sense. What should I check on that slave node to fix its communication with the master node?

    The root crontab for that slave node hasn't been modified; all lines are enabled. There are 4 entries: acme.sh, server.sh, cron.sh, and create_daily_nginx_access_logs.sh. server.sh and cron.sh are configured with * * * * *
     
  4. lccwill

    lccwill New Member

    This is from another post where the user needed help testing comms between master and slave nodes. I've tested both localhost and the master node- both tests were successful. I'm not sure where the communication issue is at then.
     

Share This Page