If an application installation from the Data Mammoth Marketplace fails, this guide helps you identify the cause and resolve it so you can successfully deploy your application.
Common Causes of Installation Failure
| Cause | Solution |
|---|---|
| Insufficient disk space | Free up space or upgrade your plan |
| Insufficient RAM | Close unused services or upgrade |
| Port conflict | Another service is using the required port |
| OS incompatibility | Use a supported operating system |
| Network issue | Server cannot reach package repositories |
| Existing software conflict | Previous installation left conflicting configs |
| Permission issues | File or directory permission problems |
Step 1 — Check the Installation Log
After a failed installation, check for an error log:
The log will usually contain the specific error message that caused the failure.
Step 2 — Check Server Resources
Disk Space
df -hIf your disk is above 90% full:
# Clean package cache
sudo apt clean # Ubuntu/Debian
sudo dnf clean all # CentOS/AlmaLinuxRemove old logs
sudo truncate -s 0 /var/log/syslog
sudo rm -f /var/log/*.gzCheck for large files
du -sh /var/log/* | sort -h | tail -10Memory
free -hIf available memory is very low, stop unnecessary services:
# List running services
systemctl list-units --type=service --state=runningStop an unused service
sudo systemctl stop unused-serviceStep 3 — Check for Port Conflicts
Many applications need specific ports. Check if the required ports are available:
# Check what is listening on common ports
ss -tuln | grep -E ':80|:443|:3306|:5432|:8080'If another service occupies the needed port:
- Stop the conflicting service.
- Change the conflicting service to use a different port.
- Configure the new application to use an alternative port.
Step 4 — Verify Network Connectivity
The installation process needs to download packages from the internet:
# Test internet connectivity
ping -c 4 8.8.8.8Test DNS resolution
ping -c 4 archive.ubuntu.comTest HTTPS connectivity
curl -I https://registry.npmjs.orgIf connectivity fails:
- Check your DNS resolver settings:
cat /etc/resolv.conf - Check firewall outbound rules — ensure outgoing traffic is allowed.
- Check if the server has an active internet connection.
Step 5 — Clean Up Failed Installation
If a partial installation left files behind, clean up before retrying:
# Example: cleaning up a failed WordPress installation
sudo rm -rf /var/www/html/wordpress
sudo mysql -u root -p -e "DROP DATABASE IF EXISTS wordpress_db;"Remove partial package installations
sudo apt --fix-broken install # Ubuntu/Debian
sudo dnf clean all # CentOS/AlmaLinuxStep 6 — Retry the Installation
After resolving the issue:
Specific Application Issues
WordPress Installation Failed
- Ensure PHP and MySQL/MariaDB are not already installed with conflicting versions.
- Check that the
DocumentRootdirectory is writable. - Verify MySQL root password if prompted.
Docker-Based App Failed
- Ensure Docker is installed and running:
sudo systemctl status docker - Check Docker disk usage:
docker system df - Clean up Docker resources:
docker system prune -a
Database App Failed
- Check if the database port is available.
- Ensure no other database instance is running on the same port.
- Verify sufficient disk space for database data directories.
Manual Installation Alternative
If the Marketplace installation continues to fail, you can install the application manually:
Data Mammoth's Knowledge Base includes manual installation guides for popular applications:
When to Contact Support
Contact support if:
- The installation log shows an error you do not understand.
- The issue persists after following all troubleshooting steps.
- You suspect a platform-level issue preventing installation.
What to Do Next
- App Marketplace Overview — Explore available apps.
- Managing Installed Apps — Manage successful installations.
- Monitoring Server Performance — Ensure sufficient resources.
- How to Upgrade Your Server Plan — Get more resources.