What version of FOG You using? 0.32, 0.33b?
My guess, is as you’re running on ubuntu you need to restart the services for nfs/portmap with:
[code]sudo service portmap restart
sudo service nfs-kernel-server restart[/code]
What version of FOG You using? 0.32, 0.33b?
My guess, is as you’re running on ubuntu you need to restart the services for nfs/portmap with:
[code]sudo service portmap restart
sudo service nfs-kernel-server restart[/code]
I’m only going out on a limb here, but it seems, based on looking at the configuration, you’re not seeing the menu option for DSL? Is this correct?
It’s because of the line that says:
[code]MENU LABELDSL LIVE CD[/code]
It should say:
[code]MENU LABEL DSL LIVE CD[/code]
What’s the bug you’re saying these files correct?
I looked at the differences between these files and the only differences in HostManager.class.php is that You moved the isValidMACAddress function and removed the isSafeHostName function. The only auto.register.php difference is instead of using isSafeHostName you’re trying to have it use isHostnameSafe, which for all intents and purposes, they’re the same function.
Can you show us the configuration so we can try to help you out.
Does the task actually perform?
What version of FOG are you using?
Can you give us, right after you’ve created an upload/deploy/advanced task, a snippet of your error.log file located in /var/log/apache2/error.log?
Add more video resources from the host to the VM Client that’s running this. Maybe 128M?
Try this command for mounting the nfs: (I don’t know if it will work but we can always try.)
[code]mount -t nfs -o proto=tcp,port=2049 <IP.OF.FOG.SERVER>:/tmp/nfsshare[/code]
kernal fog/dban/memdisk
Should be:
kernel fog/dban/memdisk
Then there’s something else going on. At that point, it can’t be the kernel. How slow were your “known good systems” when you started imaging them? Where they done to the same EXTREME Slow, or just slightly slower than before?
Excel,
I appreciate this, but I’ve also built a kernel that contains all possible network drivers on my kernel.
What did you build from? Core, PeterSykes, KitchenSink?
Is this kernel only going to be used on the Asrock MB’s, or do you plan on using this kernel as your main kernel?
Just wondering and hoping to help if needed.
Scott,
Once again, I’ve rebuilt the kernel.
Try this one as it’s specific to your machine (hopefully):
[url]https://mastacontrola.com/fogboot/kernel/bzImageIntelNETOnly[/url]
The kernel I’ve recently built has Virtio Drivers built in.
Download from:
[url]https://mastacontrola.com/fogboot/kernel/bzImage[/url]
Hope this helps you out.
As another addition to this particular issue, while rather dated, it still happens today. You can actually correct this issue, if you know the kernel has the appropriate network drivers for your client machines, by looking at the /var/www/{fog||html/fog}/service/auto.register.php file.
To help with troubleshooting if it’s this file and the web related configurations, look at your apache error logs when the host is attempting to send inventory. You can actually keep the system in this state. Once you make the configuration correct, it will actually inventory the host as expected even though it was, seemingly, stuck in a loop.
I don’t know how to correct for that.
I’m working on something at the moment. It just seems odd that it slows down where, to my knowledge, others haven’t been having that issue.
I’m going to try building just a core kernel with only your network drivers. That should limit any issues on the kernel’s side.
I’m rebuilding a kernel as we speak with virtio drivers enabled. It should be up shortly.
[quote=“variable205, post: 19704, member: 359”]Hey Tom! Thanks for taking the passed torch of FOG! I love this system, and I’m glad its still being updated :)[/quote]
Thank you and Please don’t be afraid to test.
It’s now available to test. It has been for a little bit now.
It sounds like the partitioning scheme on the hdd is causing this particular issue.
You may try an fdisk on the drive to verify what partitioning scheme is setup on it. It sounds like the first drive was initialized with the MBR tables and the other one is partitioned with GUID Tables.
I don’t have much more information to help out with this.
Is you system setup so your FOG Server is the DHCP server for FOG Clients?
If anything, I’d take a look at the dhcpd.conf file. It should be located at: /etc/dhcpd.conf though I don’t know what OS you’re using. Look for the line that says:
[code]option routers X.X.X.X;[/code]
I think you’d need the gateway, but make sure, if your FOG Server is the DHCP Server, that you use your FOG Server’s IP address rather than the actual gateway. DNS should then point to the proper DNS Server and as long as your fog server can access the internet, your FOG Client’s should be able to access the internet as well.
This is just my guess.
Scott,
I’m currently rebuilding another 3.12.0 kernel that is based strictly off the Core Config. Removed the KMS Requirements and added all network drivers back. There are no other tweaks to this configuration. Please test this new kernel to see if you have an improvement. If you don’t I’ll keep tweaking the kernel settings as then I know it’s likely something with the drivers that’s causing your issue.
It will probably be about 30 minutes or so, but it will be at the same link as it’s the same file. Just give me till the turn of the next hour and it’ll be up. I hope this helps.