Here’s a very comprehensive, up-to-date troubleshooting guide for JFrog Artifactory 7.x, covering the application, database, core components, all services, log files, and all the key troubleshooting commands.
This guide is tailored for self-hosted, Linux-based deployments but can be adapted for containers or Kubernetes as well.

---

---

1️⃣ Artifactory Application Troubleshooting Steps

A. Check if Artifactory is Running

sudo systemctl status artifactory
sudo systemctl status artifactory-router
sudo systemctl status artifactory-access

• For containerized installs: docker ps or kubectl get pods -n <namespace>

Common problems: Service not started, Java crash, port not listening, out-of-memory.

---

B. Application Log Files & What to Look For

Log Directory:
/opt/artifactory-pro-7.23.3/var/log/

• console.log: JVM and startup errors, fatal exceptions, low memory.
• artifactory-service.log: Main service lifecycle, stacktraces, upgrades.
• artifactory-request.log: HTTP requests to Artifactory REST API.
• artifactory-request-trace.log: Trace of REST requests with debug detail.
• artifactory-binarystore.log: Filestore and storage backend issues.
• artifactory-metrics.log: Metrics, monitoring, custom endpoint hits.
• archived/: Older rotated logs.
• tomcat/: Tomcat-specific logs if needed.

Quick check for startup issues:

tail -100f /opt/artifactory-pro-7.23.3/var/log/console.log
Code language: JavaScript (javascript)

---

C. Useful App Diagnostic Commands

ps -ef | grep artifactory
lsof -i :8082           # Is Artifactory listening?
df -h /mnt/efs          # Storage mount status (EFS/NFS)
free -m                 # Memory available
top                     # JVM process CPU/ram usage
Code language: PHP (php)

Restart service:

sudo systemctl restart artifactory

Check service logs quickly:

sudo journalctl -u artifactory --since "2 hours ago"
Code language: JavaScript (javascript)

---

2️⃣ Artifactory Database Troubleshooting Steps

A. Basic Connectivity

• Test DB connection from host:psql -U artifactory -h <db-host> -d artifactory
  • Look for authentication errors, permission issues, or connection refused.

B. Common DB Problems

• Connection refused: DB not running, firewall, wrong system.yaml/JDBC URL.
• Authentication failed: DB user/password mismatch.
• Permission denied for schema public: User lacks schema/table create rights.

C. Log Files for DB Errors

• console.log: Usually shows DB connection errors and stacktraces.
• artifactory-service.log: Migration and DB schema update failures.

D. DB Permissions Fix Commands (Postgres Example)

GRANT ALL ON SCHEMA public TO artifactory;
ALTER SCHEMA public OWNER TO artifactory;
Code language: PHP (php)

To see DB connections (Postgres):

sudo -u postgres psql -c "SELECT * FROM pg_stat_activity WHERE datname='artifactory';"
Code language: JavaScript (javascript)

---

3️⃣ Artifactory Components Troubleshooting Steps

A. Filestore (NFS/EFS)

• Check mount: df -h /mnt/efs mount | grep /mnt/efs ls -l /mnt/efs
• Permission issues: Files must be owned by artifactory:artifactory.
• Log files:
  • artifactory-binarystore.log
  • artifactory-service.log

Common issues:
“Permission denied”, “cannot write to storage”, “No space left on device”.

B. Router Service

• Service status: sudo systemctl status artifactory-router
• Logs:
  • router-service.log
  • router-request.log
  • router-traefik.log

C. Access Service

• Service status: sudo systemctl status artifactory-access
• Logs:
  • access-service.log
  • access-request.log
  • access-audit.log
  • access-security-audit.log

D. Frontend Service

• Logs:
  • frontend-service.log
  • frontend-request.log

E. Metadata Service

• Logs:
  • metadata-service.log
  • metadata-request.log
  • metadata-metrics.log

F. Event Service

• Logs:
  • event-service.log
  • event-request.log

---

4️⃣ Each Artifactory Service Troubleshooting Steps

Key Artifactory services in systemd (native install):

• artifactory (main node)
• artifactory-access (access control)
• artifactory-router (reverse proxy/router)
• (plus optional xray, metadata, event, frontend if separate)

Restart or check each individually:

sudo systemctl restart artifactory-router
sudo systemctl status artifactory-router

sudo systemctl restart artifactory-access
sudo systemctl status artifactory-access

Check if ports are listening:

sudo ss -ltnp | grep 8082   # Artifactory main
sudo ss -ltnp | grep 8046   # Router
sudo ss -ltnp | grep 8040   # Access
Code language: PHP (php)

---

5️⃣ Log Files Reference Table

Log File	Description
console.log	JVM, core, and startup issues
artifactory-service.log	Main app events, errors
artifactory-request.log	Incoming HTTP/REST API calls
artifactory-request-trace.log	Debug request tracing
artifactory-binarystore.log	Storage/filestore operations
access-service.log	Identity/SSO/auth events
router-service.log	Router internal events
router-traefik.log	Traefik (router/proxy) details
frontend-service.log	Web UI service
metadata-service.log	Metadata service
event-service.log	Events and notifications
tomcat/*	Embedded Tomcat (legacy)
archived/	Rotated older logs

---

6️⃣ Essential Troubleshooting Commands

Command	What It Does
systemctl status <svc>	See service status
journalctl -u <svc> --since "1 hour ago"	Recent service logs
tail -f <logfile>	Live log tail
df -h /mnt/efs	Filestore disk status
`ps -ef	grep artifactory`
`ss -ltnp	grep `
curl http://localhost:8082/artifactory/api/system/ping	Health ping
curl http://localhost:8046/router/api/v1/system/health	Router health
psql -U artifactory -h <db-host> -d artifactory	Test DB connectivity

---

7️⃣ Web/API Health Checks

• Artifactory Ping:
  http://localhost:8082/artifactory/api/system/ping
  (returns OK when running)
• HA Node Status:
  http://localhost:8082/artifactory/api/system/ha/nodes
• Router Health:
  http://localhost:8046/router/api/v1/system/health

---

8️⃣ Common Problems & Fixes Table

Problem/Symptom	Logs to Check	Common Causes / Fixes
Service won’t start	console.log, systemctl	Java heap, permission, config, storage
DB connection fails	console.log, artifactory-service.log	Wrong URL/creds, DB down, pg_hba.conf, privileges
Filestore errors	artifactory-binarystore.log	NFS/EFS mount, permissions, quota
Router 502/503	router-service.log, router-traefik.log	Port conflict, network, wrong service startup order
UI login fails	access-service.log, artifactory-request.log	Access service down, DB error, clock skew
401/403 from API	access-service.log, artifactory-request.log	Token/SSO issue, missing permission
Out-of-memory	console.log, systemctl	JVM heap size, large requests, memory leak
Disk full	console.log, df -h, binarystore	Too many artifacts, logs, backups; clear space or expand volume
HA node not visible	artifactory-service.log, UI	Wrong node.id, clock skew, network, missing joinKey

---

9️⃣ When All Else Fails:

• Increase log level:
  Edit logback.xml to set DEBUG or TRACE for modules.
• Reboot host/server (if Java process hung).
• Clear browser cache (if UI rendering breaks).
• Check NTP/time sync on all nodes (important for HA).
• Restore from backup if data loss/corruption.

---

🔟 Support Tools

• JFrog Support Diagnostics Tool curl -u admin:password -X POST "http://localhost:8082/artifactory/api/system/support/bundle"
• Official Troubleshooting Docs

---

✅ Proactive Monitoring

• Enable Metrics:
  Use Prometheus endpoint /artifactory/api/v1/metrics for integration.
• External monitoring:
  Set up monitoring/alerts for memory, disk, process, ping.

---

🟢 Summary Table: Core Troubleshooting Steps

Area	Key Files/Commands	What to Check
Application	console.log, artifactory-service.log, systemctl status	JVM, startup, ports
Database	console.log, psql, DB logs	Connectivity, privileges
Filestore	binarystore.log, df -h, mount, chown	Storage, mount, perms
Access/Router	access-service.log, router-service.log, status, health API	Inter-service comms
HA	UI (nodes), logs, joinKey, clock sync	All nodes visible

---

Older Guide

Below is a comprehensive, practical troubleshooting guide for JFrog Artifactory 7.x, designed for sysadmins and SREs handling production systems. It covers core areas: application, database, components, individual services, log file references, common commands, and hands-on debugging actions.

1. Artifactory Application Troubleshooting Steps

A. General Application Health

• Check Service Status: text# Systemd-based sudo systemctl status artifactory # Init script $JFROG_HOME/artifactory/app/bin/artifactory.sh status
• Web UI/REST API Reachability:
  • Access http://<host>:8082/artifactory/
  • Test API: textcurl -u admin:<password> http://<host>:8082/artifactory/api/system/ping
• Check for Maintenance Mode or Lock Files:
  • Look for .lock, .maintenance, or upgrade flags in $JFROG_HOME/artifactory/var/etc.

B. Configuration Issues

• Validate system.yaml: text$JFROG_HOME/artifactory/app/bin/diagnostics/diagnosticsUtil validate yaml \ $JFROG_HOME/artifactory/var/etc/system.yaml \ $JFROG_HOME/artifactory/var/etc/system.full-template.yaml --uncomment-before-parse
• Check for Tabs/Bad Indentation (YAML is space-sensitive).
• Restart Artifactory after config changes.

2. Artifactory Database Troubleshooting Steps

A. Connectivity

• Test Database Connection as Artifactory User: text# PostgreSQL Example psql -h <db-host> -U artifactory -d artifactory
• Validate JDBC Configuration:
  Confirm in system.yaml (shared: database:) and that the JDBC driver .jar is placed in $JFROG_HOME/artifactory/var/bootstrap/artifactory/tomcat/lib.

B. Permissions

• Check Schema Privileges: sql-- In psql: \c artifactory GRANT ALL ON SCHEMA public TO artifactory; ALTER SCHEMA public OWNER TO artifactory; GRANT ALL PRIVILEGES ON ALL TABLES IN SCHEMA public TO artifactory; GRANT ALL PRIVILEGES ON ALL SEQUENCES IN SCHEMA public TO artifactory; GRANT ALL PRIVILEGES ON ALL FUNCTIONS IN SCHEMA public TO artifactory;
• For Startup/Migration Failures:
  Look for permission denied for schema public or no pg_hba.conf entry—fix DB configuration as above.

C. Availability & Performance

• Is the DB process running? textsudo systemctl status postgresql # Or for MySQL/MariaDB sudo systemctl status mysql
• Network Check: texttelnet <db-host> 5432 # or nc -zv <db-host> 5432

3. Artifactory Components Troubleshooting Steps

Typical Components:

• Artifactory Core
• Access Service (auth, tokens)
• Router
• Metadata
• Frontend
• Event

A. How to Check Component Health

• Service Logs: Review logs per component (see Log List below).
• Service Ports: ComponentDefault PortRouter8082Artifactory Core8081Access8040Metadata8086Event8061Frontend8070 Verify with netstat -ltnp or ss -tuln.
• Process Status and Errors: textps aux | grep java systemctl status artifactory

B. Troubleshoot Inter-component Issues

• If Router is down: UI/API not available.
• If Access Service is down: Authentication, permissions fail.
• If Metadata/Event: Metadata sync, repo events, webhooks may fail.

4. Artifactory Services Troubleshooting Steps

A. Service-Specific Health Checks

Service	Key Function	Main Log File	Common Checks
Artifactory (Core)	Repositories, REST/API	artifactory-service.log	8081 active, log errors
Access	Tokens, Auth, RBAC	access-service.log	8040 active, token/auth tests
Router	API Gateway/Reverse Proxy	router-service.log, router-traefik.log	8082 active, 502/404s
Metadata	Package metadata service	metadata-service.log	8086 active, catalog queries
Event	Event handling	event-service.log	8061 active, event failures
Frontend	UI layer	frontend-service.log	8070 active, UI up

B. Restart & Status Commands

text# To restart all manually via scripts
$JFROG_HOME/artifactory/app/bin/artifactory.sh restart

# Or check per systemd service (custom setups may have separate units)
sudo systemctl status artifactory
sudo systemctl restart artifactory

C. Advanced: Debug Mode

• Increase log verbosity (in logback.xml or via UI/REST).
• Monitor logs real-time: texttail -f /opt/artifactory-pro-7.23.3/var/log/artifactory-service.log

5. Artifactory Log Files: What They Are For

Located in: /opt/artifactory-pro-7.23.3/var/log/

Log File	Purpose
artifactory-service.log	Core server start/stop, errors, core ops
artifactory-request.log	All incoming REST/API/UI requests
artifactory-request-out.log	Outbound requests from Artifactory
artifactory-access.log	Records logins and permission checks
access-service.log	Auth/token system main log
access-audit.log	Access/repo security audit trail
access-request.log	All token/authz requests
access-security-audit.log	Security-specific audit logs
router-service.log	API Gateway/router-level events
router-traefik.log	Reverse-proxy and routing errors
frontend-service.log	UI layer startup/errors
event-service.log	Event publication and failures
metadata-service.log	Metadata service ops/errors
artifactory-binarystore.log	Binary store actions/issues
artifactory-import-export.log	Import/export progress and errors
console.log	System stdout/stderr, JVM exceptions
archived/	Older rotated logs
…	Additional logs as features/plugins warrant

6. Essential Troubleshooting Commands

text# List running Java processes (inspect PIDs)
ps aux | grep java

# List open/listening ports (find which service is listening)
netstat -plnt
ss -tulnp

# Check disk space (low space can break Artifactory)
df -h
du -sh $JFROG_HOME/artifactory/var

# Monitor system resources
top
htop

# Search for errors in logs
grep -i error /opt/artifactory-pro-7.23.3/var/log/artifactory-service.log
grep 'Caused by:' /opt/artifactory-pro-7.23.3/var/log/*

# Validate YAML configurations
python3 -c 'import yaml,sys; yaml.safe_load(open(sys.argv[1]))' system.yaml

# Test DB access (PostgreSQL example)
psql -h <dbhost> -U artifactory -d artifactory

7. Common Problems & Fast Solutions

Symptom	Check/Remedy
Cannot start Artifactory	Check main logs (service.log, router-service.log), disk
Web UI/API unavailable	Router down? Port open? LB misrouting?
“permission denied for schema public” on Postgres	Grant permissions to artifactory user (see above)
Connection refused to DB	DB process/host/port, firewall, pg_hba.conf
Frequent 503/502, node not joining cluster	Licenses, join key, file store mount, node id unique, logs
“YAML validation failed”	Tabs, structure, check with template/validator
Plugins/Integrations don’t load	Plugin logs, config in etc/plugins, service logs
Slow response, GC pauses	JVM heap, DB/query latency, disk IO

8. Advanced: Network & HA Debugging

• Cluster Node Status:
  • Check UI → Admin → Cluster → Node status
  • Review router-service.log for join/ping errors
• Storage/NFS Status for Filestore: textdf -h /mnt/nfs-volume/filestore # Check mount status and permissions
• Database Failover/Replication Logs:
  • For DB clusters: check replication, failover logs on DB host(s)

9. Proactive Monitoring & Best Practices

• Enable system monitoring (CPU, mem, disk, DB connections)
• Configure log rotation and retention (archived logs)
• Periodic backup and test restores of configuration and filestore
• Restarts after configuration changes or upgrades
• Regularly review logs for new/unexpected patterns after upgrade/plugins

Summary Table – Artifactory Logs and Services Quick Reference

Component	Main Log File	Service Port	Command Example
Artifactory	artifactory-service.log	8081	tail -f artifactory-service.log
Access	access-service.log	8040	tail -f access-service.log
Router	router-service.log, router-traefik.log	8082	tail -f router-service.log
Event	event-service.log	8061	tail -f event-service.log
Metadata	metadata-service.log	8086	tail -f metadata-service.log
Frontend	frontend-service.log	8070	tail -f frontend-service.log

This guide can serve as your operational reference for rapidly diagnosing and resolving issues with JFrog Artifactory 7 in any enterprise environment. Adjust specific paths, ports, and credentials as per your deployment. For detailed root cause analysis, escalate persistent issues with logs and config files to JFrog Support.