@sebastian-roth No good reason. I actually have git update ready to run install.sh from.
[root@brt1-fog01 postinitscripts]# ls -al /images/dev/postinitscripts/
total 12
drwxrwxrwx 2 fog root 4096 Jun 14 10:16 .
drwxrwxrwx 5 fog root 4096 Dec 13 2019 ..
-rwxr-xr-x 1 root root 249 Jun 14 10:16 fog.postinit
[root@brt1-fog01 postinitscripts]# mount | grep images
/dev/sdb1 on /images type ext4 (rw,relatime,data=ordered)
Thanks
@sebastian-roth It never gets to failed. Just sits at ‘running post init scripts…’
I dont believe I ever have used post init scripts but the /images/dev/postinitscripts folder contains a script called ‘fog.postinit’ which contains:
#!/bin/bash
## This file serves as a starting point to call your custom pre-imaging/post init loading scripts.
## <SCRIPTNAME> should be changed to the script you're planning to use.
## Syntax of post init scripts are
#. ${postinitpath}<SCRIPTNAME>
Thanks!
I found a couple topics similar to this with no resolution
You are currently running version: 1.5.5
Latest stable version is 1.5.9
Latest dev-branch version is 1.5.9.93
Latest alpha-branch version is 1.6.0-alpha.1110
I am unable to deploy an imiage as the process hangs at Running Post Init Scripts
/images/dev/postinitscripts is mounted
Permissions are 777
I recreated the fog.postinit based on what the default file should look like
I can create other files on the filesystem
Thanks!
@mmethe How is FTP involved on the local machine?
Hello All,
I was having all sorts of trouble going from 1.2 to trunk on an appliance version of Fog. So, I built a new Centos 7 VM and installed fresh.
My images are on a disk presented by a SAN. I:
-Created the images in the new trunk server
-Attached the SAN volume and mounted in on /images
-Verified that I can see all the images on the volume
When I look at image management on the new TRUNK server, they show as ZERO (0.00 iB) size. Is there I can get these images to be ‘seen’ by this new servers?
Thanks!
-Mike M
@Wayne-Workman Can I simply obtain the most current kernel somehow and point to it?
@Wayne-Workman So, I am using the SVN method to switch to trunk. All goes well until I am told to hot the GUI and do the schema update. When I hit the GUI URL I get:
SQLSTATE[42S22]: Column not found: 1054 Unknown column ‘hosts.hostPending’ in ‘where clause’ SQL: [94] SELECT COUNT(hosts.hostID) AS total FROM hosts WHERE hosts.hostPending=‘1’ LIMIT 1 Params: 0
SQL is running. There were no errors reported during the installation script execution.
Thanks!!
@Wayne-Workman Thank You. the problem I am seeing is that the most updated kernel is dated July 22, 2015. Seems a little old. Is there a repository where I can look for something more current than a year ago?
@Wayne-Workman Also, if DHCP was failing would ‘ip a s’ still list the eth without an IP? There is nothing but loopback listed as 127.0.0.1
@Wayne-Workman Yes, portfast is enabled on this port.
This is the ONLY model PC this is happening with. I am leaning toward a kernel/driver issue I think. It is an HP ProDesk 600 G2 with an Intel NIC. Where can I get the most recent kernel build?
Thanks for all the help so far!
@mmethe I launched a debug job at the target. Initially the machine gets to fog and drops to a console. It then appears to lose its network config as the only adapter listed by ‘ip a s’ is the loopback adapter. I have tried this from both the subnet local to the fog server as other VLANS and the same thing happens.
Does this sound like a target computer NIC driver issue? I am using the most recent kernel listed on the kernel updates page.
Thanks!
Hello All,
I am running FOG 1.2 on Ubuntu. Everything was working fine until a reboot of the server. I found that SAN volume had not remounted so images were not there. the mount point was but there was nothing behind it. I remounted it and images can be SENT to machines as expected.
When I attempt to create an image though, it fails. The following issue:
From a windows machine, I can mount this NFS export to a drive letter so I know the network is reachable. Both the windows machine and FOG client are on the same VLAN.
Is fog trying to mount the image to a local /image path on the client?
Thanks!!!
mmethe