Posts made by TaTa

@Daniel-Miller I created the files but it’s still not working. This is a new installation. I don’t think it looks into .fogsettings before creating this new account.

@Sebastian-Roth I changed it to 14 and 16 but is getting this error. Looks like password is not complex enough

Changing shell for fogproject.
New password: BAD PASSWORD: The password contains less than 1 digits
Retype new password: BAD PASSWORD: is too simple
Retype new password: Password change aborted.
New password: Password change aborted.
New password: Password change aborted.
passwd: Have exhausted maximum number of retries for service
Changing password for user fogproject.
New password: Retype new password: Retype new password: Password change aborted.
New password: Password change aborted.
New password: Password change aborted.
passwd: Have exhausted maximum number of retries for service
New password: BAD PASSWORD: The password contains less than 1 uppercase letters
Retype new password: BAD PASSWORD: is too simple
Retype new password: Password change aborted.
New password: Password change aborted.
New password: Password change aborted.
passwd: Have exhausted maximum number of retries for service
Changing password for user fogproject.
New password: Retype new password: Retype new password: Password change aborted.
New password: Password change aborted.
New password: Password change aborted.
passwd: Have exhausted maximum number of retries for service
Changing password for user fogproject.
New password: Retype new password: Retype new password: Password change aborted.
New password: Password change aborted.
New password: Password change aborted.
passwd: Have exhausted maximum number of retries for service
Changing password for user fogproject.

@Sebastian-Roth Thank you! I’m getting a bit further. The installer can’t set a password for fogproject account due New password: BAD PASSWORD: The password is shorter than 14 characters. Is there a way I can set it manually or change password length in the script so will be 14 characters or more?

@Sebastian-Roth I get ls: cannot access /var/lib/mysql*: No such file or directory.

mysql-community-libs-5.7.26-1.el7.x86_64
php-mysqlnd-7.2.24-1.el7.remi.x86_64
mysql-community-libs-compat-5.7.26-1.el7.x86_64
mariadb101u-config-10.1.35-1.ius.el7.x86_64
mysql-community-devel-5.7.26-1.el7.x86_64
nagios-plugins-mysql-2.2.2-2.20190926git1b8ad57.el7.x86_64
mysql-community-client-5.7.26-1.el7.x86_64
mysql-community-common-5.7.26-1.el7.x86_64

Last few lines in error log:

Package(s) mariadb available, but not installed.
Package(s) mariadb-server available, but not installed.
No packages marked for update
Loaded plugins: package_upload, product-id, search-disabled-repos, subscription-
              : manager
Package mariadb-server is obsoleted by mysql-community-server, trying to install mysql-community-server-5.7.26-1.el7.x86_64 instead
Resolving Dependencies
--> Running transaction check
---> Package mysql-community-server.x86_64 0:5.7.26-1.el7 will be installed
--> Processing Conflict: 1:mariadb101u-config-10.1.35-1.ius.el7.x86_64 conflicts mysql-community-server
--> Finished Dependency Resolution
Error: mariadb101u-config conflicts with mysql-community-server-5.7.26-1.el7.x86_64
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

I’m getting Installing package: mariadb-server..........................Failed! (Will try later)

@Sebastian-Roth Thank you. What are the risks?

@Sebastian-Roth You are absolutely correct. This server was built and is managing by another team outside of our institution. We don’t have direct control over it.

Hello All,

I’m getting some issues with installation FOG on RHEL7.7 (I have a working box with Debian but we have to migrate it to RHEL due to some policy reason). The installation stop at Installing now everything is updated ........Failed…Upon inspecting fog_error_1.5.7.50.log, I saw a bunch of errors like this:

Update notice FEDORA-EPEL-2014-4398 (from epel) is broken, or a bad duplicate, skipping.
Update notice FEDORA-EPEL-2019-4e237c3a93 (from epel) is broken, or a bad duplicate, skipping.
Update notice FEDORA-EPEL-2016-b072b4c9c7 (from epel) is broken, or a bad duplicate, skipping.

and

Package mariadb-server is obsoleted by mysql-community-server, trying to install mysql-community-server-5.7.26-1.el7.x86_64 instead
Resolving Dependencies
--> Running transaction check
---> Package mysql-community-server.x86_64 0:5.7.26-1.el7 will be installed
--> Processing Conflict: 1:mariadb101u-config-10.1.35-1.ius.el7.x86_64 conflicts mysql-community-server
--> Finished Dependency Resolution
Error: mariadb101u-config conflicts with mysql-community-server-5.7.26-1.el7.x86_64
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Does anyone have any experience or has anyone encountered this similar issues?

Thanks in advance for any assistance.

@Sebastian-Roth Thank you very much. We had an outage last week so I didn’t have time to follow up. I just upgraded to latest dev-branch and things are working now. Advanced menu is working as it was before. Thanks everyone involved!

@Sebastian-Roth Whenever I selected Advanced Menu and signed in, the machine will either beep or display a black screen (sounded like missing RAM beeping sound). I installed dev-branch on a test server with fresh installed ubuntu 18.04 with same issues.

@kafluke It happens to me too. Also on the latest dev-branch, Advance Menu has stopped working.

@Sebastian-Roth @Wayne-Workman Thank you for reminding me about another DHCP server. I double checked with our network admin and we found the old IP in DHCP server. We did some tests before but couldn’t get pxe to work so we opted for dnsmasq option and left the IP there.
Thank you again for your help!

We have to migrate our servers to a different building so we need to change our FOG IP. I follow instructions to change the server IP and IP in FOG website as instructed in here: https://forums.fogproject.org/topic/10841/problems-after-changing-fog-server-ip/2. I even ran updateIP tool and reran the installation several times. Client boots up fine but when it gets the palce to download default.ipxe file through tftp, it is still looking for the OLD server IP. FOG is running on Debian 8.11 with DNSMASQ 2.76. I checked dnsmasq configuration file and it does have the new IP and it’s not providing tftp service. I’m using tftpd-hpa for TFTP service . config.class.php does have the new IP as well. What am I missing here?

Thanks in advance for your helps or suggestions.

@nsherin I didn’t use any other files beside the ones came with 18.04.1 LTS. Can you re-extract all files in 18.04.1LTS iso and then reupload them back to /images/os/ubuntu/18.04/mate. You might need to add this line to your /etc/exports file and restart nfs services or restart your fog server.

/images/os/ubuntu/18.04/mate *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)

Internet connection is still an issue with this method. You need to go to /etc/network/interfaces and change from manual to dhcp then restart your interface sudo /etc/init.d/networking restart

You need to add initrd=initrd.lz. I found it here: https://forums.fogproject.org/topic/11063/ubuntu-17-10-desktop-pxe-boot-no-internetl and it worked for me.

Your code should look something like this.

kernel nfs://192.168.0.14/images/os/ubuntu/18.04/mate/casper/vmlinuz
initrd nfs://192.168.0.14/images/os/ubuntu/18.04/mate/casper/initrd.lz 
imgargs vmlinuz initrd=initrd.lz root=/dev/nfs boot=casper netboot=nfs nfsroot=192.168.0.14:/images/os/ubuntu/18.04/mate/ locale=en_GB.UTF-8 keyboard-configuration/layoutcode=gb quiet splash toram ip=dhcp rw
boot || goto MENU

@Sebastian-Roth @Tom-Elliott Huge thanks for the fix. 1709 is uploading after updating init and init_32.

@Sebastian-Roth Thanks a million. You’ve nailed it. I’ve tested it and it is the case with Sierra.

@CoolbluHat as Sebastian Roth said, you need to bless your clients (SIP must be disabled) or you can create a bootable usb

1. Format USB as FAT32
2. create folders in USB drive EFI\BOOT
3. Copy ipxe.efi in your tftpboot directory in your FOG server to EFI\boot and rename this file to bootx64.efi (try different *.efi files if this one does not work)

Prepare to upload image:
Like you do for Windows machines, create a standard image, add a new host for this Mac
create a new image in Image Management. Select Apple Mac OS, Multiple Partition Image - Single Disk
Schedule an image capture
Boot up this Mac using USB (hold down alt and select EFI).

You might need to grow the disk if you download the image to a bigger drive.

This method does not work for all Macs at least does not work on my MacBook Air early 2014 but worked on MacBook Air late 2015 using thunderbolt to ethernet with ssd formatted in 4K cluster size and most of the models with a built-in Ethernet card.