Introduction to Abiquo logs
Abiquo recommends that customers first consult the Event logs in Events view in the Abiquo UI.
By default, you can find all of the logs for the Abiquo services in the /opt/abiquo/tomcat/logs folder.
The Abiquo platform automatically archives the logs by date. It renames the existing log to include the creation date (application-year-month-day.log) and creates a new log at 00 hours the next day.
catalina.out - Tomcat server
This log is the general log of Tomcat instance on each Tomcat server.
The Tomcat Catalina
log file is /opt/abiquo/tomcat/logs/catalina.out
This is the best log to start troubleshooting because it gives you a summary view of all the web apps running on the Tomcat Server (for API or RS) and it contains the output from all parts of the platform at the same time.
But for performance reasons, this log has a shorter version of the events than the other logs. The Catalina.out log includes the Events View messages, which include the following.
Messages | See messages in Catalina.out and Events view |
Actions | See Events view in the actions table section and the Events table |
Severity codes | See Events view in the severity table section and the Events table |
Catalina is the servlet container for Tomcat, which implements the Java specifications for servlet and Java Server Pages or JSP.
health.log - health check service
To ensure the best performance of all the components, Abiquo includes a health check for the Remote Services from each datacenter.
Date and time | Type | Process information | Remote service ________________________ | Datacenter |
|---|---|---|---|---|
2011-10-05 02:02:25,863 | DEBUG | c.a.a.h.RemoteServicesCheck (RemoteServicesCheck.java:98) | Checking Remote Service (Storage Manager) of | datacenter (1) |
localhost.yyyy-mm-dd.log
An error compilation for events occurring between the Tomcat's local host and the web applications. These logs are not normally used for troubleshooting procedures because they contain less detailed information than the other specific logs.
api.log - Abiquo API
The API log file is /opt/abiquo/tomcat/logs/api.log
The API log contains API messages. You can find more Information API errors in the Developer's Guide under Basic behaviors and in the API Error Code List
server.log - Abiquo server
This is mainly a record of events between the Abiquo environment and the database, including the messages that will appear in the Events View, which in turn, are stored in the MySQL database.
Date and time | Type | Process information | Message _ ________________________ _______________________________ | Related to _____________ |
|---|---|---|---|---|
2011-10-14 08:29:31,838 | INFO | c.a.t.s.LoggingTracerProcessor (LoggingTracerProcessor.java:38) | Received message: Severity(INFO), Event(USER_LOGIN), Component(USER), Timestamp(1318552171822), Description(), User(admin) | Event View |
2011-10-14 08:29:31,840 | DEBUG | c.a.t.s.TracerCollector (TracerCollector.java:165) | Dispatched payload to:com.abiquo.abiserver.tracerprocessor.DBTracerProcessor | Database Connection |
bpm-async.log - Asynchronous business process manager
For the V2V remote service, this log contains details of the Business Process Manager and V2V conversions.
A standard conversion output
2011-10-05 03:43:49,000 DEBUG c.a.a.b.s.u.ConverterUtils [ConverterUtils.java:90] Output:command: rm -f /opt/vm_repository/1/192.168.5.1/CentOS-40GB-2/formats/CentOS5.6_HDD40GB-disk1.vmdk-VHD_SPARSE.vhd command: VBoxManage clonehd --format VHD /opt/vm_repository/1/192.168.5.1/CentOS-40GB-2/CentOS5.6_HDD40GB-disk1.vmdk /opt/vm_repository/1/192.168.5.1/CentOS-40GB-2/formats/CentOS5.6_HDD40GB-disk1.vmdk-VHD_SPARSE.vhd Sun VirtualBox Command Line Management Interface Version 3.1.8_OSE (C) 2005-2010 Sun Microsystems, Inc. All rights reserved. 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% Clone hard disk created in format 'VHD'. UUID: c8318b48-52b2-4582-bb93-64406cfe89cb command: chmod 644 /opt/vm_repository/1/192.168.5.1/CentOS-40GB-2/formats/CentOS5.6_HDD40GB-disk1.vmdk-VHD_SPARSE.vhd 2011-10-05 03:43:49,000 DEBUG c.a.a.b.s.u.ConverterUtils [ConverterUtils.java:91] Error:base64: invalid input base64: invalid input 2011-10-05 03:43:49,000 DEBUG c.a.a.b.s.u.ConverterUtils [ConverterUtils.java:92] ErrorCode:0 2011-10-05 03:43:49,000 INFO c.a.a.b.s.i.ImageConverterService [ImageConverterService.java:61] Status: FINISHED 2011-10-05 03:43:49,000 DEBUG c.a.a.b.s.i.ImageConverterService [ImageConverterService.java:77] Image conversion took: 105342 milliseconds.
am.log - appliance manager
For the Appliance Manager, this log contains error messages related to virtual image templates and the Catalogue (NFS Repository).
Date and time | Type | Process information | Message | Related to ________________________ |
|---|---|---|---|---|
03:55:58.322 | DEBUG | c.a.a.s.download.DownloadingFile | File /opt/vm_repository/1/abiquo-remote-repository.repository.com/ | A virtual machine template will be downloaded |
nars.log - discovery manager
Contains messages about the discovery, addition and status of the physical hypervisor nodes and public cloud regions. Manages virtual resource discovery.
Date and time | Type | Process information | Message | Related to ________________________ _ |
|---|---|---|---|---|
2019-04-15 16:15:35,784 | DEBUG | c.abiquo.gen.server.utils.Execution | Connecting to ConnectionData{Host ip=10.60.2.56, Type=ESX} | Connection between discovery manager and hypervisor |
2019-04-15 16:16:12,596 | WARN | c.a.p.e.utils.ServiceInstanceUtils | InvalidLogin retry 3 | One of multiple login attempts with bad credentials
|
2019-04-15 16:16:18,589 | DEBUG | c.abiquo.gen.server.utils.Execution | Disconnecting from ConnectionData{Host ip=10.60.2.56, Type=ESX} | Disconnection of discovery manager from hypervisor |
ssm.log - Storage System Manager
Contains messages related to all storage functions.
Date and Time | Type | Process information | Message______________________________________________ | Related to ________________________ |
|---|---|---|---|---|
2011-10-01 01:10:14,350 | INFO | c.a.s.r.PoolsResource (PoolsResource.java:79) | Getting pools at 192.168.5.2 | User added a new pool |
2011-10-01 01:10:14,788 | INFO | c.a.s.r.PoolsResource (PoolsResource.java:83) | Found 1 pools | Response to previous request |
2011-10-01 01:10:46,158 | DEBUG | c.a.s.p.StoragePluginManager (StoragePluginManager.java:80) | Loading plugin for device LVM | SSM is telling us which plugin will be used for the following tasks |
2011-10-01 01:10:46,158 | INFO | c.a.s.r.VolumeResource (VolumeResource.java:150) | Creating volume 1c98dc49-a7cd-485b-82a7- | Volume created by user |
virtualfactory.log - Virtualization Manager
Contains information about virtual appliance deployment and virtual machine management operations such as configuration changes.
Virtual Appliance Deployment
2011-10-13 11:23:57,826 DEBUG c.a.v.v.i.VirtualapplianceresourceDeployerPremium [VirtualapplianceresourceDeployerPremium.java:101] [PUT CALL] OVF: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <ns1:Envelope xmlns:ns2="http: //schemas.dmtf.org/wbem/wscim/1[..]
This will be followed by the virtual machine description sent by Abiquo to the Hypervisor, which can contain information related to disks, network, etc. See the VM Template Guide (Introduction to Virtual Machine Templates#OVF for Abiquo).
Date and time | Type | Process information | Message____________________________________________ | Related to ________________________ |
|---|---|---|---|---|
2011-10-13 11:23:57,837 | DEBUG | c.a.v.m.o. OVFModelToVirtualAppliance (OVFModelToVirtualAppliance. java:919) | Attaching disk (192.168.5.2|ip-192.168.5.2:3260\\
-iscsi-iqn.2008-03.com.abiquo.lvm01: | An external volume is attached to the virtual machine |
2011-10-13 11:23:57,837 | DEBUG | c.a.v.m.o. OVFModelToVirtualAppliance (OVFModelToVirtualAppliance. java:926) | Attaching NIC (00155Ddad9e9) generation sequence (0) | A new NIC is attached to the VM |
2011-10-13 11:23:57,837 | DEBUG | c.a.v.m.o. OVFModelToVirtualAppliance (OVFModelToVirtualAppliance. java:930) | The remote desktop port is : 5903 | The VNC connection port |
2011-10-13 11:23:59,956 | INFO | c.a.v.m.AbsVirtualMachine (AbsVirtualMachine.java:105) | Changing the state of virtual machine: ABQ_57135f47-cf29-4a14-a76f-f1e6a980aad0 to: POWER_OFF | User has sent a power off order |
2011-10-13 11:23:59,982 | INFO | c.a.v.m.AbsVirtualMachine (AbsVirtualMachine.java:229) | Virtual machine: ABQ_57135f47-cf29-4a14-a76f -f1e6a980aad0 changed successfully to state : POWER_OFF | The event tells us the new VM status |
vsm.log - Virtual system monitor - monitor manager
This remote resource uses an event subscription to inform Abiquo about all changes made on a physical machine and the virtual machines deployed on it. Contains information about changes in virtual appliance and virtual machine states. See States in Virtual Appliances and Virtual Machines in the User Guide.
Date and time | Type | Process information | Message_____________________________ | Related to ________________________ |
|---|---|---|---|---|
2011-10-13 11:22:24,505 | INFO | c.a.v.r.p.RedisSubscriberCallback (RedisSubscriberCallback.java:226) | Physical machine address: http: //192.168.7.1:5985/ | VSM is suscribed to the hypervisor on that address |
2011-10-13 11:22:24,505 | INFO | c.a.v.r.p.RedisSubscriberCallback (RedisSubscriberCallback.java:227) | Physical machine type: HYPERV_301 | Hypervisor type |
2011-10-13 11:24:00,690 | INFO | c.a.v.VSMManager (VSMManager.java:174) | Checking VSM status... | VSM checks its database status and connectivity |
2011-10-13 11:24:00,692 | INFO | c.a.v.VSMManager (VSMManager.java:213) | VSM is up and running properly. | Preview event status |
2011-10-13 11:24:00,712 | INFO | c.a.v.m.MonitorManager (MonitorManager.java:266) | Unsubscribing from ABQ_57135f47-cf29-4a14-a76f-f1e6a980aad0 on http: /192.168.7.1:5985/ | Will stop receiving information from this virtual machine due to undeploy |
RabbitMQ log
By default the RabbitMQ logs are found at: /var/log/rabbitmq.
Redis
By default Redis logs are found at: /var/log/redis and Redis is configured in verbose mode, which can generate very large log files of up to 10 GB.
MariaDB
By default the MariaDB log is found at: /var/lib/mysql/hostname.err.
Messages in Catalina.out and Events view
The tracer messages are found in the Catalina.out log file and in Events View. The tracer messages are documented in the Events view pages in the Tracer column and ordered by the events that may produce the messages.
These messages are targeted to different users and in Events view, they will only be displayed for users with privileges to view the message for an event. For convenience, in the documentation, the event messages are divided by the default roles: Cloud Admin can see all the messages, and Enterprise Admin and user can see those their privileges allow.
Cloud Admin messages: Events table
The variables in the messages that represent entity names and numbers have been replaced with tokens (e.g. APPLICATION_NAME). At times the tracers may also be accompanied by another another error message code - usually from the API Error Code List, which is documented for users: User interface messages and developers: API Error Code List