@Doctrg Might be worth trying https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#Try_to_get_a_file_with_Windows:
I found my fog user password had changed, showed up on a simple ftp open test.
Also under storage management on the web GUI, double-check your paths.
@Wayne-Workman Thanks for yours and Toms advice. It’s working 
I found the Linux user “fog” password had changed. Must have missed that on the upgrade. I found it by trying to connect via ftp from a windows machine to the fog server as per : https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#Try_to_get_a_file_with_Windows:
I still found the capture looped, I found in the apache/error.logs the following:- (bold is the important bit)
[Mon Jan 23 14:18:52.008806 2017] [:error] [pid 22907] [client 192.168.0.207:46956] PHP Fatal error: Uncaught exception ‘Exception’ with message ‘Type: 2, File: /var/www/fog/lib/fog/fogftp.class.php, Line: 708, Message: ftp_put(/images/dev/64006a90ca4a): failed to open stream: No such file or directory, Host: 192.168.0.3, Username: fog’ in /var/www/fog/lib/fog/fogftp.class.php:367\nStack trace:
n#0 /var/www/fog/lib/fog/fogftp.class.php(772): FOGFTP->ftperror(Array)\n#1 /var/www/fog/lib/reg-task/taskqueue.class.php(366): FOGFTP->rename(‘/images/dev/640…’, ‘/images/Default…’)\n#2 /var/www/fog/lib/reg-task/taskqueue.class.php(413): TaskQueue->_moveUpload()\n#3 /var/www/fog/service/Post_Stage2.php(24): TaskQueue->checkout()\n#4 {main}\n thrown in /var/www/fog/lib/fog/fogftp.class.php on line 367
My storage location is /var/backups/images
I looked back into the fog storage management setting and noticed something I had over looked, we have an extra setting FTP path.
It was set to /images, I corrected to /var/backups/images.
The original storage path was correct.
Works now
@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.
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?
@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.
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,
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
I forgot to say all the computers are running win7 pro
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.
@george1421 Is the donate task meant to work for 1.3.3 as far as you know?
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