Image uploading fails after upgrading Ubuntu to 16.04 and fog to latest version.
-
@Quazz I changed settings as you suggested, but same error occurs.
-
@alismayilov Does the upload process stop? If it continues, does the resulting image work ok?
Just want to figure out if it’s actually something serious or just looks scary.
-
@Quazz Upload process stop. I don’t see any image on the server later. And task stays active on the Fog.
-
This picture reads, to me, that there’s a problem with the HDD.
-
@Tom-Elliott It is my understanding that this refers to the client HDD, yes? If so, I would find it odd if this were to suddenly happen to several computers.
-
@Quazz Still looks like a bad hard drive.
I would almost suspect the “mode” in which the drive is setup could be the cause. Maybe it’s in RAID mode when it should be in AHCI or IDE?
-
@Tom-Elliott I tested other laptops. All of them has this error. But at the end this message appears:
"
Cloned successfully.- Image captured
- Stopping FOG STatus Reporter … Done
- Task Complete
- Updating database … Failed
- Error returned: * Reattempting to update database … failed
- Error returned: * Reattempting to update database …failed
… (several times of this message)
"
May be an error in the screenshot is not important error. I am checking other settings.
-
@Tom-Elliott @Quazz Yes, it refers to the client HDD. I could not find anything useful. In apache2 error log, it says “PHP warning: ftp_login(): Login incorrect.” Could this be a reason? But I don’t understand, if ftp login does not work how pxe works and client can get image from server?
-
@Tom-Elliott How can I check “mode”?
-
@alismayilov said in Image uploading fails after upgrading Ubuntu to 16.04 and fog to latest version.:
“PHP warning: ftp_login(): Login incorrect.”
That’s probably exactly the reason. Bad Storage Node credentials will cause the Database Updating part to fail, now. Look in the wiki for “Troubleshoot FTP”.
-
@alismayilov As Wayne already said you should read this wiki artice on how to fix the “update database” issue. The other messages are not related I am pretty sure.
-
I was under the impression uploading stopped when you started seeing the ata errors. This would, if it were true that imaging stopped when these errors appeared, indicate an HDD issue or one that’s about to occur. The other side of the coin is what version of FOG you’re running. In the past the code that handled progress reporting to the GUI had a buffer overflow of which @Sebastian-Roth and I were able to figure out, which should prevent the “strange” display. Based on what I’m gathering, your “latest version” is 1.2.0? See latest version doesn’t help us out at all because it’s relative to what you’re running. If you’re running “stable” 1.2.0 is the latest. If you’re on the RC wagon, the latest version would be 1.3.0-RC-8. If you’re only running developmental builds the latest version would be 24. You understand?
As @Wayne-Workman and @Sebastian-Roth have pointed out, it appears, then, that imaging for capture/deploy is working properly, but the login information in regards to FTP is wrong in which case https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP will help you out.
-
@alismayilov Please read through this: https://lime-technology.com/forum/index.php?topic=45792.0
Possibly the PCs you have are just not assembled properly?! Check the (S)ATA cables and try different ones to see if it makes a difference.
Or is it a mSATA disk? Then read this: https://bbs.archlinux.org/viewtopic.php?id=195875
-
I changed ip address of my server, removed /opt/fog/.fogsettings and reinstalled fog again. Now it works like a charm. May be, there was a compatibility issue between old fog settings and new fog version. Now, I don’t see any strange error like above.
