search

Seravo / wordpress

The WordPress project layout used by many of Seravo's customers, suitable also for local development with Vagrant and git deployment
https://seravo.com
GNU General Public License v3.0
104 stars 54 forks source link

RawFile#0 failed to create the raw output file /home/petri/seravo/wp-palvelu-vagrant/ubuntu-bionic-18.04-cloudimg-console.log (VERR_FILE_NOT_FOUND) #166

Closed ottok closed 3 years ago

ottok commented 3 years ago

With box 'seravo/wordpress' (v20201205.0.0) running vagrant up yielded:

...
==> seravocom-box: Running 'pre-boot' VM customizations...
==> seravocom-box: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "be948521-2eae-45ab-b686-7b518348bf2f", "--type", "headless"]

Stderr: VBoxManage: error: RawFile#0 failed to create the raw output file /home/petri/seravo/wp-palvelu-vagrant/ubuntu-bionic-18.04-cloudimg-console.log (VERR_FILE_NOT_FOUND)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

VirtualBox shows:

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

The problem does not manifest when using the Vagrant box seravo/wordpress-beta

marttihyvonen commented 3 years ago

I have a same issue, thanks for investigating this :)

elguitar commented 3 years ago

^ Accidental close. That SHOULD work though

marttihyvonen commented 3 years ago

I also got this fixed, when I disabled serial port in VirtualBox configuration as advised in here: https://github.com/joelhandwell/ubuntu_vagrant_boxes/issues/1

elguitar commented 3 years ago

Thank you for reporting @marttihyvonen!

The connected serial port is indeed the problem at hand.

elguitar commented 3 years ago

Could you test with the new wordpress-beta box (v20210114.0.0)?

With the new box, the serial connection disconnecting should not be needed anymore.

ottok commented 3 years ago

Latest wordpress-beta works on the machine where I was able to reproduce the original error, so I deem this as fixed now.

dubbajones commented 3 years ago

VM works now. Thank you!

elguitar commented 3 years ago

This is fixed now, and there has been no reports of users who use the faulty box. Closing.