Reading logs

Reading logs

Troubleshooting

Wiremaps logs a lot of things in /var/log/wiremaps/wiremaps.log (or on stdout or in the file you specified). You should watch to some important items:

• An error occured while exploring 172.31.11.137: unable to guess community: if the host does not exist this is harmless. Otherwise, you either have a firewall problem or the community does not match.
• An error occured while exploring 172.31.10.118: unknown equipment with OID .1.3.6.1.4.1.3375.2.1.3.4.10: Wiremaps does not know how to handle this host. See How to extend Wiremaps to tell him how to handle this host.
• An error occured while exploring 172.31.10.114: LLDP does not seem to be running: by default, there is very little information that is available for Linux hosts. Therefore, Wiremaps requires that you install an LLDP daemon to get more accurate information.

If you have logs like the following, this should be a bug in the application. A companion traceback gives usually more information.

 2008/10/07 13:09 CEST [-] The following error occured while exploring 172.31.10.206:
 2008/10/07 13:09 CEST [-] [Failure instance: Traceback: libpq.OperationalError: ERROR: duplicate key violates unique constraint "cdp_pkey"

Upgrading

When upgrading to a new version of the application, you will get logs like that:

 2008/10/08 18:09 CEST [-] Upgrade database: add 'last' column to 'equipment' table
 2008/10/08 18:09 CEST [-] adbapi connecting: pyPgSQL.PgSQL ('localhost:5432:wiremaps:wiremaps:wiremaps',)
 2008/10/08 18:09 CEST [-] adbapi connecting: pyPgSQL.PgSQL ('localhost:5432:wiremaps:wiremaps:wiremaps',)
 2008/10/08 18:09 CEST [-] database upgrade completed

If you get an error, this means that there is a problem while upgrading the database. You can try to start from scratch.