For this course.
I assume you have vagrant installed on your system.
If not, please refer to the additional materiality at the end of the course where you will find a lecture
on how to install vagrant.
So I am now in the project directory and to download and run an ubuntu instance, I'll run vagrant in
it.
Ubuntu slash trusty 64 and vagrant up commands then vagrant ssh.
Now let's install engine x on Ubuntu.
Engine x is a popular open source web server that is widely used for web hosting and reverse proxy services.
Step one Update System Packages.
Before installing any software, it is always a good practice to update the system packages, open the
terminal and run the following command to update the package index.
Sudo apt update.
Step two to install engine x run sudo apt install engine x step three start engine x service.
Once the installation is complete, start the engine x service by running the following command pseudo
system CTL Start engine X.
Okay, we've got an error here.
The error message pseudo system CTL command not found.
It indicates that the system CTL command is not installed on the system.
This error occurs because the system CTL command is part of the system.
DH System and service manager, which is not installed by default on all distributions of Ubuntu.
To resolve this issue, you need to install system D by running the following command sudo appkit install
system rd.
After installing system rd, you should be able to use the system settle command to manage services
on your system.
And we've got an error again.
The error message failed to issue method call unit Engine X service failed to load no such file or directory.
It indicates that the engine X service unit file could not be found.
This error occurs because the service unit file is not properly installed on the system.
To resolve this issue, you need to create the Engine X service unit file.
Run the following command in the terminal to create the unit file pseudo nano slash ETSI system DX slash
system slash engine X service.
And an error.
Again, the error message job for Engine X service failed.
It indicates that there was a problem starting the Engine X service to troubleshoot the issue.
You can check the status of the Engine X service and view the system logs to check the status of the
engine X service.
Run the following command in the terminal pseudo system.
CTL Status Engine X Service.
This command will provide detailed information about the Engine X service and any errors that may have
occurred while starting the service.
You can also view the system logs by running the following command pseudo journal CTL.
Ken.
This command will show you the logs generated by the system, including logs related to the Engine X
service.
By reviewing the status and logs, you should be able to identify the problem and take the necessary
steps to resolve it.
It could be a misconfigured engine x configuration file.
Missing dependencies or another issue.
Let's troubleshoot it.
We'll copy this command and run it System CTL Status Engine X Service.
The error Message Engine X bind to Port 80 failed address already in use indicates that the Engine X
service is unable to bind to Port 80 as another process is already using that port.
To resolve this issue, you need to find the process that is using Port 80 and either stop that process
or configure engine X to use a different port to find the process that is using port 80.
You can run the following command pseudo net stat rt ulp and vertical bar grep 80.
This command will show you a list of all the processes that are listening on Port 80.
Once you have identified the process that is using port 80, you can either stop that process or configure
engine X to use a different port to configure engine X, To use a different port, you need to edit
the engine X configuration file, run the following command in the terminal to edit the configuration
file.
Pseudo nano slash etsy engine x engine x conf in the configuration file.
Find the line that starts with listen 80 and change 80 to the desired port number.
For example, you can change it to listen 8080 after making the changes save the file by pressing Ctrl
plus x, then y and finally enter, then restart the engine X service by running the following command
pseudo system CTL Restart Engine X.
The Engine X service should now be listening on the new port.
So here the output of the command pseudo net start rt ulp and vertical bar grep 80 confirms that engine
X is indeed listening on port 80 since another process.
In this case engine X is already using port 80.
You need to either stop that process or configure engine X to use a different port to stop the process
that is using port 80.
You can use the kill command with the process id of the process that is using port 80.
The process ID can be obtained from the output of the command sudo net stat rt ulp and vertical bar
grep 80.
In the example you provided, the process id is 2469.
To stop this process, run the following command in the terminal pseudo kill 2469.
After stopping the process, you can start again by running the following command pseudo system CTL
start engine X Engine X should now be able to bind to Port 80 and start serving web pages.
So we did the following.
Pseudo kill 2469 pseudo net stat to check the port usage again.
Pseudo system CTL start engine x pseudo system, CTL status Engine X service and it looks like Engine
X has started successfully now as the output of the pseudo system.
CTL Status Engine X service Command shows that it is active running.
You can confirm that Engine X is up and running by accessing a web page hosted by Engine X in a web
browser or by using the CURL command in the terminal curl http slash local host.
This should return the default engine x welcome page indicating that engine X is working correctly.