a11ywatch build command fails with "Failed to execute compose-compose command" error about a11ywatch HOT 16 CLOSED

I accidentally closed that. I was going to add that the issue seems to be related to me not running it with elevated permissions- sudo and root both say it is not found.

from a11ywatch.

Hello. I reinstalled crawler, turned out it wouldn't install because it did not have the apt package protobuf-compiler. I got this error when starting allywatch :

found 0 vulnerabilities
constellation@pop-os:~$

@a11ywatch/[email protected] start
NODE_ENV=production node ./server.js

Platform node has already been set. Overwriting the platform with node.
Application started in SUPER mode. All restrictions removed.
MongoDB not established. Start mongo on port 27017 to persist data.
node:internal/errors:491
ErrorCaptureStackTrace(err);
^

Error: listen EADDRINUSE: address already in use 0.0.0.0:3280
at Server.setupListenHandle [as _listen2] (node:net:1733:16)
at listenInCluster (node:net:1781:12)
at doListen (node:net:1930:7)
at process.processTicksAndRejections (node:internal/process/task_queues:83:21) {
code: 'EADDRINUSE',
errno: -98,
syscall: 'listen',
address: '0.0.0.0',
port: 3280
}

Node.js v18.13.0

This is the error for the crawl, i still don't think it is starting:

constellation@pop-os:~$ a11ywatch crawl -d -u https://a11ywatch.com > results.json thread 'main' panicked at 'called Result::unwrap()on anErrvalue: Status { code: Unknown, message: "transport error", source: Some(tonic::transport::Error(Transport, hyper::Error(Io, Kind(BrokenPipe)))) }', /home/constellation/.cargo/registry/src/github.com-1ecc6299db9ec823/a11ywatch_cli-0.8.36/src/rpc/client.rs:61:50 note: run withRUST_BACKTRACE=1environment variable to display a backtrace constellation@pop-os:~$ RUST_BACKTRACE=full a11ywatch crawl -d -u https://a11ywatch.com > results.json thread 'main' panicked at 'calledResult::unwrap()on anErr value: tonic::transport::Error(Transport, hyper::Error(Connect, ConnectError("tcp connect error", Os { code: 111, kind: ConnectionRefused, message: "Connection refused" })))', /home/constellation/.cargo/registry/src/github.com-1ecc6299db9ec823/a11ywatch_cli-0.8.36/src/rpc/client.rs:51:44 stack backtrace: 0: 0x564d8b1df840 - std::backtrace_rs::backtrace::libunwind::trace::h32eb3e08e874dd27 at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5 1: 0x564d8b1df840 - std::backtrace_rs::backtrace::trace_unsynchronized::haa3f451d27bc11a5 at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5 2: 0x564d8b1df840 - std::sys_common::backtrace::_print_fmt::h5b94a01bb4289bb5 at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/sys_common/backtrace.rs:66:5 3: 0x564d8b1df840 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hb070b7fa7e3175df at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/sys_common/backtrace.rs:45:22 4: 0x564d8b2055ae - core::fmt::write::hd5207aebbb9a86e9 at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/core/src/fmt/mod.rs:1202:17 5: 0x564d8b1d93c5 - std::io::Write::write_fmt::h3bd699bbd129ab8a at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/io/mod.rs:1679:15 6: 0x564d8b1e1073 - std::sys_common::backtrace::_print::h7a21be552fdf58da at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/sys_common/backtrace.rs:48:5 7: 0x564d8b1e1073 - std::sys_common::backtrace::print::ha85c41fe4dd80b13 at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/sys_common/backtrace.rs:35:9 8: 0x564d8b1e1073 - std::panicking::default_hook::{{closure}}::h04cca40023d0eeca at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:295:22 9: 0x564d8b1e0d5f - std::panicking::default_hook::haa3ca8c310ed5402 at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:314:9 10: 0x564d8b1e171a - std::panicking::rust_panic_with_hook::h7b190ce1a948faac at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:698:17 11: 0x564d8b1e1617 - std::panicking::begin_panic_handler::{{closure}}::hbafbfdc3e1b97f68 at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:588:13 12: 0x564d8b1dfcec - std::sys_common::backtrace::__rust_end_short_backtrace::hda93e5fef243b4c0 at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/sys_common/backtrace.rs:138:18 13: 0x564d8b1e1332 - rust_begin_unwind at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:584:5 14: 0x564d8aee2be3 - core::panicking::panic_fmt::h8d17ca1073d9a733 at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/core/src/panicking.rs:142:14 15: 0x564d8aee2d33 - core::result::unwrap_failed::hfaddf24b248137d3 at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/core/src/result.rs:1785:5 16: 0x564d8afb8409 - <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::hcf9baeb36b983707 17: 0x564d8af0a122 - tokio::runtime::park::CachedParkThread::block_on::h14b2d2762408a3f4 18: 0x564d8afa3e06 - tokio::runtime::scheduler::multi_thread::MultiThread::block_on::h93054af401d283e0 19: 0x564d8afd586d - tokio::runtime::runtime::Runtime::block_on::h166363f22be387fc 20: 0x564d8afbdeed - a11ywatch::commands::api::grpc::ApiClient::crawl_website::h1c1ca65f08ed1c24 21: 0x564d8afef7cb - a11ywatch::main::h3a6c1c072f7db8e9 22: 0x564d8af7a293 - std::sys_common::backtrace::__rust_begin_short_backtrace::h2c94df0a5e32694f 23: 0x564d8afceb19 - std::rt::lang_start::{{closure}}::hc77ce6720182e2b3 24: 0x564d8b1d3e1f - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::hb69be6e0857c6cfb at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/core/src/ops/function.rs:283:13 25: 0x564d8b1d3e1f - std::panicking::try::do_call::h396dfc441ee9c786 at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:492:40 26: 0x564d8b1d3e1f - std::panicking::try::h6cdda972d28b3a4f at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:456:19 27: 0x564d8b1d3e1f - std::panic::catch_unwind::h376039ec264e8ef9 at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panic.rs:137:14 28: 0x564d8b1d3e1f - std::rt::lang_start_internal::{{closure}}::hc94720ca3d4cb727 at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/rt.rs:148:48 29: 0x564d8b1d3e1f - std::panicking::try::do_call::h2422fb95933fa2d5 at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:492:40 30: 0x564d8b1d3e1f - std::panicking::try::h488286b5ec8333ff at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panicking.rs:456:19 31: 0x564d8b1d3e1f - std::panic::catch_unwind::h81636549836d2a25 at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/panic.rs:137:14 32: 0x564d8b1d3e1f - std::rt::lang_start_internal::h6ba1bb743c1e9df9 at /rustc/897e37553bba8b42751c67658967889d11ecd120/library/std/src/rt.rs:148:20 33: 0x564d8aff0878 - main 34: 0x7fac88029d90 - __libc_start_call_main at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16 35: 0x7fac88029e40 - __libc_start_main_impl at ./csu/../csu/libc-start.c:392:3 36: 0x564d8aee2f15 - _start 37: 0x0 - <unknown>

I'm going to reboot now, will update, but i think i'm getting to the bottom of this. Thank you for helping.

from a11ywatch.

@GECORegulatory thank you for the issue. The error message is actually incorrect. Just fixed it here e5c757f (available on cargo install a11ywatch_cli). Can you try running docker-compose --help in shell to see if the output is valid?

from a11ywatch.

constellation@pop-os:~$ docker-compose --help
Define and run multi-container applications with Docker.

Usage:
docker-compose [-f ...] [--profile ...] [options] [--] [COMMAND] [ARGS...]
docker-compose -h|--help

Options:
-f, --file FILE Specify an alternate compose file
(default: docker-compose.yml)
-p, --project-name NAME Specify an alternate project name
(default: directory name)
--profile NAME Specify a profile to enable
-c, --context NAME Specify a context name
--verbose Show more output
--log-level LEVEL Set log level (DEBUG, INFO, WARNING, ERROR, CRITICAL)
--ansi (never|always|auto) Control when to print ANSI control characters
--no-ansi Do not print ANSI control characters (DEPRECATED)
-v, --version Print version and exit
-H, --host HOST Daemon socket to connect to

--tls Use TLS; implied by --tlsverify
--tlscacert CA_PATH Trust certs signed only by this CA
--tlscert CLIENT_CERT_PATH Path to TLS certificate file
--tlskey TLS_KEY_PATH Path to TLS key file
--tlsverify Use TLS and verify the remote
--skip-hostname-check Don't check the daemon's hostname against the
name specified in the client certificate
--project-directory PATH Specify an alternate working directory
(default: the path of the Compose file)
--compatibility If set, Compose will attempt to convert keys
in v3 files to their non-Swarm equivalent (DEPRECATED)
--env-file PATH Specify an alternate environment file

Commands:
build Build or rebuild services
config Validate and view the Compose file
create Create services
down Stop and remove resources
events Receive real time events from containers
exec Execute a command in a running container
help Get help on a command
images List images
kill Kill containers
logs View output from containers
pause Pause services
port Print the public port for a port binding
ps List containers
pull Pull service images
push Push service images
restart Restart services
rm Remove stopped containers
run Run a one-off command
scale Set number of containers for a service
start Start services
stop Stop services
top Display the running processes
unpause Unpause services
up Create and start containers
version Show version information and quit
constellation@pop-os:~$

Here is the output from that command. After this, I recompiled with cargo install a11ywatch_cli However it still seems to be providing me with a permissionError in a python script. Here's a traceback:

Finished release [optimized] target(s) in 2m 52s

Replacing /home/constellation/.cargo/bin/a11ywatch
Replaced package a11ywatch_cli v0.8.35 with a11ywatch_cli v0.8.36 (executable a11ywatch)
constellation@pop-os:~$ a11ywatch build
WARNING: The EMAIL_SERVICE_URL variable is not set. Defaulting to a blank string.
WARNING: The EMAIL_CLIENT_ID variable is not set. Defaulting to a blank string.
WARNING: The EMAIL_CLIENT_KEY variable is not set. Defaulting to a blank string.
WARNING: The EMAIL_SERVICE_PASSWORD variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_L1_PLAN variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_L1_PLAN_YEARLY variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_L2_PLAN variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_L2_PLAN_YEARLY variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_L3_PLAN variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_L3_PLAN_YEARLY variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_L4_PLAN variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_L4_PLAN_YEARLY variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_L5_PLAN variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_L5_PLAN_YEARLY variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_H1_PLAN variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_H1_PLAN_YEARLY variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_H2_PLAN variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_H2_PLAN_YEARLY variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_H3_PLAN variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_H3_PLAN_YEARLY variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_H4_PLAN variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_H4_PLAN_YEARLY variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_H5_PLAN variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_H5_PLAN_YEARLY variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_CLIENT_KEY variable is not set. Defaulting to a blank string.
WARNING: The STRIPE_WH_SECRETS variable is not set. Defaulting to a blank string.
WARNING: The PAGESPEED_API_KEY variable is not set. Defaulting to a blank string.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699, in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 394, in _make_request
conn.request(method, url, **httplib_request_kw)
File "/usr/lib/python3.10/http/client.py", line 1282, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/lib/python3.10/http/client.py", line 1328, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/lib/python3.10/http/client.py", line 1277, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/lib/python3.10/http/client.py", line 1037, in _send_output
self.send(msg)
File "/usr/lib/python3.10/http/client.py", line 975, in send
self.connect()
File "/usr/lib/python3/dist-packages/docker/transport/unixconn.py", line 30, in connect
sock.connect(self.unix_socket)
PermissionError: [Errno 13] Permission denied

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755, in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 532, in increment
raise six.reraise(type(error), error, _stacktrace)
File "/usr/lib/python3/dist-packages/six.py", line 718, in reraise
raise value.with_traceback(tb)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699, in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 394, in _make_request
conn.request(method, url, **httplib_request_kw)
File "/usr/lib/python3.10/http/client.py", line 1282, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/lib/python3.10/http/client.py", line 1328, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/lib/python3.10/http/client.py", line 1277, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/lib/python3.10/http/client.py", line 1037, in _send_output
self.send(msg)
File "/usr/lib/python3.10/http/client.py", line 975, in send
self.connect()
File "/usr/lib/python3/dist-packages/docker/transport/unixconn.py", line 30, in connect
sock.connect(self.unix_socket)
urllib3.exceptions.ProtocolError: ('Connection aborted.', PermissionError(13, 'Permission denied'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/docker/api/client.py", line 214, in _retrieve_server_version
return self.version(api_version=False)["ApiVersion"]
File "/usr/lib/python3/dist-packages/docker/api/daemon.py", line 181, in version
return self._result(self._get(url), json=True)
File "/usr/lib/python3/dist-packages/docker/utils/decorators.py", line 46, in inner
return f(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/docker/api/client.py", line 237, in _get
return self.get(url, **self._set_request_timeout(kwargs))
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 555, in get
return self.request('GET', url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 498, in send
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', PermissionError(13, 'Permission denied'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/bin/docker-compose", line 33, in
sys.exit(load_entry_point('docker-compose==1.29.2', 'console_scripts', 'docker-compose')())
File "/usr/lib/python3/dist-packages/compose/cli/main.py", line 81, in main
command_func()
File "/usr/lib/python3/dist-packages/compose/cli/main.py", line 200, in perform_command
project = project_from_options('.', options)
File "/usr/lib/python3/dist-packages/compose/cli/command.py", line 60, in project_from_options
return get_project(
File "/usr/lib/python3/dist-packages/compose/cli/command.py", line 152, in get_project
client = get_client(
File "/usr/lib/python3/dist-packages/compose/cli/docker_client.py", line 41, in get_client
client = docker_client(
File "/usr/lib/python3/dist-packages/compose/cli/docker_client.py", line 170, in docker_client
client = APIClient(use_ssh_client=not use_paramiko_ssh, **kwargs)
File "/usr/lib/python3/dist-packages/docker/api/client.py", line 197, in init
self._version = self._retrieve_server_version()
File "/usr/lib/python3/dist-packages/docker/api/client.py", line 221, in _retrieve_server_version
raise DockerException(
docker.errors.DockerException: Error while fetching server API version: ('Connection aborted.', PermissionError(13, 'Permission denied'))

I believe this could possible be because I am not bui

from a11ywatch.

@GECORegulatory thank you for the detailed response, I believe this occurred from updating the perms on docker compose. Can you try to re-install it? This bug was valid due to the error message. Feel free to close if it solved on afterwards.

from a11ywatch.

You can also use a11ywatch build --local && a11ywatch start --local if you have nodejs and rust installed on the machine to skip docker if you are just experimenting with it. If you pass the -f flag in either step you can include the frontend UI.

from a11ywatch.

I reinstalled node.js and I think the build was successful but I can't access the frontend (none of those links work in the browser) or able to send in CLI scan requests. What should I do now? Here's the terminal output:
`

constellation@pop-os:~$ a11ywatch build -f --local && a11ywatch start --local
npm WARN deprecated [email protected]: We've written a new parser that's 6x faster and is backwards compatible. Please use @formatjs/icu-messageformat-parser
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: The apollo-server-plugin-base package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023). This package's functionality is now found in the @apollo/server package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.
npm WARN deprecated [email protected]: The apollo-server-types package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023). This package's functionality is now found in the @apollo/server package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.
npm WARN deprecated [email protected]: The apollo-server-errors package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023). This package's functionality is now found in the @apollo/server package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.
npm WARN deprecated [email protected]: The apollo-datasource package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023). See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.
npm WARN deprecated [email protected]: The apollo-server-env package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023). This package's functionality is now found in the @apollo/utils.fetcher package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.
npm WARN deprecated [email protected]: The apollo-reporting-protobuf package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023). This package's functionality is now found in the @apollo/usage-reporting-protobuf package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.
npm WARN deprecated [email protected]: The apollo-server-express package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023). This package's functionality is now found in the @apollo/server package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.
npm WARN deprecated [email protected]: The apollo-server-fastify package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023). This package's functionality is now found in the @apollo/server package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.
npm WARN deprecated [email protected]: The apollo-server package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023). This package's functionality is now found in the @apollo/server package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.
npm WARN deprecated [email protected]: The apollo-server-core package is part of Apollo Server v2 and v3, which are now deprecated (end-of-life October 22nd 2023). This package's functionality is now found in the @apollo/server package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.

added 804 packages, and audited 805 packages in 3m

56 packages are looking for funding
run npm fund for details

2 vulnerabilities (1 moderate, 1 high)

Some issues need review, and may require choosing
a different dependency.

Run npm audit for details.

added 3 packages, and audited 4 packages in 2s

found 0 vulnerabilities
npm WARN ERESOLVE overriding peer dependency
npm WARN deprecated [email protected]: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
npm WARN deprecated [email protected]: Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated [email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

added 705 packages, and audited 706 packages in 59s

115 packages are looking for funding
run npm fund for details

14 high severity vulnerabilities

To address all issues, run:
npm audit fix

Run npm audit for details.
npm WARN using --force Recommended protections disabled.
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /home/constellation/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/home/constellation/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR! /home/constellation/.npm/_logs/2023-01-14T22_48_41_243Z-debug-0.log
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /tmp/a11ywatch/web/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/tmp/a11ywatch/web/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR! /home/constellation/.npm/_logs/2023-01-14T22_48_41_694Z-debug-0.log
constellation@pop-os:~$

@a11ywatch/[email protected] start
NODE_ENV=production node ./server.js

Platform node has already been set. Overwriting the platform with node.
Application started in SUPER mode. All restrictions removed.
MongoDB not established. Start mongo on port 27017 to persist data.
Server ready at http://localhost:3280
GraphQL server ready at http://localhost:3280/graphql
Subscriptions ready at ws://localhost:3280/graphql
/bin/sh: 1: website_crawler: not found

exec error: Error: Command failed: website_crawler
/bin/sh: 1: website_crawler: not found

Server listening on http://127.0.0.1:8090
gRPC server running at http://127.0.0.1:50054
gRPC server running at 0.0.0.0:50053
gRPC server running at http://127.0.0.1:50052
Starting the MongoMemoryServer Instance failed, enable debug log for more information. Error:
StdoutInstanceError: Instance failed to start because a library is missing or cannot be opened: "libcrypto.so.1.1"
at MongoInstance.checkErrorInLine (/home/constellation/.nvm/versions/node/v18.13.0/lib/node_modules/@a11ywatch/a11ywatch/node_modules/mongodb-memory-server-core/lib/util/MongoInstance.js:381:62)
at MongoInstance.stderrHandler (/home/constellation/.nvm/versions/node/v18.13.0/lib/node_modules/@a11ywatch/a11ywatch/node_modules/mongodb-memory-server-core/lib/util/MongoInstance.js:303:14)
at Socket.emit (node:events:513:28)
at Socket.emit (node:domain:489:12)
at addChunk (node:internal/streams/readable:324:12)
at readableAddChunk (node:internal/streams/readable:297:9)
at Readable.push (node:internal/streams/readable:234:10)
at Pipe.onStreamRead (node:internal/stream_base_commons:190:23)
gRPC server running at 0.0.0.0:50051
public - gRPC server running at 0.0.0.0:50050
gRPC clients connected - pagemind, crawler, cdn, and mav.
chrome launched and connected on: ws://0.0.0.0:9222/devtools/browser/516bcfc6-3ae3-4d31-836c-9565656687e4

constellation@pop-os:~$ a11ywatch scan -d --url https://a11ywatch.com > results.json
error: Found argument '-d' which wasn't expected, or isn't valid in this context

    If you tried to supply `-d` as a value rather than a flag, use `-- -d`

USAGE:
a11ywatch scan [OPTIONS] --url

For more information try --help
constellation@pop-os:~$
`

from a11ywatch.

@GECORegulatory The -d flag is only available for the crawl command. It looks like an issue with the docs for that flag ( fixing now).

It looks like the crawler package failed to install locally.

Depending on your OS you will need to follow the install docs for https://github.com/a11ywatch/crawler.

This is the first time I have heard of Pop!_OS, it may be easier to just use the docker build instead of local.

The command for a valid crawl a11ywatch crawl -d -u https://a11ywatch.com > results.json

from a11ywatch.

Fixed the incorrect scan flag cbdc885 thanks for the issue again. You can also use --help across any of the commands to get more detailed info.

ex:

a11ywatch --help
a11ywatch crawl --help

from a11ywatch.

I made an issue here hyperium/tonic#1238 to remove the manual steps required for the crawler.
Completely forgot about the manual steps on the local installation. Going to add a fix for this next release in the tonic repo or https://github.com/a11ywatch/crawler v0.6.56.

from a11ywatch.

I think if you restart/reboot the system should be good to do. The error logs helped out a lot!! Feel free to ask any questions and you are welcome anytime.

from a11ywatch.

Hello, after a restart I get a different error, i think it is dependency related? I ran several commands so I put it all in a pastebin for better readability.

https://pastebin.com/2NdN7bXN

Do I need to go and troubleshoot npm audit fix or is that not part of the issue. i'm going to try reinstalling the cargo package.

from a11ywatch.

@GECORegulatory great debugging, it looks like you got past the main setup to get the backend running.

For the front-end we use next.js. It looks like it was installed with npm and not yarn. The issue is on the build_machine.rs file at a11ywatch/cli/src/commands/build_machine.rs. I should have this fixed later tonight or in the morning. You helped out a lot, thank you!

from a11ywatch.

A temp work around for the local instances non docker frontend:

Run the command below to the find project folder for a11ywatch files:
a11ywatch --find-tmp-dir.

Navigate inside the web folder and run yarn.

Build the production web app:
yarn build

Start the app:
yarn start.

from a11ywatch.

#50 new issue created to hold the problem.

from a11ywatch.

I will close this and move #50 as the earlier patch fixed the "compose-compose" problem.

from a11ywatch.