Error and debug
messages
"Incorrect
XML"
This messages appears when the manager cannot
load configuration. The real error can be found in Apache logs.
"Byte order is not compatible" ou "Magic number checking on storable
string failed"
This error message apprears when stored
configuration is corrupted or on versions earlier than 0.8.2.3 when you're
using Lemonldap::NG with different server types (32 and 64 bits for
example). In this case, you've to upgrade your Lemonldap::NG to at least
0.8.2.3.
"Configuration is in
old format, you've to migrate !"
This warning message means that you are using a
configuration generated by an earlier version than 0.8.2.3 with a more
up-to-date Lemonldap::NG component. You just have to re-save configuration
with a recent manager to avoid this warning.
"My::Package: get configuration
1"
Information message: an Apache child process load
configuration.
"My::Package: store
configuration 1"
Information message: an Apache child process
stores the last configuration in the local cache. It will be read by other
Apache childs before 10 minutes.
"My::Package: No cookie
found"
Information message: one non-authenticated user
tries to connect to the protected application.
"Redirect
<x.x.x.x> to portal (url was /)"
Debug message: the client x.x.x.x is redirected
to the authentication portal.
"Found a
CDA id. Redirecting"
Debug message: the client has been authenticated
in another domain (CDA mechanism). The handler generates the cookie in the
new domain.
"User someone was
authorizated to access to /"
Debug message: the user "someone" has been
authorizated to access to this URL.
"My::Package: removing
cookie"
Debug message: after grant, the handler removes
hides the cookie. Protected application needs only headers.
"Error
while reading configuration with globalStorageOptions key:"
Configuration is corrupted. See the following
error.
"User
rejected because VirtualHost test.example.com has no
configuration"
When a virtual host is protected but not
configured, Lemonldap::NG block it. Update your configuration to add this
new virtual host, save and apply it.
"The cookie xxxx isn't yet available: Object does not exist in the data
store at /usr/share/perl5/Apache/Session/Store/File.pm line
90.n"
This message appears when a user use an old
cookie that has been deleted from session database. He has to
re-authenticated itself.
"The cookie xxxx isn't yet available: <Apache::Session error message>
This message appears when an handler can not
access to session database. The real error is reported.