Jump to content

Maksim Y

Members
  • Posts

    1
  • Joined

  • Last visited

Posts posted by Maksim Y

  1. Добрый день, установил на Debian 10 KES14. Инсталлирую Kaspersky Security Center 14 Web Console Linux после установки нет доступа к web интерфейсу.

    Выбор ранее не выбранного пакета ksc-web-console.
    (Чтение базы данных … на данный момент установлено 188659 файлов и каталогов.)
    Подготовка к распаковке ksc-web-console-14.0.1330.x86_64.deb …
    Распаковывается ksc-web-console (14.0.1330) …
    Настраивается пакет ksc-web-console (14.0.1330) …
    Create sanitized environment...
    Installer started on default branch
    Installer config params {
    address: '192.168.0.7',
    port: 8080,
    defaultLangId: 1049,
    enableLog: false,
    trusted: '192.168.0.7|13299|/var/opt/kaspersky/klnagent_srv/1093/cert/klserver.cer|KSC Server',
    acceptEula: true,
    certPath: '/var/opt/kaspersky/klnagent_srv/1093/cert/klserver.cer',
    webConsoleAccount: 'kladmins:ksc',
    managementServiceAccount: 'kladmins:ksc'
    }
    ON INSTALL: Try to call on uninstall sequence
    Stop and remove Web console services: start
    Daemon KSCWebConsoleManagement is already unregistered
    Daemon KSCWebConsolePlugin is already unregistered
    Daemon KSCWebConsole is already unregistered
    Daemon KSCSvcWebConsole is already unregistered
    Daemon KSCWebConsoleMessageQueue is already unregistered
    Stop and remove Web console services: successfully finished
    Remove KL service users: start
    Remove KL service users: successfully finished
    ON INSTALL: On uninstall sequence finished successful
    Patch config: start
    crtPath=/var/opt/kaspersky/klnagent_srv/1093/cert/klserver.cer; keyPath=undefined.
    Required parameters for custom certificates set up was not passed.
    Skip custom certificate update
    Patch config: successfully finished
    Patch Management Service config: start
    Patch Management Service config: successfully finished
    Generate certificates: start
    Start vault
    Vault started successfully
    Error: connect ECONNREFUSED 127.0.0.1:8200
    ==> Vault server configuration:
    
    Cgo: disabled
    Go Version: go1.18
    
    Listener 1: tcp (addr: "127.0.0.1:8200", cluster address: "127.0.0.1:8201", max_request_duration: "1m30s", max_request_size: "33554432", tls: "disabled")
    Log Level: info
    Mlock: supported: true, enabled: false
    Recovery Mode: false
    Storage: inmem
    Version: Vault v1.9.3
    
    ==> Vault server started! Log data will stream in below:
    
    
    2022-10-05T21:31:04.904+0500 [INFO] proxy environment: http_proxy="\"\"" https_proxy="\"\"" no_proxy="\"\""
    2022-10-05T21:31:04.904+0500 [WARN] no `api_addr` value specified in config or in VAULT_API_ADDR; falling back to detection if possible, but this value should be manually set
    2022-10-05T21:31:04.905+0500 [INFO] core: Initializing VersionTimestamps for core
    
    2022-10-05T21:31:14.849+0500 [INFO] core: security barrier not initialized
    
    2022-10-05T21:31:14.850+0500 [INFO] core: security barrier initialized: stored=1 shares=1 threshold=1
    2022-10-05T21:31:14.851+0500 [INFO] core: post-unseal setup starting
    
    2022-10-05T21:31:14.864+0500 [INFO] core: loaded wrapping token key
    
    2022-10-05T21:31:14.865+0500 [INFO] core: Recorded vault version: vault version=1.9.3 upgrade time="2022-10-05 21:31:14.864944478 +0500 +05 m=+10.105080492"
    2022-10-05T21:31:14.865+0500 [INFO] core: successfully setup plugin catalog: plugin-directory="\"\""
    2022-10-05T21:31:14.865+0500 [INFO] core: no mounts; adding default mount table
    
    2022-10-05T21:31:14.869+0500 [INFO] core: successfully mounted backend: type=cubbyhole path=cubbyhole/
    
    2022-10-05T21:31:14.870+0500 [INFO] core: successfully mounted backend: type=system path=sys/
    
    2022-10-05T21:31:14.871+0500 [INFO] core: successfully mounted backend: type=identity path=identity/
    
    2022-10-05T21:31:14.876+0500 [INFO] core: successfully enabled credential backend: type=token path=token/
    2022-10-05T21:31:14.877+0500 [INFO] rollback: starting rollback manager
    2022-10-05T21:31:14.879+0500 [INFO] core: restoring leases
    2022-10-05T21:31:14.880+0500 [INFO] expiration: lease restore complete
    2022-10-05T21:31:14.885+0500 [INFO] identity: entities restored
    
    2022-10-05T21:31:14.905+0500 [INFO] identity: groups restored
    
    2022-10-05T21:31:14.906+0500 [INFO] core: post-unseal setup complete
    
    2022-10-05T21:31:14.907+0500 [INFO] core: usage gauge collection is disabled
    
    2022-10-05T21:31:14.908+0500 [INFO] core: root token generated
    2022-10-05T21:31:14.908+0500 [INFO] core: pre-seal teardown starting
    
    2022-10-05T21:31:14.909+0500 [INFO] rollback: stopping rollback manager
    
    2022-10-05T21:31:14.909+0500 [INFO] core: pre-seal teardown complete
    
    2022-10-05T21:31:14.934+0500 [INFO] core.cluster-listener.tcp: starting listener: listener_address=127.0.0.1:8201
    2022-10-05T21:31:14.934+0500 [INFO] core.cluster-listener: serving cluster requests: cluster_listen_address=127.0.0.1:8201
    2022-10-05T21:31:14.934+0500 [INFO] core: post-unseal setup starting
    2022-10-05T21:31:14.934+0500 [INFO] core: loaded wrapping token key
    2022-10-05T21:31:14.935+0500 [INFO] core: successfully setup plugin catalog: plugin-directory="\"\""
    2022-10-05T21:31:14.944+0500 [INFO] core: successfully mounted backend: type=system path=sys/
    
    2022-10-05T21:31:14.946+0500 [INFO] core: successfully mounted backend: type=identity path=identity/
    2022-10-05T21:31:14.946+0500 [INFO] core: successfully mounted backend: type=cubbyhole path=cubbyhole/
    
    2022-10-05T21:31:14.952+0500 [INFO] core: successfully enabled credential backend: type=token path=token/
    
    2022-10-05T21:31:14.953+0500 [INFO] rollback: starting rollback manager
    
    2022-10-05T21:31:14.956+0500 [INFO] core: restoring leases
    
    2022-10-05T21:31:14.961+0500 [INFO] expiration: lease restore complete
    
    2022-10-05T21:31:14.963+0500 [INFO] identity: entities restored
    2022-10-05T21:31:14.963+0500 [INFO] identity: groups restored
    2022-10-05T21:31:14.963+0500 [INFO] core: post-unseal setup complete
    2022-10-05T21:31:14.963+0500 [INFO] core: vault is unsealed
    2022-10-05T21:31:14.964+0500 [INFO] core: usage gauge collection is disabled
    
    Vault is up. Starting operations
    Mounting PKI
    2022-10-05T21:31:14.988+0500 [INFO] core: successful mount: namespace="\"\"" path=kl/ type=pki
    
    Writing URL configs
    Creating "nsq-server" role
    Creating "web-server" role
    Creating "plugin" role
    Creating "utilility" role
    Generating Root CA
    Generating nsq-server certificates
    Generating plugin certificates
    Generating utilility certificates
    Generating web-server certificates
    All operations are finished successfully.
    Generate certificates: successfully finished
    Generate keys: start
    ==> Vault shutdown triggered
    
    2022-10-05T21:31:26.476+0500 [INFO] core: marked as sealed
    2022-10-05T21:31:26.476+0500 [INFO] core: pre-seal teardown starting
    2022-10-05T21:31:26.476+0500 [INFO] rollback: stopping rollback manager
    2022-10-05T21:31:26.477+0500 [INFO] core: pre-seal teardown complete
    2022-10-05T21:31:26.477+0500 [INFO] core: stopping cluster listeners
    2022-10-05T21:31:26.477+0500 [INFO] core.cluster-listener: forwarding rpc listeners stopped
    
    2022-10-05T21:31:26.973+0500 [INFO] core.cluster-listener: rpc listeners successfully shut down
    2022-10-05T21:31:26.973+0500 [INFO] core: cluster listeners successfully shut down
    
    2022-10-05T21:31:26.973+0500 [INFO] core: vault is sealed
    
    Generate keys: successfully finished
    Register users: start
    Register users: successfully finished
    Grant user rights to nwc folder: start
    Grant user rights to nwc folder: successfully finished
    Setup infrastructure: start
    Setup infrastructure: successfully finished
    Start services: start
    Start services: successfully finished

     

×
×
  • Create New...