Code: [Sat Jul 28 21:40:09 2007] [notice] Apache/2.0.52 (Red Hat) configured -- resuming normal operations [Sat Jul 28 21:45:08 2007] [notice] caught SIGTERM, shutting down [Sat Jul 28 21:45:18 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:19 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:19 2007] [notice] Digest: generating secret for digest authentication ... [Sat Jul 28 21:45:19 2007] [notice] Digest: done [Sat Jul 28 21:45:19 2007] [notice] LDAP: Built with OpenLDAP LDAP SDK [Sat Jul 28 21:45:19 2007] [notice] LDAP: SSL support unavailable [Sat Jul 28 21:45:19 2007] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads. [Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:45:19 2007] [notice] Apache/2.0.52 (Red Hat) configured -- resuming normal operations [Sat Jul 28 21:50:08 2007] [notice] caught SIGTERM, shutting down [Sat Jul 28 21:50:08 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Sat Jul 28 21:50:08 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Sat Jul 28 21:50:08 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? ........
This just started a few hours ago. This is in my inbox:
06:54:01 PM cpanel@server.mydomain mysql on server.mydomain failed 06:45:11 PM cpanel@server.mydomain mysql on server.mydomain failed 06:36:25 PM cpanel@server.mydomain mysql on server.mydomain failed 06:27:34 PM cpanel@server.mydomain mysql on server.mydomain failed 06:18:46 PM cpanel@server.mydomain mysql on server.mydomain failed 06:09:57 PM cpanel@server.mydomain mysql on server.mydomain failed 06:01:05 PM cpanel@server.mydomain mysql on server.mydomain failed 05:51:46 PM cpanel@server.mydomain mysql on server.mydomain failed 05:42:58 PM cpanel@server.mydomain mysql on server.mydomain failed 05:34:08 PM cpanel@server.mydomain mysql on server.mydomain failed 05:25:19 PM cpanel@server.mydomain mysql on server.mydomain failed 05:16:31 PM cpanel@server.mydomain mysql on server.mydomain failed 05:07:43 PM cpanel@server.mydomain mysql on server.mydomain failed 04:58:53 PM cpanel@server.mydomain mysql on server.mydomain failed 04:50:05 PM cpanel@server.mydomain mysql on server.mydomain failed 04:41:09 PM cpanel@server.mydomain mysql on server.mydomain failed 04:32:15 PM cpanel@server.mydomain mysql on server.mydomain failed 04:23:28 PM cpanel@server.mydomain mysql on server.mydomain failed 04:14:36 PM cpanel@server.mydomain mysql on server.mydomain failed 04:05:48 PM cpanel@server.mydomain mysql on server.mydomain failed 03:56:57 PM cpanel@server.mydomain mysql on server.mydomain failed 03:48:09 PM cpanel@server.mydomain mysql on server.mydomain failed
And they're still arriving to my inbox. When you look at the time stamps, it's failing every 9 minutes. I looked in the crontab and there is nothing running every 9 minutes. Not even close. But there's something happening every 9 minutes. Where do I look?
Even though I have set notification_interval from 120 to 120m. It might take the changed interval_limit from nagios.cfg.
I am receiving far too many e-mails and text messages in case of downtime at the moment. We're testing our monitoring servers at the moment, but we don't need a new notification every 25 minutes...
I recently signed up (just yesterday) with this company on the grounds of pricing and reviews. I especially noted the fact that they respond "in minutes" well. I have opened 2 tickets thusfar:
first: Created On: 15 Jul 2007 04:54 PM Last Update: 15 Jul 2007 06:06 PM
second: reated On: 16 Jul 2007 02:25 AM
I am new to the VPS hosting game. Are support times generally longer than with shared hosting? Or am I just encountering some bad luck? To me, you should want to be impressing newly registered customers. Especially concerning support and when the client has stated VPS is new to him.
I don't have a problem with Bluehost, but after getting this email tonight I would have thought that it's not that hard to have enough fuel and a big enough generator to last more than five minutes after a power outage. It seems like pretty poor redundancy planning if a major host can't last more then five minutes with no power. Hospitals and other places don't have any problem doing it with similar or bigger power demands.
Dear Bluehost Customer,
This evening (July 14th) from about 5:25pm-6:55pm many of our servers were offline causing significant downtime for many of our users. The outage was due to a severe power outage in the north end of Orem, Utah where our servers are located. We do have UPS backup as well as diesel generators, but at about 5:30 they finally gave out. The power outage was for much longer than that period of time, but the reserve power was eventually consumed in its entirety. When it rains it pours.
For users on box65-box145 there have been periodic problems with the Redhat linux kernel that we were using that was causing problems with the filesystem that your data is stored on. This issue has been causing periodic problems for users on those boxes. In the last few days we have resolved that issue which also caused those boxes to require a reboot.
The downtime is extremely regretable. We apologize profusely for the inconvenience to our customers and in turn to those who were trying to visit your sites during the outage. With the fixes we have put in place in the last few days coupled with other upgrades you should experience MUCH better uptime in the future.
My entire experience with Gigenet has been very bad. I will post a 30 day review once I have completed my first and only billing cycle with them. This topic will be solely focused on the way Gigenet handled my server being down for 17 hours and 50 minutes. I have paid Gigenet for 30 days of service, one billing cycle. My account is set to be terminated on the 7th of June.
I pay Gigenet to actively monitor my server. These services are called "NOC Response from Monitoring" and "Host Ping (ICMP) and TCP Service Monitoring". The extra "service" cost $10/mo.
I realized that my server was down after 7 hours of downtime. I sent in a "critical" support ticket at about 3 AM.
Here is a timeline of my support ticket with Gigenet
Quote:
Originally Posted by ME - 05 Jun 2009 03:11 AM
My Server is down. Any reason for the down time?
Quote:
Originally Posted by ME - Posted On: 05 Jun 2009 03:24 AM
Can I at least get a confirmation that this issue is being worked? It's 3:32 AM...I have to work tomorrow morning and would prefer to get some sleep.
Thanks...
* Note: I am not exactly clear why the time stamp and the time mentioned by me in the ticket don't line up.
Quote:
Originally Posted by Gigenet - Posted On: 05 Jun 2009 03:24 AM
I'm looking into your issue now, all updates will be posted here.
Quote:
Originally Posted by ME - Posted On: 05 Jun 2009 03:29 AM
I have server monitoring. Can you also explain to me how SEVEN HOURS of down time was over looked by your "server monitoring"?
Quote:
Originally Posted by Gigenet - Posted On: 05 Jun 2009 03:37 AM
This server has been marked for cancellation.
I see that the date set was for June 7th and today is the 5th, I will need to speak to a Billing representative before I can re-enable this device. The Billing Department will not be in until 10am, I will leave this ticket open and I will speak to them first chance I get.
* Note my server is still down at this point.
Quote:
Originally Posted by ME - Posted On: 05 Jun 2009 03:44 AM
Yes, because canceling my service two days earlier makes a lot of sense. I paid Gigenet for 30 days, I should get all 30 days. Maybe I'm misunderstanding something?
Please respond so I can get to bed...
Quote:
Originally Posted by Gigenet - Posted On: 05 Jun 2009 03:55 AM
I understand your concern, but your server port was administratively shutdown and I was able to find the cancellation ticket. I need to speak with someone from Billing concerning this issue. This looks to be a mistake on our end, but I don't have all the details in front of me. I will attempt to contact my manager and get this straightened out. All further updates will be posted here.
It was nearly 4:00 AM at this point. I had to be at work by 6:30 AM. My server was still down, so I went to bed.
The next day I received this response:
Quote:
Originally Posted by Gigenet Posted On: 05 Jun 2009 01:43 PM
Hello,
Your server should be back online until the 7th. We're very sorry for the inconvenience. I've confirmed the server's availability via ping from my workstation. Please let us know if you have problems accessing it and we'll take another look.
At this point in time my server was restored. The total downtime was 17 hours and 50 minutes. I monitor my server with a third-party service called "HyperSpin".
Seeking an answer to explain nearly 18 hours of downtime; I sent this response.
Quote:
Originally Posted by ME - Posted On: 05 Jun 2009 04:14 PM
What is the reason for the downtime? Is 17 hours and 50 minutes of unexplainable downtime something that I should expect from Gigenet?
Quote:
Originally Posted by Gigenet -Posted On: 05 Jun 2009 04:22 PM
Hello,
Unfortunately I' not exactly sure what happened. I think the server may have been prematurely canceled, but I'm not totally certain. The server should be back up and I've put in the necessary ticket to make sure it stays on until the 7th, as you requested. We're very sorry for this inconvenience.
So, the best I can get out of Gigenet is that my server may have been shutdown prematurely. I don't understand why Gigenet can not fully explain nearly 18 hours of downtime. No one seems to know exactly what happened...
We've had a VPS for just over a month now. I am not going to mention the host by name (yet) but they advertise here and other people here reported liking them.
Sadly it's not my experience and I regret my purchase.
Every morning for the past few weeks, we get load spikes every 30 minutes that make our site unusable for a minute (on our VPS, any load over 1.0 is sluggish, over 2.0 is virtually unusable, over 3 is unresponsive)
Here's a series of days as an example: [url]
The worst part about this is the host insists 1. either it's not happening or 2. they can't find it
I know it's happening because when I try to load a page on the half-hour, it takes over 13 seconds (less than 1 second normally). And it's fairly obvious it's someone doing a cron job with some nasty downloading, uploading, or maybe a massive mysql update.
Someone tell me what to tell them because this is driving me out of my mind. The load is NOT being caused by ourselves, I've made sure all our cron jobs don't happen on the exact half hour and we get lots of traffic later in the day without loads.
Recently we have launched our new cpanel server, We have some problems on that.
When we restart httpd, all things will be good before 15 min, but after that, speed goes down to 1/10 and after some hours that will get as low as nobody can view pages on the server.
We are using cPanel latest release and CSF on CentOS4.5.
Apache 1.3.7 and PHP4.4.7 is running on the server with Zend.
i use the following perl script(created by me) to save server load every 30 minutes to a log file i just keep it running in the background(probably would be more effective using cron)
I will wanted to know if hmailserver lets configure the quantity of outgoing emails it is permitted in an hour or minutes. I have found this:
hMailServer is pre-configured to have high security when it comes to relaying and authentication so that no one can use your server to send spam messages.
But I do not know if It refers to what I want or to an antihack or something like that to protect my server.
Firstly, I want to say that I signed up with Softlayer because I heard they had better support than EV1. If that's the case, EV1 must be really horrible.
That being said, I've had an issue with my server every since I got it from them a few days ago. I moved a bunch of high traffic sites that use PHP and MySQL on a dual core dual processor server with 2 gigs of ram and a scsi 10k disk.
It is running Plesk 8 (which I theorize 'could' be the problem).
I am not stating it is a hardware problem or a software problem because I have no idea what the problem is. Here are the symptoms:
- Every few minutes all my PHP and MySQL sites begin to run very slow. It takes about 10 seconds before a page is loaded.
- During this time, sites that do not use MySQL and PHP seem to run fast, but perhaps a little slower than normal.
- When i attempt to log into SSH during these moments, it pauses on the screen with the black cursor and waits and takes about 30 seconds to log in.
- When I log in, or when I am already logged in and I view the load and memory usage during these times, there is no correlation between the cpu usage or memory usage and the slow downs
- They occur all day and all night.
- When these moments do not occur, the sites are all blazingly fast.
- Load is rarely ever above 1
- I have MySQL and PHP running on the same box.
- I have disabled any possible Plesk cron jobs including drweb and the backup cron that runs every 15 mintues. However, I have manually run it and tested the server and it does not cause any slow down.
- One cron job I have on one of the sites I host (http://www.perfectpeople.net) updates a new image every 25 minutes. This certainly does not cause the problem, and recently two images have shown up not found but the db is updated so you see that image not found error. This has never occurred before and I theorize this is the result of the same issue.
---------
None of these issues occurred with any previous servers. Softlayer techs keep telling me everything is fine, repeating over and over that it loads fine on their side, being completely unhelpful.
Some notes to avoid pointless responses:
1. If other sites load fine, and ping is fine, it is not a bandwidth or traceroute issue.
2. If CPU and memory usage is fine, it is not a load issue.
---------
The only thing I can theorize based on my limited knowledge is that it could be a hard drive seek. I do not know if that will cause SSH connections to slow down and PHP and MySQL.
On our production service, we've been getting numerous malformed POST requests to some of our CGI scripts that are showing up as 500 errors in our logs. They are malformed in the sense that the actual content length doesn't match the Content-Length specified in the request.
Here's the most trivial example I can come up with that reproduces the problem for us:
In addition to the 500 error in the access log, we see the corresponding error in the error log:
(70014)End of file found: Error reading request entity data
Based on the nature of the POST request and the error response, it does appear that Apache is doing the right thing here.
The POST never actually makes it as far as the script being targeted (/some_valid_alias in the above example); in other words, Apache returns 500 to the client, writes the error to the error log and never executes the script.
Is there a way to capture/avoid internal Apache errors like 70014, and return some other HTTP status besides 500 (like 403)? It's particularly annoying in our case, because our server sends us an email for all 500 errors.
So far, our best "defense" against these 500 errors is to disallow POST for these aliases, which normally just ignore the POST data anyway (when the request is not malformed):
I've had this problem a long time now with my hosting network and decided to ask here hoping I get some good solutions, or if someone is willing to looking at this (I'll pay if they want).
Here's what I mean: [url]
Problem is as you can see apache processes constantly rise infinitely, at least until I restart apache (/etc/init.d/httpd restart). The point of restart is shown in red lines.
And after restart, it goes down again for X amount of hours then eventually rises again infinitely until it's restarted again.
But the fact that after restart it remains down, it means it had the potential to be down all along.
So my question is: what could be causing this and does anyone have solution to keep them low at all times (as per graphs)?
The Linux Server got down when the MaxClients 256 is reached. Error Log:
"server reached MaxClients setting, consider raising the MaxClients setting"
So that I have tried to increased the MaxClients Value to 500, after changed the value in httpd.conf and restart I get following error message.
" [notice] SIGHUP received. Attempting to restart WARNING: MaxClients of 500 exceeds ServerLimit value of 256 servers, lowering MaxClients to 256. To increase, please see the ServerLimit directive."
So that I tried changed the Server limit in /usr/local/apache/include/httpd.h header file. but it seems like there is no entry.
Apache Version : 2.2.8
So I have added the ServerLimit 500 entry in httpd.conf file and restart the httpd service. But still shows the same warning mesg. Please help me regarding this.
We have the Dedicated server for Flash Game Server with following configuration.
RHEL4 OS 2GB RAM Intel(R) Xeon(R) X3210 @ 2.13GHz Cpanel Installed. Apache 2.2.8 PHP 5.2.4 MySQL 4.1.2 (MySQL Server is working in differend server)
This redirect works fine on Apache 2.2.8, but doesn't work on Apache 1.3.41
The following is the entry from error_log: RewriteRule: cannot compile regular expression '^sap-latest-news/([0-9]*)/([A-Za-z0-9_-.]*).htm$'
A simple Rewrite is working fine in Apache 1.3, but the above regualar expression doesn't seem to be working on Apache 1.3. Does anyone know whether Apache 1.3 doesn't support it?
I am having an issue where I have a server that Directadmin is installed on. I go to the a url that is on the server and all i see is the default page of apache saying congrats, it is installed. Although there is no file like that in the public_html any longer and I can see my files in the public_html folder of that specific site.
I'm building a new server for a predominantly php5/mysql5 website and was wondering which version of apache to put on. I know there are some issues with PHP and Apache in MPM, but what's the performance comparison between Apache 1.3 and Apache 2 Prefork?
I am trying to install dedicated web server on my Slackware 12.0.0 machine. I am a novice in Linux, but succeeded in MySQL & proFTPd installation. The problem now in httpd compiling.
I downloaded the latest Apache 2.2.9, but it needs Apache Portable Runtime 1.3.2 installed. I downloaded 1.3.2 version and run ./configure
1. checking size of size_t... 4 2. checking which format to use for apr_size_t... %u 3. checking size of off_t... 4 4. checking for mmap64... yes 5. checking for sendfile64... yes 6. checking for sendfilev64... no 7. checking for mkstemp64... yes 8. checking for readdir64_r... yes 9. checking which type to use for apr_off_t... off64_t 10. checking whether ino_t and unsigned long are the same... yes 11. configure: using unsigned long for ino_t 12. checking size of pid_t... 4 13. checking whether byte ordering is bigendian... no 14. checking size of struct iovec... 8 15. checking for strnicmp... no 16. checking for strncasecmp... yes 17. checking for stricmp... no 18. checking for strcasecmp... yes 19. checking for strdup... yes 20. checking for strstr... yes 21. checking for memchr... yes 22. checking for strtoll... yes 23. 24. Checking for DSO... 25. checking for dlopen... no 26. checking for dlopen in -ldl... yes 27. adding "-ldl" to LIBS 28. checking for dlsym... yes 29. 30. Checking for Processes... 31. checking for waitpid... yes 32. checking for Variable Length Arrays... yes 33. checking struct rlimit... yes 34. 35. Checking for Locking... 36. checking for semget... yes 37. checking for semctl... yes 38. checking for flock... yes 39. checking for semaphore.h... (cached) yes 40. checking OS.h usability... no 41. checking OS.h presence... no 42. checking for OS.h... no 43. checking for library containing sem_open... none required 44. checking for sem_close... yes 45. checking for sem_unlink... yes 46. checking for sem_post... yes 47. checking for sem_wait... yes 48. checking for create_sem... no 49. checking for working sem_open... yes 50. checking for union semun in sys/sem.h... no 51. checking for LOCK_EX in sys/file.h... yes 52. checking for F_SETLK in fcntl.h... yes 53. checking for SEM_UNDO in sys/sem.h... yes 54. checking for POLLIN in poll.h sys/poll.h... yes 55. checking for PTHREAD_PROCESS_SHARED in pthread.h... yes 56. checking for pthread_mutexattr_setpshared... yes 57. checking for working PROCESS_SHARED locks... yes 58. checking for robust cross-process mutex support... yes 59. decision on apr_lock implementation method... SysV IPC semget() 60. checking if all interprocess locks affect threads... no 61. checking if POSIX sems affect threads in the same process... no 62. checking if SysV sems affect threads in the same process... no 63. checking if fcntl locks affect threads in the same process... no 64. checking if flock locks affect threads in the same process... no 65. checking for entropy source... /dev/urandom 66. 67. Checking for File Info Support... 68. checking for struct stat.st_blocks... yes 69. checking for struct stat.st_atimensec... no 70. checking for struct stat.st_ctimensec... no 71. checking for struct stat.st_mtimensec... no 72. checking for struct stat.st_atim.tv_nsec... yes 73. checking for struct stat.st_ctim.tv_nsec... yes 74. checking for struct stat.st_mtim.tv_nsec... yes 75. checking for struct stat.st_atime_n... no 76. checking for struct stat.st_ctime_n... no 77. checking for struct stat.st_mtime_n... no 78. checking for inode member of struct dirent... d_fileno 79. checking for file type member of struct dirent... d_type 80. 81. Checking for OS UUID Support... 82. checking uuid.h usability... no 83. checking uuid.h presence... no 84. checking for uuid.h... no 85. checking uuid/uuid.h usability... yes 86. checking uuid/uuid.h presence... yes 87. checking for uuid/uuid.h... yes 88. checking for library containing uuid_create... no 89. checking for library containing uuid_generate... -luuid 90. checking for uuid_create... no 91. checking for uuid_generate... yes 92. checking for os uuid usability... yes 93. 94. Checking for Time Support... 95. checking for struct tm.tm_gmtoff... yes 96. checking for struct tm.__tm_gmtoff... no 97. 98. Checking for Networking support... 99. checking for type in_addr... yes 100. checking if fd == socket on this platform... yes 101. checking style of gethostbyname_r routine... glibc2 102. checking 3rd argument to the gethostbyname_r routines... char 103. checking style of getservbyname_r routine... glibc2 104. checking if TCP_NODELAY setting is inherited from listening sockets... yes 105. checking if O_NONBLOCK setting is inherited from listening sockets... no 106. checking whether TCP_NODELAY and TCP_CORK can both be enabled... yes 107. checking for TCP_CORK in netinet/tcp.h... yes 108. checking for TCP_NOPUSH in netinet/tcp.h... no 109. checking for SO_ACCEPTFILTER in sys/socket.h... no 110. checking whether SCTP is supported... no 111. checking for struct ip_mreq... yes 112. checking for set_h_errno... no 113. 114. Checking for IPv6 Networking support... 115. checking for library containing getaddrinfo... none required 116. checking for library containing gai_strerror... none required 117. checking for library containing getnameinfo... none required 118. checking for gai_strerror... yes 119. checking for working getaddrinfo... yes 120. checking for negative error codes for getaddrinfo... yes 121. checking for working getnameinfo... yes 122. checking for sockaddr_in6... yes 123. checking for sockaddr_storage... yes 124. checking for working AI_ADDRCONFIG... yes 125. checking if APR supports IPv6... yes 126. checking langinfo.h usability... yes 127. checking langinfo.h presence... yes 128. checking for langinfo.h... yes 129. checking for nl_langinfo... yes 130. 131. Restore user-defined environment settings... 132. restoring CPPFLAGS to "" 133. setting EXTRA_CPPFLAGS to "-DLINUX=2 -D_REENTRANT -D_GNU_SOURCE -D_LARGEFILE64_SOURCE" 134. restoring CFLAGS to "" 135. setting EXTRA_CFLAGS to "-g -O2 -pthread" 136. restoring LDFLAGS to "" 137. setting EXTRA_LDFLAGS to "" 138. restoring LIBS to "" 139. setting EXTRA_LIBS to "-luuid -lrt -lcrypt -lpthread -ldl" 140. restoring INCLUDES to "" 141. setting EXTRA_INCLUDES to "" 142. configure: creating ./config.status 143. config.status: creating Makefile 144. config.status: creating include/apr.h 145. config.status: creating build/apr_rules.mk 146. config.status: creating build/pkg/pkginfo 147. config.status: creating apr--config 148. config.status: WARNING: 'apr-config.in' seems to ignore the --datarootdir setting 149. config.status: creating apr.pc 150. config.status: creating test/Makefile 151. config.status: creating test/internal/Makefile 152. config.status: creating include/arch/unix/apr_private.h 153. config.status: executing default commands 154. config.status: include/apr.h is unchanged 155. config.status: include/arch/unix/apr_private.h is unchanged
After that I am trying make and have error at the end:
In the middle of recompiling apache (via whm) after upgrading postgresql to 8.3, apache went down and remains down even after restart. Recompile is still in progress (about 15 minutes in)
tail -f /usr/local/apache/logs/error_log [Wed Nov 12 15:24:44 2008] [warn] No JkShmFile defined in httpd.conf. Using default /usr/local/apache/logs/jk-runtime-status [Wed Nov 12 15:24:44 2008] [notice] ModSecurity for Apache/2.5.7 (http://www.modsecurity.org/) configured. [Wed Nov 12 15:24:46 2008] [warn] No JkShmFile defined in httpd.conf. Using default /usr/local/apache/logs/jk-runtime-status [Wed Nov 12 15:24:46 2008] [alert] getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive [Wed Nov 12 15:24:46 2008] [alert] getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive [Wed Nov 12 15:24:46 2008] [alert] getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive [Wed Nov 12 15:24:46 2008] [alert] getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive [Wed Nov 12 15:24:46 2008] [alert] getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive [Wed Nov 12 15:24:46 2008] [notice] Apache/2.2.10 (Unix) mod_ssl/2.2.10 OpenSSL/0.9.7a mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 mod_jk/1.2.25 PHP/5.2.6 configured -- resuming normal operations [Wed Nov 12 15:24:46 2008] [alert] Child 22588 returned a Fatal error... Apache is exiting! httpd configtest Syntax OK ps -ef | grep ^httpd (no result) Cpanel/Centos