fog creates thousands of new empty images - after one deletion
-
@Wayne-Workman thanks. apache2 is now stopped. We’re going to deploy images to hundreds of computers this week…
-
@Tom-Elliott We’re indeed on an imaging-spree. Up- and download continued to work normally - at least within the first hour after the start of this nightmare. A bunch of systems were waiting to checkin, but that might be the normal consequence of out host limit.
-
@Handtuch It kind of is, and it’s the only situation in which I can see this issue even being potentially possible of happening. Please try upgrading to trunk. All should be well, of course feel free to take a snapshot or make a backup before. Trunk, while not necessarily perfect, is MUCH faster and overall more stable than 1.2.0 was. Yes 1.2.0 was released, but there’s a reason development continues moving forward.
-
@Tom-Elliott thanks for this idea. Do you assume upgrading will fix this problem - or will it “only” prevent it to re-appear again?
-
@Handtuch It won’t fix what went strange, but it should prevent it from re-appearing.
-
@Handtuch it will fix it in the sense that fake images will stop being made. You will still need to play the cleanup game in MySQL. When I’m at a real computer I can provide commands for this.
-
@Wayne-Workman @Tom-Elliott thanks for your advice. I’m in the process of upgrading right now.
-
@Wayne-Workman @Tom-Elliott
You were wrong
After upgrading to trunk, the empty images disappeared automagically. Let’s hope everything will work like expected on tomorrow’s next imaging-spree. At least, this specific problem has been solved.
Thanks a lot. I really mean it. -
@Handtuch I have been working hard and I don’t remember all the work I’ve done.
-
@Handtuch cool. Glad to be wrong in this case lol.
-
@Tom-Elliott And you can’t calculate all the hours you’ve saved for other admins.
