Version: This solution is applicable for all versions of Jiffy.
Pre-requisites: Putty, Jiffy Server jiffyapp-usr credentials.
Steps to do:
• Open putty and login to Jiffy server.
• Change the user to jiffyapp-usr and go to JIFFY_HOME folder.
su jiffyapp-usr
Note: JIFFY_HOME -- usually it will be in /opt/jiffy folder. However, this differs from client-to-client and depends on the location where jiffy is installed.
• Log in to linux server through putty and check the “supervisorctl status”.
• Everything should be up and running fine.
• Please refer FAQ:1 if you see any of the process having issues.
• If everything is running fine, check the 'Diskspace' in RabbitMQ link:
Please refer FAQ:5 for the steps.
• If diskspace is low in RabbitMQ, then scheduling processes will not run.
• For this we should delete some old log files and make some space.
• Login to putty and go to /var/log/rabbitmq
• Remove huge sized *.gzip log files
• This should solve the issue. But if disk space looks good then check the ‘Queues’ to see if there are high pending messages to be processed.
• Please refer FAQ:4 for the steps.
• If any of the queues are showing high numbers in 100+ messages, this means one of the jiffy processes is hung or having some issue.
• So try restarting all the processes:
ie., login to putty as jiffyapp-usr.
• Stop all the jiffy processes under user "jiffyapp-user": [jiffyapp-usr@localhost scripts]$ ./stop_all.sh
• . start all the jiffy processes and check the uptime : [jiffyapp-usr@localhost scripts]$ ./start_all.sh jiffy
• Please refer FAQ:1 for detailed steps.
• Now verify the queues in RabbitMQ , it should get cleared.
• If any of the processes are not running then stop and start that service alone.
• Refer FAQ:12 for the steps.