New Lenovo M900 Tiny Computers
-
@Wayne-Workman, I just looked the logs in FOG, and it appears as though there may be an FTP credential issue? I see this over and over.
[Wed Jul 13 08:34:33.547856 2016] [:error] [pid 5725] [client 10.15.32.99:36668] PHP Warning: ftp_login(): Login incorrect. in /var/www/html/fog/lib/fog/fogftp.class.php on line 107
-
@Towndrunk That is what I was suspecting. When the files don’t get moved (but remain in the /images/dev folder), its typically an FTP authentication issue. This is where the (linux) fog account password isn’t in line with the password defined for the storage node configuration.
-
@george1421 In this case, since he went to trunk recently, I’m wondering if it’s a bad username/password or not because the installer now checks to see if the DB’s node credentials match what it’s setting the local fog account to. I suppose the credentials could have been changed manually at a later time after the installer ran.
@Towndrunk Simply re-running the installer should correct the ftp credentials, you might also check what credentials you have stored inside of
/opt/fog/.fogsettingsand set what you want there. -
This happened the yesterday when I did the install as well. I’m using Ubuntu 14.04, and during the install of Trunk my screen turns off after being inactive for a certain amount of time. When I bring it back up, my password to log in is no longer valid. I have to get into the GRUB prompt to get back in. I don’t know if the install even really finished or not.
-
@Wayne-Workman, I don’t believe I ever set a password for SQL. During the initial installation it asked if I wanted a password, and said to leave it blank if I didn’t want one. I wasn’t to worried about it since the server was used for FOG and nothing else.
I just ran the Trunk install again, and made sure the entire install went through. Afterwards I checked the contents of the /opt/fog/.fogsettings and here is what I found.
ipaddress=‘10.15.31.20’
interface=‘eth0’
routeraddress=‘option routers 10.15.31.1;’
plainrouter=‘10.15.31.1’
dnsaddress=‘option domain-name-servers 8.8.8.8;’
dnsbootimage=“8.8.8.8”;
password=“6GtO35zHL+Ypw7VVFu+i7S4kp2keVoDv0rHurDnjI7Y=”
osid=‘2’
osname=‘Debian’
dodhcp=‘n’
bldhcp=‘0’
installtype=‘N’
snmysqluser=‘root’
snmysqlpass=“”
snmysqlhost=‘localhost’
installlang=‘’
donate=‘0’
fogupdateloaded=1
submask=‘’
dhcpd=‘’
blexports=‘1’
storageLocation=‘/images’
username=‘fog’
docroot=‘/var/www/html/’
webroot=‘/fog/’
caCreated=‘yes’
startrange=‘’
endrange=‘’
bootfilename=‘undionly.kpxe’
packages=‘apache2 build-essential cpp curl g++ gcc gzip htmldoc lftp libapache2-mod-php5 libc6 libcurl3 m4 mysql-client mysql-server net-tools nfs-kernel-server openssh-server php5 php5-cli php5-curl php5-fpm php5-gd php5-json php5-mcrypt php5-mysqlnd php-gettext sysv-rc-conf tar tftpd-hpa tftp-hpa vsftpd wget xinetd zlib1g ’
noTftpBuild=’’
notpxedefaultfile=‘’
sslpath=‘/opt/fog/snapins/ssl/’
backupPath=‘/home/’
php_ver=‘5’
php_verAdds=‘-5.6’ -
I’m starting to wonder if at this point it may be best to just remove FOG and re-install it again. I have nothing in there at this time that I can’t afford to lose.
-
@Towndrunk This is the fog password and FTP password:
password="6GtO35zHL+Ypw7VVFu+i7S4kp2keVoDv0rHurDnjI7Y=“If you don’t like that, you can change it and re-run the installer - it will update everything for you.
-
@Wayne-Workman, thank you. I changed that password, and re-installed Trunk. Oddly I wasn’t locked out of this time like I had been in the past. I also wasn’t prompted to update the DB like before. Something that was cleared by restarting the SQL DB.
I was able to Register my Windows 7 machine, and capture an image from the PC.
I was also able to deploy that image to another PC that I had registered, and it worked as it should.The issue that I’m still having is associated with the Windows 10 PC that I performed a custom install on, wiping all partitions on the drive during the installation.
When I try and capture and image, I fails with the following message. I’m assuming it has something to do with the drive? When I ran the compatibility test earlier though, it didn’t detect any issues.
Failed to complete capture (savePartition)
Args passed: /dev/sda2 1 /images/002324b78577 all -
@Towndrunk There should be a step where it reports an error prior to that if I’m not mistaken, that should tell us more about why that failed.
But as a stab in the dark I’m going to say you need to turn off Fast Startup and do a chkdsk /f on your windows partition.
-
@Quazz, I followed your recommendation and turned off Fast Startup and ran a chkdsk. FOG was able to capture and image, however it was very slow. Had a few moments where I thought it was going to fail since it sort of stopped doing anything. It did complete, and rebooted when done though.
I’m in the process of trying to deploy that image to another PC right now to make sure that it is working as it should.
-
Things appear to be working now for all three instances. Default Windows 7 install, upgrade to Windows 10 install, as well as the drive that was loaded from the Windows 10 disk. I’m going to do a few more tests to make sure things continue to work as they should, but it look promising.
I do have one question, and I’m not sure if this is due to the upgrade or not. When I do a full inventory on a new host, it asks at the end would you like to deploy this image now. In the past, it would just deploy the image right away, but for me to get it to work now, I have to reboot. Is that normal, or am I just mistaken and it would always reboot?
-
@Towndrunk It always reboots.
-
@Tom-Elliott, thanks. I believe we can close this thread. Things are working now as far as a Capture/Deploy aspect goes. I’m having issues with my images not joining the domain. I have done some reading here and all of my settings appear to be correct. If I can’t get it working, I can start another thread.
Thanks for all of the help. There is no way that I would have got this working without you guys. Thanks.
