Run Yarn Dev on Boot

Here's how you can set it up:

### Step 1: Create a Systemd Service File
1. SSH into your EC2 instance:

ssh ubuntu@ec2-16-170-254-93.eu-north-1.compute.amazonaws.com

2. Create a new systemd service file:

sudo nano /etc/systemd/system/yarn-dev.service

3. Add the following content to the file:

[Unit]
   Description=Yarn Dev Server
   After=network.target

   [Service]
   User=ubuntu
   WorkingDirectory=/var/www/share
   ExecStart=/usr/bin/yarn run dev
   Restart=always
   RestartSec=5
   Environment=NODE_ENV=development

   [Install]
   WantedBy=multi-user.target

Make sure to adjust:
– `User=ubuntu` to match your EC2 username.
– `WorkingDirectory=/var/www/share` to your project directory.
– `ExecStart=/usr/bin/yarn run dev` path to the yarn executable (you can confirm the path with `which yarn`).

### Step 2: Reload Systemd and Enable the Service
Run the following commands to reload the systemd daemon, enable the service, and start it:

# Reload systemd to recognize the new service
sudo systemctl daemon-reload

# Enable the service to start on boot
sudo systemctl enable yarn-dev.service

# Start the service immediately
sudo systemctl start yarn-dev.service

### Step 3: Check the Status of Your Service
You can verify if the service is running correctly:

sudo systemctl status yarn-dev.service

You should see output indicating that the `yarn run dev` process is active and running.

### Step 4: View Logs
To see the logs generated by your service, use:

journalctl -u yarn-dev.service -f

### Notes:
– If you make changes to the service file in the future, remember to reload systemd:

sudo systemctl daemon-reload
  sudo systemctl restart yarn-dev.service

This setup will ensure that `yarn run dev` starts automatically on boot and restarts if it crashes.

Here's how to set up `yarn run dev` with **PM2** on your EC2 Ubuntu instance:

### Step 1: Install PM2 (if not already installed)
1. SSH into your EC2 instance:

ssh ubuntu@ec2-16-170-254-93.eu-north-1.compute.amazonaws.com

2. Make sure you have Node.js and Yarn installed. If not, install them first:

sudo apt update
   sudo apt install -y nodejs npm
   npm install -g yarn

3. Install PM2 globally:

npm install -g pm2

### Step 2: Start the Yarn Development Server with PM2
1. Navigate to your project directory:

cd /var/www/share

2. Start your `yarn run dev` command using PM2:

pm2 start yarn --name "yarn-dev" -- run dev

– `–name "yarn-dev"` gives your process a recognizable name.
– `– run dev` specifies the Yarn script to run.

3. Confirm that your process is running:

pm2 list

### Step 3: Set Up PM2 to Start on Boot
To ensure your `yarn run dev` process starts automatically when your server reboots:

pm2 startup

This command will generate a command specific to your OS. It will look something like:

sudo env PATH=$PATH:/usr/bin pm2 startup systemd -u ubuntu --hp /home/ubuntu

Copy and run the generated command to set up the PM2 startup script.

4. Save the current PM2 process list and environment:

pm2 save

### Step 4: Managing Your PM2 Process
– To view logs:

pm2 logs yarn-dev

– To restart the process:

pm2 restart yarn-dev

– To stop the process:

pm2 stop yarn-dev

– To delete the process:

pm2 delete yarn-dev

### Step 5: Verify PM2 Auto-Start on Reboot
Reboot your server to ensure everything is set up correctly:

sudo reboot

After the server restarts, SSH back in and check if your PM2 process is running:

pm2 list

This setup using PM2 provides you with better control, monitoring, and automatic restarts for your `yarn run dev` process.

### Step 1: Generate the PM2 Startup Command
First, execute:

pm2 startup

### Step 2: Copy and Execute the Generated Command
After running the above command, you will see output similar to the following:

[PM2] Init System found: systemd
[PM2] To setup the Startup Script, copy/paste the following command:
sudo env PATH=$PATH:/usr/bin pm2 startup systemd -u ubuntu --hp /home/ubuntu

The exact command may vary based on your environment. **Copy the entire command** that PM2 generates and paste it into your terminal to execute it. For example:

sudo env PATH=$PATH:/usr/bin pm2 startup systemd -u ubuntu --hp /home/ubuntu

### Step 3: Save the PM2 Process List
After setting up the startup script, save your currently running processes so they will restart on reboot:

pm2 save

### Step 4: Reboot and Verify
You can now reboot your server to test if the process starts automatically:

sudo reboot

Once the server is back online, SSH into it again and check if your `yarn run dev` process is running:

pm2 list

If you see your `yarn-dev` process in the list, then PM2 has successfully set up the startup script, and your process will automatically run every time your server boots up.

[Service]
Type=forking
User=root
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
Environment=PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
Environment=PM2_HOME=/root/.pm2
PIDFile=/root/.pm2/pm2.pid
Restart=on-failure

ExecStart=/usr/lib/node_modules/pm2/bin/pm2 resurrect
ExecReload=/usr/lib/node_modules/pm2/bin/pm2 reload all
ExecStop=/usr/lib/node_modules/pm2/bin/pm2 kill

[Install]
WantedBy=multi-user.target

Target path
/etc/systemd/system/pm2-root.service
Command list
[ 'systemctl enable pm2-root' ]
[PM2] Writing init configuration in /etc/systemd/system/pm2-root.service
[PM2] Making script booting at startup…
[PM2] [-] Executing: systemctl enable pm2-root…
Created symlink /etc/systemd/system/multi-user.target.wants/pm2-root.service → /etc/systemd/system/pm2-root.service.
[PM2] [v] Command successfully executed.
+—————————————+
[PM2] Freeze a process list on reboot via:
$ pm2 save

[PM2] Remove init script via:
$ pm2 unstartup systemd

Here's a breakdown of what happened and how to adjust it if necessary:

### What PM2 Did
– PM2 created a systemd service file at `/etc/systemd/system/pm2-root.service` to manage processes for the **root** user.
– It added a symlink to enable this service at startup.
– It prompted you to run `pm2 save` to ensure your processes are restored on reboot.

### If You Want to Use the `ubuntu` User Instead of `root`
If you want your PM2 process to run under the `ubuntu` user instead of `root`, you'll need to adjust the setup:

#### Step 1: Undo the Existing PM2 Setup for `root`
To remove the current PM2 startup configuration, run:

sudo pm2 unstartup systemd

#### Step 2: Set Up PM2 to Run Under the `ubuntu` User
Now, generate the startup script for the `ubuntu` user:

pm2 startup systemd -u ubuntu --hp /home/ubuntu

You'll see an output similar to the previous one, but this time it will be configured for the `ubuntu` user. It will generate a new command that looks like this:

sudo env PATH=$PATH:/usr/bin pm2 startup systemd -u ubuntu --hp /home/ubuntu

#### Step 3: Copy and Execute the New Command
Copy the above command generated by PM2 and run it:

sudo env PATH=$PATH:/usr/bin pm2 startup systemd -u ubuntu --hp /home/ubuntu

#### Step 4: Save Your PM2 Processes
Save the current list of PM2 processes so that they are restored on reboot:

pm2 save

#### Step 5: Reboot and Verify
Reboot your server to ensure the setup works:

sudo reboot

After the reboot, SSH back into your server and check if your PM2 process is running:

pm2 list

### Additional Commands for Managing PM2
– To view logs:

pm2 logs

– To stop a specific process:

pm2 stop <process_name>

– To restart a process:

pm2 restart <process_name>

– To delete a process:

pm2 delete <process_name>

This ensures that your `yarn run dev` command runs under the correct user and starts automatically on system boot.

### Step 1: Check PM2 Logs
The first step is to inspect the logs for the `yarn-dev` process to get more details on why it's failing.

pm2 logs yarn-dev

Look for any error messages that indicate why the process is failing to start.

### Step 2: Check the Specific Error Logs
If the above logs aren't clear enough, you can check the error logs:

pm2 logs yarn-dev --err

### Step 3: Verify Your Yarn Command
Ensure that your `yarn run dev` command works outside of PM2. Navigate to your project directory and run:

cd /var/www/share
yarn run dev

If this command results in any errors, you'll need to resolve them first before using PM2.

### Step 4: Confirm the Yarn Path
Sometimes, PM2 might not use the correct environment variables, especially if `yarn` is not installed in a standard location. You can find out where `yarn` is installed by running:

which yarn

This should return something like `/usr/bin/yarn` or `/usr/local/bin/yarn`. Make sure that the path is correctly specified in your PM2 service.

If the `which yarn` output is different from `/usr/bin/yarn`, you need to update your PM2 process:

pm2 delete yarn-dev
pm2 start /path/to/yarn --name "yarn-dev" -- run dev

Replace `/path/to/yarn` with the actual path you found.

### Step 5: Restart the PM2 Process
If you made any changes, restart the PM2 process:

pm2 restart yarn-dev

### Step 6: Ensure Correct Node.js Version
If you're using **nvm** (Node Version Manager) or have multiple versions of Node.js, ensure that PM2 uses the correct one:

pm2 delete yarn-dev
pm2 start yarn --name "yarn-dev" -- run dev --interpreter $(which node)

### Step 7: Check Environment Variables
If your project relies on environment variables, make sure they are accessible to PM2. You can add them when starting your PM2 process:

pm2 start yarn --name "yarn-dev" -- run dev --env NODE_ENV=development

Or you can set up an `.env` file in your project directory.

### Step 8: Clear PM2 Logs (Optional)
If logs are cluttered, you can clear them to start fresh:

pm2 flush

After going through these steps, run the following to ensure everything is running correctly:

pm2 save
pm2 list

Let me know what the logs reveal or if any of these steps resolved your issue!

The error message `SyntaxError: missing ) after argument list` typically occurs due to a syntax mistake in the script, likely caused by an environment mismatch or corruption.

### Step 1: Check Node.js and Yarn Compatibility
Ensure that the versions of Node.js and Yarn installed are compatible. You can check the versions by running:

node -v
yarn -v

Make sure you are using a version of Node.js that is compatible with the Yarn version you're running. If they are mismatched, you may need to update one or both.

#### To update Yarn:
You can try reinstalling or updating Yarn to ensure it's installed correctly:

sudo npm install -g yarn

### Step 2: Reinstall Yarn
If the Yarn installation is corrupted, you can try reinstalling it:

1. **Uninstall Yarn**:

sudo npm uninstall -g yarn

2. **Clear npm cache**:

sudo npm cache clean -f

3. **Reinstall Yarn**:

sudo npm install -g yarn

After reinstalling Yarn, check the version again and try running `yarn run dev` directly to ensure it's working.

### Step 3: Check the `yarn` Script for Errors
The error seems to be related to the script at `/usr/share/yarn/bin/yarn`. You can open the file and check if there is a syntax error or something looks wrong:

sudo nano /usr/share/yarn/bin/yarn

Look for any misplaced parentheses or incorrect syntax around the beginning of the script. If you find something, you can either fix it or reinstall Yarn to ensure the script is correct.

### Step 4: Use `npx` to Run Yarn (Temporary Workaround)
If the issue persists and you need to run your development server, you can try using `npx` (which comes with npm) to execute Yarn without directly using the global Yarn installation:

npx yarn run dev

This should bypass any potential issues with the global Yarn installation.

### Step 5: Restart the PM2 Process
After resolving the issue with Yarn, restart the PM2 process to ensure it's running correctly:

pm2 restart yarn-dev

Then check the logs again:

pm2 logs yarn-dev

### Conclusion
If the issue persists, it could be related to a specific setup in your system (like a corrupt Yarn installation or an incompatible Node.js version). Reinstalling Yarn or using `npx` should help isolate the issue. Let me know how it goes or if any of the steps resolve the issue!

### Step 1: Upgrade Yarn to the Latest Version
Yarn v1.22.22 is an older version. Upgrading Yarn to the latest version can resolve any potential issues related to compatibility or bugs in the older version.

To upgrade Yarn globally, run:

sudo npm install -g yarn

After upgrading, verify the new version:

yarn -v

### Step 2: Clear the Cache and Reinstall Dependencies
Sometimes, issues arise from corrupted cache or outdated dependencies. Let's clear Yarn's cache and reinstall your project dependencies:

1. **Clear the Yarn cache**:

yarn cache clean

2. **Reinstall dependencies**:

Go to your project directory and reinstall the dependencies:

cd /var/www/share
   yarn install

### Step 3: Ensure Node Version Compatibility
While Node.js v22.11.0 is relatively new, there could be some issues with certain packages not fully supporting the latest versions. If you continue to see errors, you can consider downgrading Node.js to a more stable version like v18 (LTS).

#### To install Node.js v18 (LTS) using **nvm** (Node Version Manager):

1. **Install nvm (if not already installed)**:

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.3/install.sh | bash

2. **Install Node.js v18**:

nvm install 18

3. **Use Node.js v18**:

nvm use 18

4. **Verify Node.js version**:

node -v

5. **Reinstall Yarn** (since `nvm` uses a separate environment):

sudo npm install -g yarn

### Step 4: Test Yarn Directly
After updating Yarn and verifying your Node.js version, test the `yarn run dev` command directly (without PM2) to ensure it works:

cd /var/www/share
yarn run dev

If it works, then you can proceed to restart the PM2 process.

### Step 5: Restart the PM2 Process
After everything is working locally, restart the PM2 process to ensure it starts correctly:

pm2 restart yarn-dev

Check the PM2 logs again to confirm the process is running without errors:

pm2 logs yarn-dev

### Conclusion
Upgrading Yarn, clearing the cache, and ensuring Node.js compatibility should help resolve the issue. If the error persists, consider downgrading Node.js to v18 (LTS). Let me know how it goes!

### Step 1: Stop All Running PM2 Processes
Before uninstalling PM2, it's a good idea to stop all the processes that are managed by PM2:

pm2 stop all

### Step 2: Delete All PM2 Processes
After stopping the processes, you can delete them:

pm2 delete all

### Step 3: Remove PM2 Startup Script
If you have set up PM2 to start on boot (systemd or other init systems), you need to remove the startup script:

pm2 unstartup systemd

This will remove the startup configuration for PM2.

### Step 4: Uninstall PM2
To uninstall PM2, run the following command:

sudo npm uninstall -g pm2

### Step 5: Remove PM2’s Saved Data and Logs
PM2 creates a `pm2` folder in the home directory for process information and logs. If you want to remove these as well:

rm -rf ~/.pm2

This will delete all PM2-related data.

### Step 6: Verify PM2 Removal
To verify that PM2 has been successfully removed, you can run:

pm2 -v

You should get a command not found error if PM2 was successfully removed.

### Conclusion
These steps will completely remove PM2 from your system, including stopping processes, removing the startup script, and uninstalling the package. Let me know if you need any further assistance!

—

### Step 1: Check the Status of the Service
If you've set up a systemd service to run `yarn run dev`, check its status:

sudo systemctl status <service-name>

Replace “ with the name of your service (e.g., `yarn-dev`).

– If the service is running, you’ll see a status of **active (running)**.
– If the service is not running, you’ll see an error or **inactive** status.

—

### Step 2: View Service Logs
To see detailed logs of the service, use:

sudo journalctl -u <service-name>

This will display logs from the service, including errors or runtime information.

—

### Step 3: Verify the Process is Running
You can also check if the process itself is running by searching for the `yarn` process:

ps aux | grep 'yarn run dev'

If the service is running, you should see an entry for the `yarn run dev` process.

—

### Step 4: Test the Application
Depending on what the `yarn run dev` command does, test the application (e.g., by visiting a URL or checking for specific functionality) to confirm that it’s working as expected.

—

### Step 5: Restart the Service (If Needed)
If the service is not running or stuck, you can restart it:

sudo systemctl restart <service-name>

Then recheck its status:

sudo systemctl status <service-name>

—

### Debugging Tips
– If the service fails to start, check the **ExecStart** command in your service file to ensure the path to `yarn` is correct. Use:

which yarn

Replace `/usr/bin/yarn` with the correct path if necessary.

– After modifying the service file, reload systemd and restart the service:

sudo systemctl daemon-reload
  sudo systemctl restart <service-name>

Let me know if you need help troubleshooting further!

– The process **`node /usr/bin/yarn run dev`** is running with PID **5155** under the user `ubuntu`.
– The **`grep`** process is just a result of your `ps aux | grep 'yarn run dev'` command, so you can ignore it.

This confirms that **`yarn run dev`** is actively running on your server.

—

### Additional Steps to Verify:
#### 1. **Confirm the Application is Working**
If this command is supposed to serve an application (e.g., a local development server), visit the corresponding URL in your browser or use a tool like `curl` to confirm the application is responding:

curl http://localhost:<port>

Replace “ with the port number the application runs on (e.g., `3000` or `8000`).

#### 2. **Monitor the Logs**
To monitor real-time output from the application, check its logs. Assuming your `yarn run dev` command generates logs in the terminal:

journalctl -u <service-name> -f

Replace “ with the name of the systemd service managing `yarn run dev`, if applicable.

#### 3. **Stop or Restart the Process**
To stop the process manually:

kill 5155

To restart (if it's managed by systemd):

sudo systemctl restart <service-name>

—

If everything looks good, you're all set. Let me know if you encounter any issues!

Failed to load resource: the server responded with a status of 504 (Outdated Optimize Dep)

Here are a few steps to troubleshoot and resolve this:

### Step 1: **Clear Cache**
The issue could be due to cached data. Clear the cache to ensure the most recent version of your assets and dependencies are being used:

– **Clear browser cache**: Sometimes, an outdated cached file can cause issues. Try clearing the browser cache or test in an incognito window.
– **Clear Laravel Cache**: Run the following command to clear Laravel’s cache:

php artisan cache:clear

– **Clear Vite or Webpack Cache**: If you're using Vite or Webpack, clear their cache as well. For Vite:

rm -rf node_modules/.vite

### Step 2: **Check Dependency Versions**
Ensure all dependencies are up-to-date. If your project has outdated or incompatible dependencies, it might cause issues.

– Run the following to update your dependencies:

yarn upgrade

– If you're using `npm`, try:

npm update

### Step 3: **Check Server Logs**
A `504` error usually indicates a server-side issue. Check the logs for any errors that might be causing long processing times or delays.

– For Laravel logs:

tail -f storage/logs/laravel.log

– For Nginx or Apache logs (depending on your web server):

sudo tail -f /var/log/nginx/error.log

### Step 4: **Check for Slow Backend Operations**
If your backend is processing complex tasks (like a large database query or external API request), it might take too long, causing a timeout. Optimize any slow processes or increase the timeout settings.

### Step 5: **Increase Timeout Limits**
If the issue is related to server timeouts, you can try increasing the timeout values in your web server (e.g., Nginx or Apache).

For Nginx:

sudo nano /etc/nginx/nginx.conf

Increase the `proxy_read_timeout` and `proxy_connect_timeout` values:

proxy_read_timeout 300;
proxy_connect_timeout 300;

Then restart Nginx:

sudo systemctl restart nginx

For Apache, you can adjust the `Timeout` and `ProxyTimeout` directives.

—

Try these steps to see if the issue is resolved. If you continue to encounter problems, let me know and we can dive deeper into the logs and configurations!

Here are steps to troubleshoot and resolve the issue:

### Step 1: Check Backend Server Health
A **504 Gateway Timeout** typically indicates an issue on the server side. Ensure the backend server is running and responsive:

– **Check if the backend server is up** (e.g., if it's an API, ensure the service is running):

systemctl status <backend-service-name>

– **Check server logs** for any issues or crashes:

journalctl -u <backend-service-name>

– **Ping the server** to see if it's responsive:

ping <server-ip>

### Step 2: Check for Long-Running Requests or Deadlocks
If a specific request is taking too long, inspect your backend or database queries that might be causing delays. Look for:

– **Slow queries** in the database.
– **Long-running tasks** on the backend (e.g., heavy computation or data processing).

You can use tools like **`top`** or **`htop`** to monitor server resources and see if any processes are using too much CPU or memory.

### Step 3: Optimize Dependencies
The error message about an **Outdated Optimize Dep** might refer to a dependency issue. You should:

1. **Check for outdated packages** in your project (both client and server):

– For **Node.js** projects:

npm outdated

– For **Yarn** projects:

yarn outdated

2. **Update the dependencies**:

– For **npm**:

npm update

– For **Yarn**:

yarn upgrade

3. After updating, rebuild the project:

– For **npm**:

npm run build

– For **Yarn**:

yarn build

### Step 4: Review Axios Configuration
Ensure your **Axios** configuration is correct, especially regarding timeouts and error handling. For instance, you can increase the **timeout** value if requests are taking longer than expected:

axios({
  method: 'get',
  url: 'your-api-url',
  timeout: 10000, // Timeout in milliseconds
})
.then(response => {
  console.log(response.data);
})
.catch(error => {
  console.error(error);
});

### Step 5: Review Proxy or Load Balancer Configuration
If your application is behind a proxy (like Nginx or Apache) or a load balancer, ensure that the proxy timeout values are properly configured:

– **Nginx**: Check the `proxy_read_timeout` and `proxy_connect_timeout` values in the Nginx configuration file (`/etc/nginx/nginx.conf` or `/etc/nginx/sites-available/your-site`).

Example:

proxy_read_timeout 300;
  proxy_connect_timeout 300;

– **Apache**: Look at `ProxyTimeout` in your Apache config.

### Step 6: Test with Different Client/Network
It might be worthwhile to test the request from a different network or client (e.g., using **Postman** or **curl**) to see if the issue is related to your local setup.

curl -X GET <your-api-url>

### Step 7: Increase Server Timeout (if needed)
If the request legitimately takes longer to process, you may need to adjust the server's timeout settings (in Apache, Nginx, or your Node.js server).

#### For Node.js (Express, for example):

const server = app.listen(3000, () => {
  console.log('Server running...');
});

server.setTimeout(500000); // Set the timeout to 500 seconds, for example.

### Conclusion
A 504 error indicates a problem with the backend or network. You should check the server’s health, ensure that dependencies are up-to-date, and consider adjusting timeout settings. Let me know if you need further help!

—

### Step 1: Check the Service Logs
Run the following command to view detailed logs for the `yarn-dev.service`:

journalctl -u yarn-dev.service -f

This will show the live logs and any specific error messages generated when the service tries to start.

—

### Step 2: Test the `yarn run dev` Command Manually
Run the command outside the systemd service to confirm if it works:

cd /path/to/your/project
/usr/bin/yarn run dev

Replace `/path/to/your/project` with the actual project directory. If this fails, it will give you a clearer error message about what is going wrong.

—

### Step 3: Verify the Path to Yarn
Ensure that `/usr/bin/yarn` is the correct path for the Yarn executable. You can verify this with:

which yarn

If the path is different, update the `ExecStart` line in the service file to use the correct path.

—

### Step 4: Debug Common Issues
#### a. **Dependencies Not Installed**
Ensure all project dependencies are installed:

cd /path/to/your/project
yarn install

#### b. **Environment Variables**
If your `yarn run dev` command requires specific environment variables, add them to the service file under the `[Service]` section:

Environment=NODE_ENV=development
Environment=API_URL=https://example.com

#### c. **Permissions Issue**
Ensure the service is running under the correct user. Update the `User` in the service file to the user who owns the project files, e.g.:

[Service]
User=ubuntu
WorkingDirectory=/path/to/your/project
ExecStart=/usr/bin/yarn run dev

Then reload the systemd configuration:

sudo systemctl daemon-reload
sudo systemctl restart yarn-dev.service

#### d. **Build Issues**
If the `yarn run dev` command involves building files, ensure there are no syntax errors or misconfigured dependencies.

—

### Step 5: Check Service Status Again
After making adjustments, check the status of the service:

sudo systemctl status yarn-dev.service

—

### Step 6: Inspect Log Files
If the above steps don’t resolve the issue, inspect project-specific log files (if any) to look for errors during startup.

—

If the problem persists after following these steps, share the output of the logs or any error message you encounter while running the commands manually. This will help in pinpointing the issue.

—

### Step 1: Stop the Service
First, stop the service if it's currently running:

sudo systemctl stop yarn-dev.service

—

### Step 2: Disable the Service
Disable the service to prevent it from starting automatically on boot:

sudo systemctl disable yarn-dev.service

—

### Step 3: Remove the Service File
Delete the `yarn-dev.service` file from the systemd directory:

sudo rm /etc/systemd/system/yarn-dev.service

—

### Step 4: Reload Systemd
After removing the service file, reload the systemd manager configuration:

sudo systemctl daemon-reload

—

### Step 5: Verify Removal
Check if the service is no longer listed:

systemctl list-units --type=service | grep yarn-dev

If nothing is returned, the service has been successfully removed.

—

Let me know if you encounter any issues during this process!