I am trying to install latest Meteor 1.6 using Chocolatey on windows.
My Windows configurations is
Processor - core i7, 2nd gen, 2.2 Ghz
RAM - 8 GB,
System Type - 64 bit
I also used below command in COMMAND PROMPT to start with installation,
choco install meteor -y --execution-timeout 10000
still I am facing below issue.
meteor v0.0.2 [Approved]
meteor package files install completed. Performing other installation steps.
Downloading meteor 64 bit
from 'https://packages.meteor.com/bootstrap-link?arch=os.windows.x86_64'
Progress: 4% - Saving 8.12 MB of 171.74 MB
Download of meteor-bootstrap-os.windows.x86_64.tar.gz (171.74 MB) completed.
ERROR: Chocolatey expected a file at 'C:\Users\HP\AppData\Local\Temp\chocolatey\
meteor\0.0.2\meteor-bootstrap-os.windows.x86_64.tar.gz' to be of length '180086547' but the length was '8552029'.
The install of meteor was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\meteor\tools\chocolateyinstall.ps1'.
See log for details.
Chocolatey installed 0/1 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Failures
- meteor (exited -1) - Error while running 'C:\ProgramData\chocolatey\lib\meteo r\tools\chocolateyinstall.ps1'.
See log for details.
I suggest do not use Windows CMD, better use Power Shell and the issue will be resolved.
Chocolatey is behaving very strange as you can see my question with error log.
Below is the success I got using Power Shell
I have just attempted the installation of the meteor package on my own virtual machine, and I can tell you that the installation was indeed successful.
Looking at the log, it would appear that the download of the tar.gz did not complete successfully, and as a result, the file is not the same size as it was expected based on the response headers.
Best advice would be to try the installation again.
I had exactly the same problem (same error message while installing meteor 1.6 on windows cmd shell runnning in admin mode) until i tried installing with powershell running in admninistrator mode and suspending windows defender. Hope this helps.
I would suggest making the timeout value about 100000. This will at least save you from the occasional termination of the download process due to maybe changes in internet speeds.
Related
I'm running Vagrant version 2.2.19 with VirtualBox version 6.1 on Mac OS Monterey version 12.3.1.
When running vagrant up or vagrant up --provision, I'm receiving the following error:
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
Upon checking the logs, in provisioner-utility-source-core.log I can see the following log:
[0;38;5;2m ▷ Running the [0m[1m[0;38;5;5m'utility-source-core'[21m[0;38;5;2m provisioner...[0m[0m[0m
[0m[39m[2m* Updating the "core" utility on the "master" branch...[21m[0m
fatal: unsafe repository ('/srv/provision/utilities/core' is owned by someone else)
To add an exception for this directory, call:
git config --global --add safe.directory /srv/provision/utilities/core
[0;38;5;9m ! The [0m[1m[0;38;5;5m'utility-source-core'[21m[0;38;5;9m provisioner ran into problems, the full log is available at [0m[1m[0;38;5;5m'/var/log/provisioners/2022.04.18_18-32-31/provisioner-utility-source-core.log'[21m[0;38;5;9m. It completed in [0m[1m[0;38;5;5m0[21m[0;38;5;9m seconds.[0m[0m
In the above, can see a fatal error:
unsafe repository ('/srv/provision/utilities/core' is owned by someone else)
However, I cannot see any resources online to solve the above fatal error.
What I've tried:
Running vagrant halt then vagrant destroy and then vagrant up to create the box again, and then running vagrant up to see if it solves things (get the same error)
Added Git SSH (using this guide) in case it was a Git error
Uninstalled and then reinstalled VirtualBox
Cleared out IPs from /etc/hosts/hosts, and then ran vagrant up again, to see if there were any conflicts.
Have tried running git config --global --add safe.directory /srv/provision/utilities/core, then re-ran vagrant up --provision - but it does nothing.
Note: I have allowed oracle permissions via security and privacy and have rebooted my machine so it's in effect.
Is there any way to get VVV running again?
This is a known issue that was fixed in newer versions of VVV. Update to at least VVV 3.10.1 and re-provision.
If it is still happening despite updating to newer VVV, raise a GitHub issue.
I'm the VVV project lead, usually when we see these issues we fix them, this isn't something you should need to fix yourself. But if you use stackoverflow to report bugs we don't see it. Either raise a GitHub issue or ask in the VVV slack.
https://github.com/Varying-Vagrant-Vagrants/VVV/issues/new/choose
i want to install MariaDB in Windows10.
my pc is x64.
and i download MariaDB server 10.6.7 (x86_64)
and i installed msi file.
but can't success install.. with rolling back action.
and show message this.
MariaDB 10.6 (x64) Setup Wizard ended premature
MariaDB 10.6 (x64) Setup Wizard ended prematurely because of an error. Your system has not been modified. To install this program at a later time, run Setup Wizard again. click the finish button to exit the Setup Wizard
i tried
regsvr32 C:\Windows\System32\vbscript.dll
regsvr32 vbscript.dll
and i tried install again visual C++ new version again,
and i tried update window.
but everything not worked for me..
give me solution, please
Just had the same issue with 10.7.3
It was due to Windows system variable TMPDIR incorrectly set to a non-existant directory, causing "innodb fatal error" during database initialization.
I had the same issue, and for me it seems the problem was the system clock. It was for some reason set to far into the future, the 2070s. MariaDB successfully installed once we corrected the system date.
I have an application that builds in 5 minutes on the Mac. When I try to build in Docker or directly in Ubuntu, the machine completely hangs at some point. It so bad that I can't even ssh into the machine. It eventually times out. I am using Meteor 1.4.2.3, Ubuntu 16.04 and Docker 16.04 with Meteor installed.
I thought maybe it was related to tar and 7z, so I upgraded tar and 7z. Still hangs. It hangs when I building on web.browser. There is high I/O waits and a bunch of blocked processes according to vmstat.
This is the command I'm running:
meteor build --allow-superuser --server-only --directory /tmp/build
Is their any way to get more info about what's going wrong? I also tried to
meteor remove ecmascript --allow-superuser
b/c one article said this may be an issue. Hangs.
I'm trying to run the latest Asp.Net 5 samples (currently 1.0.0-rc1-update1) on my Ubuntu 14.04 VM guest using VirtualBox on Windows 10. The sample code is being run via shared host directory.
I have the active and default DNX set as the CoreCLR x64.
When I have run the dnu restore command against either of the 2 web projects, the restore completes but with an error message. For example, for the HelloWeb project:
Unable to locate Dependency helloweb >= 1.0.0
If I run then command dnx web for the web projects I get the error message:
Error: Unable to load application or execute command 'Microsoft.AspNet.Server.Kestrel'. Available commands: web.
I have a related question here as I am also trying to also get the same samples running on my Windows machine. As they are basic and also unmodified, so I can't understand why they are not working. To make things worse, I actually had them running on this VM yesterday in the same manner I am trying here and as far as I'm aware, nothing has changed other than I have restarted the VM in the meantime.
Can anyone suggest why the projects are referencing themselves in this way and how I can resolve it?
The issue was being caused because the source code was being shared and the project.lock.json file had been created by the dnu restore process on Windows. I created a separate set of code samples and the code restored then ran fine.
This doesn't explain why the message was appearing but I assume the message Unable to locate Dependency helloweb >= 1.0.0 is actually a red herring and possibly refers to the fact that it can't replace the lock file.
I have installed MPICH2 1.4 version on RHEL.
Whenever I'm trying to run a program then it is throwing following error
unable to find mpd.conf file
How to resolve this problem.?
This error comes from running an old version of MPICH that requires some setup. You might try upgrading to a much newer version (the latest is 3.0.4) available at http://www.mpich.org and you don't have to worry about setting up MPD because it will use the newer process manager (Hydra) by default.