FOG Server Failed to update: Installing now everything is updated ........Failed

[cojohnson]

@Tom-Elliot I am currently running sudo dpkg --configure -a

[cojohnson]

@Tom-Elliott So, I reran thew installer after the dpkg command finished. FOG sucessfully updated! Now, the nodes are not able to establish a database connection?? Should I rerun the installer on the nodes? The images I am trying to deploy are failing

FOG Version Information
Running Version: 1.4.4

Kernel Versions
DefaultMember FOG Version: ()
fog-node106 FOG Version: ("A valid database connection could not be made"1.4.4)
bzImage Version: 4.11.0
bzImage32 Version: 4.11.0
fog-node107 FOG Version: ("A valid database connection could not be made"1.4.4)
bzImage Version: 4.11.0
bzImage32 Version: 4.11.0
fog-node108 FOG Version: (1.4.4)
bzImage Version: 4.11.0
bzImage32 Version: 4.11.0
fog-node109 FOG Version: (1.4.4)
bzImage Version: 4.11.0
bzImage32 Version: 4.11.0
fog-node118 FOG Version: ()
fog-node119 FOG Version: ()

[cojohnson]

Okay, I rebooted all of the FOG Nodes and the Server. The database connection error went away!

Since I cant upload images to this forum, I took the time to type this all out!

I still cant deploy images though. The error i get when i am imaging is something like:

read ERROR:No such file or directory
ARGS passed: /images/My_Image_Name/d1p2.img* /dev/mmcblk0p2

will continue in 1 minute

clearing ntfs flag…Failed
Resizing Ntfs volume (/dev/mmcblk0p2)…Failed
An Error has been detected!
could not resize /dev/mmcblk0p2) (expandPartition)
info: ntfsresize v2016… (libntfs=3g)
Failed to open ntfs attribute: No such file or directory
Failed to load $MFT: No such file or directory
ERROR(2): Opening ‘/dev/mmcblk0p2’ as NTFS failed: No such file or directory
Args passed: /dev/mmcblk0p2

Kernal Vairiables and settings:
Most importantly (I think) chkdsk=0

Any ideas?

[Wayne Workman]

@cojohnson said in FOG Server Failed to update: Installing now everything is updated ........Failed:

fog-node106 FOG Version: ("A valid database connection could not be made"1.4.4)

That error has in the past been FTP related issues, I’d suggest running through these tests on that node: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

[cojohnson]

@Wayne-Workman
I am out of the office right now! But when I get in tomorrow I will run some tests! I do not think this is the problem however because my image deployment does start (partclone starts) and it gets about 1.7 GB through before fails… I will verify tomorrow though! I think it may have something to do with the fog nodes not picking up the “check disk disabled” option enabled on the server?

[Wayne Workman]

@cojohnson I don’t think image deployment is reliant on FTP. However capture, replication, and kernel version reporting is. Which is why I suggest troubleshooting FTP.

[Quazz]

@cojohnson mmcblk is typically an SD card or similar, which is probably why it fails at that point, it runs out of space. Remove the SD card!

[cojohnson]

@Wayne-Workman FTP is working i was able to get files from the fog nodes!

[cojohnson]

@Quazz mmcblk? in the client devices or the servers? Our fog servers are 7-8 year old desktop PCs and only have 1 normal sata HDD installed

[Quazz]

@cojohnson The client

I believe in some configurations it can also refer to eMMC memory or the like, though.

[cojohnson]

@Quazz I am imaging HP Stream 11 G3s. They have a 64 GB eMMC HDD. I am only pushing a 20 GB image. The error i am getting happens on all of the Streams

http://store.hp.com/us/en/pdp/hp-stream-11-pro-g3-notebook-pc-(energy-star)

[Quazz]

@cojohnson Looks like a Read error happens somewhere down the line. Does this image work on other models?

[Tom Elliott]

So updating FOG is fixed? Can we move the next issue into a new thread so as to keep things more direct/distinct as to issues encountered and what not?

I’m confused by this posting now. Sorry if this seems rude, but it sounds like you’re no longer having an issue with “Failed to update” anymore.

[cojohnson]

@Tom-Elliott I reran the installer script a second time on the nodes and that seemed to fix my problems! I want to thank everyone for your support and ideas! Much Appreciated!