After I installed Ros Noetic with this command - sudo apt install ros-noetic-desktop-full. There are 2-3 errors which are of not being able to fetch a few packages(armadillo and other). I downloaded them later.
But after I typed this command - source /opt/ros/noetic/setup.bash, I got this error of - no such file or directory. I then added this command in .bashrc file and removed it after one execution realizing this file cannot be found by the computer (may be a different location but still can't locate). Then I reinstalled ROS noetic, this time in another folder I made .... and I still cannot locate the file and I am getting the same error again. I am using Oracle VM VirtualBox Manager with UBUNTU_20.04. I also installed Guest editions(for full screen purposes)
Related
I'm using a Linux Debian terminal, trying to install a Github .zip file by following a walkthrough (from Chromebook). They're using a Windows terminal and access the zip file from a G: drive. They run the following:
C:\Users\zasur>G:
G:\>cd filename.zip
G:\filename>npm install
Which installs the Github zip. I've looked all over online and tried a few different solutions but can't get past the second command they run.
I was able to open /mnt/chromeos/MyFiles/Downloads from Linux by sharing the Downloads folder with it.
I'm not sure how to change the directory from here to the filename.zip and/or run commands from it. Whenever I try to run cd filename.zip or cd /mnt/chromeos/MyFiles/Downloads/filename.zip it always fails. Is this even possible on a Chromebook?
In my windows 10, after I installed
vagrant plugin install vagrant-vmware-desktop
then i execute vagrant up I get error:1
>vagrant up
Vagrant encountered an error while attempting to load the utility
service key file. This error can occur if the Vagrant VMware Utility
has not yet been installed, or if it was installed incorrectly. If
this error persists after running the Vagrant VMware Utility installer
again, please contact support at: support#hashicorp.com
Information about the Vagrant VMware Utility, including installation
instruction, can be found here:
https://www.vagrantup.com/docs/vmware/vagrant-vmware-utility.html
Path: C:/ProgramData/hashicorp/vagrant-vmware-desktop/certificates/vagrant-utility.client.crt
Error: No such file or directory # rb_sysopen - C:/ProgramData/hashicorp/vagrant-vmware-desktop/certificates/vagrant-utility.client.crt
It seems the Vagrant Vmware utility is missing, you can run the following command and check if the Vmware utility service is running or not
net start vagrant-vmware-utility
If it is not present, install it from here for windows. you can look for other links for different platforms.
Once installed re-install the utility -
vagrant plugin install vagrant-vmware-desktop
After installation is complete you should have a folder similar to this:
C:\HashiCorp\VagrantVMwareUtility
Windows 10 / VirtualBox / Vagrant / Homestead
I've begun experiencing random errors like the following every time I run laravel new PROJECT:
85/95 [=========================>--] 89% Failed to extract laravel/framework: (2) unzip -qq '/home/vagrant/code/PROJECT/vendor/composer/tmp-f4716ecd4eeb00c7e1d90a043cc4a5b5' -d '/home/vagrant/code/PROJECT/vendor/composer/123a874a'
/home/vagrant/code/PROJECT/vendor/composer/123a874a/laravel-framework-6350d19/src/Illuminate/Database/Eloquent/Collection.php bad CRC 5a1bfd51 (should be 58446226)
The archive may contain identical file names with different capitalization (which fails on case insensitive filesystems)
Unzip with unzip command failed, falling back to ZipArchive class
The errors occur on different packages each time. Sometimes the process completes and displays Application ready!, many times it fails.
So far I've tried:
composer clearcache
reinstalling vagrant
reinstalling vagrant laravel/homestead box
reinstalling homestead
deactivating the Windows Linux subsystem. I had enabled it for another purpose around the time the errors began, and wondered if it did something with case sensitivity.
All with no effect. Any ideas?
Solved
Finally made it work only by reinstalling VirtualBox, Vagrant, the Vagrant homestead box, and Homestead. Before reinstalling VirtualBox and Vagrant, I removed my homestead directory and all related application data files (in my case located in C:\Users\USERNAME).
It appears networking issues within VirtualBox were corrupting files pulled by "git clone" commands in the "laravel new" process.
So I am having some issues with vagrant. I had initially tried to report this as an issue on the vagrant github issue boards, but they kept closing the issues without responding to them. I guess they decided I wasn't worth their time, or they were just behaving unprofessionally. Anyway, Here is the problem: I use vagrant with virtualbox, and a new version of virtualbox was recently released that is, unfortunately, not compatible with the latest vagrant installation.
However, the people at hashicorp have already updated the source code so that it is compatible with the new version of virtualbox, but you have to build the vagrant executable from the source repo (instructions here). So I followed the instructions and vagrant is working just like it used to.....when the only command I need to run is vagrant up. I should also mention ahead of time that, in order to run the vagrant dev build, the current working directory needs to be the root of the source code repo and the dev build can only be run using the following command with ruby:
bundle exec vagrant
With that being said, I needed to update one of my custom boxes, so I built a vm in the updated version of virtualbox and ran the below command
bundle exec vagrant package --base go --vagrantfile ../../vagrant/vagrantfile
After an extended period of time, vagrant spat back out the following error
The executable 'bsdtar' Vagrant is trying to run was not found in the %PATH% variable. This is an `error. Please verify this software is installed and on the path.`
I should also note that I use a windows machine and that this error never occurred when using the installed version of vagrant. At this point, I had posted the issue on github to get some input from the devs, but they (very unprofessionally) decided to ignore my requests for help and close the issues without providing any response. I used the GNUwin32 project to make numerous unix commands available to my Windows environment and added the folder to my PATH environment variable. I then run the same command again to create my new box and it works!! So then I upload it to the vagrant cloud and attempt to update the vagrant box that is stored on my system by running the following command:
bundle exec vagrant box update
Then, after waiting for a while, vagrant then spat this error out at me:
The box failed to unpackage properly. Please verify that the box
file you're trying to add is not corrupted and that enough disk space
is available and then try again.
The output from attempting to unpackage (if any):
C:\gnuwin32\bin/bsdtar.EXE: invalid option -- s
Usage:
List: bsdtar.EXE -tf <archive-filename>
Extract: bsdtar.EXE -xf <archive-filename>
Create: bsdtar.EXE -cf <archive-filename> [filenames...]
Help: bsdtar.EXE --help
Another error, and still involving this bsdtar tool. It does not appear that anyone else is reporting the issue I am running into because I think they are just waiting for hashicorp to release the new official installation, but, just to give you a look into their priorities, the version of virtualbox that was released which no longer worked with vagrant was released back on December 10. It has been over a month since and there is still no updated release.
So, I am hoping that someone out there might be able to find out why I keep running into these errors when trying to use vagrant's dev build and provide a solution. If not, then maybe if someone else is able to reproduce the issue and report it to hashicorp, maybe they will listen to someone else.
If you are on Ubuntu 20.04 then bsdtar was removed. Try to install libarchive-tools package.
$ sudo apt-get install libarchive-tools
I figured it out. My original hypothesis was correct: since vagrant is a tool that was built primarily to be run on linux machines, then vagrant runs in windows, the installation includes a mingw environment with all of the dependencies vagrant needs to function and which the installed vagrant executable imports into the console session when run. This why the dev build kept failing: because it was not importing this mingw environment. So, in order to fix the issue, I first cloned the vagrant source code repo from github and followed the instructions I linked to above to build the executable from the source repo. I then copied all of the files in the source repo into the following folder:
<hashicorp install folder root>\Vagrant\embedded\gems\2.2.6\gems\vagrant-<version num>
So, for me, the destination directory is C:\HashiCorp\Vagrant\embedded\gems\2.2.6\gems\vagrant-2.2.6
This directory is identical to the source code repo, and copying the source code repo to the above folder replaces the installation version of vagrant with the dev build. After I did this, running the vagrant commands which had failed previously normally (as in, without using ruby or bundle) worked. I hope this helps someone else out there who Hashicorp has decided is not worth their time.
I am running MacOS Mojave 10.14 with XAMPP 7.2.5
Earlier today, I tried to start up XAMPP after a crash/restart. XAMPP Manager was unable to start the MYSQL Server. Apache did start correctly.
Figuring there was a potential corruption, I used my Time Machine to restore my XAMPP folder (to a 36-hour old file) in Applications.
Now when I try to run XAMPP Manager, I get a "Cannot find any readable ctl script" error message.
I've tried to run MYSQL Server directly from CLI. I receive the following message:
./mysql.server: line 200: my_print_defaults: command not found
Starting MariaDB
ERROR! Couldn't find MariaDB server (/Applications/XAMPP/xamppfiles/bin/mysqld_safe)
Any thoughts on how to resolve?
The issue has to do with a quirk with Time Machine - it does not completely regenerate all recorded folders/files. A bit of a pain.
I was able to run XAMPP from the command line:
-> cd /Applications/xampp/xamppfiles
-> sudo ./xampp start
To check on MYSQL status:
-> mysql status -u [username] -p [password]
Issue resolved
I spend a day on this and the solution in my case was:
Uninstall XAMPP
Delete all files except my databases folders from Applications/XAMPP/xamppfiles/var/mysql (there was some .err and log files if I remember well)
Reinstall XAMPP
Reconfigure it. If you use different user than root to access your databases you need to recreate it.
I got the "Cannot find any readable ctl script" error after a Time Machine restoration, too. I'm on 10.12.6 and XAMPP 5.6.
You are correct that it appears to be a TM issue, but I was able to resolve it by entering TM and specifically selecting the directories in XAMPP/xamppfiles/ that TM would not copy over by just selecting XAMPP/xamppfiles/. (In your case, you would not want to copy over /var/mysql, assuming you want to keep your data.)
Relief. There's nothing worse than realizing your trusty backup is not so trusty.