# VM ghost in Sunstone **URL:** \ **Category:** Product Support\ **Created:** [January 7, 2016, 1:54pm UTC](https://forum.opennebula.io/t/vm-ghost-in-sunstone/1665 "2016-01-07T13:54:33Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![DaD](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/dad/32/8466_2.png) [@DaD](https://forum.opennebula.io/u/DaD)\ **Post date:** [January 7, 2016, 1:54pm UTC](https://forum.opennebula.io/t/vm-ghost-in-sunstone/1665/1 "2016-01-07T13:54:33Z")
Hello, A virtual machine appears in a user accounting but the VM is DONE since 9 month. The VM is not reported by `onevm list -f USER=foo`. How could it be reported by accounting, here is the result of `oneacct -s 2016-01-06 -e 2016-01-07 -u foo` ``` VID HOSTNAME ACTION REAS START_TIME END_TIME MEMORY CPU NETRX NETTX DISK 725 nebula1 none none 03/17 18:34:35 - 2G 0.2 0K 0K 40G ``` There is no END\_TIME but `onevm show 725` reports ``` STATE : DONE LCM_STATE : LCM_INIT RESCHED : No START TIME : 03/17 15:13:59 END TIME : 03/18 17:21:27 ``` Any idea? ---
**Author:** ![esfreire](https://avatars.discourse-cdn.com/v4/letter/e/f4b2a3/32.png) [@esfreire](https://forum.opennebula.io/u/esfreire)\ **Post date:** [January 7, 2016, 2:03pm UTC](https://forum.opennebula.io/t/vm-ghost-in-sunstone/1665/2 "2016-01-07T14:03:22Z")
Hello @DaD I am not sure if it is the same case/issue but I was just reading about this at this moment, [http://dev.opennebula.org/issues/4000](http://dev.opennebula.org/issues/4000) . Please, have a look on link [http://docs.opennebula.org/4.14/administration/references/onedb.html](http://docs.opennebula.org/4.14/administration/references/onedb.html) at the onedb fsck paragraph. I hope it helps 🙂 Regards, Esteban ---
**Author:** ![DaD](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/dad/32/8466_2.png) [@DaD](https://forum.opennebula.io/u/DaD)\ **Post date:** [January 7, 2016, 2:16pm UTC](https://forum.opennebula.io/t/vm-ghost-in-sunstone/1665/3 "2016-01-07T14:16:25Z")
Esteban Freire [forum@opennebula.org](mailto:forum@opennebula.org) writes: > Hello @DaD Hello, > I am not sure if it is the same case/issue but I was just reading about this at this moment, [Bug #4000: History etime is not set on shutdown timeout - OpenNebula - OpenNebula Development pages](http://dev.opennebula.org/issues/4000) . > > Please, have a look on link [Onedb Tool — OpenNebula 4.14.2 documentation](http://docs.opennebula.org/4.14/administration/references/onedb.html) at the onedb fsck paragraph. > > I hope it helps 🙂 I’ll plan a downtime of the service to run “onedb fsck”. ## Regards. Daniel Dehennin Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF [signature.asc](https://canada1.discourse-cdn.com/flex031/uploads/opennebula/original/2X/d/d07667aeca083a1536886bd36a2a974d0a05f570.asc) (342 Bytes) ---
**Author:** ![DaD](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/dad/32/8466_2.png) [@DaD](https://forum.opennebula.io/u/DaD)\ **Post date:** [January 8, 2016, 12:22pm UTC](https://forum.opennebula.io/t/vm-ghost-in-sunstone/1665/4 "2016-01-08T12:22:44Z")
Daniel Dehennin [forum@opennebula.org](mailto:forum@opennebula.org) writes: > > I am not sure if it is the same case/issue but I was just reading about this at this moment, [Bug #4000: History etime is not set on shutdown timeout - OpenNebula - OpenNebula Development pages](http://dev.opennebula.org/issues/4000) . > > > > Please, have a look on link [Onedb Tool — OpenNebula 4.14.2 documentation](http://docs.opennebula.org/4.14/administration/references/onedb.html) at the onedb fsck paragraph. > > > > I hope it helps 🙂 > > I’ll plan a downtime of the service to run “onedb fsck”. Ok, fsck reports “UNREPAIRED” errors: ``` [UNREPAIRED] History record for VM 52 seq # 4 is not closed (etime = 0) [UNREPAIRED] History record for VM 52 seq # 5 is not closed (etime = 0) [UNREPAIRED] History record for VM 52 seq # 6 is not closed (etime = 0) [UNREPAIRED] History record for VM 725 seq # 1 is not closed (etime = 0) [UNREPAIRED] History record for VM 8691 seq # 13 is not closed (etime = 0) [UNREPAIRED] History record for VM 8691 seq # 14 is not closed (etime = 0) [UNREPAIRED] History record for VM 8691 seq # 15 is not closed (etime = 0) [UNREPAIRED] History record for VM 8691 seq # 16 is not closed (etime = 0) [UNREPAIRED] History record for VM 8691 seq # 17 is not closed (etime = 0) ``` Should I open a bug report? ## Regards. Daniel Dehennin Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF [signature.asc](https://canada1.discourse-cdn.com/flex031/uploads/opennebula/original/2X/c/c84cf79b45e7cfe4deffa2a0da0e1b274d207b04.asc) (342 Bytes) ---
**Author:** ![cmartin](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/cmartin/32/4278_2.png) [@cmartin](https://forum.opennebula.io/u/cmartin)\ **Post date:** [January 11, 2016, 11:48am UTC](https://forum.opennebula.io/t/vm-ghost-in-sunstone/1665/5 "2016-01-11T11:48:45Z")
> [@DaD](#): > > Ok, fsck reports “UNREPAIRED” errors: This is also due to bug #4000. Unfortunately the ETIME cannot be guessed from the database. The manual solution is described in the documentation: [http://docs.opennebula.org/4.14/administration/references/onedb.html](http://docs.opennebula.org/4.14/administration/references/onedb.html) ---
**Author:** ![DaD](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/dad/32/8466_2.png) [@DaD](https://forum.opennebula.io/u/DaD)\ **Post date:** [January 11, 2016, 12:00pm UTC](https://forum.opennebula.io/t/vm-ghost-in-sunstone/1665/6 "2016-01-11T12:00:37Z")
Carlos Martín [forum@opennebula.org](mailto:forum@opennebula.org) writes: > This is also due to bug #4000. Unfortunately the ETIME cannot be > guessed from the database. The manual solution is described in the > documentation: > [Onedb Tool — OpenNebula 4.14.2 documentation](http://docs.opennebula.org/4.14/administration/references/onedb.html) Thanks, I’ll do that on the next maintenance shedule. ## Regards. Daniel Dehennin Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF ---
**Author:** ![DaD](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/dad/32/8466_2.png) [@DaD](https://forum.opennebula.io/u/DaD)\ **Post date:** [January 13, 2016, 12:16pm UTC](https://forum.opennebula.io/t/vm-ghost-in-sunstone/1665/7 "2016-01-13T12:16:14Z")
Daniel Dehennin [forum@opennebula.org](mailto:forum@opennebula.org) writes: > Carlos Martín [forum@opennebula.org](mailto:forum@opennebula.org) writes: > > > This is also due to bug #4000. Unfortunately the ETIME cannot be > > guessed from the database. The manual solution is described in the > > documentation: > > [Onedb Tool — OpenNebula 4.14.2 documentation](http://docs.opennebula.org/4.14/administration/references/onedb.html) > > Thanks, I’ll do that on the next maintenance shedule. ## I did the manipulation, thanks. Daniel Dehennin Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF