service httpd restart -> having this message

dannygoh

Verified User
Joined
Feb 9, 2004
Messages
391
Location
Malaysia
[root@sun domains]# service httpd restart
Stopping httpd: [ OK ]
/etc/init.d/httpd: line 46: ulimit: open files: cannot modify limit: Invalid argument
/etc/init.d/httpd: line 47: ulimit: open files: cannot modify limit: Invalid argument
/etc/init.d/httpd: line 48: ulimit: open files: cannot modify limit: Invalid argument
/etc/init.d/httpd: line 49: ulimit: open files: cannot modify limit: Invalid argument
Starting httpd:
[Sun Aug 29 11:28:13 2004] [warn] NameVirtualHost xxx.xx.105.38:80 has no VirtualHosts
[Sun Aug 29 11:28:13 2004] [warn] NameVirtualHost xxx.xx.105.38:443 has no VirtualHosts
[Sun Aug 29 11:28:13 2004] [warn] NameVirtualHost xxx.xx.105.44:80 has no VirtualHosts
[Sun Aug 29 11:28:13 2004] [warn] NameVirtualHost xxx.xx.105.44:443 has no VirtualHosts
[Sun Aug 29 11:28:13 2004] [warn] NameVirtualHost xxx.xx.101.97:80 has no VirtualHosts
[Sun Aug 29 11:28:13 2004] [warn] NameVirtualHost xxx.xx.101.97:443 has no VirtualHosts
[Sun Aug 29 11:28:13 2004] [warn] NameVirtualHost xxx.xx.101.87:80 has no VirtualHosts
[Sun Aug 29 11:28:13 2004] [warn] NameVirtualHost xxx.xx.101.87:443 has no VirtualHosts
[ OK ]

BTW, i have assigned the IP to DA but do not have any user using this IP
 
I don't know what's wrong with your lines 46 through 49; since the httpd startup doesn't report any error, I wouldn't worry about it.

As for those startup warnings, they're normal if you don't have any sites assigned to those IP#s.

Jeff
 
They are indeed normal if "you don't have any sites assigned to those IP's".

how you got those entries is what you should put your effort towards. The way you got rid of the errors is common method and should not cause any issue.
 
Back
Top