Opened 3 months ago

Closed 3 months ago

#13802 closed Task/To do item (wontfix)

move stokely and menchu to medgar

Reported by: https://id.mayfirst.org/jamie Owned by: https://id.mayfirst.org/jaimev
Priority: Medium Component: Tech
Keywords: Cc:
Sensitive: no

Description

Both stokely and menchu have repeatedly run into resource problems.

I think they will fare better on medgar.

Change History (8)

comment:1 Changed 3 months ago by https://id.mayfirst.org/jamie

  • Owner set to https://id.mayfirst.org/jaimev
  • Status changed from new to assigned

Once you get back home next week, can you pick a time to make this guest move? Thanks!

comment:2 Changed 3 months ago by https://id.mayfirst.org/jaimev

Should be able to get this done between today and tomorrow.

comment:3 Changed 3 months ago by https://id.mayfirst.org/jaimev

Just got started with this yesterday after all. Initial sync is complete. I'll send out a service advisory for this evening to do the final sync.

comment:4 Changed 3 months ago by https://id.mayfirst.org/jaimev

I stopped both vms and was able to complete the final sync for each of them but then was unable to start the systemd service for the vms on medgar https://support.mayfirst.org/wiki/kvm-manager

comment:5 Changed 3 months ago by https://id.mayfirst.org/jaimev

0 medgar:~# systemctl status kvm@stokely.service
● kvm@stokely.service - KVM Manager virtual guest management script for stokely
   Loaded: loaded (/usr/local/share/kvm-manager/kvm@.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2018-06-26 04:57:42 UTC; 18min ago
  Process: 4408 ExecStartPre=/usr/local/sbin/kvm-setup stokely (code=exited, status=1/FAILURE)

Jun 26 04:57:42 medgar systemd[1]: Failed to start KVM Manager virtual guest management script for stokely.
Jun 26 04:57:42 medgar systemd[1]: kvm@stokely.service: Unit entered failed state.
Jun 26 04:57:42 medgar systemd[1]: kvm@stokely.service: Failed with result 'exit-code'.
Jun 26 04:57:42 medgar systemd[1]: kvm@stokely.service: Service hold-off time over, scheduling restart.
Jun 26 04:57:42 medgar systemd[1]: Stopped KVM Manager virtual guest management script for stokely.
Jun 26 04:57:42 medgar systemd[1]: kvm@stokely.service: Start request repeated too quickly.
Jun 26 04:57:42 medgar systemd[1]: Failed to start KVM Manager virtual guest management script for stokely.
Jun 26 04:57:42 medgar systemd[1]: kvm@stokely.service: Unit entered failed state.
Jun 26 04:57:42 medgar systemd[1]: kvm@stokely.service: Failed with result 'exit-code'.

comment:6 Changed 3 months ago by https://id.mayfirst.org/jamie

Thanks Jaime! And sorry you hit an error starting the kvm. I know it's a pain to get everything sync'ed and then have to do it all over again :(.

I just expanded the trouble shooting tips on the kvm manager page.

I'm pretty sure the problem was that networking could not start properly because it was not properly torn down.

Maybe there was a different error that caused it to fail the first time? If so, we might encounter that error again.

However, I hope the extended debugging instructions will help uncover whatever error it might be and generally demystify the whole process.

comment:7 Changed 3 months ago by https://id.mayfirst.org/jaimev

I was able to get stokely switched over last night. I couldn't get menchu to start even after trying teardown and setup several times. I started menchu from debirf on medgar and checked that I was able to establish networking did a file systemcheck on all of the logical volumes. Everything looked ok but after shutting down I was still unable to get it to boot from its own logical volume. You can see the kind of output I was getting in the screen session in /home/menchu/servicelog on medgar.

comment:8 Changed 3 months ago by https://id.mayfirst.org/jamie

  • Resolution set to wontfix
  • Status changed from assigned to closed

We looked at it together and determined that newer versions of grub seem to need more space at the start of the partition then is available on menchu (which starts at 63s). this may be a future problem dealing with old guests.

for now we've decided not to move it.

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.