HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Apache Startup
Operating System - HP-UX
1829737
Members
2131
Online
109992
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2002 09:06 AM
06-30-2002 09:06 AM
Apache Startup
I am having a problem with a new server getting apache to start. The error_log states that it is unable to resolve the server name. I can ping the server name, and complete a forward/reverse lookup of the name/ip. Does anyone have any ideas about this??
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2002 11:08 AM
06-30-2002 11:08 AM
Re: Apache Startup
hi.
are you doing this on the new server?
seams a problem of name resulution on the server.
check the /etc/resolv.conf and /etc/nsswitch.conf
hth
regards
-PP
are you doing this on the new server?
seams a problem of name resulution on the server.
check the /etc/resolv.conf and /etc/nsswitch.conf
hth
regards
-PP
Goodbye Douglas! Whereever you are now, keep your towel and don't panic.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2002 12:07 PM
06-30-2002 12:07 PM
Re: Apache Startup
Ron,
You may want to use the following parameter in your httpd.conf:
ServerName webserver.domain.com
It should however be able to pickup the server name via DNS. Check your /etc/nsswitch.conf to see how your are resolving hostnames. Also be sure your /etc/hosts file has the FQDN for this server.
Hope that helps.
-Mike
You may want to use the following parameter in your httpd.conf:
ServerName webserver.domain.com
It should however be able to pickup the server name via DNS. Check your /etc/nsswitch.conf to see how your are resolving hostnames. Also be sure your /etc/hosts file has the FQDN for this server.
Hope that helps.
-Mike
The network is the computer, yeah I stole it from Sun, so what?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-30-2002 02:43 PM
06-30-2002 02:43 PM
Re: Apache Startup
Make sure that you have your /etc/nsswitch.conf
file resolving to your local hosts files first.
This will save you a lot of grief. We use a simple ftp script to get the latest copy of DNS every 24 hours.
/etc/nsswitch.conf
hosts: files [NOTFOUND=continue UNAVAIL=return TRYAGAIN=return] dns [NOTFO
UND=return UNAVAIL=continue TRYAGAIN=return]
# more /etc/resolv.conf
domain mydomain.com.au
nameserver 10.33.100.2
nameserver 10.43.100.3
file resolving to your local hosts files first.
This will save you a lot of grief. We use a simple ftp script to get the latest copy of DNS every 24 hours.
/etc/nsswitch.conf
hosts: files [NOTFOUND=continue UNAVAIL=return TRYAGAIN=return] dns [NOTFO
UND=return UNAVAIL=continue TRYAGAIN=return]
# more /etc/resolv.conf
domain mydomain.com.au
nameserver 10.33.100.2
nameserver 10.43.100.3
Anyone for a Mutiny ?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP