Codeceptjs Error - Please make sure Selenium Server (ChromeDriver or PhantomJS) is running and accessible - selenium-chromedriver

CodeceptJS v3.0.5
Using test root "/Users/bhupendrarautela/extram"
login --
✖ "before all" hook: codeceptjs.beforeSuite for "test something" in 17ms
Error: Can't connect to WebDriver.
Error: Failed to create session.
Unable to connect to "http://127.0.0.1:4444/wd/hub", make sure browser driver is running on
that address.
If you use services like chromedriver see initialiseServices logs above or in wdio.log file
as the service might had problems to start the driver.
Please make sure Selenium Server (ChromeDriver or PhantomJS) is running and accessible
-- FAILURES:
1) login
"before all" hook: codeceptjs.beforeSuite for "test something":
Can't connect to WebDriver.
Error: Failed to create session.
Unable to connect to "http://127.0.0.1:4444/wd/hub", make sure browser driver is running on
that address.
If you use services like chromedriver see initialiseServices logs above or in wdio.log file
as the service might had problems to start the driver.
Please make sure Selenium Server (ChromeDriver or PhantomJS) is running and accessible
Error: Failed to create session.
Unable to connect to "http://127.0.0.1:4444/wd/hub", make sure browser driver is running
on that address.
If you use services like chromedriver see initialiseServices logs above or in wdio.log file as the service might had problems to start the driver.
FAIL | 0 passed, 1 failed // 19ms
Run with --verbose flag to see complete NodeJS stacktrace
Please help me with how to make sure Selenium Server (ChromeDriver or PhantomJS) is running and accessible.

Related

SASL Error connecting to remote libvirt over SSH: No worthy mechs found

I have a server running Ovirt Node that I'm trying to manage remotely using libvirt. I have an SSH keypair installed and can ssh user#server -i ssh-privkey successfully. When I try to connect to qemu+ssh//user#host/system?keyfile=ssh-privkey, I get this error:
authentication failed: Failed to start SASL negotiation: -4 (SASL(-4): no mechanism available: No worthy mechs found)
That led me down the path of getting TLS keys and certificates installed on the client and the server mostly according to these instructions (the configuration is slightly different because I have only one host and am using Terraform to manage the certificates*). However, I still get the same error. When I look at the output of libvirt --listen --verbose on the server when a connection failed, the only useful output is this:
error : virNetSocketReadWire:1792 : End of file while reading data: Input/output error
I have checked every firewall between the client and the server and they should all be wide open. What else could be the cause of this error?
* The goal is ultimately to use Terraform to provision libvirt resources, however I get the same errors trying to connect with virsh and virt-manager.
UPDATE: It's easier to connect just via SSH; this question exists because I couldn't figure out how to turn off SASL. It turns out SASL is enabled for SSH connections due to vdsm setting auth_unix_rw="sasl" in /etc/libvirt/libvirtd.conf. Removing that config means I can just use my SSH private key as I intended. The TLS configuration was a wild goose chase that was further hindered by vdsm changing the configured location of all the PKI files.
You're likely missing a RPM package on your client host. First on the virtualization host check /etc/sasl2/libvirt.conf and see what 'mech_list' setting is uncommented.
Back on your client you'll need to install a 'cyrus-sasl-XXXX' RPM that provides the same mechanism that the server is set to use. For a modern libvirt install it will probably be using 'cyrus-sasl-scram' for plain username/password auth, but for older installs, it might still be using 'cyrus-sasl-md5'

Openshift oc login failed from mac

Whenever I try to login to Openshift through CLI I get the following error.
error: dial tcp: lookup api.rhocp1.xxx.com on xxx.xxx.225.1:53: no such host - verify you have provided the correct host and port and that the server is currently running.
But from windows it works absolutely fine. Strange.
Any help is appreciated.

VerneMQ MySQL authentication

I already have installed vernemq in my cloud server, everything seems running fine. But from any client, it is unable to connect the broker using username/password authentication. The authentication is based on MySQL, the Lua script is running fine. But strangely the authentication not working or something is wrong. I couldn't trace anything as nothing shows in Log. The only debug message I see is as follows:
[debug] <0.227.0>#plumtree_broadcast:schedule_lazy_tick:720 0ms mailbox traversal, schedule next lazy broadcast in 10000ms, the min interval is 10000ms
OS : Ubuntu 18.04
MySQL Version : 5.7.29
VerneMQ Version : 1.10
That debug log message is unrelated (it shows load information on the metadata exchange protocol).
Please make sure the password formats/hashing methods are compatible between VerneMQ and MySQL.

Server requires auth switch, but no auth switch handler provided

I'm using node-mysql2 and receiving this error message when connecting to a production instance of mysql via a wan:
Server requires auth switch, but no auth switch handler provided
This error is not received when connecting to our local dev server.
Furthmore, connecting to this mysql instance by other means works fine (mysql cli, Toad)
node-mysql2 version: mysql2#1.1.2 installed via npm.
This error was allegedly fixed back in Aug (RC9) https://github.com/sidorares/node-mysql2/pull/331
I'm not very familiar with mysql, Is there a server setting we can change to workaround this issue?
So it turns out this error also occurs with other libraries which give more meaningful error messages, e.g.: Authentication with old password no longer supported, use 4.1 style passwords
Solution from here: https://forums.mysql.com/read.php?38,593423,593423
SET SESSION old_passwords=0;
SET PASSWORD=PASSWORD('YOURDATABASEPASSWORD');

app breaks down and cannot use rhc commands

My app (rails a ruby-1.9) is currently serving a 503.
All the rhc commands don't work. I cannot even do rhc ssh <my-app>.
I tried to restart the app from the web, it gives me this:
Unable to perform action on app object. Another operation is already running.
Unhandled exception reference #78227deaed799856c3c386744c8be9c4: Unable to perform action on app object. Another operation is already running.