By rising the log level, at the boot I find these diagnostics messages in /var/log/daemon:
May 14 09:59:24 g1s maradns.etc_maradns_mararc: Adding root nameserver icann for zone . May 14 09:59:24 g1s maradns.etc_maradns_mararc: Log: Root directory changed May 14 09:59:24 g1s maradns.etc_maradns_mararc: Log: Binding to address 127.0.0.1 May 14 09:59:24 g1s maradns.etc_maradns_mararc: Log: Socket opened on UDP port 53 May 14 09:59:24 g1s maradns.etc_maradns_mararc: Log: Root privileges dropped May 14 09:59:24 g1s maradns.etc_maradns_mararc: Log: All RRs have been loaded May 14 09:59:24 g1s maradns.etc_maradns_mararc: Log: Awaiting data on port 53 I can confirm these are the messages sent to the syslog system at the very boot. It seems that the daemon is started and then dies somehow. At the end of the boot I start maradns manually with "sudo /etc/init.d/maradns start" and I found exactly the very same lines in the logs but the last line: May 14 10:05:02 g1s maradns.etc_maradns_mararc: Adding root nameserver icann for zone . May 14 10:05:02 g1s maradns.etc_maradns_mararc: Log: Root directory changed May 14 10:05:02 g1s maradns.etc_maradns_mararc: Log: Binding to address 127.0.0.1 May 14 10:05:02 g1s maradns.etc_maradns_mararc: Log: Socket opened on UDP port 53 May 14 10:05:02 g1s maradns.etc_maradns_mararc: Log: Root privileges dropped May 14 10:05:02 g1s maradns.etc_maradns_mararc: Log: All RRs have been loaded So I could argue the problem is not in the script itself but in the binary process. Any hint? -- maradns init script silently fails during the boot, but works when run manually https://bugs.launchpad.net/bugs/370932 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
