VirtualBox Guest (Ubuntu 16.04) unresponsive, freezes / crashes

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
evance
Posts: 1
Joined: 24. Jun 2017, 11:38

VirtualBox Guest (Ubuntu 16.04) unresponsive, freezes / crashes

Post by evance »

Introduction
I have been struggling for the last two weeks with my VM and the issue just doesn't go away... The problem is, that my Ubuntu 16.04 is freezing and completely unusable – the timing differs and sometimes I can even use the machine just fine but it reappears constantly and right now it has gotten to the point that I cannot reach my local website at all (only the initial call goes through, afterwards the system hangs).

Since I am fairly new to the whole VM- & server-thing I apologize upfront if I get something wrong, am issing out on certain things etc.

The website/project I am building is based upon roots.io/trellis/ which provides a ready-to-use server (LEMP) stack and has a lot of nifty features for provisioning the server etc. so I am following their guidelines and best-practices. I have already inquired in their forum (discourse.roots.io/t/going-loco-over-local-dev-not-working-cannot-get-server-to-respond/9806) but obviously it isn't related to the software I am using but much rather the OS and/or VirtualBox.

I have searched on Google and explicitly on this forum but no related issue came up.

The issue
As said in the intro, the problem arises somewhat randomly and is hard to predict... I am starting the server via "vagrant up" and when the VM/server is ready I call upon my website wp-api-test.dev. Either I am lucky and things are working or the system almost immediately 'freezes' and I can't do nothing no more.

The VirtualBox log says:

Code: Select all

00:31:17.551095 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:31:17.689466 VMMDev: GuestHeartBeat: Guest is alive (gone 4 138 644 903 ns)
00:31:32.186560 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:31:32.380940 VMMDev: GuestHeartBeat: Guest is alive (gone 4 199 485 966 ns)
00:31:36.385276 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:31:36.443238 VMMDev: GuestHeartBeat: Guest is alive (gone 4 062 300 208 ns)
00:31:40.443390 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:31:40.474361 VMMDev: GuestHeartBeat: Guest is alive (gone 4 031 119 359 ns)
00:31:44.476323 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
00:31:44.806642 VMMDev: GuestHeartBeat: Guest is alive (gone 4 332 283 101 ns)
[and so on...]

This state never resolves itself, I have to restart the VM/server but most of the times the problem just comes back.

Thinking that maybe the Ubuntu 16.04 OS could be crashing I checked the logs but nothing there (at least as far as I can see, compare log-section below as well) – the only thing I noticed was the nfs process not responding so I did

Code: Select all

ping 192.168.50.1
but that went OK (doesn't mean the nfs is well though).

I am thinking that whatever is going on here either is due to a bug in VirtualBox or in the Ubuntu 16.04 OS. My problem is though:
  • How can I debug this properly?
    How can I trace the error and resolve it?
Any help is greatly appreciated, this whole thing is slowing me down immensly and I am far from having an answer to all of this.

Thanks so much!

Stuff I already did
  • Updating all dependencies of Trellis (Ansible, VirtualBox, Vagrant, bower, ...)
    Pinging the server (192.168.50.5), all good
    Installing (an de-installing) the vagrant-vbguest plugin since some users reported that this fixed the issue, unfortunately not for me though
    Making sure nginx is running, it's running and the error.log is empty...
    Checked /etc/exports for any duplicate or conflicting entries, deleted all of them to make sure this isn't causing any trouble
    Destroyed and Upped the VM multiple times
    Un-installed VirtualBox and re-installed, restarted my machine afterwards
    Installed earlier versions of VirtualBox, hoping for a recent bug I could evade thereby
    Did a clean install of the example project of Trellis/Bedrock/Sage, same issue
Logs
Find the VirtualBox-logs attached.

Code: Select all

tail -f /var/log/kern.log
Jun 24 10:10:30 wp-api-test kernel: [   28.925705] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s3: link becomes ready
Jun 24 10:10:30 wp-api-test kernel: [   30.045029] Adding 524284k swap on /dev/mapper/vagrant--vg-swap_1.  Priority:-1 extents:1 across:524284k FS
Jun 24 10:10:36 wp-api-test kernel: [   37.255739] vboxsf: Successfully loaded version 5.1.22 (interface 0x00010004)
Jun 24 10:10:46 wp-api-test kernel: [   45.469018] ip_tables: (C) 2000-2006 Netfilter Core Team
Jun 24 10:10:55 wp-api-test kernel: [   55.029088] IPv6: ADDRCONF(NETDEV_UP): enp0s8: link is not ready
Jun 24 10:10:57 wp-api-test kernel: [   57.019934] e1000: enp0s8 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Jun 24 10:10:57 wp-api-test kernel: [   57.020565] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s8: link becomes ready
Jun 24 10:11:18 wp-api-test kernel: [   78.405266] FS-Cache: Loaded
Jun 24 10:11:19 wp-api-test kernel: [   78.500515] FS-Cache: Netfs 'nfs' registered for caching
Jun 24 10:13:47 wp-api-test kernel: [  226.898966] nfs: server 192.168.50.1 not responding, still trying

Code: Select all

tail -f /var/log/syslog
Jun 24 10:11:18 wp-api-test rpc.statd[2564]: Flags: TI-RPC
Jun 24 10:11:18 wp-api-test systemd[1]: Started NFS status monitor for NFSv2/3 locking..
Jun 24 10:11:18 wp-api-test kernel: [   78.405266] FS-Cache: Loaded
Jun 24 10:11:19 wp-api-test kernel: [   78.500515] FS-Cache: Netfs 'nfs' registered for caching
Jun 24 10:11:35 wp-api-test mailhog[1843]: [APIv1] KEEPALIVE /api/v1/events
Jun 24 10:12:35 wp-api-test mailhog[1843]: [APIv1] KEEPALIVE /api/v1/events
Jun 24 10:13:47 wp-api-test kernel: [  226.898966] nfs: server 192.168.50.1 not responding, still trying
Jun 24 10:13:35 wp-api-test mailhog[1843]: [APIv1] KEEPALIVE /api/v1/events
Jun 24 10:14:35 wp-api-test mailhog[1843]: [APIv1] KEEPALIVE /api/v1/events
Jun 24 10:15:01 wp-api-test CRON[2942]: (vagrant) CMD (cd /srv/www/wp-api-test.website/current && wp cron event run --due-now > /dev/null 2>&1)
Jun 24 10:15:35 wp-api-test mailhog[1843]: [APIv1] KEEPALIVE /api/v1/events
Jun 24 10:16:35 wp-api-test mailhog[1843]: [APIv1] KEEPALIVE /api/v1/events
Jun 24 10:17:01 wp-api-test CRON[3012]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun 24 10:17:35 wp-api-test mailhog[1843]: [APIv1] KEEPALIVE /api/v1/events
Jun 24 10:24:35 wp-api-test mailhog[1843]: message repeated 7 times: [ [APIv1] KEEPALIVE /api/v1/events]
Jun 24 10:25:09 wp-api-test systemd[1]: Starting Cleanup of Temporary Directories...
Jun 24 10:25:09 wp-api-test systemd-tmpfiles[3014]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Jun 24 10:25:09 wp-api-test systemd[1]: Started Cleanup of Temporary Directories.
Jun 24 10:25:35 wp-api-test mailhog[1843]: [APIv1] KEEPALIVE /api/v1/events

Code: Select all

--- 192.168.50.1 ping statistics ---
49 packets transmitted, 49 received, 0% packet loss, time 48124ms
rtt min/avg/max/mdev = 0.226/1.334/8.974/1.888 ms
Attachments
wp-api-test.dev-2017-06-24-12-09-46.log
(96.33 KiB) Downloaded 21 times
wp-api-test.dev-2017-06-24-11-53-09.log
(104.57 KiB) Downloaded 21 times
wp-api-test.dev-2017-06-24-11-36-02.log
(91.24 KiB) Downloaded 23 times
Post Reply