[FAILED] failed to start LSB: havp virus-scanning HTTP proxy

Asked by michael

[FAILED] failed to start LSB: havp virus-scanning HTTP proxy
I get this error on boot. Googled it, found one answer. Tried their commands.

michael@michael-Inspiron-620:~$ sudo systemctl status vmware.service
Unit vmware.service could not be found.
michael@michael-Inspiron-620:~$ sudo /etc/init.d/vmware status
sudo: /etc/init.d/vmware: command not found
michael@michael-Inspiron-620:~$ sudo /etc/init.d/vmware start
sudo: /etc/init.d/vmware: command not found
michael@michael-Inspiron-620:~$ uname -r
5.19.0-38-generic
michael@michael-Inspiron-620:~$ vmware --version
vmware: command not found
michael@michael-Inspiron-620:~$

If I don't have vmware, why do I get this error?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Manfred Hampl
Solved:
Last query:
Last reply:
Revision history for this message
michael (yellupcm-gmail) said :
#1

Ubuntu 22.04

Revision history for this message
Manfred Hampl (m-hampl) said :
#2

What output do you receive for the following commands:

uname -a
lsb_release -crid
apt policy havp
systemctl --no-pager --full status havp.service

Revision history for this message
michael (yellupcm-gmail) said :
#3

michael@michael-Inspiron-620:~$ uname -a
Linux michael-Inspiron-620 5.19.0-38-generic #39~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 17 21:16:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
michael@michael-Inspiron-620:~$ lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 22.04.2 LTS
Release: 22.04
Codename: jammy
michael@michael-Inspiron-620:~$ apt policy havp
havp:
  Installed: 0.93-2build1
  Candidate: 0.93-2build1
  Version table:
 *** 0.93-2build1 500
        500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
        100 /var/lib/dpkg/status
michael@michael-Inspiron-620:~$ systemctl --no-pager --full status havp.service
× havp.service - LSB: HAVP virus-scanning HTTP proxy
     Loaded: loaded (/etc/init.d/havp; generated)
     Active: failed (Result: exit-code) since Sat 2023-04-22 10:18:01 EDT; 47min ago
       Docs: man:systemd-sysv-generator(8)
    Process: 1591 ExecStart=/etc/init.d/havp start (code=exited, status=1/FAILURE)
        CPU: 28ms

Apr 22 10:18:01 michael-Inspiron-620 havp[1591]: Mounting /var/lib/havp/havp.loop under /var/spool/havp ...done
Apr 22 10:18:01 michael-Inspiron-620 havp[1591]: Cleaning up /var/spool/havp... done
Apr 22 10:18:01 michael-Inspiron-620 havp[1591]: Starting havp:
Apr 22 10:18:01 michael-Inspiron-620 havp[1676]: Starting HAVP Version: 0.93
Apr 22 10:18:01 michael-Inspiron-620 havp[1702]: Filesystem not supporting mandatory locks!
Apr 22 10:18:01 michael-Inspiron-620 havp[1702]: On Linux, you need to mount filesystem with "-o mand"
Apr 22 10:18:01 michael-Inspiron-620 havp[1676]: Exiting..
Apr 22 10:18:01 michael-Inspiron-620 systemd[1]: havp.service: Control process exited, code=exited, status=1/FAILURE
Apr 22 10:18:01 michael-Inspiron-620 systemd[1]: havp.service: Failed with result 'exit-code'.
Apr 22 10:18:01 michael-Inspiron-620 systemd[1]: Failed to start LSB: HAVP virus-scanning HTTP proxy.
michael@michael-Inspiron-620:~$

Revision history for this message
Manfred Hampl (m-hampl) said :
#4

I do not know any details about HAVP, but it seems to complain that one of your file systems lacks a feature that havp needs for its function.

see https://forum.howtoforge.com/threads/mount-filesystem-for-havp.28324/

What's in your fstab file?

Revision history for this message
michael (yellupcm-gmail) said :
#5

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during installation
UUID=739fe4ae-11cd-4359-b8f7-bf1de62e2934 / ext4 errors=remount-ro 0 1
/swapfile none swap sw 0 0

Revision history for this message
Manfred Hampl (m-hampl) said :
#6

if I interpret https://forum.howtoforge.com/threads/mount-filesystem-for-havp.28324/ correctly, then you should edit the /etc/fstab file and change
... / ext4 errors=remount-ro 0 1
to
... / ext4 mand,errors=remount-ro 0 1
and with the next boot the message should not be shown any more and havp should run.

Remarks:
I do not know what side effects that change may have.
You should make sure that you have a working Ubuntu installer device at hand, such that you can boot into "try Ubuntu without installing" mode to be able to revert the change, in case that it has the effect that the system does not boot any more.
Are you sure that you want/need havp running?

Revision history for this message
michael (yellupcm-gmail) said :
#7

Manfred

Are you sure that you want/need havp running? Your statement.

I know of no reason, I need it running. The only reason, I would want it running, is to remove error on boot. Is there any way to just remove the error on boot? If not, I will leave it alone, and the error will be just part of boot up.

Revision history for this message
Best Manfred Hampl (m-hampl) said :
#8

I see four possibilities for coping with the error message:

1. Deinstall havp (if havp is not installed, then it will not run into the error).

2. Disable the havp.service process (if havp is not trying to start, then it will not run into the error).
You have to be aware, that a version upgrade may automatically re-enable it and the error message may then come back.

3. Set the fstab option

4. Leave it as it is.

Revision history for this message
michael (yellupcm-gmail) said :
#9

Manfred

michael@michael-Inspiron-620:~$ sudo apt remove havp
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'havp' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
michael@michael-Inspiron-620:~$

This solved my problem!
Thank You

Revision history for this message
michael (yellupcm-gmail) said :
#10

Thanks Manfred Hampl, that solved my question.