kernel update problem github 7238 ubuntu 14.04
-
I have a fresh installation of fog git 7238 and Ubuntu 14.04.
I tried to update the Client Kernel in the gui and there i got a error that the file or folder does not exist. -
This is a known issue at the moment. For now, I’m just going to link all these threads together so the devs can easily traverse the threads and so people know more information.
https://forums.fogproject.org/topic/7216/kernel-update-problem-github-7238-ubuntu-14-04
https://forums.fogproject.org/topic/7205/pxe-boot-fails-on-fresh-install-centos-7-build-7218
https://forums.fogproject.org/topic/7190/slow-ui-response-and-cannot-update-kernel
-
@MaMu Tom just pushed a fix a couple of minutes ago… Can you please update and see!
-
@Sebastian-Roth I have the exact same problem, and just updatet with git and this is the result.
-
@goempie What’s the version in the cloud?
-
@Tom-Elliott You are currently running version: 7254
-
@goempie What OS are you running?
-
@Quazz ubuntu 14.04
-
@goempie Apache errors?
-
-
@goempie What revision are you on currently?
-
@Wayne-Workman I update every day for the last week.
-
@goempie Can you provide the output of
ls -lahRt /var/www/html/fog/service/ipxe
please? -
@Wayne-Workman
Sorry for the late response
-
@goempie Can you try to update first? 7306 is old and had issues in itself.
-
I’m updating every day.
Now i’m on Version: 7428 -
@goempie I think we need a join.me session so I can see what’s going on.
This issue that you’re reporting feels like, while you’re pulling the latest, it’s not actually updating any files. Especially if when you go to the FOG Configuration Page it’s reporting a version 7306. I only state that because of the reply showing the version from FOG COnfiguration Page.
-
Remoted in and found the issue was the TFTP FTP username and password. Once updated, this was fixed.
-
To be clear, FTP credentials can cause the above error? I need to be sure before I put it into the wiki.
-
@Wayne-Workman yes. Because it can’t connect to the server the put the data. It should’ve failed to connect if the credentials were wrong, of which they weren’t. It couldn’t rename or put because the user that was logged in had no rights to where the files were to be placed.