Af-Arch servers error codes

On this page you will find the following error descriptions:

AF0001 Unable to initialize database access.

This happens when the server configuration is not correct or the database backend is down. You have to check the following configuration items in the server configuration file usually found at /etc/af-arch:

This error is also thrown when server SQL schema is not installed. When Af-Arch server nodes are started, they make an initial connection to the database.

AF0002 Unable to get access to server configuration file

Server configuration files are stored inside /etc/af-arch/. Usually, server configuration files are stored using the same server name. For a server called af-test it should exist a file called: /etc/af-arch/af-test.cfg.

This error is due to the file is missing or permissions have to be checked.

AF0003 Unable to get listening port configuration

This error is due to listening port [positive] didn't be defined.

AF0004 Unable to start Af-Arch server

This error usually means there is another process using the server port (a bind error). This error is also used to report that something have happens while starting the server without know the concret error.

AF0005 Unable to register server exported services

Every server developed inside the Af-Arch framework needs to register its services to against the Af-Kernel. This is done using the option --update-services. This option is included for all servers developed.

This error is showed when previous process has failed.

AF0006 Unable to register server while starting the server

Every Af-Arch server register its location on the central server at startup. This enables central server to notify Af-Arch clients where are located server components.

This error is showed when previous process has failed.

You have to check that Af-Kernel server is running. You have to also check if you already register exported services for the server (using --update-services).

AF0007 Value for listening hostname value not found

This error is showed when listening hosname [string] value didn't be defined. You have to check server configuration file.

AF0008 Unable to get current hostname

This error is showed when listening hosname [string] has "auto" as value. This means Af-Arch framework needs to get current host name.

You have to check that hostname command retuns a right value. hostname gets current host name configuration from /etc/hosts and /etc/hostname.

AF0009 Unable to get current IP address

This error is showed when current hostname configuration doesn't returns any IP address. Check you have actually set a hostname value for listening hosname [string] that resolves to a IP address.

You can also use IP addresses to listening hosname [string].

AF0010 Unable to found central server configuration

This error is showed when the location set at server [string] and kernel port [positive] is not correct or the server at the configuration location is down.

AF0011 Connection error

This error is showed on connection errors.

AF0012 Server configuration file have wrong permissions

Because server configuration file have security information, every Af-Arch server makes a permission checking to ensure he is the only one that can actually get access to the config file.

This error is showed when the previous check has failed.

AF0013 Config value for afkey expiration not found

This is an Af-Kernel especific error.

This error is showed when the configuration value afkey expiration [positive] wasn't found.

AF0014 Config value for session expiration not found

This is an Af-Kernel especific error.

This error is showed when the configuration value session expiration [positive] wasn't found.

AF0015 Unable to create enough database connections

This is a error which can be produced on any Af-Arch server. Means the Af-Arch server could create the predefined database connections.