• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. kibade
    3. Posts
    K
    • Profile
    • Following 0
    • Followers 0
    • Topics 5
    • Posts 27
    • Best 2
    • Controversial 0
    • Groups 0

    Posts made by kibade

    • RE: Installing 1.5.9 on Debian Bullseye fails

      @george1421 Just installed the Dev-Branch and it worked. Everything looks great šŸ™‚
      Thanks.

      One minor point, even though I selected N for DHCP service

      * Using FOG DHCP: No
       * DHCP will NOT be setup but you must setup your
       | current DHCP server to use FOG for PXE services.
      

      It still installed isc-dhcp-server

      * Installing package: isc-dhcp-server.........................OK
      

      I confirm it didn’t enable dhcp, just odd that it installed the package.

      * Setting up and starting DHCP Server.........................Skipped
      
      systemctl status isc-dhcp-server.service
      ā— isc-dhcp-server.service - LSB: DHCP server
           Loaded: loaded (/etc/init.d/isc-dhcp-server; generated)
           Active: failed (Result: exit-code) since Mon 2022-10-31 09:48:44 PDT; 5min ago
             Docs: man:systemd-sysv-generator(8)
              CPU: 47ms
      
      Oct 31 09:48:42 fog dhcpd[53890]: before submitting a bug.  These pages explain the proper
      Oct 31 09:48:42 fog dhcpd[53890]: process and the information we find helpful for debugging.
      Oct 31 09:48:42 fog dhcpd[53890]:
      Oct 31 09:48:42 fog dhcpd[53890]: exiting.
      Oct 31 09:48:44 fog isc-dhcp-server[53875]: Starting ISC DHCPv4 server: dhcpdcheck syslog for diagnostics. ...
      Oct 31 09:48:44 fog isc-dhcp-server[53895]:  failed!
      Oct 31 09:48:44 fog isc-dhcp-server[53896]:  failed!
      Oct 31 09:48:44 fog systemd[1]: isc-dhcp-server.service: Control process exited, code=exited, status=1/FAILURE
      Oct 31 09:48:44 fog systemd[1]: isc-dhcp-server.service: Failed with result 'exit-code'.
      Oct 31 09:48:44 fog systemd[1]: Failed to start LSB: DHCP server.
      
      posted in FOG Problems
      K
      kibade
    • Installing 1.5.9 on Debian Bullseye fails

      I have a fresh Debian Bullseye install. I cloned fog 1.5.9. Running ./install.sh initially failed on the php-gettext, but found on this forum that you edit lib/ubuntu/config.sh and change php-gettext to php-php-gettext. That worked.

      However, now it failed with this error:

      Failed to stop php-fpm.service: Unit php-fpm.service not loaded.
      

      It should be called php7.4-fpm.service

      systemctl status php7.4-fpm.service
      ā— php7.4-fpm.service - The PHP 7.4 FastCGI Process Manager
           Loaded: loaded (/lib/systemd/system/php7.4-fpm.service; enabled; vendor preset: enabled)
           Active: active (running) since Thu 2022-10-27 15:15:51 PDT; 22min ago
      

      Is there a method I could correct this on my install like I did with the package list?

      posted in FOG Problems
      K
      kibade
    • RE: Dev branch 1.5.9.79 Installing package: php-gettext.............................Failed! has to use -X switch to get it to work.

      @kibade I did the editing of the lib/ubuntu/config.sh, posted on the forum as a fix, seemed to work, but I have a new fail with ā€œFailed to stop php-fpm.service: Unit php-fpm.service not loaded.ā€ However, the service is called ā€œphp7.4-fpm.serviceā€

      I look to see if anyone has solved this here.

      posted in Bug Reports
      K
      kibade
    • RE: Dev branch 1.5.9.79 Installing package: php-gettext.............................Failed! has to use -X switch to get it to work.

      Is this bug still open? I just installed Debian Bullseye and fog 1.5.9 and I get this when installing fog:
      ā€œ* Installing package: php-gettext…Failed! (Will try later)ā€

      I see the correct package is php-php-gettext

      How do I get the install to pick the correct package?

      Thanks,

      posted in Bug Reports
      K
      kibade
    • RE: HostNameChanger unable to join domain V1.3.4

      This is a Face Palm picnic error!

      I was updating the main fog settings. I was thinking if I changed that setting it would change it for all hosts. I forgot I have to edit the host information to make a change to a existing host. (Did this via a group)

      Still, my username and password hadn’t changed between the fog upgrade, so something was wrong, but I should have spotted my error when trouble shooting šŸ™‚

      This ticket can be closed

      posted in FOG Problems
      K
      kibade
    • RE: HostNameChanger unable to join domain V1.3.4

      I forgot to say all the computers are running win7 pro

      posted in FOG Problems
      K
      kibade
    • HostNameChanger unable to join domain V1.3.4

      I’ve setup a computer as normal. I’ve always just before imaging removed the computer off the domain and renamed the computername to something random. Capture the image and deploy to my lab. Since my upgrade from 1.2.4 to 1.3.4 no computer will join the domain automactially.
      The computer name is correctly changed, just no joining onto the domain. In the fog.log I get
      HostnameChanger Hostname is correct
      HostnameChanger Attempting to join domain
      HostnameChanger Logon failure: unknown username or bad password, code = 1326.

      I can manually add any of these computers to the domain, confirming the username and password is correct.
      In fog settings I’ve tried only using the FOG_AD_DEFAULT_PASSWORD, allowing it to encrypt the password for me. I’ve tried only using FOG_AD_DEFAULT_PASSWORD_LEGACY, with me using FOGCrypt.exe to first encrypt my password. I’ve also tried both being set.

      I also tried removing the newer fog service of the computer and restoring the original on the computer. No change. Not sure what to try next.

      posted in FOG Problems
      K
      kibade
    • RE: Issues with advanced tasks

      @george1421 OK. Thanks

      posted in FOG Problems
      K
      kibade
    • RE: Issues with advanced tasks

      @george1421 Is the donate task meant to work for 1.3.3 as far as you know?

      posted in FOG Problems
      K
      kibade
    • RE: Issues with advanced tasks

      It was more of a bug report. I currently have 1.3.3 running nicely. It captures and deploys fine. I was running clamav just because it was a different AV to the one I have, might catch something the other one missed, no big deal. The donate was a curiosity as the fog team deserve something for this product, I was just exploring options. I listed it as an issue only because it was a feature, when I tried it, it didn’t work šŸ™‚

      posted in FOG Problems
      K
      kibade
    • Issues with advanced tasks
      Server
      • FOG Version: 1.3.3
      • OS: Debian Jessie
      Client
      • Service Version:
      • OS: Win7
      Description

      I’m using 1.3.3. I’ve tried the following advanced tasks, clamav and donate. Both report errors and reboot.
      Clamav complains it can’t mount /opt/fog/clamav that is because there is no clamav in /opt/fog

      /opt/fog# ls
      log service snapins

      Donate lets me know it can be stopped if I press a key, it going looking for servers, says it will power down the monitor, then a message says ā€œ/bin/fog.donate.monitor: line 8: clearscreen: command not foundā€

      It then reboots and ends the task.

      Mem test works.
      Haven’t been able to test other tasks

      posted in FOG Problems
      K
      kibade
    • RE: Quick registration stop auto deploy of image

      @Tom-Elliott It’s working perfectly, thanks šŸ™‚

      posted in General Problems
      K
      kibade
    • RE: Quick registration stop auto deploy of image

      @Tom-Elliott Awesome. I’ll try that now, makes sense that this will work. I’ll post back how it went.
      Thanks

      posted in General Problems
      K
      kibade
    • RE: Client system will not load pxe image

      @rbasart The normal reason you don’t have this is the fog installed failed before it finished installing. .fogsettings is the last thing it does. Can you re-run ./install.sh and see if anything says ā€œfailedā€ please?

      posted in FOG Problems
      K
      kibade
    • RE: Quick registration stop auto deploy of image

      @Tom-Elliott This is what I have. I couldn’t find much on the quick reg settings, so mainly used the ā€œ?ā€ info. I might have misunderstood what it wanted?
      0_1485900585798_upload-52a77a02-15b7-41fb-835c-217ba13e407a

      posted in General Problems
      K
      kibade
    • RE: Client system will not load pxe image

      @rbasart Can you check for me what you have under /opt/fog/.fogsettings

      I’m most interested if your sql user fog password matches
      snmysqluser=ā€˜fog’
      snmysqlpass=ā€˜ā€™

      posted in FOG Problems
      K
      kibade
    • RE: Quick registration stop auto deploy of image

      Sorry Tom, I can see the AUTOREG. I only want to stop the image at the end of the registration, everything thing else is great.

      posted in General Problems
      K
      kibade
    • RE: PartClone fail on deploy - error code 1

      @coop90 Strange as 14 seconds in that is the error. I’ve seen this before. When I examined the two drives, one was a few blocks smaller. Admittedly the two drive were not the same make, to might not be the same issue. I bet if you shrink the original computers partition and re-upload it works.

      posted in FOG Problems
      K
      kibade
    • RE: Quick registration stop auto deploy of image

      I had a few problems when I upgraded fog to 1.3.3, in the process the sql database had to be re-installed and I lost the fog database. (My fault) So as far as Fog is concerned, it’s never seen these computers before, but they are all up to date. I just want to add them to the database, not -re-image them. I’ll look into the AUTOREG. Not seen this option, will try and find it.
      Thanks

      posted in General Problems
      K
      kibade
    • RE: PartClone fail on deploy - error code 1

      The error is saying the target computer has a smaller HDD than the computer the imaged came from. Can you check and see if the image is from a computer with a larger HDD.

      posted in FOG Problems
      K
      kibade
    • 1 / 1