INIT 6, http go Down

luizccm

Verified User
Joined
Oct 24, 2004
Messages
41
Location
Brazil, Brasilia D.F
I am nowadays with only a domain installed in the server of directadmin. I have for this domain 2 ips exclusive (174.142.xx.yyy and 174.142.xx.yyz). every time I do the process (INIT 6) in the server, the domain is unavailable for access. Noted that to solve the problem, I have to remove these 2 ips of the retailer, and to attribute again the retailer and then to the domain. Doing this procedure, the domain comes back to accessible being. But if come back to give the command (INIT 6), the problem comes back happen.
Thanks,
Luiz:eek:
 
If you do a shutdown -r now, same problem occurs?
If yes, seems that the changes are not really written to disk or something, so they are lost after the reboot.

You already did a diskcheck or checked your logs for disk problems?

Are owner and rights correct for the directory's? Because it could also be cause by wrong filerights, causing the changes not to be written.
 
DirectAdmin doesn't manage IP#s through your OS network manager. If you stop networking for any reason you need to run the startips script located in the DirectAdmin scripts directory.

Jeff
 
INIT 6, httpd down

Hello,
thank you very much for have answered.
This problem started to happen when there was an energy problem in the purveyor, and all the servers were turned off without the standard procedure. I ran the procedure (/etc/init.d/startips start) normalizing the situation after (INIT 6), but I need solve this situation returning to the normal. Already I reinstalled directadmin admin again, but the problem persists. I do not know which the command that can run to correct some problem that exists in the disk.
Thanks,
Luiz:rolleyes:
 
Is this a reason why you're calling this a DNS issue? What do you know that you haven't told us?

Do you think you've got a hard disk problem? If you do, then read man fsck for information on how to check and possibly repair the disk (beware: you shouldn't run fsck on mounted partitions; you could damage your partition beyond repair).

You may need to have an experienced administrator completely check your server.

Jeff
 
Back
Top