Issues after upgrading from 1.2.0 to 1.4.3
-
Server
- FOG Version: 1.4.3
- OS: Ubuntu 14.04
Client
- Service Version:
- OS:
Description
I just upgrade from 1.2.0 to 1.4.3 and ran into a few issues.
- Kernel update issues, in the web interface I’ve attempted to get a new kernel and get the following error:
“Type: 2, File: /var/www/html/fog/lib/fog/fogftp.class.php, Line: 707, Message: ftp_put(): Could not create file., Host: 10.1.39.250, Username: fog”
I’ve added the fog user to the www-data group but there still seems to be permission issues with saving the kernel.
- DHCP issues After upgrade, the newly placed configuration file seems to have a syntax error:
Jun 23 18:32:38 fog-server dhcpd: /etc/dhcp/dhcpd.conf line 24: expecting numeric value.
Jun 23 18:32:38 fog-server dhcpd: subnet 0.0.0.0 netmask {
Jun 23 18:32:38 fog-server dhcpd: ^
Jun 23 18:32:38 fog-server dhcpd: /etc/dhcp/dhcpd.conf line 26: range declaration not allowed here.
Jun 23 18:32:38 fog-server dhcpd: range
Jun 23 18:32:38 fog-server dhcpd: ^
Jun 23 18:32:38 fog-server dhcpd: /etc/dhcp/dhcpd.conf line 71: expecting a declaration
Jun 23 18:32:38 fog-server dhcpd: }
Jun 23 18:32:38 fog-server dhcpd: ^I’ve tried to replace the configuration file with the original one, (before the upgrade), which allowed the service to start, but the client still doesn’t pick up and address, (getting the “No DHCP or proxyDHCP” error).
Any help would be appreciated.
-
Issue is resolved:
Our Fog server is now running and working.The issue was that after the upgrade the new DHCP configuration was misconfigured. To what I can tell the during the upgrade process the new configurations are read from the .fogsetttings file, (which had some oddly set values, including the wrong outdated DNS server).
Going directly into the /etc/dhcpd/dhcpd.conf file and manually configuring the service worked.
-
In regards to #1 when you installed 1.4.3 you will have the latest kernel. There is no need to download again. That doesn’t address your issue, but know that you have the latest kernel.
I have to ask you, did you make any changes to the linux user called
fogthis is not the default web ui user account, this is the linux account. That account is an internal account used by the FOG application. I’ve seen people attempt to use/change the password on that linux account and use it for system administration. Doing so will break FOG.As for your isc-dhcp config file, we really need to see it to identify what’s wrong. There is a great example of what the config file needs to be if you review this document (example 1) : https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence
-
As far as I know the fog account was not changed, (but cannot rule it out). Prior to upgrading, everything was working with the existing permissions. Before the current message there was another message indicating a login failure, (which I did fix with synchronizing the fog password on the system to the one known in the fog settings.
isc-dhcp config is completely different from the one saved from before, (which leads me to thing the new file is from the stock file in the 1.4.3 installation). Just more surprised that what seems to be a “configuration file syntax error” occurred.
-
@jlouie.smart said in Issues after upgrading from 1.2.0 to 1.4.3:
As far as I know the fog account was not changed, (but cannot rule it out)
You can test this by attempting to connect to the fog server using a ftp client on windows. If you can login with the fog credentials in the /opt/fog/.fogsettings file (which should match the uid and password listed in the storage node configuration) then the linux account is set correctly.
EDIT: Once you get connected via FTP change to the /images/dev directory and just upload any file, move it to the /images directory and then delete it using FTP commands. This will test the entire process that FOS uses when capturing a file.
-
@jlouie.smart said in Issues after upgrading from 1.2.0 to 1.4.3:
isc-dhcp config is completely different from the one saved from before, (which leads me to thing the new file is from the stock file in the 1.4.3 installation). Just more surprised that what seems to be a “configuration file syntax error” occurred.
FOG 1.2.0 built the /etc/dhcp/dhcpd.conf file differently than 1.3+ does. Parts of the file /opt/fog/.fogsettings are used to generate the dhcp config. Since this was an upgrade and not a fresh install, the problem is probably there. Probably older values that weren’t converted over correctly during upgrade.
You would need to share your
/opt/fog/.fogsettingsfile with one of the moderators or developers so we can see what got butchered, as well as the output ofip addr showfrom your fog server. -
Issue is resolved:
Our Fog server is now running and working.The issue was that after the upgrade the new DHCP configuration was misconfigured. To what I can tell the during the upgrade process the new configurations are read from the .fogsetttings file, (which had some oddly set values, including the wrong outdated DNS server).
Going directly into the /etc/dhcpd/dhcpd.conf file and manually configuring the service worked.
-
@jlouie.smart Please ensure the .fogsettings file is accurate or you may have the same issue again the next time you update fog.
BTW: fog 1.4.4 was just released.
-
You can also turn off DHCP config generation by setting bldhcp to 0 in .fogsettings
