Log Files

The log files generated by HSYCO are contained in sub-directories under hsyco/logs.

Message Log

HSYCO writes a separate log file each day, in a different directory for each year, in the MMGG-message.log format. For example, the log file for January 4th 2012 will be hsyco/logs/2012/0104-message.log.

The information details contained in the log files depend on the settings of the log options defined in hsyco.ini.

All the relevant events detected from the field, commands sent, users access information and possible errors can be traced.

Every log line starts with date and time (local time is always used according to the server settings), in the format:

AAAA.MM.GG HH:MM:SS:MMM

followed by the “+” character for errors, “-” for information messages and “*” for the remote logs generated by the JavaScript code of the Web interface.

Some examples of log messages that appear in typical situations are described below.

Starting HSYCO Without a License Key

2012.01.04 11:39:14.402 - HSYCO Ver. 3.0.0 Build 0086 (USER Ver. No User Code) started
2012.01.04 11:39:16.133 - Starting HTTP Server
2012.01.04 11:39:16.180 - Starting HTTPS SSL Server
2012.01.04 11:39:16.751 - HTTP server accepting connections on port: 80. Document root: www
2012.01.04 11:39:18.126 - HTTPS server accepting connections on port: 443. Document root: www

When the software license key is not available or is not valid, only the HTTP and HTTPS servers are activated.

HSYCO Normal Start-up Process

2012.01.04 11:39:14.402 - HSYCO Ver. 3.0.0 BETA Build 0086 (USER Ver. No User Code) started
2012.01.04 08:14:10.943 - Starting HTTP Server
2012.01.04 08:14:10.951 - Starting HTTPS SSL Server
2012.01.04 08:14:11.167 - HTTP server accepting connections on port: 80. Document root: www
2012.01.04 08:14:12.012 - Starting I/O Monitor [0]
2012.01.04 08:14:12.015 - Starting OpenWebNet Polling [0]
2012.01.04 08:14:12.019 - Starting Cameras Polling [0]
2012.01.04 08:14:12.021 - Starting Cameras Polling [1]
2012.01.04 08:14:12.022 - Cameras polling started [0]
2012.01.04 08:14:12.049 - Cameras polling started [1]
2012.01.04 08:14:12.078 - Starting User Time Callback Server
2012.01.04 08:14:12.110 - Starting Device Timer
2012.01.04 08:14:12.111 - User Time Callback Server started
2012.01.04 08:14:12.113 - Starting Timer Server
2012.01.04 08:14:12.115 - Device Timer started
2012.01.04 08:14:12.122 - Starting SysLog UDP Server
2012.01.04 08:14:12.124 - Timer Server started
2012.01.04 08:14:12.127 - Starting Music Players Status Polling
2012.01.04 08:14:12.134 - SysLog UDP server accepting packets on port: 514
2012.01.04 08:14:12.138 - Music Players Polling started
2012.01.04 08:14:12.143 - Starting IRTrans Monitor [0]
2012.01.04 08:14:12.146 - Starting SlimServer Monitor
2012.01.04 08:14:12.151 - IRTrans Monitor [0] connection established
2012.01.04 08:14:12.179 - SlimServer Monitor connection established
2012.01.04 08:14:12.200 - HTTPS server accepting connections on port: 443. Document root: www
2012.01.04 08:14:33.480 - ioMonitor - started [knx]

In normal conditions, all HSYCO subsystems are activated:

• HTTP Server
• HTTPS Server
• I/O Server (for each I/O sub-system)
• Cameras Polling (for each camera)
• User Time Callback Server
• Device Timer
• Timer Server
• Music Players Status Polling
• SysLog UDP Server
• IRTrans Monitor (for each IRTrans).

For each of these systems, you will see a log line at the beginning of the activation and one to confirm the successful activation.

I/O Servers Connection Errors

2012.01.04 18:22:45.989 + ioMonitor - Exception [knx] - connect timed out
2012.01.04 18:22:46.401 + ioMonitor - Handshake error (2) in OpenWebNet monitor thread [myhome] - SCS server requires authentication

In this case, we have a time-out connection error on the KNX server and an authentication error on the OpenWebNet gateway.

IRTrans Connection Errors

2012.01.04 18:22:46.916 + IRTransMonitor - Couldn't get I/O for IRTrans [0] - Connection refused

This message signals a connection error to the first IRTrans – [0] IRTrans – defined in the IRTrans parameter in hsyco.ini.

Writing Errors of the Cameras Images

2012.01.04 20:00:00.000 + cameraRecSet - Camera recording skipped - Disk full

This message indicates that the disk storage space for saving camera images is insufficient to record new camera images.

2012.01.04 20:00:00.000 + cameraFlushAgedFrames -  Early delete [camera] frames - Disk full

This message indicates that the disk storage space for saving camera images is low, and HSYCO is deleting older images sooner than the configured expiration time.

Security Messages

All messages concerning security are identified by the heading:

SECURITY ALERT

PIN not found; only the first and the last digit of the wrong PIN are shown in the log:

2012.01.04 19:27:02.121 + SECURITY ALERT: CHECKAUTHREQ FAILED - REASON: PIN NOT FOUND - IP: 127.0.0.1 PIN: 1***5

Valid PIN, but wrong PUK; the PIN is not written in the log. HPIN is the encrypted PIN saved in access.ini:

2012.01.04 19:30:44.739 + SECURITY ALERT: CHECKAUTHREQ FAILED - REASON: PIN/PUK AUTH FAILED - IP: 127.0.0.1 HPIN: 556342...

Error in the URLKEY used to access the HSYCO Web interface:

2012.01.04 19:29:47.111 + SECURITY ALERT: CHECKPINPAGEREQ FAILED - REASON: KEY NOT FOUND - IP: 127.0.0.1 KEY: alsldkekds

The access.ini file has been modified and, as a consequence, reloaded by HSYCO:

2012.01.04 19:31:48.383 - SECURITY ALERT: access.ini file reloaded

Login and logout messages of the user identified by the default name:

2012.01.04 19:28:16.734 - SECURITY ALERT: USER LOGIN - IP: 127.0.0.1 USER: default
2012.01.04 19:29:08.159 - SECURITY ALERT: USER LOGOUT - IP: 127.0.0.1 USER: default

New user created through the users management Web page:

2012.01.04 09:48:41.275 - SECURITY ALERT: WEB ADMIN - USER [myuser]  NEW [ack]

Changes to an existing user from the users management Web page:

2012.01.04 09:50:40.000 - SECURITY ALERT: WEB ADMIN - USER [myuser] UPDATE [ack]

User deleted from the users management Web page:

2012.01.04 09:52:40.000 - SECURITY ALERT: WEB ADMIN - USER [myuser] DELETE [ack]

Commands Sent from the Web Interface

Examples of commands sent to I/O Servers data points, to DMX channels and user buttons:

2012.01.04 20:04:25.956 - WEB I/O COMMAND [domino.o133.20=flip]: [OK]
2012.01.04 21:44:18.493 - WEB I/O COMMAND [dummy.light.1=0]: [OK]
2012.01.04 21:44:31.252 - WEB I/O COMMAND [myhome.scene.94.5=flip]: [OK]
2012.01.04 21:45:11.412 - WEB USER COMMAND [var1]: 2 [OK]
2012.01.04 21:47:21.300 - WEB DMX COMMAND [100*190]: [OK]

Web Wi-Fi Clients Location services

When the association of a Wi-Fi device (the device should be running a Web Browser with an active HSYCO session) to an Access Point is detected, the log message is:

2012.01.04 20:14:45.228 - LOCATION: 192.168.0.209 LOCATED AT 2p

When the device is disconnected, or de-associated from an Access Point, the message is:

2012.01.04 20:16:17.752 - LOCATION: 192.168.0.180 POSITION UNKNOWN

Phone Calls Log

Call notifications managed by the telephone systems integrated to HSYCO are recorded in the log file.

2012.01.04 20:14:45.228 - PBX CALL [192.168.1.13]: FROM: 210 TO: 310 [OK]

The security.log File

If any anti-intrusion units is connected to HSYCO, the security.log file will be written in the same directories as the daily log files.

This file contains the list of all events of activation, deactivation and alarm detected on the anti-intrusion units.

2012.01.04 12:38:25.861 [0] OFF - ZONES 1
2012.01.04 12:46:36.392 [0] ON - ZONES 1234
2012.01.04 12:47:08.703 [0] ALARM - INTRUSION - ZONE 1
2012.01.04 12:47:25.055 [0] OFF - ZONES 1234
2012.01.04 13:14:23.629 [0] ON - ZONES 1