Problems with platform update

To identify problems with platform update, check the /usr/local/mgr5/var/pkg.log. The main problems with updating the BILLmanager platform are described below.

The platform update went through without errors, but the version remained the same

Description

After a successful update, the platform version may remain the same if a particular version is specified in the repository files. If a repository contains a particular version, BILLmanager will not update above it.

A particular version can be specified in ISPsystem repository files if:

a particular version was selected when installing the platform;
repository files were manually edited;
in Settings → System configuration → Update software automatically set to "do not update". To update the platform, set the value to "update ISPsystem products" or "update all the system packages".

To perform the diagnostics:

Connect to the server via SSH.
Check the repository version with the command:
```
cat /usr/local/mgr5/etc/repo.version
```
Example output of the command with a specific version:
```
[root@billmanager ~]# cat /usr/local/mgr5/etc/repo.version
6.70.0-stable6
```
In the example above, BILLmanager will not update above stable 6.70.0.

Solution

To perform the update:

Connect to the server via SSH.
Edit repo.version in any convenient editor:
- specify another specific version of BILLmanager. See the changelog on our website for versions;
- leave just stable6 or beta6 without specifying a specific version. In this case, the latest stable or beta version will be installed when the update is launched. For more information on the difference between versions, see the article Panel Versions: Stable or Beta.

If you need to change from stable to beta repository, you can do it with the command:

echo 'beta' > /usr/local/mgr5/etc/repo.version
/usr/local/mgr5/sbin/licctl fetch billmgr

However, switching back from beta to stable has its own subtleties that must be taken into account for the platform to work correctly. For more details, see the article How to change the repository from beta to stable.

Examples of repo.version contents:

Running the update will install the latest up-to-date stable version:
```
cat /usr/local/mgr5/etc/repo.version
stable6
```
Running the update will install the latest up-to-date beta version:
```
cat /usr/local/mgr5/etc/repo.version
beta6
```

Running the update will install a particular platform version:

cat /usr/local/mgr5/etc/repo.version
6.72-stable6

cat /usr/local/mgr5/etc/repo.version
6.72.0-stable

If the above steps did not help you to complete the update, please contact the support team.

Platform update ended with Error: Package

Description

When updating the platform, the Error: Package: <package_name> error occurs. This indicates that there are third-party repositories present on the server that are preventing the upgrade. The reasons could be the following:

the platform was not installed on a "clean" server. Third-party repositories were present;
other platforms (ISPsystem or third-party) were installed on the same server as BILLmanager;
additional third-party modules, packages were added after installation;
In rare cases, a package installed by default with an earlier version of BILLmanager prevents the update, if this default package is not present in the latest up-to-date version.

The official repositories of the operating system are used for software updates. Connecting third-party repositories may cause conflicts. It is recommended to disable third-party repositories after using them.

Solution

To perform the update, disable or remove the package specified in the error.

BILLmanager should be installed on an unmodified OS without third-party repositories. For more details, see the article Server Requirements. If other products (ISPsystem or third-party products) are installed on the server besides BILLmanager, put them on different servers. To learn how to transfer BILLmanager data to a new server, see the article Migration between servers from BILLmanager Documentation.

Update fails

Description

A platform update is not starting and is not running. The reason may be that the ISPsystem repository server is unavailable.

Solution

To check if the server is available, run the command:

curl http://download.ispsystem.com

If the command output is empty, check your network settings or firewall rules.