Topic: DNS Problems: DNS not work and log files empty

[alex_rhys-hurn]

Dear All,

Apologies in advance if I have missed a key point or an obvious blunder. My searches on the forums have not yet found an answer to my problem.

I am running SME 7.4 on an HP Proliant ML110 g5 with Xeon Processor and 2 GB Ram and 2 x 250gb SATA disks.

The machine has been running for three months in a production environment of a small office with 5 PC's.

It is configured in Server only mode. It sits behind an IPCop Firewall. It does NOT have any DNS forwarder set in the Modify corporate DNS settings menus.

I can log in to the SME Server both with the Web interface and as root on the console.

I Confirm that I can ping LAN hosts and also hosts on the internet.
I can telnet to port 53 of my ISP DNS server, as well as port 53 of the IPCOP and also port 53 on 127.0.0.2 when I am loggedin to the SME as root. This indicates to me that the DNS daemons are running.

When I try to view the dnscache and dnscache.forwarder and tinydns log files they are all of zero size and are empty. There are many log files so it looks like they are rolling over properly but are empty.

I CANNOT resolve any hostnames. I cannot even resolve the SME hostname.

Using the dig command would normally list the root nameservers that the SME is using but it returns a no servers could be reached.

Given that I cannot view any log files (they are empty) this is difficult to troubleshoot.

I have carried out the following with no change:

Code: [Select]

config detele dnscache
config delete dnscache.forwarder
signal event post-upgrade ; signal event reboot
I have also attempted to add a corporate DNS entry using both my ISP dns as well as the IP Cop. None of these has made any difference.

Please can somebody advise me on how I can troubleshoot this?

Best regards to all.

Alex

[alex_rhys-hurn]

Dear All,

An Update:

It seems my Log files are not reporting anything because the disk is full. Here is the output of df:

Code: [Select]

[root@server tmp]# df -T
Filesystem    Type   1K-blocks      Used Available Use% Mounted on
/dev/mapper/main-root
              ext3   238162576 237869744         0 100% /
/dev/md1      ext3      101018     13348     82454  14% /boot
none         tmpfs      517076         0    517076   0% /dev/shm

[root@server tmp]#
This is mighty puzzling because we dont have that much data on the system. The user quotas page in server administrator only shows that there is approx 105 gigabytes of user data there. The server has 250GB of storage.

How do I find out what is eating my disk space and what things can I remove?

Help much appreciated.

Alex

[alex_rhys-hurn]

Dear All,

I apologise for wasting your time. I have solved the problem.

The DNS error and empty log files were a symptom of another problem.

For some reason (that I have yet to figure) when plugging in our Iomega USB HDD to performa the backup from the console, a Directory was created under /media and instead of mounting the disk, the backup was performed to that directory on the main disk. So, smeserver.tgz grew to the point that the whole disk was full.

Deleting the smeserver.tgz and then deleting the /media/Iomega_HDD directory has solved my problem.

Now I have an operational server, but need to troublshoot the backups. A job for tomorrow.

goodnight.

Alex