Multiple images with no title, no size, no storage node and no data
-
@kman1232 What distribution of Linux?
-
Would you be willing to update to trunk? I ask because while I have no clue why you are seeing these entries being made, it looks to me like something is wrong. The fact that you can view the images tells me that something is inject false entries into that particular table. Is this still happening? Or was this more of what I would say is a one off case that happened but is not continuously occurring? Upgrading to trunk wouldn’t fix this for you, but it would, hopefully, cleanup any invalid elements automatically. I guess maybe I’m partial to trunk but I know I can be of more help on it than 1.2.0. While I did code 1.2.0, it is over a year old and I have made a LOT of progress since that time.
-
@Wayne-Workman We are using Ubuntu 14.04.2 currently. Does anyone know of a way to delete images besides having to go through the Image Management User Interface and having to click the delete button? If so this would save us a LOT of manual time in removing these entries. To answer your question Tom at this time we are not ready to upgrade to Trunk. I’ll have to read up on exactly what that entails.
-
@kman1232 Do you have any REAL image definitions on your server right now, or just the image definitions that appear to be “randomly created”?
-
Yes we do have real images stored on the system and they are working fine. I’d say we have roughly 20 real images. If the only recourse is deleting all images I suppose we could recreate the images we had on the system. If there is a way around this that would be preferable. I’m not sure if the Trunk version has the ability to delete multiple images at one time but maybe a feature worth thinking about.
-
@kman1232 Trunk DOES have multi delete. This goes for all fields, hosts, tasks, images, etc…
That said, if you know how the blank named images are stored, you could do an sql statement to delete them all.
For example:
DELETE FROM fog.images WHERE imageName IN ('',NULL); -
@kman1232 said:
Yes we do have real images stored on the system and they are working fine. I’d say we have roughly 20 real images. If the only recourse is deleting all images I suppose we could recreate the images we had on the system. If there is a way around this that would be preferable. I’m not sure if the Trunk version has the ability to delete multiple images at one time but maybe a feature worth thinking about.
Do not delete all you images. That is ridiculous. We can help you fix it via TeamViewer if you need help. Follow Tom’s advice, be careful, and it’ll be fixed, or ask for help via TeamViewer from a Moderator or Developer.
Take a backup of your DB before you make changes in case you make a mistake.
FOG Configuration -> Configuration Save -> Export. -
@kman1232 had over 7,000 blank images that somehow was created in fog 1.2.0.
I was able to find some data unique to these blanks and delete them all. Here’s what I used:
delete from images where imageFormat is null; -
@Tom-Elliott You asked if we would upgrade to Trunk. I haven’t considered it since reading in the wiki https://wiki.fogproject.org/wiki/index.php/FOGUserGuide under the Upgrade to Trunk section states with yellow highlight that “Trunk installs are almost always buggy” If this is no longer the case I would advise making an edit to this section.
-
@kman1232 said:
@Tom-Elliott You asked if we would upgrade to Trunk. I haven’t considered it since reading in the wiki https://wiki.fogproject.org/wiki/index.php/FOGUserGuide under the Upgrade to Trunk section states with yellow highlight that “Trunk installs are almost always buggy” If this is no longer the case I would advise making an edit to this section.
I wouldn’t advise it at this particular moment. the latest is in question.
However, an older rev like 4571 seems fine to me. that’s what I’m using. I’d highly recommend virtualizing your FOG server if you’re going to use trunk, and you have to keep up on your DB and image backups and snapshots and server backups.
