On running command solana-test-validator on windows system, getting an error
[2022-01-06T06:54:41.602352800Z INFO solana_test_validator] solana-validator 1.9.0 (src:7782d34b; feat:378846963)
[2022-01-06T06:54:41.602479300Z INFO solana_test_validator] Starting validator with: ArgsOs {
inner: [
"solana-test-validator",
],
}
[2022-01-06T06:54:41.602617400Z WARN solana_perf] CUDA is disabled
[2022-01-06T06:54:41.602720300Z INFO solana_perf] AVX detected
[2022-01-06T06:54:41.602823600Z INFO solana_perf] AVX2 detected
[2022-01-06T06:54:41.606436300Z INFO solana_faucet::faucet] Faucet started. Listening on: 0.0.0.0:9900
[2022-01-06T06:54:41.606635600Z INFO solana_faucet::faucet] Faucet account address: 2P4mpwfirxqrL3naJD7C5UHYynPgVugaRu9sBT6m73EZ
Ledger location: test-ledger
Log: test-ledger\validator.log
⠁
⠉ Initializing...
[2022-01-06T06:54:44.975790700Z INFO solana_ledger::blockstore] "test-ledger\\rocksdb" open took 3.3s
[2022-01-06T06:54:44.981740300Z INFO solana_metrics::metrics] metrics disabled: SOLANA_METRICS_CONFIG: environment variable not found
[2022-01-06T06:54:44.982273700Z INFO solana_metrics::metrics] datapoint: shred_insert_is_full total_time_ms=0i slot=0i ⠒ Initializing...
[2022-01-06T06:54:45.595853800Z ERROR solana_ledger::blockstore] tar stdout:
[2022-01-06T06:54:45.596099200Z ERROR solana_ledger::blockstore] tar stderr: tar: Can't launch external program: bzip2
Error: failed to start validator: Failed to create ledger at test-ledger: blockstore error```
This is a current annoyance with natively using Windows with solana-test-validator. It shells out to tar with bzip2, which isn't available in the default Windows shell.
As a workaround, try installing Git BASH and then running solana-test-validator from a Git BASH shell.
Source code for the issue can be found at: https://github.com/solana-labs/solana/blob/f1e2598baa80a0ad4e8450c8b5e3c5ab164f501c/ledger/src/blockstore.rs#L3789-L3814 -- the j flag indicates to use bzip2
I have tried the solutions I found online for this, but none of them seem to work...
Even after installing blogdown from github and updating hugo, I get a timeout error.
remotes::install_github('rstudio/blogdown')
blogdown::update_hugo()
That is, when I run blogdown::serve_site I get this error:
Launching the server via the command: C:\Users\Master\AppData\Roaming\Hugo\hugo.exe server --bind 127.0.0.1 -p 4321 --themesDir themes -t hugo-future-imperfect -D -F --navigateToChanged ERROR: The process "10244" not found. Error: It took more than 30 seconds to launch the server. There may be something wrong. The process has been killed. If the site needs more time to be built and launched, set options(blogdown.server.timeout) to a larger value.
Is there another way to fix this?
What is causing this error?
Thanks!
I have the same problem on Kubuntu 20.10. I installed latest blogdown and hugo serveral days ago. I have blogdown 0.21.47 and hugo 0.79.0 on Kubuntu. Finally, I found a method to fix it.
Close Rstudio
Open terminal
Enter directory of your website
Execute hugo server -D
Press Ctrl C to stop
Open Rstudio
Click Addin -> BLOGDOWN -> Serve Site
I don't know why it works or whether it works in your case. Please test it and let us know whether it works.
I am running into the same problem.
blogdown::serve_site()
wont work:
Error: It took more than 30 seconds to launch the server. An error might have occurred with hugo. You may run blogdown::build_site() and see if it gives more info. If the site is very large and needs more time to be built, set options(blogdown.server.timeout) to a larger value.
although blogdown::build_site() works smoothly. The blogdown::serve_site() function works fine for a newly created project/website.
For repository see here.
Not sure if it is a blogdown, hugo or academic theme issue.
sessionInfo()
R version 4.0.3 (2020-10-10)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows 10 x64 (build 17763)
Matrix products: default
locale:
[1] LC_COLLATE=Dutch_Netherlands.1252 LC_CTYPE=Dutch_Netherlands.1252
[3] LC_MONETARY=Dutch_Netherlands.1252 LC_NUMERIC=C
[5] LC_TIME=Dutch_Netherlands.1252
attached base packages:
[1] stats graphics grDevices utils datasets methods base
other attached packages:
[1] servr_0.20
loaded via a namespace (and not attached):
[1] Rcpp_1.0.5 rstudioapi_0.13 knitr_1.30 magrittr_2.0.1 mnormt_2.0.2 pbivnorm_0.6.0
[7] R6_2.5.0 rlang_0.4.9 tools_4.0.3 tmvnsim_1.0-2 xfun_0.19 htmltools_0.5.0
[13] yaml_2.2.1 digest_0.6.27 lavaan_0.6-7 bookdown_0.21 processx_3.4.5 later_1.1.0.1
[19] promises_1.1.1 ps_1.4.0 evaluate_0.14 rmarkdown_2.5 blogdown_0.21.50 compiler_4.0.3
[25] stats4_4.0.3 jsonlite_1.7.1 httpuv_1.5.4
I had the same problem on. Installing "go" (https://golang.org/doc/install) helped - this was missing after my clean install of big sur.
I'm trying to update debian 9 and virtualbox can't be upgrated...
I'm getting the error:
vboxdrv.sh: failed: Cannot unload module vboxdrv.
Does anybody has any idea ?
$ apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
virtualbox-5.1
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/66.9 MB of archives.
After this operation, 6,144 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 261193 files and directories currently installed.)
Preparing to unpack .../virtualbox-5.1_5.1.36-122089~Debian~stretch_amd64.deb ...
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
dpkg: error processing archive /var/cache/apt/archives/virtualbox-5.1_5.1.36-122089~Debian~stretch_amd64.deb (--unpack):
subprocess new pre-removal script returned error exit status 1
A copy of VirtualBox is currently running. Please close it and try again.
Please note that it can take up to ten seconds for VirtualBox to finish running.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxdrv.service → /lib/systemd/system/vboxdrv.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxballoonctrl-service.service → /lib/systemd/system/vboxballoonctrl-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxautostart-service.service → /lib/systemd/system/vboxautostart-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxweb-service.service → /lib/systemd/system/vboxweb-service.service.
vboxdrv.sh: failed: Cannot unload module vboxdrv.
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root.
Errors were encountered while processing:
/var/cache/apt/archives/virtualbox-5.1_5.1.36-122089~Debian~stretch_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Seen in the error messages you posted:
A copy of VirtualBox is currently running. Please close it and try again.
Please note that it can take up to ten seconds for VirtualBox to finish running.
Did you try that ?
I have Debian Linux(64-bit) in VirtualBox.
Ram: 8Gb (for Debian 4Gb)
CPU: i5-3470
If any other details are needed please tell me.
I have followed instructions written here, and here you can see the console log.
For some reason I am unable to to build phantomjs and I can't understand why its not working... Have searched a lot, but couldn't find any thread which would be about this error.
--- EDIT ---
When I executed this command:
./configure --with-openssl-includes=/usr/include/openssl-1.0/ --with-openssl-libraries=/usr/lib/openssl-1.0/
Output was this:
--with-openssl-includes=/usr/include/openssl-1.0/: invalid command-line switch
--with-openssl-libraries=/usr/lib/openssl-1.0/: invalid command-line switch
The output of the console has changed but I still get errors: https://pastebin.com/wbgi8syg
Looks like you are on stretch (or later) and that you are already aware of the libssl vs libssl1.0 case.
Therefore, if you don't have libssl-dev installed, this line will get you further:
python build.py --qt-config "-I /usr/include/openssl-1.0/ -L /usr/lib/openssl-1.0/"
If you already have it installed and my suggestion doesn't work, you can uninstall libssl-dev for the time to build phantomjs which will likely avoid having to play further with configuration related variables.
I install Erl7.3 and rabbitmq-server 3.6.2. I using Win7 32bit. After installing when I run 'rabbitmq-server' command it gives:
ERROR: node with name "rabbit" already running on "admin-PC"
When I run 'net stop RabbitMQ && net start RabbitMQ' it stopped RabbitMQ service and restarted successfully.
After that When I run "rabbitmq-plugins enable rabbitmq_management", it gives following errors and nothing is shown at http://localhost:15672:
Plugin configuration unchanged.
Applying plugin configuration to rabbit#admin-PC... failed.
Error: {undef,[{crypto,module_info,[attributes],[]},
{rabbit_misc,module_attributes,1,
[{file,"src/rabbit_misc.erl"},{line,817}]},
{rabbit_misc,'-all_module_attributes/1-fun-0-',3,
[{file,"src/rabbit_misc.erl"},{line,837}]},
{lists,foldl,3,[{file,"lists.erl"},{line,1262}]},
{rabbit_boot_steps,find_steps,1,
[{file,"src/rabbit_boot_steps.erl"},
{line,40}]},
{rabbit_boot_steps,run_boot_steps,1,
[{file,"src/rabbit_boot_steps.erl"},
{line,26}]},
{rabbit,start_apps,1,[{file,"src/rabbit.erl"},{line,451}]},
{rabbit_plugins,ensure,1,
[{file,"src/rabbit_plugins.erl"},{line,52}]}]}
For your information, I set environmental variables as:
'Variable name: ERLANG_HOME', 'Variable value: C:\Program Files\erl7.3';
'Variable name: RABBITMQ_SERVER', 'Variable value: C:\Program Files\RabbitMQ Server\rabbitmq_server-3.6.2'
and system path "%ERLANG_HOME%;;%RABBITMQ_SERVER%\sbin"
How to resolve this errors?
rabbitmq management plugin needs the cryptopakage to work.
see:
Error: {undef,[{crypto,module_info,[attributes],[]},
{rabbit_misc,module_attributes,1,
Try to use the Erlang 18.3 version.
EDIT
After installing when I run 'rabbitmq-server' command it gives:
ERROR: node with name "rabbit" already running on "admin-PC"
This is normal since rabbitmq-server starts the server, but you have rabbitmq installed and running as windows service.
And you should use the 64 bit version