Hi Clint. Thanks for your answer.
I spent all the afternoon checking my configuration and starting racoon
manually. And indeed there was an IP that wasn't answering properly but
now it's fixed.
I've just seen your message and tried the script at init.d again and it
printed the "." and the newline. So the problem was probably, as you
said, that my wrong configuration prevented racoon to start.
Testing it further, if I do "/etc/init.d/racoon start" twice, the first
time the daemon will start and will print the new line. The second time
it will fail because it's already running, but no error message is given
and no newline will be printed. The problem seems to be in the --quiet
option passed to start-stop-daemon. If I remove it I get:
elo...@tangamandapio-laptop:~$ sudo /etc/init.d/racoon start
Starting IKE (ISAKMP/Oakley) server: racoon/usr/sbin/racoon already running.
elo...@tangamandapio-laptop:~$
The script seems to be assuming that the error, the "." and the newline
will be printed by start-stop-daemon, but the --quiet option prevents
it.
Now, the quiet option is probably there for some reason, and I'm not
sure if it's a bug. So I don't know what's next :)
Thanks again,
pura vida.
** Changed in: ipsec-tools (Ubuntu)
Status: Incomplete => New
** Summary changed:
- Racoon daemon script is missing a newline
+ if racoon daemon fails to start no error message is printed and newline is
missing
--
if racoon daemon fails to start no error message is printed and newline is
missing
https://bugs.launchpad.net/bugs/606375
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ipsec-tools in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
