I am trying to containerize my application build, though, when running the build that uses bazel with bazel-gazelle inside a container I will get this error:
$ bazel run --spawn_strategy=local //:gazelle --verbose_failures
INFO: Analyzed target //:gazelle (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
ERROR: /home/workstation/.cache/bazel/_bazel_workstation/fb227af4c7b6aa39cc5b15d7fd9b737a/external/go_sdk/BUILD.bazel:43:15: GoToolchainBinary external/go_sdk/builder [for host] failed: (Exit 1): go failed: error executing command
(cd /home/workstation/.cache/bazel/_bazel_workstation/fb227af4c7b6aa39cc5b15d7fd9b737a/execroot/__main__ && \
exec env - \
GOROOT_FINAL=GOROOT \
external/go_sdk/bin/go tool link -o bazel-out/host/bin/external/go_sdk/builder bazel-out/host/bin/external/go_sdk/builder.a)
# Configuration: e0f1106e28100863b4221c55fca6feb935acec078da5376e291cf644e275dae5
# Execution platform: #local_config_platform//:host
/opt/go/pkg/tool/linux_amd64/link: mapping output file failed: invalid argument
Target //:gazelle failed to build
INFO: Elapsed time: 2.302s, Critical Path: 0.35s
INFO: 2 processes: 2 internal.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully
I tried to run it standalone:
$ /home/workstation/.cache/bazel/_bazel_workstation/fb227af4c7b6aa39cc5b15d7fd9b737a/external/go_sdk/bin/go tool link -o bazel-out/host/bin/external/go_sdk/builder bazel-out/host/bin/external/go_sdk/builder.a
/opt/go/pkg/tool/linux_amd64/link: mapping output file failed: invalid argument
and still got no success.
Never had this kind of link problem and the linker don't provide much more information. Tried to install all packages I could think of and still no luck.
For context:
Running Ubuntu 20.04 LTS
Docker 20.10.9
Bazel 4.2.2
Rules GO v0.31.0
Bazel Gazelle v0.25.0
Also tried to run it with the strace, though I don't think I am skilled enough to find meaningful information from the tool output.
#edit
For more context:
e$ /home/workstation/.cache/bazel/_bazel_workstation/fb227af4c7b6aa39cc5b15d7fd9b737a/external/go_sdk/bin/go tool link -v -o bazel-out/host/bin/external/go_sdk/builder bazel-out/host/bin/external/go_sdk/builder.a
HEADER = -H5 -T0x401000 -R0x1000
searching for runtime.a in /opt/go/pkg/linux_amd64/runtime.a
/opt/go/pkg/tool/linux_amd64/link: mapping output file failed: invalid argument
This question already has answers here:
WebDriverException: unknown error: DevToolsActivePort file doesn't exist while trying to initiate Chrome Browser
(44 answers)
unknown error: DevToolsActivePort file doesn't exist error while executing Selenium UI test cases on ubuntu
(15 answers)
Tests fail immediately with unknown error: DevToolsActivePort file doesn't exist when running Selenium grid through systemd
(2 answers)
Closed 2 years ago.
I have a testNG.xml test suite that i execute as maven project, the maven command works fine when executed through my terminal in local machine, but executing the same through Jenkins gives below error.
org.openqa.selenium.WebDriverException:
unknown error: Chrome failed to start: exited abnormally
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'
System info: host: 'jenkins-desktop', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.15.0-112-generic', java.version: '1.8.0_265'
Driver info: driver.version: ChromeDriver
remote stacktrace: #0 0x558d443c8959
The Webdriver instance is created in #BeforeMethod, below is code and ChromeOptions i have set.
public static void setChromeDriverProperty() {
WebDriverManager.chromedriver().setup();
//Set Chrome Driver properties.
ChromeOptions options = new ChromeOptions();
options.addArguments("--headless", "--disable-gpu", "--window-size=1920,1080","--ignore-certificate-errors");
options.addArguments("start-maximized"); // open Browser in maximized mode
options.addArguments("disable-infobars"); // disabling info-bars
options.addArguments("--disable-extensions"); // disabling extensions
options.addArguments("--disable-gpu"); // applicable to windows os only
options.addArguments("--no-sandbox", "--disable-dev-shm-usage"); // Bypass OS security model, overcome limited resource problems
driver = new ChromeDriver();
driver.manage().window().maximize();
}
I already have installed JMeter 5.X, I don't know why bzt is trying to download it again.
I edited the .bzt-rc file. Provided path of installed JMeter. Below code from .bzt-rc file.
path: C:\001_team\apache-jmeter-5.2.1\bin # path to local jmeter installation ~/.bzt/jmeter-taurus/{version}/bin/jmeter
Didn't find a way to set the existing path of installed JMeter.
Tried ti use existing JMETER in cmd:
bzt -o modules.jmeter.path=C:\001_Team\apache-jmeter-5.2.1\bin InContact.jmx
C:\001_TeamPlatinum>bzt InContact.jmx
13:29:30 INFO: Taurus CLI Tool v1.14.1[0m
13:29:30 INFO: Starting with configs: ['C:\\Users\\teams\\AppData\\Local\\Temp\\jmx_u679qs83.json'][0m
13:29:30 INFO: Configuring...[0m
13:29:30 INFO: Artifacts dir: C:\001_Team\2020-02-21_13-29-30.812601[0m
13:29:30 INFO: Preparing...[0m
[33m13:29:31 WARNING: Failed to check for updates[0m
13:29:31 INFO: Will install JMeter into C:\Users\teams\.bzt\jmeter-taurus\5.2.1[0m
[31m13:29:31 ERROR: Can't fetch https://jmeter.apache.org/download_jmeter.cgi[0m
13:29:31 INFO: Downloading: https://archive.apache.org/dist/jmeter/binaries/apache-jmeter-5.2.1.zip[0m
[31m13:29:32 ERROR: Error while downloading https://archive.apache.org/dist/jmeter/binaries/apache-jmeter-5.2.1.zip: Unsuccessful download from https://archive.apache.org/dist/jmeter/binaries/apache-jmeter-5.2.1.zip[0m
100% [ ] ETA: --:--:--
[31m13:29:32 ERROR: Internal Error: JMeter download failed: No more links to try[0m
13:29:32 INFO: Post-processing...[0m
13:29:32 INFO: Artifacts dir: C:\001_TeamPlatinum\2020-02-21_13-29-30.812601[0m
[33m13:29:32 WARNING: Done performing with code: 1[0m
This path setting must point to the root folder of your JMeter installation, not to the "bin" subfolder
So change your configuration to look like:
path: C:\001_team\apache-jmeter-5.2.1
or
bzt -o modules.jmeter.path=C:\001_Team\apache-jmeter-5.2.1
and Taurus should pick up your local JMeter installation.
References:
JMeter Location & Auto-Installation
Navigating your First Steps Using Taurus
I am using centos6.5 in which successfully deployed ambari-server2.4 with 3 nodes where hadoop,yarn,strom are successfully running.
I am using this url as reference for metron installation:
https://community.hortonworks.com/articles/60805/deploying-a-fresh-metron-cluster-using-ambari-serv.html
I am getting stuck when i try to install metron in ambari-server, adding metron in ambari-repository list is succeed but when installing metron nodes and elasticsearch over target node i get below exception:
Ambari-server Console error:
2017-05-25 16:33:01,138 - Installing package elasticsearch-2.3.3 ('/usr/bin/yum -d 0 -e 0 -y install elasticsearch-2.3.3')
2017-05-25 16:33:02,132 - Execution of '/usr/bin/yum -d 0 -e 0 -y install elasticsearch-2.3.3' returned 1. Error: Cannot retrieve repository metadata (repomd.xml) for repository: METRON-0.4.0. Please verify its path and try again
2017-05-25 16:33:02,132 - Failed to install package elasticsearch-2.3.3. Executing '/usr/bin/yum clean metadata'
2017-05-25 16:33:02,497 - Retrying to install package elasticsearch-2.3.3 after 30 seconds
Command failed after 1 tries
Terminal error:
file:///localrepo/repodata/repomd.xml: [Errno 14] Could not open/read file:///localrepo/repodata/repomd.xml
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: METRON-0.4.0. Please verify its path and try again
I can't seem to make RabbitMQ work on a fresh OS X Mountain Lion.
It simply fails to start.
System config below:
OS X 10.8.4
Xcode 4.6.3
Brew 0.9.4
I've upgraded brew and updated all packages:
brew upgrade
brew update
Installed RabbitMQ using the following command (I've also tried reinstalling it a couple of times without any luck):
brew install rabbitmq
Install output below:
server1:~ server1$ brew install rabbitmq
==> Downloading http://www.rabbitmq.com/releases/rabbitmq-server/v3.1.3/rabbitmq
Already downloaded: /Library/Caches/Homebrew/rabbitmq-3.1.3.tar.gz
==> /usr/bin/unzip -qq -j /usr/local/Cellar/rabbitmq/3.1.3/plugins/rabbitmq_mana
==> Caveats
Management Plugin enabled by default at http://localhost:15672
Bash completion has been installed to:
/usr/local/etc/bash_completion.d
To have launchd start rabbitmq at login:
ln -sfv /usr/local/opt/rabbitmq/*.plist ~/Library/LaunchAgents
Then to load rabbitmq now:
launchctl load ~/Library/LaunchAgents/homebrew.mxcl.rabbitmq.plist
Or, if you don't want/need launchctl, you can just run:
rabbitmq-server
==> Summary
🍺 /usr/local/Cellar/rabbitmq/3.1.3: 964 files, 23M, built in 2 seconds
Tried to start the server using the following command:
sudo rabbitmq-server start
Which gives me the following output:
Password:
RabbitMQ 3.1.3. Copyright (C) 2007-2013 VMware, Inc.
## ## Licensed under the MPL. See http://www.rabbitmq.com/
## ##
########## Logs: /usr/local/var/log/rabbitmq/rabbit#localhost.log
###### ## /usr/local/var/log/rabbitmq/rabbit#localhost-sasl.log
##########
Starting broker...
BOOT FAILED
===========
Error description:
{badmatch,{error,{no_such_vhost,<<"/">>}}}
Log files (may contain more information):
/usr/local/var/log/rabbitmq/rabbit#localhost.log
/usr/local/var/log/rabbitmq/rabbit#localhost-sasl.log
Stack trace:
[{rabbit_error_logger,boot,0,
[{file,"src/rabbit_error_logger.erl"},{line,42}]},
{rabbit,'-run_boot_step/1-lc$^1/1-1-',1,
[{file,"src/rabbit.erl"},{line,488}]},
{rabbit,run_boot_step,1,[{file,"src/rabbit.erl"},{line,487}]},
{rabbit,'-start/2-lc$^0/1-0-',1,[{file,"src/rabbit.erl"},{line,453}]},
{rabbit,start,2,[{file,"src/rabbit.erl"},{line,453}]},
{application_master,start_it_old,4,
[{file,"application_master.erl"},{line,274}]}]
BOOT FAILED
===========
Error description:
{could_not_start,rabbit,
{bad_return,
{{rabbit,start,[normal,[]]},
{'EXIT',
{rabbit,failure_during_boot,
{badmatch,{error,{no_such_vhost,<<"/">>}}}}}}}}
Log files (may contain more information):
/usr/local/var/log/rabbitmq/rabbit#localhost.log
/usr/local/var/log/rabbitmq/rabbit#localhost-sasl.log
{"init terminating in do_boot",{rabbit,failure_during_boot,{could_not_start,rabbit,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot,{badmatch,{error,{no_such_vhost,<<1 byte>>}}}}}}}}}}
Crash dump was written to: erl_crash.dump
init terminating in do_boot ()
server1:~ server1$
server1:~ server1$ sudo rabbitmq-server start
RabbitMQ 3.1.3. Copyright (C) 2007-2013 VMware, Inc.
## ## Licensed under the MPL. See http://www.rabbitmq.com/
## ##
########## Logs: /usr/local/var/log/rabbitmq/rabbit#localhost.log
###### ## /usr/local/var/log/rabbitmq/rabbit#localhost-sasl.log
##########
Starting broker...
BOOT FAILED
===========
Error description:
{badmatch,{error,{no_such_vhost,<<"/">>}}}
Log files (may contain more information):
/usr/local/var/log/rabbitmq/rabbit#localhost.log
/usr/local/var/log/rabbitmq/rabbit#localhost-sasl.log
Stack trace:
[{rabbit_error_logger,boot,0,
[{file,"src/rabbit_error_logger.erl"},{line,42}]},
{rabbit,'-run_boot_step/1-lc$^1/1-1-',1,
[{file,"src/rabbit.erl"},{line,488}]},
{rabbit,run_boot_step,1,[{file,"src/rabbit.erl"},{line,487}]},
{rabbit,'-start/2-lc$^0/1-0-',1,[{file,"src/rabbit.erl"},{line,453}]},
{rabbit,start,2,[{file,"src/rabbit.erl"},{line,453}]},
{application_master,start_it_old,4,
[{file,"application_master.erl"},{line,274}]}]
BOOT FAILED
===========
Error description:
{could_not_start,rabbit,
{bad_return,
{{rabbit,start,[normal,[]]},
{'EXIT',
{rabbit,failure_during_boot,
{badmatch,{error,{no_such_vhost,<<"/">>}}}}}}}}
Log files (may contain more information):
/usr/local/var/log/rabbitmq/rabbit#localhost.log
/usr/local/var/log/rabbitmq/rabbit#localhost-sasl.log
{"init terminating in do_boot",{rabbit,failure_during_boot,{could_not_start,rabbit,{bad_return,{{rabbit,start,[normal,[]]},{'EXIT',{rabbit,failure_during_boot,{badmatch,{error,{no_such_vhost,<<1 byte>>}}}}}}}}}}
Crash dump was written to: erl_crash.dump
init terminating in do_boot ()
I also get the following output when running the rabbitmqctl status:
server1:~ server1$ rabbitmqctl status
Status of node rabbit#localhost ...
Error: unable to connect to node rabbit#localhost: nodedown
DIAGNOSTICS
===========
nodes in question: [rabbit#localhost]
hosts, their running nodes and ports:
- localhost: [{rabbitmqctl1391,49583}]
current node details:
- node name: rabbitmqctl1391#server1
- home dir: /Users/server1
- cookie hash: 5K+867WqzDShyhtWE7X49Q==