SVN 4543
-
Some issues I had after upgrading to new trunk:
- hostname changer - disabled and still changing name while downloading image (disabled globaly and on host, previous built probably too, not testet, using unattended instalalation with hostname setting)
- storage node setting FTP - new setting, using default value /image until changed to //new-path downloading image not possible (Must upload image first message)
- dhcp server want start after upgrade (range was definet as .10 .254 asked for number - changed to my own settings)
- error while downloading image to host (previous builds too):“Populating /dev using udev: udevd[2208]: error creating epoll fd: Function not implemented”
- very slow image downloading - on previous built downloading image between 2,5 - 3 minutes, now - more then 5
- uploading seem the same, not testet properly (around 22 minutes for 25GB space in use?)
-
@mrzo said:
Some issues I had after upgrading to new trunk:
- hostname changer - disabled and still changing name while downloading image (disabled globaly and on host, previous built probably too, not testet, using unattended instalalation with hostname setting)
This is probably because the Hostname_early checkbox is selected in the global settings. - storage node setting FTP - new setting, using default value /image until changed to //new-path downloading image not possible (Must upload image first message)
I don’t understand the issue here. Is it not allowing you to create an image? Or you’re saying it’s not allowing you to image until you have an image uploaded? If it’s the latter, this is totally expected. How can you image if you don’t have an image to image from? - dhcp server want start after upgrade (range was definet as .10 .254 asked for number - changed to my own settings)
Again, Don’t understand the issue. It creates it based on defaults if they’re not specified by the installer options.
It creates the file using the ip, subnet, and network range of the selected interface. - error while downloading image to host (previous builds too):“Populating /dev using udev: udevd[2208]: error creating epoll fd: Function not implemented”
This is a non issue. I don’t build the kernels with epolling support. I did for a little bit, but that caused more errors to display in more “dangerous” areas of the imaging process. - very slow image downloading - on previous built downloading image between 2,5 - 3 minutes, now - more then 5
Don’t understand. What is the network, what is the hardware, how many systems were going?. - uploading seem the same, not testet properly (around 22 minutes for 25GB space in use?)
What is the image compression set to?.
- hostname changer - disabled and still changing name while downloading image (disabled globaly and on host, previous built probably too, not testet, using unattended instalalation with hostname setting)
-
- hostname changer - disabled and still changing name while downloading image (disabled globaly and on host, previous built probably too, not testet, using unattended instalalation with hostname setting)
Disable early hostname change.
FOG Configuration -> FOG Settings -> General Settings -> FOG_CHANGE_HOSTNAME_EARLY- storage node setting FTP - new setting, using default value /image until changed to //new-path downloading image not possible (Must upload image first message)
Update your /etc/exports file
- dhcp server want start after upgrade (range was definet as .10 .254 asked for number - changed to my own settings)
Disable DHCP on boot, and turn it off in the /opt/fog/.fogsettings file
- error while downloading image to host (previous builds too):“Populating /dev using udev: udevd[2208]: error creating epoll fd: Function not implemented”
This happens to everyone right now - there is no impact.
- very slow image downloading - on previous built downloading image between 2,5 - 3 minutes, now - more then 5
FOG Trunk is probably 300% faster than FOG Stable when downloading. Something in your setup is not right - we need details to help with that.
- uploading seem the same, not testet properly (around 22 minutes for 25GB space in use?)
Uploading has seen a small improvement.
-
@Wayne-Workman said:
- hostname changer - disabled and still changing name while downloading image (disabled globaly and on host, previous built probably too, not testet, using unattended instalalation with hostname setting)
Disable early hostname change.
FOG Configuration -> FOG Settings -> General Settings -> FOG_CHANGE_HOSTNAME_EARLYthanks will try
- storage node setting FTP - new setting, using default value /image until changed to //new-path downloading image not possible (Must upload image first message)
Update your /etc/exports file
no need to update this, my /new-path image path was working before upgrading to new trunk version, but setting from it was not copied to new seeting FTP path (it is propably the same, because when I changed it to //new-path, image downloading was working again, not sure
- dhcp server want start after upgrade (range was definet as .10 .254 asked for number - changed to my own settings)
Disable DHCP on boot, and turn it off in the /opt/fog/.fogsettings file
why? I want DHCP to start after boot… I edited dhcp.conf and started DHCP manualy
- error while downloading image to host (previous builds too):“Populating /dev using udev: udevd[2208]: error creating epoll fd: Function not implemented”
This happens to everyone right now - there is no impact.
yeah, it was working with it, through some versions, but I mentioned it to be sure
- very slow image downloading - on previous built downloading image between 2,5 - 3 minutes, now - more then 5
FOG Trunk is probably 300% faster than FOG Stable when downloading. Something in your setup is not right - we need details to help with that.
what details? I was on older version of trunk until today, upgraded to newest version and download time is two times as before
No changing to system or FOG configuration, except what I mentioned earlier.- uploading seem the same, not testet properly (around 22 minutes for 25GB space in use?)
Uploading has seen a small improvement.
can be… I tested it only once -
Just trying to get updated information. I’m assuming most or all of things described as problems have been fixed. Is this true? Can we solve this thread?
