VM ghost in Sunstone

Community Support
1

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?

2

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 .

Please, have a look on link http://docs.opennebula.org/4.14/administration/references/onedb.html at the onedb fsck paragraph.

I hope it helps :slightly_smiling:

Regards,
Esteban

3

Esteban Freire 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 .

Please, have a look on link Onedb Tool — OpenNebula 4.14.2 documentation at the onedb fsck paragraph.

I hope it helps :slightly_smiling:

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 (342 Bytes)

4

Daniel Dehennin 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 .

Please, have a look on link Onedb Tool — OpenNebula 4.14.2 documentation at the onedb fsck paragraph.

I hope it helps :slightly_smiling:

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 (342 Bytes)

5

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

6

Carlos Martín 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

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

7

Daniel Dehennin forum@opennebula.org writes:

Carlos Martín 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

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