Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 9 subscribers
  • Views 2281 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Linux free version 5.74.0 on Mint 19.3

BerndWille

I encounter a tremendous lot of errors (no 24) "could not open file". This is new after running the program for severals years and I cannot tell what I changed in my system.

 

snippet from file:

Could not open mythes (errno is 24)
Could not open hunspell (errno is 24)
Could not open /home/bernd/wine/dosdevices/z:/var/lib/flatpak/runtime/org.freedesktop.Platform.html5-codecs/x86_64/18.08/active/files/bin/ffmpeg
Could not open /home/bernd/wine/dosdevices/z:/var/lib/flatpak/runtime/org.freedesktop.Platform.html5-codecs/x86_64/18.08/active/files/etc/group
Could not open ssl (errno is 24)
Could not open pkcs11 (errno is 24)
Could not open /home/bernd/wine/dosdevices/z:/var/lib/flatpak/runtime/org.freedesktop.Platform.html5-codecs/x86_64/18.08/active/files/etc/rpc
Could not open profile.d (errno is 24)
Could not open /home/bernd/wine/dosdevices/z:/var/lib/flatpak/runtime/org.freedesktop.Platform.html5-codecs/x86_64/18.08/active/files/etc/passwd
Could not open xdg (errno is 24)
Could not open pulse (errno is 24)
Could not open dbus-1 (errno is 24)
Could not open /home/bernd/wine/dosdevices/z:/var/lib/flatpak/runtime/org.freedesktop.Platform.html5-codecs/x86_64/18.08/active/files/etc/machine-id
Could not open fonts (errno is 24)
Could not open ffmpeg (errno is 24)
Could not open pkgconfig (errno is 24)
Could not open libavdevice (errno is 24)
Could not open libavcodec (errno is 24)

 

Best regards

Bernd



This thread was automatically locked due to age.
Parents
  • 0

    Hello Bernd,

    how is this related to Sophos, are you referring to SAV when saying the program? If so - what is 5.74.0? From where is it?

    Christian

  • 0 in reply to QC

    ~$ savscan -v
    SAVScan virus detection utility
    Copyright (c) 1989-2020 Sophos Limited. All rights reserved.

    System time 12:45:49 PM, System date 03 July 2020

    Product version           : 5.74.0
    Engine version            : 3.79.0
    Virus data version        : 5.76
    User interface version    : 2.03.079
    Platform                  : Linux/AMD64
    Released                  : 23 June 2020
    Total viruses (with IDEs) : 51915882

    Information on additional data files:

    Data file name            : /opt/sophos-av/lib/sav/steal-yj.ide
    Data file type            : IDE
    Data file date            : 26 May 2020, 11:35:34
    Data file status          : Loaded

     

    command line:

    savscan -f -s -nc /home/bernd -exclude /var/lib/flatpack/runtime

    output directed to file the snippet in the first mail was taken from.

    Best regards

    Bernd

  • 0 in reply to BerndWille

    Hello Bernd,

    Product version           : 5.74.0
    I see, never bother to check the version number savscan displays.

    You still get these errors? errno 24 is EMFILE (the per-process limit on the number of open file and message queue descriptors has been reached). Don't think that savscan would suddenly misbehave. might have a hint what the cause could be.

    Christian

  • 0 in reply to BerndWille

    Hi Bernd,

     

    That version is the sweep version, rather than the SAV version, which makes it slightly harder to trace back. (/opt/sophos-av/bin/savdstatus --version to get the SAV version)

     

    Having said that, that looks like the most recent release. It's possible that there is a file descriptor leak in that build, which had fixes for some security issues.

     

    Did the scan earlier have a lot of symlinks it was unable to follow (broken symlinks or lacking permission to follow)?

     

    Thanks,

    Douglas.

Reply
  • 0 in reply to BerndWille

    Hi Bernd,

     

    That version is the sweep version, rather than the SAV version, which makes it slightly harder to trace back. (/opt/sophos-av/bin/savdstatus --version to get the SAV version)

     

    Having said that, that looks like the most recent release. It's possible that there is a file descriptor leak in that build, which had fixes for some security issues.

     

    Did the scan earlier have a lot of symlinks it was unable to follow (broken symlinks or lacking permission to follow)?

     

    Thanks,

    Douglas.

Children
Unfiltered HTML