Categories

• Technical Help

  Get help with your FOG system.

  FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
  13k Topics

  115k Posts

  T

  @Strahd @Strahd Those logs were exactly what I needed, thank you. Two separate things going on
  and neither one is your fault.

  First, this line is your 500:

  [proxy:error] (111)Connection refused: AH00957: FCGI: attempt to connect to 127.0.0.1:9000 (*) failed [proxy_fcgi:error] AH01079: failed to make connection to backend: 127.0.0.1

  Apache was trying to hand PHP off on port 9000 and php-fpm wasn’t listening there yet.
  Notice apache came back up at 08:57:16 and there are no more of those errors after it.
  So before you do anything else, just reload the page:

  http://10.46.10.40/fog/management

  There’s a decent chance it works now.

  Second, “Updating Database…Failed!” is the part I still need to see. That curl’s
  output goes into the install log, so please post:

  sudo grep -A5 -i "schema\|Updating Database" /root/fogproject/bin/error_logs/fog_error_1.6.0-beta.3050.log | tail -60

  That’ll tell me why the schema update itself came back an error, which is the last piece.

  Third - you found a real bug. On 1.6 the schema page makes you log in first, but the
  login reads a database column that doesn’t exist until the schema update runs. So it
  asks you to sign in, sign in can’t work, and there’s no way out. That hits everyone
  upgrading from any released FOG, not just you. I’ve fixed it and pushed it, tracked in
  #927.

  If the page is still dead, here’s the manual way to force the database update. Get your
  token:

  sudo grep FOG_SCHEMA_INSTALL_TOKEN /var/www/html/fog/lib/fog/config.class.php

  Then paste it into this:

  sudo curl -X POST -H "X-Fog-Install-Token: PASTE_TOKEN_HERE" -d "schemaupdate=1" \ "http://10.46.10.40/fog/management/index.php?node=schema"

  You want to see:

  {"msg":"Schema updated successfully!","title":"Schema Update Success"}

  I tested that against a real 1.5.9 database on PHP 7.4 here, it works.

  And to put your mind at ease - none of this touches /images or your tftpboot files. You
  are not going to lose your images over this, so please don’t rebuild the box yet.

  One last thing. Your install log still had these:

  ln: failed to create symbolic link '/lib/systemd/system/mysql.service': File exists

  I fixed those on the 27th and the current code can’t print them anymore, so I don’t think
  your checkout took. Run this and show me what it says:

  cd /root/fogproject git rev-parse --abbrev-ref HEAD git log -1 --oneline

  Thanks for sticking with this one. You’ve found two real bugs so far

• Announcements

  Get the latest news on what's happening.

  Security Advisories
  184 Topics

  825 Posts

  A

  @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

• General Topics

  View tutorials or talk about FOG in general.

  General Tutorials
  2k Topics

  19k Posts

  8

  @Cpasjuste

  Thank you, I appreciate that. And yes, I did spend a lot of time on it.

  I agree that it bypasses the official installer in order to make use of Docker environment variables; however, at this stage, I don’t believe that FOG is going to change so dramatically that it’ll break it often.

  I will add that if this could get adopted as an official docker image, we could work with the FOG team to make sure nothing gets to pushed to the FOG code that would break the container until we can adjust the container as well.

• Developers

  Report bugs, request features, or get the latest progress.

  General Feature Request Bug Reports
  2k Topics

  21k Posts

  T

  @Valer Thanks for the report and the writeup, that’s a good catch. You’re right about the cause. Debian 13 dropped the sysv-rc-conf package since it’s fully on systemd now, so the installer chokes trying to apt-get it. We never actually use that tool on a systemd system anyway, it only ever got called on the old non-systemd paths, so it was just dead weight on Trixie.

  I pushed a fix to working-1.6. It leaves the package off the list on Debian 13 and up, and it also strips it out of a cached .fogsettings so an in-place upgrade doesn’t drag it back in. Older Debian keeps installing it like before so nothing changes there.

  If you want to get moving before you pull the update, you can either grab the latest working-1.6 and rerun the installer, or just open /opt/fog/.fogsettings and delete sysv-rc-conf from the packages line, then run the installer again. Either one gets you past it.

  Let me know if you hit anything else on Trixie.