Quote:
Originally Posted by agriz
How to fix this problem?
|
This may be a bitter pill to swallow but your first and foremost problem is that
you do not know what you are doing, as evidenced by:
Quote:
Originally Posted by agriz
Gave chown named:named / with 755. But still same problem
|
Issued as root this command makes everything on the file system be owned by owner and group "named". Current processes may seem to run without problems but Real Soon Now this error will show to break a lot of things.
Undo what you did. Reverting ownership back works easily enough when your distribution can 'rpm -qa --setperms --setugids;' or when you can restore attributes from backup or read them from say a Samhain or AIDE database. After that you should read something like
Learning the Linux Command Line (LQ: Telengard web log) and your distributions basic documentation before doing anything else.
Quote:
Originally Posted by agriz
I tried to delete the symlink. After restart, it got the symlink again.
|
Processes, or init scripts that start processes, save the Process Id for process management. Deleting a PID file is only necessary if the process or init script did not remove the PID file (no clean exit).
Quote:
Originally Posted by agriz
named dead but subsys locked[/PHP]
|
Either named was installed and it ran OK (and then it didn't anymore) or it never ran OK. In the first case undo what you did and ponder your modifications. In the latter case read the basic documentation ISC BIND comes with and configure it properly.
Quote:
Originally Posted by agriz
I tried to configure with chroot. Webmin was having problem with chroot. I removed chroot just to use bind.
|
ISC BIND existed long before Webmin comes along. ISC BIND runs more securely if it can chroot itself. If you have problems running Webmin then fix the problems Webmin has, not cripple ISC BIND.
