LINUX ADMIN: January 2016

Friday, January 15, 2016

root@- [~]# /etc/init.d/httpd restart

httpd not running, trying to start

root@- [~]# tail -f /usr/local/apache/logs/error_log

[Tue Jan 12 20:19:33 2016] [alert] (EAI 2)Name or service not known: mod_unique_id: unable to find IPv4 address of "-"

Configuration Failed

[Tue Jan 12 20:21:52 2016] [alert] (EAI 2)Name or service not known: mod_unique_id: unable to find IPv4 address of "-"

Configuration Failed

I have checked the Apache configuration syntax file and it was fine.

root@- [~]# httpd -t

Syntax OK

checking the file “/etc/hosts” the server hostname was incorrect. After correcting the Apache service was working fine.

iptables-restore: unable to initializetable ‘mangle’

If you’re getting the following error on your server, iptables update might have caused this issue.

=====================

[root@mon ~]# /etc/init.d/iptables start

iptables: Applying firewall rules: FATAL: Module ip_tables not found.

iptables-restore v1.4.7: iptables-restore: unable to initialize table 'mangle'

Error occurred at line: 2

Try `iptables-restore -h' or 'iptables-restore --help' for more information.

====================

To resolve this, check the output of iptables -L if that gives any output, save it using following command and then restart iptables as shown below.

Saving iptables rules:

[root@mon ~]# iptables -L

Chain INPUT (policy ACCEPT)

target prot opt source destination

Chain FORWARD (policy ACCEPT)

target prot opt source destination

Chain OUTPUT (policy ACCEPT)

target prot opt source destination

[root@mon ~]# iptables-save > /etc/sysconfig/iptables

[root@mon ~]# /etc/init.d/iptables restart

iptables: Setting chains to policy ACCEPT: filter [ OK ]

iptables: Flushing firewall rules: [ OK ]

iptables: Unloading modules: [ OK ]

iptables: Applying firewall rules: [ OK ]

The issue has been sorted out. It removed the unsupported rules from iptables list.

Friday, January 15, 2016