@Technolust Ok, please let us know if you need further help or how you solved the issue (might be helpful for others reading in the forums!)…

@MoonDancer said in Unable to locate image store: error invalid Login Can you post a picture of that error? Have you ever logged in (or more important changed the password) of the Linux system account called fog? Please run grep -A1 -e FTP_PASS -e password /var/www/html/fog/lib/fog/config.class.php /opt/fog/.fogsettings on your FOG server console. It should print a password three times. Don’t post that here, just check if they all match up. If they do then see if the password really works. Go to another machine within your network (Windows client will do), open a command prompt and try to connect to your server via FTP using that password (I know it’s quite long!): C:\Windows\System32> ftp 10.113.2.169 Connected to 10.113.2.169. 220 (vsFTPd 3.0.3) Name (10.113.2.169:user): fog 331 Please specify the password. Password: 230 Login successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> quit 221 Goodbye. I’m wondering if a FOG update would resolve my issues. Yes it actually might solve your issue. But as we don’t really know what’s exactly wrong it’s just like shooting in darkness. Might help but could cause other issues as well. Let’s see what you get from the stuff posted above and in the other thread and take it from there.

@MoonDancer Ok, I am a bit relieved. From what you where saying at first I thought you might have a very old setup. CentOS 7.5 is fairly new and a good Linux OS. Don’t run the FOG installer yet. We’ll guide you through that later on. Possible your FOG server was setup to run in a separated network without internet connection (numbers on the login page not loading). Some people want to have it this way. It is possible but needs some extra work to be done because you cannot install or update FOG without internet connection. To check internet connection please run the following commands on the CentOS server shell: ip a s ip r s cat /etc/resolv.conf ping -c 3 9.9.9.9 ping -c 3 ix.de Take a picture and post here. In the pictures I also see you have FOG version 1.5.4 - it’s printed in the lower right corner, when you are logged in to the web UI as well. About the missing buttons for canceling tasks: I can imagine the Konquerer used as browser is not set to run JavaScript or simply unable to render those properly. As the rest seems fine and the buttons are indeed added to that view via JavaScript it’s very likely to be the case. Simply use another browser (even on a different machine within the same network) and open that URL http://10.113.2.169/fog/

@Reagan Well now I know what’s going on. Thanks for posting the picture of the log. The installer doesn’t finish and so never gets to copy the new web interface stuff. to /var/www/html/fog. So no wonder you were always stuck with 1.5.4!!! Did you notice it stopped on “Setting up fog password … Failed!”?? Please take a look at the installer error_log directory. There should be a second text file with detailed installer output. Copy and paste that (or at least the last 20 lines of it) to the forums. I can’t imagine why it would fail at that point.

@salted_cashews Correction. This is what I use for updating Debian based systems: apt-get update;apt-get -y dist-upgrade;apt-get -y autoclean;apt-get -y autoremove

@george1421 Just open thoughts on changing storage location. Update .fogsettings storagelocation field. Update /etc/exports to from /images and /images/dev to new locations /fogserver/images and /fogserver/images/dev Copy everything from /images to /fogserver/images cp -r -f /images/* /fogserver/images Make sure directory permissions match between /images and /fogserver/images In the web ui update Fog Settings->Fog Configuration Expand all settings and then search for /images and replace with proper path Go to default storage node settings and update /images to /fogserver/images Then back to the linux command prompt and rerun the fog installer script. Double check /etc/exports to ensure that /fogserver/images is still shared. Reboot the fog server At the linux command prompt key in showmount -e 127.0.0.1. It should show /fogserver/images being exported after a reboot. That should do it.

@Sebastian-Roth Thanks for checking it out. In the meantime, I ended up migrating the database to another build, and then instead of installing fog with https, I stuck with a normal install, and then reconfigured the apache2 config to redirect to https and use my certificates. Everything is working correctly now, but eventually it’d be nice to run it all in https again.

I open the FOG web UI from other browser (in this case Chrome, normally I use Firefox), and same situation. I don’t understand very well how works it. I logon successfully and appears the dashboard, if I try to search something (for example a hostname) in the search text box, how knows FOG what I am searching and where shows me the results?

@Andrew-Seals The standards for the ipxe boot loaders are: BIOS: undionly.kpxe (kkpxe only if you have problems with kpxe. UEFI: ipxe.efi (or sndonly.efi if you have problems iwht ipxe.efi) If your environment has to support both uefi and bios systems and you have a Windows 2012 or newer dhcp server or a linux dhcp server you can setup dynamic boot file assignment by following here: https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence

@anhphuong all assigned to that host. i agree that being able to select what snapins you want at the time of deploy would be nice, but the logic is tricky and there hasn’t been a lot of demand for it.

@Lenain I think that you find a bug XD. Well, I think that we can apply a workaround. Go to the database: select * from roleUserAssoc; ±------±--------±----------±----------+ | ruaID | ruaName | ruaRoleID | ruaUserID | ±------±--------±----------±----------+ | 27 | | 2 | 180 | | 96 | | 1 | 216 | Is your user in this table? Do you use the LDAP plugin?

Hola @linuxba : el uso mayoritario de FOG es para clonar discos completos, no por particiones. ¿Se puede hacer? Si, se puede hacer. La limitación es que se descarga una sola partición por tarea. ¿Cómo? Creando una imagen de una partición Creando varias definiciones de una partición Crear nueva partición: Nombre de la imagen: mi_disco_part1 Tipo de imagen: One disk / no resizable Particionado: Partition 1 only Creamos tantas imágenes como particiones tenga el disco. Subimos las particiones una a una. Luego desplegamos la particion que queramos. Esto tiene una limitación: el tamaño del disco de origen y que hay que clonar completamente el disco previamente. ==================== Google traductor Hello @linuxba: the majority use of FOG is to clone complete discs, not by partitions. Can be done? It can be done. The limitation is that only one partition is downloaded per task. How? Creating an image of a partition Creating several definitions of a partition Create new partition: Name of the image: my_disco_part1 Image type: One disk / non-resizable Partitioning: Partition 1 only We create as many images as partitions have the disk. We upload the partitions one by one. Then we deploy the partition that we want. This has a limitation: the size of the source disk and that you have to completely clone the disk previously.

@okta Ok, I’ll look into this later on.

@mstrolo Good thing we have a wiki article addressing this exact issue: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Repair_broken_database

@Sebastian-Roth I’ll add the command pacman -Sy archlinux-keyring && pacman -Syyu into the mix soon, I’m sure it’ll resolve the issue.

@maouu If this is checked and we release a new client version (within a FOG server update) it will update itself on the clients too. I’d recommend leaving that option set as it will save you a lot of work. If you don’t update the FOG server there will be no automatic client update either. As well we have not updated the fog-client package in the last releases so this is not something that happens very often right now.

Thinking a bit more about this I reckon we don’t really want to fully lock that account. It might even cause more people to ask in the forums. Better we try to inform the user as soon as we detect someone is using the account. And I mean informing beginners in particular. So for me it boils down to a couple of places we need to check and take care to inform the user. Fresh install - check if account already exists and setup a new account for the user in case it does - prompting for name and password and explaining why we do this. Upgrade with .fogettings (and therefore fog account) existing - check if the account was ever used to login on the machine (last | grep "^fog" and lastlog -u fog should do the job) and again setup a new account for the user - prompting for name and password and explaining why we do this. Print out a message to the user when opening a shell/terminal or login as fog user (~/.bashrc seems most appropriate to me) Print a X dialog when a user logs in as fog user (~/.config/autostart/ seems to be standard, works great with Ubuntu - anyone can try other distros as well?) mkdir -p /home/fog/.config/autostart/ cat >/home/fog/.config/autostart/warnfogaccount.desktop <<EOF [Desktop Entry] Type=Application Name=Warn users using the fog account Exec=/opt/fog/warnfogaccount.sh Comment=Warn users who use the fog system account to logon EOF chown fog:fog /home/fog/.config/autostart/warnfogaccount.desktop cat >/opt/fog/warnfogaccount.sh <<EOF #!/bin/bash title="FOG account" text="You seem to be using the 'fog' system account to logon and work \non your FOG server system.\n\nIt's NOT recommended to use this account! Please create a new \naccount for administrative tasks.\n\nIf you re-run the installer it would reset the 'fog' account \npassword and therefore lock you out of the system!\n\nTake care, \nyour FOGproject team" z=$(which zenity) x=$(which xmessage) n=$(which notify-send) if [[ -x $z ]] then $z --error --width=480 --text="$text" --title="$title" elif [[ -x $x ]] then echo -e $text | $x -center -file - else $n -u critical "$title" "$(echo $text | sed -e 's/ \\n/ /g')" fi EOF chmod 755 /opt/fog/warnfogaccount.sh

@sgennadi Thanks again for the report. Obviously I have missed out on purging php-mycrypt from the fogsettings automatically when we decided to not use that package for FOG anymore last Autumn. I just tested and pushed a fix to dev-branch. Please pull the latest and give it a try.

@Rhywden said in Error while installing FOG on Ubuntu 18.04: enp6s0 Do you have an IP configured on that interface enp6s0 before running the installer?? FOG does not do this for you! IP needs to be set beforehand.

@quinniedid I don know but is easy to check it :) don t use spaces in one role. You can see the entries in the database in the rule* and role* tables