The EPIC PR2 returns Unable to locate package when you run sudo apt install mariadb-server; repeated package-name searches do not fix it if the package index is missing, stale, or does not contain that package.
Stop retrying the install and package searches
- Running
sudo apt install mariadb-serveragain cannot make APT discover a package absent from its current index. - Repeating
sudo apt-cache searchwith variations of “maria” or “db” only searches the same local package index. It does not test whether the EPIC reached a repository or downloaded its package lists. - A successful ping or other indication that the repository host is reachable does not prove that APT can retrieve repository files over HTTP, or that the configured repository provides
mariadb-server.
Check the result of sudo apt update first. It reports whether APT can refresh package indexes and whether a repository or download error is preventing that refresh.
Separate repository access from package availability
APT resolves an install request against local package indexes. The install error means the package name was not found in the indexes APT searched; it does not, by itself, identify why.
| Observation | Likely direction |
|---|---|
apt update reports connection, timeout, or fetch errors |
Investigate network path, proxy or firewall rules, DNS, and repository access. A host being reachable by ping is not enough to clear HTTP access. |
apt update completes without errors, but search finds no package |
Check which sources and package components are configured, and whether the configured repository for this EPIC PR2 software release contains the package. |
| Package appears in search, but installation still fails | Read the full install output; the failure may be dependency or package-selection related rather than package discovery. |
Check the EPIC PR2 repository and refreshed indexes
- Run
sudo apt updateand retain the complete output. Look for failed fetches, unreachable hosts, name-resolution errors, and repository metadata errors. Do not treat a partial update as a clean refresh. - Inspect the configured APT source entries and confirm they point to the intended EPIC PR2 repository and software release. The reported setup identifies firmware v4; verify the configured release rather than substituting a repository for another device or release.
- After correcting any repository or network issue, run
sudo apt updateagain. Confirm it finishes without relevant fetch or index errors before testing package availability. - Search the refreshed index with
apt-cache search mariadb, then inspect the exact package withapt-cache policy mariadb-server. If no candidate is listed, APT still has no installable candidate from its configured indexes.
Test the network path that APT actually uses
If update output shows failed downloads, troubleshoot the EPIC’s path to the repository rather than relying on a ping result. The reported device was on a network that might have restrictions, and HTTP access on port 80 was raised as a possibility, not confirmed as the cause.
- Compare an update attempt on the current network with one on a network whose repository access policy is known.
- Ask the network administrator to check DNS resolution and whether outbound HTTP traffic to the repository host is allowed; also check any proxy requirements or filtering.
- Use the failed URL and error text shown by
apt updateto identify the blocked or failing request. Do not open network access broadly based only on the package error.
Verify the fix before installing MariaDB
Once apt update completes cleanly, repeat the package search and policy check. Install only when APT shows an available candidate for mariadb-server; then review the install output for download and dependency errors.
If changing to a known-permissive network makes the package appear, the original network path was the differentiator. If the update is clean but no candidate appears, focus on the configured source and package availability for the device’s release instead of continuing to adjust firewall rules.
Know when to stop and escalate
Stop changing repository entries if you cannot verify the correct source for the EPIC PR2 firmware release. Provide official Opto 22 support or your system administrator with the full apt update output, configured source entries, and the result of apt-cache policy mariadb-server; do not share credentials or private network details.
Frequently asked questions
What happens if apt update succeeds but MariaDB is still missing?
APT refreshed the indexes it could access, but the configured sources may not provide mariadb-server. Check the source entries and apt-cache policy mariadb-server for an installable candidate.
What happens if I can ping the repository but apt cannot find the package?
Ping does not verify that APT can fetch repository files or that the repository contains the package. Use the errors from sudo apt update to check the actual repository requests.
What should I check first for “Unable to locate package” on an EPIC PR2?
Run sudo apt update and inspect its complete output before searching again or retrying installation. Confirm the configured repository matches the device’s software release.
What happens if MariaDB appears after I switch networks?
The network path was affecting repository access or index retrieval. Compare update output across the two networks and ask the network administrator to verify the specific repository traffic that failed.