Author Topic: Zentyal network module failed to start  (Read 794 times)

vmb

  • Zen Apprentice
  • *
  • Posts: 46
  • Karma: +5/-0
    • View Profile
Zentyal network module failed to start
« on: May 19, 2016, 12:13:18 pm »
I have a Zentyal server that powers off overnight and starts up automatically on BIOS alarm in the morning. The system is backed up and updates from the repos are automatically applied before shutdown. Today it couldn't load the Zentyal network and dns modules. Login for all users except root were affected.

I found this in /var/log/syslog

Code: [Select]
May 19 08:18:29 pc26415 named[1082]: ----------------------------------------------------
May 19 08:18:29 pc26415 named[1082]: BIND 9 is maintained by Internet Systems Consortium,
May 19 08:18:29 pc26415 named[1082]: Inc. (ISC), a non-profit 501(c)(3) public-benefit
May 19 08:18:29 pc26415 named[1082]: corporation.  Support and training for BIND 9 are
May 19 08:18:29 pc26415 named[1082]: available at https://www.isc.org/support
May 19 08:18:29 pc26415 named[1082]: ----------------------------------------------------
May 19 08:18:29 pc26415 named[1082]: adjusted limit on open files from 4096 to 1048576
May 19 08:18:29 pc26415 named[1082]: found 1 CPU, using 1 worker thread
May 19 08:18:29 pc26415 named[1082]: using 1 UDP listener per interface
May 19 08:18:29 pc26415 named[1082]: using up to 4096 sockets
May 19 08:18:29 pc26415 named[1082]: loading configuration from '/etc/bind/named.conf'
May 19 08:18:29 pc26415 named[1082]: open: /etc/bind/named.conf: permission denied
May 19 08:18:29 pc26415 named[1082]: loading configuration: permission denied
May 19 08:18:29 pc26415 named[1082]: exiting (due to fatal error)

I looked at /etc/bind/named.conf and ownership and permissions were root:bind 0400
I changed the permissions to 0640 and rebooted.

The Zentyal dns module started OK but networking still reported a fail.

On the console I executed the command
Quote
sudo /etc/init.d/zentyal network status
It chugged along for a while, in fact I thought the system had hung, but eventually Zentyal reported that the module was running. This was confirmed by all users being able to login in again and email flowing inbound and outbound.
« Last Edit: May 19, 2016, 12:25:48 pm by vmb »