To stay updated on your favorite discussions, please create an account or log in. Then, click the Bookmark icon to subscribe and receive notifications.

Activation of WithSecure Linux Security 64 breaks on Ubuntu

john_dashwood
john_dashwood W/ Member Posts: 4 Security Scout

During activation occures info:

flock: 1.000

flock: 1.000 and so on,

incorrect time interval value 1.000 and activation stops.

Dependencies: libc6, libgcc1, libcurl6, python are present in the system - Ubuntu 20.04.06 LTS or Ubuntu 22.04 LTS. However, Linux Security 64 is activated and connected with proper computer in the WithSecure Elements portal but not in the computer.

Re-activation results in info:

activation impossible due to lack of free seats.

Tagged:

Answers

  • Sethu Laks
    Sethu Laks W/ Partner, W/ Staff, W/ Moderator Posts: 220 Moderator

    Hi @john_dashwood

    Thank you for reaching out the WithSecure Community,

    May I ask you to uninstall the Linux Security64 as instructed here?

    Re-install the following dependencies.

    • Ubuntu 20.04: libcurl4, python3
    • Ubuntu 22.04: libcurl4, python3

    You can now check again, if the issue remains, please share with us the full error message during installation/activation of Linux Security64.

    Best regards,
    Sethu
    Community Moderator | Technical Support Engineer
    WithSecure™ https://www.withsecure.com/en/home

  • john_dashwood
    john_dashwood W/ Member Posts: 4 Security Scout

    Here are my actions:

    reinstallation of Ubuntu 20.04.06 LTS

    python3 -reinstalled 3.8.2-0ubuntu2
    libcurl4 -installed 7.68.0-1ubuntu2.21
    libc6 -updated 2.31-0ubuntu9.14
    libgcc1 -installed 1:10.5.0-1ubuntu1~20.04 .

    1. New installation system answers (system answers in Polish - translated into English):

    sudo dpkg -i f-secure-linuxsecurity.deb

    [sudo] user's password :

    Chosing earlier non-selected packet f-secure-linuxsecurity.
    (Reading the database ... 195194 files and directories actually installed.)
    Preparing to unpacking of f-secure-linuxsecurity.deb ...
    Unpacking of f-secure-linuxsecurity (12.0.54-1) ...
    Configuring of f-secure-linuxsecurity (12.0.54-1) ...

    2. New activation system answers (system answers in Polish - translated into English):

    sudo /opt/f-secure/linuxsecurity/bin/activate --psb --subscription-key ***********************************

    Unfinished WithSecure Linux Security 64 activation found. Restarting activation.

    Installing WithSecure Linux Security 64
    flock: incorrect limit time value: '1.000'
    flock: incorrect limit time value: '1.000'
    flock: incorrect limit time value: '1.000'
    flock: incorrect limit time value: '1.000'
    flock: incorrect limit time value: '1.000'
    setup: timed out on waiting for channel update configuration
    2024-03-26 21:15:06 src/fsbootstrap.c:446[7] executing '/opt/f-secure/linuxsecurity/download/linuxsecurity-1200-linux-x86_64/1710768478/content/setup' failed, result 256
    2024-03-26 21:15:06 src/fsbootstrap.c:209[7] install failed
    activate: activation failed: exit status 2.

    Content of /var/opt/f-secure/fsbg/setup logs for the next attempt of installation and activation that has ended the same way as upper:

    setup-mgmt.log:

    2024-03-26 21:52:18.910822: Unconfigured mode set
    2024-03-26 21:52:25.998814: Registration of default subscription completed
    2024-03-26 21:52:26.064816: psb mode configured
    2024-03-26 21:52:26.074666: Stop fsbg-pmd
    2024-03-26 21:52:26.085118: Restart fsma2
    2024-03-26 21:52:26.248105: Start fsbg-pmd
    2024-03-26 21:52:26.770301: Services restarted

    setup-registry.log

    2024-03-26 21:52:19.213468: Adding new server fsbg
    2024-03-26 21:52:19.284844: Adding new server databases
    2024-03-26 21:52:19.336849: Adding new server production
    2024-03-26 21:52:19.430869: Adding new channel fsbg
    2024-03-26 21:52:19.482961: Adding new channel hydra
    2024-03-26 21:52:19.537620: Adding new channel aquarius
    2024-03-26 21:52:19.590599: Adding new channel fmlib
    2024-03-26 21:52:19.642322: Adding new channel antispam
    2024-03-26 21:52:19.693827: Adding new channel cram
    2024-03-26 21:52:19.747229: Adding new channel famp
    2024-03-26 21:52:19.801017: Adding new channel sensor
    2024-03-26 21:52:19.856693: Adding new channel sensor-db
    2024-03-26 21:52:19.908670: Adding new channel pinned-certificates
    2024-03-26 21:52:22.320542: Adding new server linuxsecurity
    2024-03-26 21:52:22.371167: Adding new channel linuxsecurity
    2024-03-26 21:52:22.472106: Adding new product 1007.

    dpkg.log removing and installing -f-secure-linuxsecurity

    2024-03-26 21:45:55 startup packages remove
    2024-03-26 21:45:55 status installed f-secure-linuxsecurity:amd64 12.0.54-1
    2024-03-26 21:45:56 remove f-secure-linuxsecurity:amd64 12.0.54-1 <brak>
    2024-03-26 21:45:56 status half-configured f-secure-linuxsecurity:amd64 12.0.54-1
    2024-03-26 21:45:56 status half-installed f-secure-linuxsecurity:amd64 12.0.54-1
    2024-03-26 21:45:56 status config-files f-secure-linuxsecurity:amd64 12.0.54-1
    2024-03-26 21:45:56 status not-installed f-secure-linuxsecurity:amd64 <brak>
    2024-03-26 21:49:21 startup archives install
    2024-03-26 21:49:21 install f-secure-linuxsecurity:amd64 <brak> 12.0.54-1
    2024-03-26 21:49:21 status half-installed f-secure-linuxsecurity:amd64 12.0.54-1
    2024-03-26 21:49:22 status unpacked f-secure-linuxsecurity:amd64 12.0.54-1
    2024-03-26 21:49:22 configure f-secure-linuxsecurity:amd64 12.0.54-1 12.0.54-1
    2024-03-26 21:49:22 status half-configured f-secure-linuxsecurity:amd64 12.0.54-1
    2024-03-26 21:49:22 status installed f-secure-linuxsecurity:amd64 12.0.54-1

    And this is a part of syslog presenting last actions of system before stopping activation:

    Mar 26 21:52:26 (name) fsma2: started
    Mar 26 21:52:26 (name) systemd[1]: Started F-Secure Management Agent 2.
    Mar 26 21:52:26 (name) systemd[1]: Started F-Secure BaseGuard status update manager.
    Mar 26 21:52:26 (name) systemd[1]: Starting F-Secure BaseGuard daemon...
    Mar 26 21:52:26 (name) systemd[1]: Stopping F-Secure BaseGuard update manager...
    Mar 26 21:52:26 (name) systemd[1]: fsbg-updated.service: Succeeded.
    Mar 26 21:52:26 (name) systemd[1]: Stopped F-Secure BaseGuard update manager.
    Mar 26 21:52:26 (name) systemd[1]: Starting F-Secure BaseGuard update manager...
    Mar 26 21:52:26 (name) fsbg-updated[24335]: regime: on_arrival
    Mar 26 21:52:26 (name) fsbg-updated[24335]: schedule:
    Mar 26 21:52:26 (name) fsbg-updated[24335]: periodic checking of updates disabled
    Mar 26 21:52:26 (name) systemd[1]: Started F-Secure BaseGuard update manager.
    Mar 26 21:52:26 (name) fsbg-updated[24335]: update at 1711489946
    Mar 26 21:52:26 (name) fsbg-updated[24336]: running /opt/f-secure/fsbg/bin/install-updates --all
    Mar 26 21:52:26 (name) fsbg-updated[24336]: command /opt/f-secure/fsbg/bin/install-updates --all exited with status 0
    Mar 26 21:52:26 (name) fsbg-updated[24336]: running /opt/f-secure/fsbg/bin/admin-notify --flush
    Mar 26 21:52:26 (name) systemd[1]: Started F-Secure BaseGuard daemon.
    Mar 26 21:52:26 (name) fsbg-updated[24336]: command /opt/f-secure/fsbg/bin/admin-notify --flush exited with status 0
    Mar 26 21:52:26 (name) fsbg-updated[24336]: running /opt/f-secure/fsbg/bin/admin-notify --flush
    Mar 26 21:52:26 (name) fsbg-updated[24336]: command /opt/f-secure/fsbg/bin/admin-notify --flush exited with status 0
    Mar 26 21:52:27 (name) fsma2_start[24317]: cosmos download failure (404)

    (End of system actions).

    Best regards

    Janusz (@john_dashwood)

  • Sethu Laks
    Sethu Laks W/ Partner, W/ Staff, W/ Moderator Posts: 220 Moderator

    Hi @john_dashwood

    The issue stems from a bug in our handling of locales. To resolve this, please include the definition of the environment variable LC_ALL=C as part of the installation command. This adjustment will ensure proper functionality.

    Setting the LC_ALL environment variable to C can indeed provide a workaround for such issues. Here’s how you can define it as part of the install command:

    LC_ALL=C [your_install_command]
    
    

    Replace [your_install_command] with the actual command you use for installation. This will set the locale to the default “C” locale, which should help avoid any locale-specific parsing issues with the flock command.

    Best regards,
    Sethu
    Community Moderator | Technical Support Engineer
    WithSecure™ https://www.withsecure.com/en/home

  • john_dashwood
    john_dashwood W/ Member Posts: 4 Security Scout

    I am very sorry, but that does not help.

    The result of actions is still the same. I would like to draw you attention to the command:

    2024-03-28 15:15:16 src/fsbootstrap.c:446[7] executing '/opt/f-secure/linuxsecurity/download/linuxsecurity-1200-linux-x86_64/1710768478/content/setup' failed, result 256.

    I tried to start file 'setup' 'manually' with command:

    'computer':/opt/f-secure/linuxsecurity/download/linuxsecurity-1200-linux-x86_64/1710768478/content$ sudo ./setup --profile-id ********* install

    and the answer was:
    setup: both --config-dir and --license-file missing.

    It is impossible to continue the activation because WithSecure portal does not deliver 'confgi-dir' and 'licence-file' to the 'setup' file in computer, I think.

    Moreover, I found in syslog that:

    Mar 28 15:15:04 'computer' fsma2_start[11702]: cosmos download failure (404)
    Mar 28 15:15:22 'computer' fsma2_start[11702]: cosmos download success (200).

    And it was the last action of WithSecure app.

    Best regards

    Janusz

  • Sethu Laks
    Sethu Laks W/ Partner, W/ Staff, W/ Moderator Posts: 220 Moderator

    Hi @john_dashwood

    Thank you for trying out the provided steps. In order to identify the root causes of the issue, we need to analyze the full fsdiag logs. Our support team is available to assist you with this. Please download fsdiag tool here and create a fsdiag log and submit it to our support request here https://www.withsecure.com/en/support/contact-support/email-support .

    Best regards,
    Sethu
    Community Moderator | Technical Support Engineer
    WithSecure™ https://www.withsecure.com/en/home

  • john_dashwood
    john_dashwood W/ Member Posts: 4 Security Scout

    Hello,

    Running file wsdiag in directory fsdiag is impossible. I have run command /opt/f-secure/linuxsecurity/bin/fsdiag.sh.

    Before I send you the logs, I will make some comments.

    Formerly, I successfully installed LinuxSecurity on Kubuntu 22.04 LTS at the end of January 2024. Yet I had to start the process of activation two or three times because of connection problems which origins were unknown to me. I checked that address "https://doorman.sc.fsapi.com/doorman/v1/healthcheck" is inaccessible in a browser on Kubuntu, Ubuntu, nor Windows 10 or Android 13.

    Linuxsecurity worked good but I observed that local application does not carry out some commands from Withsecure portal. On the other hand, scanning started this way consumed much of processor power in contrast to the proces initiated locally.

    That is why I wanted to reinstall Linuxsecurity in March. To my surprise, appeared a problem with "flock". Then, I reinstalled system into Ubuntu 20.04.06 LTS but the problem did not disappear.

    Running command "sudo LC_ALL=C dpkg -i f-secure-linuxsecurity.deb" does not result in setting LC_ALL=C. When I run command: sudo update_locale LC_ALL=C the locale was really changed but then I could not open the terminal.

    To summarize some files delivered to local app by Withsecure portal must have changed slightly within the space of the last two months, in my opinion.

    Best regards,

    Janusz

  • Sethu Laks
    Sethu Laks W/ Partner, W/ Staff, W/ Moderator Posts: 220 Moderator
    edited April 2

    Hi @john_dashwood

    Please be aware that Kubuntu 22.04 LTS is not officially tested or supported by our R&D team.
    Could you please try running the command in the following format?
    For example,

    LC_ALL=C sudo dpkg -i f-secure-linuxsecurity.deb
    
    or 
    
    sudo LC_ALL=C bash f-secure-linuxsecurity-installer
    

    If the issue persists, check the language settings on your machine by executing the following commands:

    export LC_ALL=C
    printenv | grep LANG

    For standalone fsdiag logs, you will need to download the standalone fsdiag logs from here.
    Once downloaded, unzip the fsdiag.zip to access the wsdiag tool. You can use the bash command to run the wsdiag tool:


    For example,

    bash wsdiag
    

    After running the command, please allow a few minutes for the wsdiag.12XXXX.tar file to be generated. You can find this file in the directory /tmp/wsdiag.12XXXX.

    Having said that, we can see you have already created support ticket with this reference 05XX4139. We will share more information via support ticket.

    Best regards,
    Sethu
    Community Moderator | Technical Support Engineer
    WithSecure™  https://community.withsecure.com/home/leaving?allowTrusted=1&target=https%3A%2F%2Fwww.withsecure.com%2Fen%2Fhome