Troubleshooting

Previous  Top  Next

To help in solving the problems, the Pigeon Client creates a new Client.log file in the installation directory.

The Pigeon Server will write some troubleshooting information in the Windows event database. However, to get more detailed information about any problem, a debug.log file can be created in the same directory as the Pigeon_server.exe file. In this case, the Pigeon Server service must be stopped and restarted in order to use this log file. This file might grow very quickly. If not required, it must be deleted or renamed. You must stop the Pigeon Server service before deleting or renaming the file then restart it.

There are also few mechanisms to ensure that the message will reach the Pigeon Clients:

·	Client's watchdog: Every minute, the Pigeon Client checks to see if the connection with the Pigeon Server is still working. If not, a reconnection is attempted.

·	Server's daily shutdown: Everyday between 00:00:00 and 00:00:59 (midnight), the Pigeon Server resets all connections with the Pigeon Clients, forcing them to initiate a reconnection with their watchdog.

·	During message transmission: When the Pigeon Server sends a message to the Pigeon Clients, if a connection is not responding, the communication channel is liberated and it can then be used by a new Pigeon Client.