On Thu, Aug 25, 2016 at 08:51:40AM +0200, Arturo Borrero Gonzalez wrote:
> On 25 August 2016 at 08:14, Marc Haber <mh+debian-packa...@zugschlus.de>
> wrote:
> > Package: conntrackd
> > Version: 1:1.4.4-1
> > Severity: important
> >
> > Hi,
> >
> > installing/upgrading conntrackd on my system runs into a time-out and
> > leaves the package half-installed:
> >
>
> Could you please paste your conntrackd.conf file?
As the issue remains after purge + reinstall, you can look into the
package for my configuration.
> > This is an RC bug as soon as it is clear that I am not the only
> > affected user.
> >
>
> I don't agree. The problem is probably a missing option in conntrackd.conf
> file.
If it's missing, it's missing in the package. In this case, the
software should give an error message.
[1/501]mh@swivel:~$ sudo apt install conntrackd
[sudo] password for mh on swivel:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
conntrackd
0 upgraded, 1 newly installed, 0 to remove and 19 not upgraded.
Need to get 0 B/105 kB of archives.
After this operation, 305 kB of additional disk space will be used.
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Selecting previously unselected package conntrackd.
(Reading database ... 366846 files and directories currently installed.)
Preparing to unpack .../conntrackd_1%3a1.4.4-1_amd64.deb ...
Unpacking conntrackd (1:1.4.4-1) ...
Processing triggers for systemd (231-4) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up conntrackd (1:1.4.4-1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/conntrackd.service
→ /lib/systemd/system/conntrackd.service.
Job for conntrackd.service failed because a timeout was exceeded.
See "systemctl status conntrackd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript conntrackd, action "start" failed.
● conntrackd.service - Conntrack Daemon
Loaded: loaded (/lib/systemd/system/conntrackd.service; enabled; vendor
preset: enabled)
Active: failed (Result: timeout) since Thu 2016-08-25 09:19:56 CEST; 5ms ago
Process: 8316 ExecStart=/usr/sbin/conntrackd -C $CONFIG $OPTIONS
(code=exited, status=0/SUCCESS)
Main PID: 8316 (code=exited, status=0/SUCCESS)
Aug 25 09:18:26 swivel systemd[1]: Starting Conntrack Daemon...
Aug 25 09:18:26 swivel conntrack-tools[8316]: using user-space event filtering
Aug 25 09:18:26 swivel conntrack-tools[8316]: netlink event socket buffer si...s
Aug 25 09:18:26 swivel conntrack-tools[8316]: initialization completed
Aug 25 09:18:26 swivel conntrack-tools[8316]: -- starting in console mode --
Aug 25 09:19:56 swivel systemd[1]: conntrackd.service: Start operation time...g.
Aug 25 09:19:56 swivel systemd[1]: Failed to start Conntrack Daemon.
Aug 25 09:19:56 swivel systemd[1]: conntrackd.service: Unit entered failed ...e.
Aug 25 09:19:56 swivel systemd[1]: conntrackd.service: Failed with result '...'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package conntrackd (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (231-4) ...
Errors were encountered while processing:
conntrackd
E: Sub-process /usr/bin/dpkg returned an error code (1)
[2/502]mh@swivel:~$ cat /etc/conntrackd/conntrackd.conf
#
# General settings
#
General {
#
# Number of buckets in the caches: hash table
#
HashSize 8192
#
# Maximum number of conntracks:
# it must be >= $ cat /proc/sys/net/ipv4/netfilter/ip_conntrack_max
#
HashLimit 65535
#
# Logfile: on (/var/log/conntrackd.log), off, or a filename
# Default: off
#
#LogFile on
#
# Syslog: on, off or a facility name (daemon (default) or local0..7)
# Default: off
#
Syslog on
#
# Lockfile
#
LockFile /var/lock/conntrackd.lock
#
# Unix socket configuration
#
UNIX {
Path /var/run/conntrackd.sock
Backlog 20
}
#
# Netlink socket buffer size
#
SocketBufferSize 262142
#
# Increase the socket buffer up to maximun if required
#
SocketBufferSizeMaxGrown 655355
#
# Event filtering: This clause allows you to filter certain traffic,
# There are currently three filter-sets: Protocol, Address and
# State. The filter is attached to an action that can be: Accept or
# Ignore. Thus, you can define the event filtering policy of the
# filter-sets in positive or negative logic depending on your needs.
#
Filter {
#
# Accept only certain protocols: You may want to log the
# state of flows depending on their layer 4 protocol.
#
Protocol Accept {
TCP
}
#
# Ignore traffic for a certain set of IP's.
#
Address Ignore {
IPv4_address 127.0.0.1 # loopback
}
#
# Uncomment this line below if you want to filter by flow state.
# The existing TCP states are: SYN_SENT, SYN_RECV, ESTABLISHED,
# FIN_WAIT, CLOSE_WAIT, LAST_ACK, TIME_WAIT, CLOSED, LISTEN.
#
# State Accept {
# ESTABLISHED CLOSED TIME_WAIT CLOSE_WAIT for TCP
# }
}
}
Stats {
#
# If you enable this option, the daemon writes the information about
# destroyed connections to a logfile. Default is off.
# Logfile: on, off, or a filename
# Default file: (/var/log/conntrackd-stats.log)
#
LogFile on
#
# Enable connection logging via Syslog. Default is off.
# Syslog: on, off or a facility name (daemon (default) or local0..7)
# If you set the facility, use the same as in the General clause,
# otherwise you'll get a warning message.
#
#Syslog on
}
[3/503]mh@swivel:~$
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
