1. Home
    2. /
  2. Manuals
    3. /
  3. Zyxel
    4. /
  4. ZyWALL-USG50
    5. /
  5. 160
Page 796 / 944 Scroll up to view Page 791 - 795
Appendix A Log Descriptions
ZyWALL USG 50 User’s Guide
796
Table 258
User Logs
LOG MESSAGE
DESCRIPTION
%s %s from %s has
logged in ZyWALL
A user logged into the ZyWALL.
1st %s: The type of user account.
2nd %s: The user’s user name.
3rd %s: The name of the service the user is using (HTTP,
HTTPS, FTP, Telnet, SSH, or console).
%s %s from %s has
logged out ZyWALL
A user logged out of the ZyWALL.
1st %s: The type of user account.
2nd %s: The user’s user name.
3rd %s: The name of the service the user is using (HTTP,
HTTPS, FTP, Telnet, SSH, or console).
%s %s from %s has been
logged out ZyWALL (re-
auth timeout)
The ZyWALL is signing the specified user out due to a re-
authentication timeout.
1st %s: The type of user account.
2nd %s: The user’s user name.
3rd %s: The name of the service the user is using (HTTP,
HTTPS, FTP, Telnet, SSH, or console).
%s %s from %s has been
logged out ZyWALL
(lease timeout)
The ZyWALL is signing the specified user out due to a lease
timeout.
1st %s: The type of user account.
2nd %s: The user’s user name.
3rd %s: The name of the service the user is using (HTTP,
HTTPS, FTP, Telnet, SSH, or console).
%s %s from %s has been
logged out ZyWALL (idle
timeout)
The ZyWALL is signing the specified user out due to an idle
timeout.
1st %s: The type of user account.
2nd %s: The user’s user name.
3rd %s: The name of the service the user is using (HTTP,
HTTPS, FTP, Telnet, SSH, or console).
Console has been put
into lockout state
Too many failed login attempts were made on the console
port so the ZyWALL is blocking login attempts on the
console port.
Address %u.%u.%u.%u has
been put into lockout
state
Too many failed login attempts were made from an IP
address so the ZyWALL is blocking login attempts from that
IP address.
%u.%u.%u.%u: the source address of the user’s login
attempt
Page 797 / 944
Appendix A Log Descriptions
ZyWALL USG 50 User’s Guide
797
Failed login attempt to
ZyWALL from %s (login
on a lockout address)
A login attempt came from an IP address that the ZyWALL
has locked out.
%u.%u.%u.%u: the source address of the user’s login
attempt
Failed login attempt to
ZyWALL from %s (reach
the max. number of
user)
The ZyWALL blocked a login because the maximum login
capacity for the particular service has already been reached.
%s: service name
Failed login attempt to
ZyWALL from %s (reach
the max. number of
simultaneous logon)
The ZyWALL blocked a login because the maximum
simultaneous login capacity for the administrator or access
account has already been reached.
%s: service name
User %s has been denied
access from %s
The ZyWALL blocked a login according to the access control
configuration.
%s: service name
User %s has been denied
access from %s
The ZyWALL blocked a login attempt by the specified user
name because of an invalid user name or password.
2nd %s: service name
Table 259
myZyXEL.com Logs
LOG MESSAGE
DESCRIPTION
Send registration
message to MyZyXEL.com
server has failed.
The device was not able to send a registration message to
MyZyXEL.com.
Get server response
has failed.
The device sent packets to the MyZyXEL.com server, but did
not receive a response. The root cause may be that the
connection is abnormal.
Timeout for get server
response.
zysh need to catch MyZyXEL.com agent's return code, this log
will be shown when timeout.
User has existed.
The user name already exists in MyZyXEL.com's database. So
the user can't use it for device registration and needs to
specify another one.
User does not exist.
The user name does not yet exist in MyZyXEL.com's
database. So the user can use it for device registration.
Internal server error.
MyZyXEL.com's database had an error when checking the
user name.
Device registration
has failed:%s.
Device registration failed, an error message returned by the
MyZyXEL.com server will be appended to this log.
%s: error message returned by the myZyXEL.com server
Device registration
has succeeded.
The device registered successfully with the myZyXEL.com
server.
Table 258
User Logs (continued)
LOG MESSAGE
DESCRIPTION
Page 798 / 944
Appendix A Log Descriptions
ZyWALL USG 50 User’s Guide
798
Registration has
failed. Because of
lack must fields.
The device received an incomplete response from the
myZyXEL.com server and it caused a parsing error for the
device.
%s:Trial service
activation has
failed:%s.
Trail service activation failed for the specified service, an error
message returned by the MyZyXEL.com server will be
appended to this log.
1st %s: service name
2nd %s: error message returned by the myZyXEL.com server
%s:Trial service
activation has
succeeded.
Trail service was activated successfully for the specified
service.
%s: service name
Trial service
activation has failed.
Because of lack must
fields.
The device received an incomplete response from the
myZyXEL.com server and it caused a parsing error for the
device.
Standard service
activation has
failed:%s.
Standard service activation failed, this log will append an
error message returned by the MyZyXEL.com server.
%s: error message returned by the myZyXEL.com server
Standard service
activation has
succeeded.
Standard service activation has succeeded.
Standard service
activation has failed.
Because of lack must
fields.
The device received an incomplete response from the
myZyXEL.com server and it caused a parsing error for the
device.
Service expiration
check has failed:%s.
The service expiration day check failed, this log will append
an error message returned by the MyZyXEL.com server.
%s: error message returned by myZyXEL.com server
Service expiration
check has succeeded.
The service expiration day check was successful.
Service expiration
check has failed.
Because of lack must
fields.
The device received an incomplete response from the
myZyXEL.com server and it caused a parsing error for the
device.
Server setting error.
The device could not retrieve the myZyXEL.com server's IP
address or FQDN from local.
Resolve server IP has
failed.
The device could not resolve the myZyXEL.com server's FQDN
to an IP address through gethostbyname().
Verify server's
certificate has
failed.
The device could not process an HTTPS connection because it
could not verify the myZyXEL.com server's certificate.
Connect to MyZyXEL.com
server has failed.
The device could not connect to the MyZyXEL.com server.
Do account check.
The device started to check whether or not the user name in
MyZyXEL.com's database.
Table 259
myZyXEL.com Logs (continued)
LOG MESSAGE
DESCRIPTION
Page 799 / 944
Appendix A Log Descriptions
ZyWALL USG 50 User’s Guide
799
Do device register.
The device started device registration.
Do trial service
activation.
The device started trail service activation.
Do standard service
activation.
The device started standard service activation.
Do expiration check.
The device started the service expiration day check.
Build query message
has failed.
Some information was missing in the packets that the device
sent to the MyZyXEL.com server.
Parse receive message
has failed.
The device cannot parse the response returned by the
MyZyXEL.com server. Maybe some required fields are
missing.
Change Anti-Virus
engine.
The device started to change the type of anti-virus engine.
Change Anti-Virus
engine has failed:%s.
The device failed to change the type of anti-virus engine. %s
is the server response error message.
Change Anti-Virus
engine has succeeded.
The device successfully changed the type of anti-virus engine.
Change Anti-Virus
engine type has
failed. Because of
lack must fields.
The device failed to change the type of anti-virus engine
because the response from the server is missing required
fields.
Resolve server IP has
failed. Update stop.
The update has stopped because the device couldn’t resolve
the myZyXEL.com server's FQDN to an IP address through
gethostbyname().
Verify server's
certificate has
failed. Update stop.
The device could not process an HTTPS connection because it
could not verify the myZyXEL.com server's certificate. The
update has stopped.
Send download request
to update server has
failed.
The device’s attempt to send a download message to the
update server failed.
Get server response
has failed.
The device sent packets to the MyZyXEL.com server, but did
not receive a response. The root cause may be that the
connection is abnormal.
Timeout for get server
response.
zysh need to catch MyZyXEL.com agent's return code, this log
will be shown when timeout.
Send update request to
update server has
failed.
The device could not send an update message to the update
server.
Update has failed.
Because of lack must
fields.
The device received an incomplete response from the update
server and it caused a parsing error for the device.
Update server is busy
now. File download
after %d seconds.
The update server was busy so the device will wait for the
specified number of seconds and send the download request
to the update server again.
Device has latest
file. No need to
update.
The device already has the latest version of the file so no
update is needed.
Table 259
myZyXEL.com Logs (continued)
LOG MESSAGE
DESCRIPTION
Page 800 / 944
Appendix A Log Descriptions
ZyWALL USG 50 User’s Guide
800
Device has latest
signature file; no
need to update
The device already has the latest version of the signature file
so no update is needed.
Connect to update
server has failed.
The device cannot connect to the update server.
Wrong format for
packets received.
The device cannot parse the response returned by the server.
Maybe some required fields are missing.
Server setting error.
Update stop.
The device could not resolve the update server's FQDN to an
IP address through gethostbyname(). The update process
stopped.
Build query message
failed.
Some information was missing in the packets that the device
sent to the server.
Starting signature
update.
The device started an IDP signature update.
IDP signature download
has succeeded.
The device successfully downloaded an IDP signature file.
IDP signature update
has succeeded.
The device successfully downloaded and applied an IDP
signature file.
IDP signature download
has failed.
The device still cannot download the IDP signature after 3
retries.
Anti-Virus signature
download has
succeeded.
The device successfully downloaded an anti-virus signature
file.
Anti-Virus signature
update has succeeded.
The device successfully downloaded and applied an anti-virus
signature file.
Anti-Virus signature
download has failed.
The device still cannot download the anti-virus signature after
3 retries.
System protect
signature download has
succeeded.
The device successfully downloaded the system protect
signature file.
System protect
signature update has
succeeded.
The device successfully downloaded and applied a system
protect signature file.
System protect
signature download has
failed.
The device still cannot download the system protect signature
file after 3 retries.
Resolve server IP has
failed.
The device could not resolve the myZyXEL.com server's FQDN
to an IP address through gethostbyname().
Connect to MyZyXEL.com
server has failed.
The device could not connect to the MyZyXEL.com server.
Build query message
has failed.
Some information was missing in the packets that the device
sent to the server.
Verify server's
certificate has
failed.
The device could not process an HTTPS connection because it
could not verify the server's certificate.
Table 259
myZyXEL.com Logs (continued)
LOG MESSAGE
DESCRIPTION

Rate

4.5 / 5 based on 2 votes.

Popular Zyxel Models

Famous Router IPs
Famous Router Companies
Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top