@alexamore90 Is this a typo with IP, gateway and DNS all set to the same address?
You might want to run systemctl status isc-dhcp-server
(Debian/Ubuntu) or systemctl status dhcpd
(Redhat based distros) and post output here.
@alexamore90 Is this a typo with IP, gateway and DNS all set to the same address?
You might want to run systemctl status isc-dhcp-server
(Debian/Ubuntu) or systemctl status dhcpd
(Redhat based distros) and post output here.
@alexamore90 Did the installer finish all the way to the end? When running it there is a point where you need to open the browser and let it populate the database. If you skip this the installer will fail and needs to be run again.
The node offline sounds like the installer didn’t finish properly.
@ksrvpvl As soon as the machine is registered in the FOG web UI a task can be scheduled. This would send WOL packets to wake up the machine and let it PXE boot straight into the scheduled task.
@Tauric From the pictures we see that FOG recognized the filesystem as NTFS and should be able to resize it. It’s still strange the size was larger. Good you got this fixed by reinstalling the master to capture from. No idea what could have been wrong with the other one.
@tomynocker Looks like you used the wrong field. Such an options need to go in Kernel Parameter.
@matthewadams12 It depends on the partitioning and filesystems used. If Ubuntu is installed with LVM it will be captured sector by sector (large). But if you choose plain GPT or MBR partitioning FOG should be able to capture the used space only.
Hi FOGers!!
We have some strange issues when we upload images to the server and we don´t have find the reason of this behaivour.
The issue appears when the server try to move the image from /images/dev/abcdefg12345 directory to the destiny, the FTP can´t move the file or the directory and the destiny directory appears empty.
In the vsftpd log appears the error:
Tue Oct 31 14:00:26 2023 [pid 2855049] [fogproject] FTP command: Client "10.0.15.8", "LIST -a images"
Tue Oct 31 14:00:26 2023 [pid 2855049] [fogproject] FTP response: Client "10.0.15.8", "150 Here comes the directory listing."
Tue Oct 31 14:00:26 2023 [pid 2855049] [fogproject] FTP response: Client "10.0.15.8", "226 Directory send OK."
Tue Oct 31 14:00:26 2023 [pid 2855049] [fogproject] FTP command: Client "10.0.15.8", "RNFR /images/dev/8cec4b6xxxxx"
Tue Oct 31 14:00:26 2023 [pid 2855049] [fogproject] FTP response: Client "10.0.15.8", "550 RNFR command failed."
Tue Oct 31 14:00:26 2023 [pid 2855049] [fogproject] FAIL RENAME: Client "10.0.15.8", "/images/dev/8cec4b6xxxxx"
Tue Oct 31 14:00:26 2023 [pid 2855049] [fogproject] FTP command: Client "10.0.15.8", "QUIT"
Tue Oct 31 14:00:26 2023 [pid 2855049] [fogproject] FTP response: Client "10.0.15.8", "221 Goodbye."
The permissions in /images is:
drwxrwxrwx 295 fogproject apache 16384 nov 3 09:40 images
We have migrated the old server, fog 1.5.5, to the last one, fog 1.5.10, we made a fresh install but we migrated the storage from the old one to the new one. Then in /images we have a mix of owners XD:
drwxrwxrwx 2 root root 280 ago 24 10:27 aula-vc-filologia-aulavhm2-alumno3450
drwxrwxrwx 2 fogproject apache 226 jul 26 2022 aula-vc-filologia-aulavhm2-profesor
drwxrwxrwx 2 root root 280 ago 24 14:52 aula-vc-filologia-aulavhm2-profesor3450
drwxrwxrwx 2 root root 226 jul 19 12:28 aula-vc-filologia-aulavhmm-docencia
drwxrwxrwx 2 fogproject apache 226 mar 8 2023 aula-vc-filologia-aulavhmm-docencia-LTSC
drwxrwxrwx 2 root root 226 ago 25 12:36 aula-vc-filologia-aulavht1-cabina
drwxrwxrwx 2 root root 226 ago 28 09:55 aula-vc-filologia-aulavht1-profesor
drwxrwxrwx 2 fogproject apache 226 abr 29 2021 aula-vc-filologia-aulavht1-roomserver
The question is easy Who is the owner of images directories?
@w2log Does this SuperMicro X12 have more than two NICs onboard? Then it’s probably a bug in FOG fixed in the latest dev-branch version already.
@infotc While a clean migration would surely get you to a nice clean system you can first try to get this fixed manually.
There is some logic in the FOG installer that should take care of the different package names that have changed over the years (php-mysql vs. php-mysqlnd).
Please run the following command to see what PHP packages exactly are installed at the moment:
dpkg -l | grep php
Post the output here.
Edit /opt/fog/.fogsettings
and make sure only php-mysql
(but not php-mysqlnd
) is in the packages line.
As well you might want to manually install the package needed - see if that gives you an error as well:
apt install php-mysql
@lan Which version of FOG do you currently use?
Quite possibly this is fixed in the latest dev-branch version already (fix on github).