Guest-specific operations were attempted on a machine that is not ready

[Mike Nelson]

I got this message

Guest-specific operations were attempted on a machine that is not ready for guest communication. This should not happen and a bug should be reported.

I am a relative newbie to this and not sure how to report this. I did report problems with guest additions before , never resolved.

Looked for logs but got result

o new log found in 0ms with 1B of logs, 0 skipped line(s), 0 unreadable line(s).
File /var/log/apache2/serverspectest.dev-access_log was last modified on 2017/11/07 16:45:43 at UTC, size is 0B

I had just updated to Vagrant 2.0.1 and downloaded joomlatools 1.5

after vagrant init and up it got to point

==> default: Installing NFS client...

then does not complete in hours. t

Eventually completed.

New release 1.5.0 available for joomlatools/console.

Do you want to update now? [y/N] y

==> default: Machine booted and ready!

[default] GuestAdditions 5.1.30 running --- OK.

==> default: Checking for guest additions in VM...

==> default: [vagrant-hostsupdater] Checking for host entries

==> default: [vagrant-hostsupdater] Writing the following entries to (/etc/hosts)

==> default: [vagrant-hostsupdater]   33.33.33.58  joomlatools  # VAGRANT: 176b7f9ae7c84da24fd57a2fcfd0776e (default) / eb3c4b4f-f2f4-4412-aa65-f68fbdc1be75

==> default: [vagrant-hostsupdater] This operation requires administrative access. You may skip it by manually adding equivalent entries to the hosts file.

==> default: Setting hostname...

==> default: Configuring and enabling network interfaces...

==> default: Installing NFS client... [takes over an hour]

==> default: Exporting NFS shared folders...

==> default: Preparing to edit /etc/exports. Administrator privileges will be required...

Password:

==> default: Mounting NFS shared folders...

I'm on Mac OS X macOS 10.12.4 (16E195)

Virtual Box

5.1.30 r118389 (Qt5.6.3)

Any advice please. I have not done anything more with the box yet, just concerned about the bug warning

Mike Nelson

[Steven Rombauts]

Hi Mike,

When exactly did you get the "Guest-specific operations were attempted .." message? Your Vagrant output looks fine, besides the fact that it takes a long time to complete "Installing NFS client..." step.

What shouldn't be in there however is the prompt to update Joomlatools Console.  It could be a bug: Vagrant tries to install something on the box in the background by connecting over SSH, but the shell returns our "would you like to update to joomlatools/console" prompt and then keeps waiting for input. 

Could you let me know if you have run this box before, or if it was an install from scratch? Could you also verify that joomlatools/console has been updated to version 1.5 (run the command joomla --version on the box). If it is, do you still get this error when you boot it again?

Thanks,

Steven

--

---
You received this message because you are subscribed to the Google Groups "Joomlatools Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomlatools-d...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mike Nelson]

Hi Steven
on 11 Jan i did vagrant init joomlatools/box
then vagrant up.
after it got to the  ==> default: Installing NFS client... lasted for over an hour I exited it
tried next day
==> default: Checking if box 'joomlatools/box' is up to date...
==> default: There was a problem while downloading the metadata for your box
==> default: to check for updates. This is not an error, since it is usually due
==> default: to temporary network problems. This is just a warning. The problem
==> default: encountered was:
==> default: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to vagrantcloud.com:443
==> default: If you want to check for box updates, verify your network connection
==> default: is valid and try again.
==> default: Clearing any previously set forwarded ports...
completed OK:
    default:  * Restarting Apache httpd web server apache2
    default:    ...done.
==> default: Running triggers after up...
MikesPro:newScotJoomla mike1$
MikesPro:newScotJoomla mike1$ vagrant ssh
Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 4.2.0-27-generic x86_64)
started again and then the full results leading up to this error were:

MikesPro:newScotJoomla mike1$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'joomlatools/box'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'joomlatools/box' is up to date...
==> default: Setting the name of the VM: newScotJoomla_default_1515868017363_17828
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...

==> default: Machine booted and ready!
[default] GuestAdditions 5.1.30 running --- OK.
==> default: Checking for guest additions in VM...
==> default: [vagrant-hostsupdater] Checking for host entries
==> default: [vagrant-hostsupdater] Writing the following entries to (/etc/hosts)
==> default: [vagrant-hostsupdater]   33.33.33.58  joomlatools  # VAGRANT: 176b7f9ae7c84da24fd57a2fcfd0776e (default) / eb3c4b4f-f2f4-4412-aa65-f68fbdc1be75
==> default: [vagrant-hostsupdater] This operation requires administrative access. You may skip it by manually adding equivalent entries to the hosts file.
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Installing NFS client...

==> default: Exporting NFS shared folders...
==> default: Preparing to edit /etc/exports. Administrator privileges will be required...
Password:
==> default: Mounting NFS shared folders...

Guest-specific operations were attempted on a machine that is not
ready for guest communication. This should not happen and a bug
should be reported.

Joomla Console tools version 1.5.0

I did vagrant reload
no error but still no logs available , got message:
no new log found in 3ms with 1K of logs, 0 skipped line(s), 6 unreadable line(s).
File /var/log/apache2/phpmyadmin-access_log was last modified on 2018/01/16 16:40:20 at UTC, size is 7M
So, it looks as though original problem has gone
Created new site , got error several times
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111 "Connection refused")
site was created but
Error: Failed to start application: Could not connect to MySQL server.
tried phpMyAdmin got result

MySQL said:

#2002 - Connection refused — The server is not responding (or the local server's socket is not correctly configured).

mysqli_real_connect(): (HY000/2002): Connection refused

Connection for controluser as defined in your configuration failed.

mysqli_real_connect(): (HY000/2002): Connection refused


thanks