@Sebastian-Roth said:

You should never use tools like resizefs, gparted or fdisk on your system disk (sda in your case) within the running system!

I use it each time I have to extend partition on linux within the running system 😄 (I use snapshot before 😛 )

@Tom-Elliott Thank you for the quick fix.

I’ve updated the code base to urlencode the passwords and decode them once in the FTP class. I don’t know if it will fix the issue at hand, but it’s worth a shot.

@Wayne-Workman said:

Wiki has been updated about kernel updating. I made a new article because I couldn’t find anything about it.

Article is here, it is pretty sharp looking 🙂
https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update

Looks GREAT!!!

@Junkhacker said:

worth noting here is that if you create a “Mobile/Quick Image Access Only” type account you can use the pxe menu for what you want but the info will not work to log into the web interface. slightly more secure since that way you’re not sending out the admin username/password as plain text to every host that pxe boots.

So using that method, they can create a new account with “Mobile/Quick image access only” and plug that user’s username and pass into the script below to make it more secure. Nice.

Amazing what I know sometimes, even if I can’t seem to do anything right today 🙂

@Tom-Elliott The work around has helped immensely. Thank you!

Let’s see MIcrosoft or countless other vendors give this kind of support.

@Sebastian-Roth said:

But what about the “Updating Database” error on the picture in your first post? Do you still see this?

No it´s work OK

@Wayne-Workman said:

@bsmaby FTP is used to move images from /images/dev to /images. If this fails then it’s likely a simple credentials mismatch. You will find your solution in the credentials area of our FTP Troubleshooting article, here: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

SOLVED: Thank you so much! It ended up being both a miss match of passwords through out fog and also the permissions for the image folder was an owner of root and I am using a fog user instead so I had to switch the permissions to make that work. Thanks!

@bsmaby

Everything is in the link Wayne posted. Specifically, https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP#Permissions and https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP#Credentials_.2F_Passwords

Let us know if you continue to run into issues.

@Sebastian-Roth I don’t have deep understanding of FOG internal works, but I can say that when option 67 was set to prelinux.0 the kernel panicked.

@sgtrice oh and also 1.2.0 was revision number 2094.

Current revision is 6,200+ somethin. If that tells you anything… LOT of improvements.

@Eldorado There are also more generic instructions in our Wiki here:
https://wiki.fogproject.org/wiki/index.php?title=Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server

You can also configure the FOG server as a 100% mobile fog server using a project I threw together:
https://sourceforge.net/projects/fogupdateip/

This allows your FOG server to not use a set IP, and sets up dnsmasq for you. Every time the server’s IP changes, all IP settings in FOG and dnsmasq are automatically updated.

@george1421 @Wayne-Workman

Both nodes are back online now. I had a left over “-T” in /etc/default/nfs-kernel-server on the storage node from my attempts to disable NFSv4. What I was reading said NFSv3 doesn’t use TCP and is only UDP. Well, however fog connects it needs TCP with v3.

Here is where I ended, I don’t know if the RPCNFSCOUNT of 48 is needed to be increased from the default 8, but I read that this increases the threads for nfs workers.

/etc/default/nfs-kernel-server

# Number of servers to start up # To disable nfsv4 on the server, specify '--no-nfs-version 4' here RPCNFSDCOUNT='48 --no-nfs-version 4' # Runtime priority of server (see nice(1)) RPCNFSDPRIORITY=0 # Options for rpc.mountd. # If you have a port-based firewall, you might want to set up # a fixed port here using the --port option. For more information, # see rpc.mountd(8) or http://wiki.debian.org/SecuringNFS # To disable NFSv4 on the server, specify '--no-nfs-version 4' here RPCMOUNTDOPTS='--manage-gids --no-nfs-version 4' # Do you want to start the svcgssd daemon? It is only required for Kerberos # exports. Valid alternatives are "yes" and "no"; the default is "no". NEED_SVCGSSD="no" # Options for rpc.svcgssd. RPCSVCGSSDOPTS="" # Options for rpc.nfsd. RPCNFSDOPTS=""

/etc/idmapd.conf

[General] Verbosity = 0 Pipefs-Directory = /run/rpc_pipefs # set your own domain here, if id differs from FQDN minus hostname Domain = localdomain [Mapping] Nobody-User = nobody Nobody-Group = nogroup [Translation] Method = nsswitch

/etc/default/nfs-common

# If you do not set values for the NEED_ options, they will be attempted # autodetected; this should be sufficient for most people. Valid alternatives # for the NEED_ options are "yes" and "no". # Do you want to start the statd daemon? It is not needed for NFSv4. NEED_STATD= # Options for rpc.statd. # Should rpc.statd listen on a specific port? This is especially useful # when you have a port-based firewall. To use a fixed port, set this # this variable to a statd argument like: "--port 4000 --outgoing-port 4001". # For more information, see rpc.statd(8) or http://wiki.debian.org/SecuringNFS STATDOPTS= # Do you want to start the gssd daemon? It is required for Kerberos mounts. NEED_GSSD=

@MRCUR said:

KMS would be easiest for both Windows and Office.

If you have a KMS server setup for MS Office, and if you have the KMS version of Office installed on your image. 🙂

We use a Windows KMS here for MS Office.

@_mateo said:

Since I’ve taken so much of your time I’d like to contribute, if I can!

We always need people to answer basic questions here on the forums for newbies. We always need people to update the Wiki, add hardware reported to the hardware lists, to convert tutorials posted in the forums into polished Wiki articles. to add common problems to the wiki based on things posted in the forums. There are lots of ways to contribute.

The easiest way is to maybe once a day (mornings are best) just quickly browse through the recent threads and see if there are any you know the answers to. Probably 30% to 40% of things posted here are newbie questions.

@Wayne-Workman Yeah I ended up doing that, I guess as long as my p2ving is what made it angry then there’s nothing to worry about.

I did just setup something like this last friday. Its documented in the first link Wayne posted (it did take a bit of noodling to figure this one out). The key/trick is to use a bind-mount (like a super-duper symbolic link). You can’t use symbolic links because NFS can’t share them and/or NFS doesn’t have the concept of share aliases. The bind-mounts NFS can follow and share. If you use the bind mount then you don’t have to do anything FOG since fog still sees the /images folder, the OS redirects access to the mounted directory.

The only caveat I have to say about my setup is that I have not uploaded an image yet to this setup. I can affirm that the download works as advertised.

@glienhard Another option would be, when you see that error, to run:

git reset --hard

@Wayne-Workman
Yes, I tried both trunk and no trunk version.

The trunk version was more broken with my clients than the 1.2.0. Image upload would show the size of full disk (deploying to a disk with smaller total size would not work.). Normal deployment did not work at all either, it would only fail when starting.