From: Pablo Florencio <pabloflorencio@cica.es>
To: netfilter@vger.kernel.org
Subject: conntrackd daemon stops: is conntrackd running?
Date: Mon, 12 May 2008 14:32:42 +0200 [thread overview]
Message-ID: <482838EA.7080003@cica.es> (raw)
[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]
Hi to everyone.
First of all, I apologize for my english.
I have installed conntrackd in my high availability firewall cluster and
I found one problem that I can't resolve. The installation was ok, I
used Heartbeat instead of Keepalived for set up the virtual ips and the
conntrackd script and it seems to work fine- I have checked that both
nodes can dump the internal and external cache correctly.
The problem comes when tried to use conntrackd a few minutes later since
the daemon has started, for example, if I want to dump statistics
collected by daemon I found this error message:
>conntrackd -s
>can't connect: is conntrackd running? appropriate permissions?
The commands -c -f -R -k, etc, give the same result. If I try to restart
the dameon I get this message:
>conntrackd -d
>lockfile `/var/lock/conntrack.lock' exists, perhaps conntrackd already
running?
If I look for the conntrackd process ( ps -ef | grep conntrackd ) I
found that it has disappear, so I have to delete the .lock file to be
able to start ir again.
Is there any problem using heartbeat instead of keepalived? I can see it
working fine for a few minutes but after that I mysteriously found this
error in both nodes.
Any help or ideas would be very much appreciated.
Regards
Pablo Florencio.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3881 bytes --]
next reply other threads:[~2008-05-12 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 12:32 Pablo Florencio [this message]
2008-05-12 14:16 ` conntrackd daemon stops: is conntrackd running? Maximilian Wilhelm
2008-05-15 14:07 ` Pablo Neira Ayuso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=482838EA.7080003@cica.es \
--to=pabloflorencio@cica.es \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.