2.2.4 How to run quilliup in debug mode

This manual will guide you on running quilliup in Debug mode in Linux.

Follow the next steps:

1. Go to the bin folder:

cd /opt/tomcat/bin

2. Check quilliup's status:

ps -ef | grep tomcat

3. Stop quilliup's service if it's up & running:

sudo kill -9 XXXX

For example, XXXX= 785 (near the tomcat):

4. Delete all the log files:

Go to the logs folder:

cd /opt/tomcat/logs/

Delete the contents of the folder:

(make sure you are inside the logs folder)

sudo rm -rf *

Note: run the 'ls' command to verify the deletion.

5. Delete the Catalina folder:

Go to the work folder:

cd /opt/tomcat/work/ 

Delete the contents of the folder:

(make sure you are inside the work folder)

sudo rm -rf /opt/tomcat/work/ *

6. Go to: "...opt/tomcat/webapps/ROOT/WEB-INF/classes/" folder:

cd opt/tomcat/webapps/ROOT/WEB-INF/classes/

7. Edit the log4jxml or log4j2.xml file (depend on your version):

nano log4j2.xml

Search the Application Loggers row and change it to debug.

For example:

Note: you can run quilliup also in info mode in order to reduce the amount of detailing of written log rows.

To exit, press ctrl+X (^X) and then choose No (ctrl+N).

8. Start quilliup's service:

a. Go to the bin folder:

cd /opt/tomcat/bin

b. Start quilliup's service:

sudo ./catalina.sh start

c. Check that the service is up (stays in the bin folder):

ps -ef | grep tomcat