Update to SVN 3421 broke everything in FOG
-
If you’re up fog upgrading why not, first, try 3427 (the latest)? Also, have you tried clearing your cache for the loader spinners problem.
One last bit,
As for client stuff, I’m aware 3415 and greater will likely break the new client as we’re adding more security stuff that the client you have available does not have incorporated yet. At the most, it may break all new client stuff if you’re using FOG_AES_ENCRYPT, and the least it may break hostname changer. This is expected and we’re aware of it. Especially as it’s kind of intended. We should have a new client version updated sometime fairly soon so this should be a non-issue at that point.
-
Thank you for your advice Tom!!! Moving to 3427 fixed the issues.
-
I guess I sing too fast. It is not seeing any of the images in /images.
Any advice?
-
@DarkEnergy said:
I guess I sing too fast. It is not seeing any of the images in /images.
Any advice?
Hi,
You have not any image in web ui ???
Regards,
Ch3i. -
I am not sure what you are asking. If you follow the conversation you will see that was an update.
That should answer what I think you are asking. If I had any images before. The obvious answer shall be"YES". -
@DarkEnergy said:
I am not sure what you are asking. If you follow the conversation you will see that was an update.
That should answer what I think you are asking. If I had any images before. The obvious answer shall be"YES".Ok,
It’s in the Web UI you don’t see any image or in /images ?
Regards,
Ch3i. -
You might try restarting MySQL since the images data is pulled straight from the DB.
-
@ch3i said:
@DarkEnergy said:
I am not sure what you are asking. If you follow the conversation you will see that was an update.
That should answer what I think you are asking. If I had any images before. The obvious answer shall be"YES".Ok,
It’s in the Web UI you don’t see any image or in /images ?
Regards,
Ch3i.Oh I get it now.
You’re trying to verify where the problem is. I’ll paraphrase.
Can you see that the image files are in the actual directory itself? in /images ? Are they there? or, can you just not see them inside the Web GUI ?
-
I did reboot the server to reset all services and still no go. I am thinking the pointers are not working. I am thinking something most change after doing the new update to the schema in the DB.
-
@ch3i
Thank you for clarifying. In that case, the answer is as follow:
I can see the images in /images and subfolders, all files are there.
In the web GUI; all images names, configurations, descriptions and pointers are there.
When a task is setup the response is:
Failed to create deployment tasking for the following hostsYou must first upload an image to create a download task
Even knowingly I have all the files and folders in the right location. It seems as if they were deleted from the DB.
-
@DarkEnergy said:
@ch3i
Thank you for clarifying. In that case, the answer is as follow:
I can see the images in /images and subfolders, all files are there.
In the web GUI; all images names, configurations, descriptions and pointers are there.
When a task is setup the response is:
Failed to create deployment tasking for the following hostsYou must first upload an image to create a download task
Even knowingly I have all the files and folders in the right location. It seems as if they were deleted from the DB.
This sounds, to me, like the FTP Password changed, which is a known issue.
-
Specifically this thread:
https://forums.fogproject.org/topic/4949/deployment-ftp-not-working -
Followed the advice provide and change the password under FOG Configuration->FOG Settings->TFTP Server->FOG_TFTP_FTP_PASSWORD using the password located in /opt/fog/.fogsettings; line storageftppass=" ". After that, changed the user fog password using the same password from /opt/fog/.fogsettings, line storageftppass value. Still same error.
Any other ideas?
-
Thank you Tom for pointing in the right direction. There was one more place that the password needed to be change.
The second location is under:
Storage Management >> DefaultMemeber >> Management Password.
After changing the password and submitting the changes; it seems that it is back online.Thank you so much!!!
