• Sometimes ppl fail, but recovery can be done on almost all situation somehow. It needs many factor and one of these factors is the properly logged events. I dont want fog to become a logging system, but sometimes mysteries can be less disturbing if we can see more logs.

    Some of the staff member deleted a few images to clean space and maybe mistakenly deleted wrong image. The extra and most serious problem is that it took too long time to realise it and there came the backup ( well, we have a lot of images and to keep the usage at bay, we cant take too many instances of an image, so backup is the worst for such situation: images are only replicated to a different location after a time passed).

    Normally a new image when taken has unique name, so this backup strategy is ok with it (nothing overwritten). Deletion is extra rare. Image retake to same name is not permitted and if somehow done, from backup it can be rewritten with the original file. This is the weakest point: if time goes and no one notices, it can be overwritten in backups, too.

    On limited space no “proper” method, only “best of possible” is available. But to recover disaster (or at lest shock of wth happened) I would want to see logs of events like:

    • host/image creation (who when what)
    • host/image deletion (who when what)
    • host/image overwrite (who when what)

    There is imaging log which i can see, but the above mentioned ones are sometimes even more important.

    Can it be somehow invented? 🙂

  • @george1421 thx is why i was paused blinking.

  • Moderator

    @Foglalt I can confirm that the command Wayne provided reports all objects that have been destroyed. In my query results I see users, hosts, storage nodes being deleted from the database. I have not purged any images in over a year.

    use fog;
    select * FROM  history where hText like '%dest%';

  • @Wayne-Workman i am confused:

    mysql> select * FROM  history where hText like '%dest%';
    Empty set (0.00 sec)

    I am pretty sure we had deletes before 🙂

  • @Foglalt Deletes are in the table.
    0_1490140242064_Screenshot from 2017-03-21 18-49-30.png

  • @Tom-Elliott I checked that table and see many things, but i cant see image uploads and zero delete at all. i created an imaging report to see my missing image when was last used, paired it with history table to see if imaging is maybe logged in different way, but i cant see match.

    Imaging is not reported in history table? actually i see only “updates” like mac, task and so on. No image uploads, etc. We are investigation a situation that is disturbing (deleted or missing image) and it makes a pain in the ass not to see where and what happened to that image. (i even considered to build an older version of fog server to see the pre-v1.3 images and at least use them to recreate an at least few months old version.

  • @Tom-Elliott omg, i missed to notice it? bah, shame on me. maxima mea culpa! i go to the corner and undergo my punishment 🙂

  • While not the “simplest” of systems to look at, FOG already logs creation, edit, upload, deletes in the database under the “history” database table. There isn’t any simple readable logs yet but a plugin could be built to display any/all of these types of things. That said, for now, you would need to look at the mysql database.