Hello all, we’re running Meltano in our stage kubernetes cluster as a test and are seeing this error:

meltano      | ELT could not be completed: Cannot start loader: Executable 'target-mysql' could not be found. Loader 'target-mysql' may not have been installed yet using `meltano install loader target-mysql`, or the executable name may be incorrect.
ELT could not be completed: Cannot start loader: Executable 'target-mysql' could not be found. Loader 'target-mysql' may not have been installed yet using `meltano install loader target-mysql`, or the executable name may be incorrect.

We have checked the

.meltano

folder and made sure that target-mysql exists but we’re still getting this error.

@rohith_desikan Can you run again with

meltano --log-level=debug

? The additional debug logging my reveal the underlying issue

We’re getting a successful result for the install. It’s installing 3 plug ins as expected.

That should be OK as long as the working directory is the project directory. Can you show the result of running with with

meltano --log-level=debug elt

, so that we can see the full error stacktrace?

```meltano | DEBUG Deleted configuration at /opt/wg/.meltano/run/elt/2021-07-01T180538--tap-s3-csv--target-mysql/d393000a-5740-4ffc-8b33-05a891db5479/target.config.json meltano | DEBUG Deleted configuration at /opt/wg/.meltano/run/elt/2021-07-01T180538--tap-s3-csv--target-mysql/d393000a-5740-4ffc-8b33-05a891db5479/tap.config.json meltano | DEBUG ELT could not be completed: Cannot start loader: Executable 'target-mysql' could not be found. Loader 'target-mysql' may not have been installed yet using

meltano install loader target-mysql

, or the executable name may be incorrect. Traceback (most recent call last): File "/usr/local/lib/python3.8/dist-packages/meltano/core/plugin_invoker.py", line 237, in _invoke yield (popen_args, popen_options, popen_env) File "/usr/local/lib/python3.8/dist-packages/meltano/core/plugin_invoker.py", line 249, in invoke_async return await asyncio.create_subprocess_exec( File "/usr/lib/python3.8/asyncio/subprocess.py", line 236, in create_subprocess_exec transport, protocol = await loop.subprocess_exec( File "/usr/lib/python3.8/asyncio/base_events.py", line 1630, in subprocess_exec transport = await self._make_subprocess_transport( File "/usr/lib/python3.8/asyncio/unix_events.py", line 197, in _make_subprocess_transport transp = _UnixSubprocessTransport(self, protocol, args, shell, File "/usr/lib/python3.8/asyncio/base_subprocess.py", line 36, in init self._start(args=args, shell=shell, stdin=stdin, stdout=stdout, File "/usr/lib/python3.8/asyncio/unix_events.py", line 789, in _start self._proc = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 854, in init self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: '/opt/wg/.meltano/loaders/target-mysql/venv/bin/target-mysql' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.8/dist-packages/meltano/core/runner/singer.py", line 105, in invoke p_target = await target.invoke_async( File "/usr/local/lib/python3.8/dist-packages/meltano/core/plugin_invoker.py", line 249, in invoke_async return await asyncio.create_subprocess_exec( File "/usr/lib/python3.8/contextlib.py", line 131, in exit self.gen.throw(type, value, traceback) File "/usr/local/lib/python3.8/dist-packages/meltano/core/plugin_invoker.py", line 239, in _invoke raise ExecutableNotFoundError( meltano.core.plugin_invoker.ExecutableNotFoundError: Executable 'target-mysql' could not be found. Loader 'target-mysql' may not have been installed yet using

meltano install loader target-mysql

, or the executable name may be incorrect. The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.8/dist-packages/meltano/cli/elt.py", line 237, in _run_elt await _run_extract_load(elt_context, output_logger) File "/usr/local/lib/python3.8/dist-packages/meltano/cli/elt.py", line 275, in _run_extract_load await singer_runner.run( File "/usr/local/lib/python3.8/dist-packages/meltano/core/runner/singer.py", line 257, in run await self.invoke( File "/usr/local/lib/python3.8/dist-packages/meltano/core/runner/singer.py", line 112, in invoke raise RunnerError(f"Cannot start loader: {err}") from err meltano.core.runner.RunnerError: Cannot start loader: Executable 'target-mysql' could not be found. Loader 'target-mysql' may not have been installed yet using

meltano install loader target-mysql

, or the executable name may be incorrect. The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.8/dist-packages/meltano/cli/elt.py", line 225, in _red…

So I noticed that as well, and it looks like it doesn’t exist even though the plug in says it was installed

Is

/opt/wg/

the meltano project directory?

Yes, That’s where the meltano.yml file lives and the

.meltano

folder lives.

Is there anything in

/opt/wg/.meltano/loaders/target-mysql/venv

at all?

What is in

bin

, if not

target-mysql

?

OK, so only the standard python and pip stuff, and jsonschema, so something is getting installed at least. What

pip_url

have you set for

target-mysql

in

meltano.yml

? Was this working fine locally?

Well we just have this for our loaders and it was not easy to test this locally since we have a tap-s3-csv. Note that we built off the target-mysql singer target and installed it in our own private pypi repo in AWS S3.

loaders:
  - name: target-postgres
    variant: datamill-co
    pip_url: singer-target-postgres
  - name: target-mysql
    namespace: target_mysql
    pip_url: target-mysql
    executable: target-mysql
    settings:
    - name: mysql_host
    - name: mysql_port
    - name: mysql_username
    - name: mysql_password
    - name: mysql_database

@rohith_desikan OK, that looks correct. Are you sure your fork of target-mysql still installs the

target-mysql

executable? If you install it manually with

pip install target-mysql

, can you use the executable as expected?

Yeah lemme check that

Okay, glad you’re making progress!