Your browser does not allow this site to store cookies and other data. Some functionality on this site may not work without them. See Privacy Policy for details on how we would use cookies.

PreviousNextUp[Front page] [Index]

Server Generic Messages

This section lists all syslog messages reported by SSH Tectia Certifier Server which are not specific to any service (admin,web enroll,CMP,SCEP etc.). The messages are divided into groups by their severity.

Server Messages at Level LOG_CRITICAL

  • Failed to update private key.

    The server updated its CaCom keypair and certificate but failed to store the new private key.

  • Can't find valid TLS client certificate and private key. Please restart ssh-ca-server with valid...

    Can't find valid TLS client certificate and private key. Please restart ssh-ca-server with valid shared secret ('-e' option) to enroll a new certificate.

Server Messages at Level LOG_ERR

  • ssh-ca-server: Failed to daemonize: reason for system error.

    Server failed to run in the background.

  • Failed to receive server configuration from Engine at IP address.

    Failed to fetch the server configuration (which services are to be run etc.) from the Engine.

  • Failed to write trusted root ca to filename:reason for system error.

    The server failed to write the trusted CaCom certificate just received from the Engine to disk.

  • Offered CA certificate rejected.

    The user interactively rejected the new CaCom trusted CA certificate

  • Cannot start TCP listener at port IP port, port reserved by another service.

    This server has more than one service configured to the same IP port.

  • Cannot start TCP listener server at host hostname, portIP port: reason for system error

    Server cannot listen to the port. Typically caused by another application already listening to the port, or trying to listen to ports below 1024 when the server is not run as root.

  • Cannot start HTTP server: failed to parse configuration URL configuration

  • Cannot start HTTP server at host hostname, port IP port: reason for system error.

    HTTP server cannot listen to the port. Typically caused by another application already listening to the port, or trying to listen to ports below 1024 when the server is not run as root.

  • Failed to read client certificate, enroll new one.

    The CaCom TLS certificate for this server couldn't be read.

  • TLS init failed: reason for system error.

    CaCom communication couldn't be initiated.

  • TLS init failed.

    CaCom communication couldn't be initiated.

  • Failed to read private key from 'filename': reason for system error.

  • Failed to blobify private key.

    The private key file did not contain a valid DER encoded private key.

  • Failed to write private key file filename.

  • Can't open the private key file filename.

  • Couldn't import the private key from file filename.

  • Can't open trusted certificate file filename.

  • Can't open certificate file filename.

  • Couldn't add the certificate from file filename to the certificate manager.

  • Couldn't add the trusted certificate from file filename to the certificate manager.

  • Received garbage from engine, len length of unexpected message.

    The message received from engine could not be parsed. This should not happen.

  • Received unknown (timeouted) message from engine, length of timeouted message.

    The engine replied to a request which the server had already given up on. Typically caused by a heavily loaded system or generating long keypairs when the engine is running on a slow computer.

  • Failed to enroll new client certificate from engine.

  • Failed to write new client certificate to file 'filename': reason for system error.

  • Ca-comm TLS certificate request was rejected. Check CA configuration.

    The server tried to enroll a CaCom TLS certificate, but the request was not accepted. Typically caused by an incorrect PSK or broken TLS CA policy configuration.

  • Key generation failed.

    Internal error.

  • Unknown key type type.

    Internal error.

  • Failed to aslify public key.

    Internal error.

  • Failed to write file 'private key filename': reason for system error.

Server Messages at Level LOG_NOTICE

  • Terminating upon receipt of a signal.

    Normal shutdown of server. Typically caused by system shutdown or by running the ssh-ca-stop script manually.

  • Terminating upon engine request

  • Terminating.

  • Starting server.

    The server was started in the normal secure mode.

  • Starting server in insecure communication mode.

    The server was started with the server-insecure.conf configuration file, so now it communicates to the Engine without TLS protection.

  • Shutting down services.

  • Starting service type service id service ID as integer.

  • Stopping service type service service ID as integer at port IP port.

  • Restarting server, shutting down all services.

Server Messages at Level LOG_INFO

  • Loaded private key filename.

  • Request for ca-comm TLS certificate pending, next poll in seconds seconds.

  • Failed to read client certificate from 'filename': reason for system error.

  • Wrote new client certificate to file 'filename'.

  • Reconfiguring server.

  • Heartbeat increasing heartbeat number.

  • Started TCP listener at host hostname, port IP port.

  • Assign the first HTTP handler for port port, realm realm.

  • Assign HTTP handler for port port, realm realm.

  • Engine changed the trusted ca-comm CA certificate.

  • Timeout in seconds seconds to enroll new cacomm client certificate.

  • Start to enroll new cacomm client certificate.


PreviousNextUp[Front page] [Index]

===AUTO_SCHEMA_MARKUP===