Skip to content

WildcoreDMS

Overview

This page provides various error cases and a solution for them for the WildcoreDMS.

Feel free to use the right side menu to jump to the section, that you're interested in.

Install or update problems➧

docker-compose-plugin not installed➧

Usually the error looks like this:

Issue

docker-compose must be installed on your system specifically as a plugin for Docker, rather than as a standalone utility.

Solution:

  1. Install the docker-compose-plugin package for your operating system (refer to the installation instructions in the official Docker documentation.
  2. Verify its functionality by running the command docker compose version, which should return the plugin version.
  3. Proceed with the WildcoreDMS installation by executing sudo wca-tool update.

Network errors may manifest as Connection refused,Connection timeout, or Forbidden entries in the logs.

Solution:

  1. Examine the logs to pinpoint the problematic connection attempt.
  2. Confirm the existence of the target address on the server (for HTTP, try the same curl).
  3. If the response is valid, investigate your Docker setup.

Refer to the official Docker documentation for detailed instructions. Ensure compatibility with your OS version as per the documentation or that no older versions are present.

Once the issue is resolved, you can proceed by executing the wca-tool update command.

Web panel malfunctions or wca command errors➧

Solution:

Utilize the docker ps -a command to see the currently running containers.

Inspect the logs with `docker logs ...` for containers showing errors.

On installed system➧

Step 0: Clear cache and update➧

If in the course of work you encounter problems with the agent, first of all make sure that you are using the latest version of the software.

Run the following commands to rule out possible problems:

1
2
3
4
5
6
cd /opt/wildcore-dms 
sudo docker compose down --remove-orphans
sudo docker compose up -d --build 
sleep 10 
wca cache:flush
wca cache:redis:flush-all
If the problem or error persists, try the next section with solutions to various known problems.

Step 1: Known errors and solutions to them➧

Agent registered on another IP➧

This error occurs, when the public IP of your server changes.

Solution:

  1. Go to your Personal Cabinet.
  2. Navigate to the Agents page and find the suspect agent.
  3. Press the Edit button in the upper-right corner.
  4. Press the Reset bound IP address button next to the current Registered IP.
  5. Run wca-tool register on the target server.

Customer search by MAC Address returns interfaces on transport ports➧

Solution: disable FDB collection on this interface.

Option 1: Add links to the transport interface, which prevents MAC address collection.

Option 2: Disable MAC address collection (a checkbox in the interface card).

OLT Device List and System stat Dashboard widget display different Interface counts➧

Interfaces without Status do not count towards the Device List total.

Solution: Disable the Do not clear interfaces checkbox in Configuration - System configuration - System panel.

Step 2: Contact support➧

Before applying:

  1. Make sure you are using the latest version of the agent and wca-tool
  2. Run the commands described in Step 0.
  3. Make sure the server has stable access to the hardware (like ping and snmpwalk).

If the steps above did not solve the problem, when contacting, try to describe as much as possible the actions that cause the problem, specify:

  • Characteristics of the system on which the software is running.
  • The role of the user under which the error occurs.
  • What rights are granted to this user group.

  • Which hardware (if it is) is having problems.

    It is also desirable to provide the output of the command

    wca switcher-core:call DEVICE_IP system.

  • Provide screenshots.

  • Describe what exactly is wrong, even if it is obvious to you.
  • What access level to the equipment was provided (SNMP Community String - RO or RW, login/password as a user or administrator).

Support Contacts