Bug 208753 - security/openvas-manager: openvasmd startup fails
Summary: security/openvas-manager: openvasmd startup fails
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Tijl Coosemans
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-12 18:47 UTC by kwinkelman
Modified: 2016-04-13 18:46 UTC (History)
0 users

See Also:

Attachments
patch (5.73 KB, patch)
2016-04-12 20:14 UTC, Tijl Coosemans 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description kwinkelman 2016-04-12 18:47:43 UTC 
The openvasmd service from openvas-manager-6.0.8_2 does not start correctly. It fails with a socket bind error (from openvasmd.log):

md   main:WARNING:2016-04-12 17h58.17 utc :1744: Failed to bind manager socket: Invalid argument

This is on 10.3-RELEASE.

Steps to reproduce:

1. Start openvasmd service.
2. Note that service is not running.
Comment 1 Tijl Coosemans freebsd_committer freebsd_triage 2016-04-12 20:14:59 UTC 
Created attachment 169261 [details]
patch

Can you try this patch for security/openvas-manager?
Comment 2 kwinkelman 2016-04-13 13:08:38 UTC 
This solved the issue. The service is now running and listening on the appropriate socket.
Comment 3 commit-hook freebsd_committer freebsd_triage 2016-04-13 18:43:20 UTC 
A commit references this bug:

Author: tijl
Date: Wed Apr 13 18:43:11 UTC 2016
New revision: 413228
URL: https://svnweb.freebsd.org/changeset/ports/413228

Log:
  Add a patch to pass the size of struct sockaddr_in or sockaddr_in6 to
  bind(2) instead of sockaddr_storage.  It doesn't accept the latter even
  though it's big enough.

  PR:		208753
  Tested by:	kwinkelman@mcclatchy.com

Changes:
  head/security/openvas-manager/Makefile
  head/security/openvas-manager/files/patch-src-openvasmd.c