i've made a big update of almost 300Mb.I'had a working DNS server.Now, when i boot the box, named works and it resolves all the clients.If i make any change (enter a new client for example) and of course i restart named (service named restart), named stop but does not start again !!!In order to get a working named, i 'm obliged to reboot the box?
Mandriva 2009, BIND 9.5.0-P2. Named will start however I'm getting the above error as well as these:
14-Mar-2009 15:45:37.084 general: error: zone 0.in-addr.arpa/IN: loading from master file /var/lib/named/var/named/reverse/named.zero failed: file not found 14-Mar-2009 15:45:37.084 general: error: zone 0.0.127.in-addr.arpa/IN: loading from master file /var/lib/named/var/named/reverse/named.local failed: file not found
Named shows to be running but with the errors above I know it's not running correctly. I also copied the above dir's over to /var/lib/named/var/lib/named which is where I 'believe' it's chroot'd at, though I could be wrong since I'm unfamiliar with chroot.
OS CentOS 5.4 I have a DNS server that is logging all named and dns requests to the chrooted named directory. By default named logs to /var/log/messages but I want to isolate all the dns queries and requests to separate files. I know I can add entries to /etc/syslog.conf to "roll" the logs and logrotate should pick them up but fuzzy as to the syntax. I don't know what "tag" to use in the first fieild. for example
# Log anything (except mail) of level info or higher. # Don't log private authentication messages! *.info;mail.none;authpriv.none;cron.none/var/log/messages
I updated bind to version bind-9.3.4-6.0.3.P1.el5_2 today, and then I started getting "Starting named: named: user 'named' unknown" messages. Selinux is enabled. ID named shows: uid=25(named) gid=25(named) groups=25(named) context=root:system_r:unconfined_t:SystemLow-SystemHigh
I have installed CentOS 5.5 final on VM ware 7.0 workstation.... and I was trying to install and configure bind9.. it installed alright but it refused to start because named.conf is not in the /etc/ directory. I have copied the template for /usr/share/doc/named/* to (/etc/ and /var/named/) the appropriate directory but it still fails but on it does not gives me any error message. Oh... least I forgot I was trying to configure it as a cache only server for now.
I have CentOS 5.2 just installed and massively updated with yum -update command. Than I tried to configure firewall. After changes via system_config_securitylevel_tui (open ssh, http, ftp, and 3306:TCP ports) iptables service can't start with message
> /sbin/service iptables start Flushing firewall rules: [OK] Setting chains to policy ACCEPT: mangle filter nat [OK] Unloading iptables modules: [OK] Applying iptables firewall rules: iptables-restore v1.3.5: Couldn't load match `TCP':/lib64/iptables/libipt_TCP.so: cannot open shared object file: No such file or directory Error occurred at line: 18 Try `iptables-restore -h' or 'iptables-restore --help' for more information. [FAILED]
I erased the iptables service and installed it again with yum. How can I make this service work?
system: centos 5.5 Kernel 2.6.18-194.el5 freshly installed. bind is configured in chroot environment out of the box. placed named.conf in /var/named/chroot/etc and my zone files in /var/named/chroot/var/named.
I configure named and stumble upon the following problem: named is serious about user rights, every config file named uses should be named:named. I set rights to named:named as follows, but they get changed to root:named when I restart named as root. The same thing happens with SELinux context. This results in access denied type errors.
I replaced an old server (Fedora 3) with a new machine running CentOS 5.4. Unfortunately, I'm having some problems with "named".
Once in a while the "named" daemon crashes so hard, that I can't even restart it using
because the console freezes at "Shutting down named ...". I already waited for about 20 mins, but nothing happened. I cancelled the process using CTRL+C and typed "reboot" to restart the machine. After rebooting the "named" service works fine, but sooner or later it crashes again.
I also don't think it's a config problem, because I applied the "named.conf" from the former server where the whole "named" service worked fine and never crashed before. I'm a little confused, I also googled a lot nad could not find anything that exactly matches my problem. Is this a known problem?
I'm configuring a new Centos 5.5 server in replacement of an old W2K server.The topology of our network is simple : one file/dhcp/dns relay server and workstations (PC's and some MAC's) plus network printers and scanners.All the workstations have dynamic IP addresses (easier because a lot of 'dynamic' changes : new persons with their own laptop, ...) and the server and printers/scanners have fixed IP addresses.I edited the dhcpd.conf (see here underneath), I have the file dhcpd.leases but it doesn't start !
I know similar questions have been asked but I could find an answer to my exact question. Especially in anything like laymans terms. So when I try to start my iMac G4 running linux it starts, runs lines of code, flashes black then back to code several times then "Failed to start the X server.... output to diagnose the problem..." When I click yes here is what I get:
"Caught signal 11. Sever aborting.
In the mean time codes like the following appear on the side of the screen : [ 477.501334] eth1: switching to forced 10bt [ 497.901209] eth1: switching to forced 100bt
I have SUSE Linux Enterprise Desktop 10 running on HP Mini 2133. It's been working like a dream since I got it, but one day I got the following error message when booting it: Failed to start the X server (your graphical interface). It is likely that it is not set up correctly. Would you like to view the X server output to diagnose problem? <Yes> <No>.
X server output says alot of things, but I think this is the most important: (==)Using config file: "/etc/X11/xorg.conf" ACPI: OSPMOpen Called ACPI: Opening device (EE) VIA(0): No valid modes found
I then get the login:. I'm able to login, but I have no clue on what to do. How can I fix this?
Few days ago we had a server maintenance. The system was shutdown, we fix the CPU fan, and start the system again. But somehow when the system starts, our IMAP server - dovecot is not running. It just sit like a rock. Because the machine had a CPanel/WHM, I tried to restart dovecot using cpanel and got a message:
That was not really useful....
When I tried to restart dovecot using command line, I got nothing. really nothing.
How to find out what happens to my IMAP/dovecot? And anyway to make it run again?
i am using RHEL5 at VirtualBox,at the time of installation i did create two partition one for / and another for swap.Now my /var directory is taking too much space and i decided to create a new partition with required size and mount that partition to /var.Now http service wont start and i did not reboot yet.
I installed Red-hat 5.3. Problem is that it is not showing graphical interface. Only kernel / command prompt is available. I tried startx, then I got this msg. No video BIOS modes for chosen depth. Also showing that: ERROR: Failed to start X server.
There is a nice server that I want to install Redhat 5, update 5 on. I downloaded, from Oracle edelivery, the Linux 64 bit, Redhat 5, Update 5, and wrote it to bootable CD.
"V20658-01.zip","611558646","0C35737CD35BC26C212D205DF064CE2A","D0C7EF7CFF9635FECFDDB6BB724B1523851C1733","O racle Linux Release 5 Update 5 for x86_64 (64 Bit) - CD 1 of 6" and the other 6 CDs. However, when I went to test the install, I saw the messages:
Probing for video card: ATI Technologies ES1000 Failed to start X server. Attempting to start VESA X. Failed.
This is very odd, for a few reasons:
- the card is a few years old, and the distribution is new.
- Windows finds the correct information for this card, that it is an Nvidea card.
- A different simpler card gave the same error message (NVidea GEForce 6800)