Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
TetraWiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Category:BEETEL
(section)
Category
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Training session on Beetel Project 19 Dec 2023 - Tetra Support Staff - Manish Singh== {{#ev:youtube|1Clvbt1Vin4|640}} '''Video summary:''' "Beetel Project" -- a Hindi-language KT session covering support/troubleshooting for Beetel's Java-based website (running on JBoss + Apache httpd + PostgreSQL), originally hosted on a cloud provider and later migrated by Tetra to Beetel's own in-house servers (Tetra retains VPN-based access for support, though day-to-day control sits with Beetel). Establishes the standard troubleshooting sequence for a "site is down" ticket: first check whether the site's front page loads (it may still render by default even if login is broken, so logging in with the help-desk test credentials is required to confirm the app is actually healthy), then check the three core services -- httpd, JBoss, and PostgreSQL -- restarting whichever is down (Apache/Postgres restart cleanly via `systemctl`, but JBoss additionally needs a specific follow-up command/script to fully bring the application back up after a restart). Covers the backup setup in detail: a daily 2am PostgreSQL database backup and a monthly (1st-of-month, 12am) JBoss/application backup, both driven by cron-scheduled scripts stored under root, landing first in a local backup directory (retained 7 days for DB, 4 backups for JBoss, older files auto-pruned by a custom cleanup script) and then rsynced out to a mounted remote Windows backup server share for longer-term retention. Explains how to verify backups are actually landing (checking file dates/sizes under the local and mounted remote backup paths) and flags that very old files sometimes accumulate on the remote mount and may need manual cleanup since retention there isn't automatic. Also references a rough personal migration notes file (IPs, /etc/hosts entries, DB setup steps from the original migration) as background context, explicitly noting it's not needed for day-to-day support -- the three-service-check-plus-backup-monitoring routine is what actually matters for tickets.
Summary:
Please note that all contributions to TetraWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
TetraWiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)