Appendix A Log Descriptions
Table 286 myZyXEL.com Logs (continued)
LOG MESSAGE | DESCRIPTION |
Change | The device failed to change the type of |
engine type has | response from the server is missing required fields. |
failed. Because of |
|
lack must fields. |
|
Resolve server IP has | The update has stopped because the device couldn’t resolve the |
failed. Update stop. | myZyXEL.com server's FQDN to an IP address through |
| gethostbyname(). |
Verify server's | The device could not process an HTTPS connection because it could |
certificate has | not verify the myZyXEL.com server's certificate. The update has |
failed. Update stop. | stopped. |
Send download request | The device’s attempt to send a download message to the update |
to update server has | server failed. |
failed. |
|
Get server response | The device sent packets to the MyZyXEL.com server, but did not |
has failed. | receive a response. The root cause may be that the connection is |
| abnormal. |
Timeout for get server | zysh need to catch MyZyXEL.com agent's return code, this log will be |
response. | shown when timeout. |
Send update request to | The device could not send an update message to the update server. |
update server has |
|
failed. |
|
Update has failed. | The device received an incomplete response from the update server |
Because of lack must | and it caused a parsing error for the device. |
fields. |
|
Update server is busy | The update server was busy so the device will wait for the specified |
now. File download | number of seconds and send the download request to the update |
after %d seconds. | server again. |
Device has latest | The device already has the latest version of the file so no update is |
file. No need to | needed. |
update. |
|
Device has latest | The device already has the latest version of the signature file so no |
signature file; no | update is needed. |
need to update |
|
Connect to update | The device cannot connect to the update server. |
server has failed. |
|
Wrong format for | The device cannot parse the response returned by the server. Maybe |
packets received. | some required fields are missing. |
Server setting error. | The device could not resolve the update server's FQDN to an IP |
Update stop. | address through gethostbyname(). The update process stopped. |
Build query message | Some information was missing in the packets that the device sent to |
failed. | the server. |
Starting signature | The device started an IDP signature update. |
update. |
|
IDP signature download | The device successfully downloaded an IDP signature file. |
has succeeded. |
|
IDP signature update | The device successfully downloaded and applied an IDP signature file. |
has succeeded. |
|
774 |
| |
ZyWALL USG 100/200 Series User’s Guide |
| |
|
|
|