I has Parallels Ples 11.X with Cent OS 6.5 and yesterday i tried to upgrade to PLESK 12.0.18.
Now, I can't start the apache module because it´s impossible to create the config file
The issue is:
Details: [2014-09-17 19:46:27] ERR [util_exec] proc_close() failed
[2014-09-17 19:46:34] ERR [panel] Apache config (14109759800.30476400) generation failed: Template_Exception: Can not restart web server: Service /etc/init.d/httpd failed to start
Service /etc/init.d/httpd failed to start
file: /usr/local/psa/admin/plib/Service/Driver/Web/Server/Apache.php
line: 104
code: 0
Can not restart web server: Service /etc/init.d/httpd failed to start
Service /etc/init.d/httpd failed to start
I try with cp the certifies and writing a new private key but it didn't work.
i use Plesk on a vserver which was offering it in version 11.x, i upgraded to 12.0.18, then i installed Dovecote on the panel. Everything went fine. Mail server is working.BUT sieve does not allow me to login and create filters.I tried telnet against 4190, and it works:
Connected to mail.xxxxxxxx.xxx. Escape character is '^]'. "IMPLEMENTATION" "Dovecot Pigeonhole" "SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave imapflags notify" "NOTIFY" "mailto" "SASL" "PLAIN LOGIN DIGEST-MD5 CRAM-MD5" "STARTTLS" "VERSION" "1.0" OK "Dovecot ready."
But when i use my sieve plugin for thunderbird OR access plesk's webmailclient Roundcube opening the filter module, it doesnt work. On Thunderbird i see the loading animation, thats it. On Roundcube it says "Unable to connect to sieve server".
Looks like something is missing. I can definitely access 4190 on my server from anywhere. So no firewall issue. I didnt change anything on configs, since plesk is handling it.Roundcube log doesnt give me anything. I dont even see logs added (to syslog or mail.*) while i try to connect.
Recently upgraded to Plesk 11.5 & upgraded to the latest CentOS kernel. Whenever I reboot the server DNS services do not work, can't view any websites hosted on the server etc.
Once I either restart BIND through Plesk Panel or
Code: # service named restart
Everything works perfectly.
My var/log/boot.log shows named started [OK]
When I run
Code: # service named status
Immediately after reboot everything looks normal, despite not resolving DNS until restarted.
I ran
Code: # ceckconfig --list
And both httpd & named services are displaying all 'off' on every runlevel. But, obviously named service is starting automatically, maybe by psa?
Should httpd & named be listed as on, is this the problem?
I want to upgrade my apache to 1.3.12 to 1.3.41 I don’t have cpanel whm, I am using centos as a OS. Is there any easy way I could do this upgrade if I install a RPM what’s happens to my old version of apache would I need to remove it?
my server running a legacy version of apache (v2.0.63) and should i upgrad it to v2.2.* ? and if yes.how cani do it without any risk and lose any data.
what about my module? forexamle suphp.suhosin or other en 2.2?
Currently my server is using apache 1.3.37 and I want to upgrade it to the latest version.
I see from WHM that I can upgrade it to Apache 2.2 with PHP 5.2.6. Just looking for a bit of advise that what specific option do I need to select for the upgrade?
Mod SuPHP EAccelerator IonCube Mod Bandwidth Tomcat Mod Mono Mod Perl Mod Security Suhosin for PHP SourceGuardian Loader Zend Optimizer
and then it goes to Exhaustive Options List....which has got a lot of options in it......Is it worth selecting any of these or just go with the defaults and I should be able to install these modules later on via WHM apache set up?
OS is OpenSuse 13.1.Yast shows the installed version of Apache2 as 2.4.6-6.23.1..I created my own CA, and used that to create a server certificate. The CA crtificate (in PEM format), and the server key and certificate have been placed in the appropriate directories in /etc/apache2 (the key in ssl.key and the certificates in ssl.crt).
When I check the status, after restarting apache, I see an error claiming that socache_shmcb_module is not installed and that it is ignored. This is, of course wrong, as I included that module in /etc/sysconfig/apache2, and the appropriate LoadModule statement in the Loadmodule.conf file (with the proper full path - /usr/lib64/apache2). This error is the only error I see on the server.
(I am using apache 2.2.25).I have this "HTML5 and CSS all in one for dummies" Book. And it tells me I have to configure the .conf file to make apache work with PHP.
At this point I have only edited the Document root folder. The book tells me to find a Loadmodule with an # with a mention of PHP (I'll put the text of the book at the end) and to add an "addtype" statement. If have found neither and when I add the manually the server doesnt work.how can I make PHP work? Also, I have noticed that the Apache commands in CMD don't work. I am running windows 8.1. URL....
On my website at www.jamescobban.net I have a directory which contains an ancient copy of my old static implementation of the site. It is there just in case someone has saved a old URL. However the data in that directory is several years out of date, so I would like to redirect the old static URLs to the equivalent dynamic URLs. For example: URLs.....
I wasn't warned that the <Directory> in the Apache conf file has to specify AllowOverride All whereas the default that is created when I install Ubuntu is AllowOverride None.I wasn't warned that I have to enable the mod_rewrite using a2enmod or else the rewrite commands are rejected.I am testing this on my private copy of the web-site where I can fiddle with options like that in the config file, but when I migrate this to my public server I do not have that privilege, so I want to try setting up the URL rewriting in .htaccess.
I tried to upgrade from apache 2.0.51 to 2.0.63 but it crashes as soon as new version is started and httpd is reloaded.
here is a part of the log
[Fri Apr 25 10:57:46 2008] [notice] Apache/2.0.63 (Unix) configured -- resuming normal operations Segmentation Fault in 3642, waiting for debugger Segmentation Fault in 3697, waiting for debugger Segmentation Fault in 3696, waiting for debugger [Fri Apr 25 10:58:11 2008] [notice] caught SIGTERM, shutting down [Fri Apr 25 10:58:22 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Fri Apr 25 10:58:22 2008] [notice] mod_security/1.9.4 configured [Fri Apr 25 10:58:22 2008] [notice] Digest: generating secret for digest authentication ... [Fri Apr 25 10:58:22 2008] [notice] Digest: done [Fri Apr 25 10:58:22 2008] [notice] LDAP: Built with OpenLDAP LDAP SDK [Fri Apr 25 10:58:22 2008] [notice] LDAP: SSL support unavailable [Fri Apr 25 10:58:23 2008] [notice] Apache/2.0.63 (Unix) configured -- resuming normal operations Segmentation Fault in 5422, waiting for debugger Segmentation Fault in 5421, waiting for debugger Segmentation Fault in 5452, waiting for debugger Segmentation Fault in 5461, waiting for debugger Segmentation Fault in 5451, waiting for debugger Segmentation Fault in 5466, waiting for debugger Segmentation Fault in 5465, waiting for debugger Segmentation Fault in 7363, waiting for debugger Segmentation Fault in 5435, waiting for debugger Segmentation Fault in 5906, waiting for debugger Segmentation Fault in 7251, waiting for debugger Segmentation Fault in 6041, waiting for debugger Segmentation Fault in 7723, waiting for debugger Segmentation Fault in 7986, waiting for debugger Segmentation Fault in 9659, waiting for debugger Segmentation Fault in 9643, waiting for debugger Segmentation Fault in 9361, waiting for debugger Segmentation Fault in 9744, waiting for debugger Segmentation Fault in 9543, waiting for debugger Segmentation Fault in 9879, waiting for debugger Segmentation Fault in 9794, waiting for debugger Segmentation Fault in 9758, waiting for debugger [Fri Apr 25 11:01:10 2008] [notice] caught SIGTERM, shutting down [Fri Apr 25 11:01:12 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Fri Apr 25 11:01:12 2008] [notice] mod_security/1.9.4 configured [Fri Apr 25 11:01:12 2008] [notice] Digest: generating secret for digest authentication ... [Fri Apr 25 11:01:12 2008] [notice] Digest: done [Fri Apr 25 11:01:12 2008] [notice] LDAP: Built with OpenLDAP LDAP SDK [Fri Apr 25 11:01:12 2008] [notice] LDAP: SSL support unavailable [Fri Apr 25 11:01:13 2008] [notice] Apache/2.0.63 (Unix) configured -- resuming normal operations Segmentation Fault in 11634, waiting for debugger Segmentation Fault in 11635, waiting for debugger Segmentation Fault in 11661, waiting for debugger Segmentation Fault in 11695, waiting for debugger Segmentation Fault in 11760, waiting for debugger Segmentation Fault in 11723, waiting for debugger Segmentation Fault in 11694, waiting for debugger Segmentation Fault in 11837, waiting for debugger Segmentation Fault in 11812, waiting for debugger Segmentation Fault in 12022, waiting for debugger Segmentation Fault in 11848, waiting for debugger Segmentation Fault in 11879, waiting for debugger Segmentation Fault in 13342, waiting for debugger Segmentation Fault in 12062, waiting for debugger Segmentation Fault in 13428, waiting for debugger Segmentation Fault in 13569, waiting for debugger Segmentation Fault in 11849, waiting for debugger Segmentation Fault in 13881, waiting for debugger Segmentation Fault in 13380, waiting for debugger [Fri Apr 25 11:02:27 2008] [notice] caught SIGTERM, shutting down [Fri Apr 25 11:02:29 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Fri Apr 25 11:02:29 2008] [notice] mod_security/1.9.4 configured [Fri Apr 25 11:02:29 2008] [notice] Digest: generating secret for digest authentication ... [Fri Apr 25 11:02:29 2008] [notice] Digest: done [Fri Apr 25 11:02:29 2008] [notice] LDAP: Built with OpenLDAP LDAP SDK [Fri Apr 25 11:02:29 2008] [notice] LDAP: SSL support unavailable [Fri Apr 25 11:02:30 2008] [notice] Apache/2.0.63 (Unix) configured -- resuming normal operations Segmentation Fault in 14123, waiting for debugger Segmentation Fault in 14154, waiting for debugger Segmentation Fault in 14156, waiting for debugger Segmentation Fault in 14273, waiting for debugger Segmentation Fault in 14114, waiting for debugger Segmentation Fault in 14308, waiting for debugger Segmentation Fault in 14316, waiting for debugger Segmentation Fault in 14274, waiting for debugger Segmentation Fault in 14315, waiting for debugger Segmentation Fault in 15562, waiting for debugger Segmentation Fault in 14113, waiting for debugger Segmentation Fault in 15583, waiting for debugger Segmentation Fault in 15615, waiting for debugger Segmentation Fault in 15616, waiting for debugger Segmentation Fault in 15584, waiting for debugger Segmentation Fault in 15637, waiting for debugger Segmentation Fault in 15631, waiting for debugger Segmentation Fault in 15614, waiting for debugger Segmentation Fault in 16332, waiting for debugger Segmentation Fault in 14262, waiting for debugger Segmentation Fault in 17504, waiting for debugger Segmentation Fault in 15638, waiting for debugger Segmentation Fault in 17515, waiting for debugger Segmentation Fault in 18105, waiting for debugger Segmentation Fault in 17516, waiting for debugger Segmentation Fault in 18163, waiting for debugger Segmentation Fault in 18175, waiting for debugger Segmentation Fault in 18177, waiting for debugger Segmentation Fault in 18178, waiting for debugger Segmentation Fault in 18149, waiting for debugger Segmentation Fault in 19931, waiting for debugger Segmentation Fault in 20098, waiting for debugger Segmentation Fault in 18176, waiting for debugger
I am on VPS and myself am quite a noob in this. Upgrade is performed by the support people.
If you guys can help please explain in lame terms Let me know if you need some specific info about the system.
I was suggested that some modules might not be upgraded yet and they cause the crash, so to fix I should remove modules one by one from httpd config until get to the problematic one.
my dedicated server is running using cPanel 11 apache 1.3.39 , php 5.2.4
i read a thread here in WHT says the " apache 2.2 with php 5.2.5 handle the load and doing high performance"
if it is true , plz anyone get the tutorials to upgrade it using /scripts/easyapache with GD libraries . and after upgrade will i have to re secure php again or what?
resolve the errors in web server configuration templates and generate the file again. The panel suggests to auto-recreate the bad config files, but the error persists.
Apache is currently working fine using an alias for one webserver, weewx. I had a heck of a time configuring the alias though, most configurations would result in a 404 error.
I'm trying to get it working with another webserver, IOG. And I'm again getting 404 errors...
Currently my IOG.conf file looks like this:
Code: Alias /IOG /home/Storage/iog <Directory /home/Storage/iog> Options Indexes AllowOverride None Require all granted </Directory>
/home/Storage/iog is good, it's the exact path and is readable/writable by all users.
Options Indexes is included because IOG does not generate an index.html.
AllowOverride None is included because I'm not using .htaccess files, and because it worked for the weewx configuration file.
Require all granted is used because I'm not serving this external to my LAN and would like all LAN machines to have access.
My (working) weewx configuration file:
Code: Alias /weewx/ "/home/Storage/weewx/" <Directory "/home/Storage/weewx/"> Options Indexes Includes FollowSymlinks AllowOverride None Require all granted </Directory>
Of course I tried that first, modifying the paths to IOG, and got a 404 error.
I make sure to reload Apache each time I make a change to the configuration file.
We currently migrating over from SunOne to HTTP Server. Flash files work fine on SunOne but not on the HTTP Server.When you go to run launch.html another window opens but the swf doesnt start playing.Both .flv (video/x-flv) and .swf application/x-shockwave-flash are in the mime.types
Launch.html file ##################################################### Include /opt/IBM/WebSphere/HTTPServer/conf/httpd.conf ##################################################### # #Listen IP address and Port Number
One site just linked to my website with incorrect URL as URL.. want to correct this by redirecting the URL to URL.... Therefore, I add the following line in my .htaccess, as follows: Redirect 301 /aor/%e2%80%9d URL...
However, this does not work. When I input URL... in Firefox or IE, the browser still said the page not found(404) error.
How To Upgrade Apache 1.3.37 to 2.2.x on Cpanel Server?
Currently, Apache is recommending:
Quote:
Apache 1.3.37 is the current stable release of the Apache 1.3 family. We strongly recommend that users of all earlier versions, including 1.3 family release, upgrade to to the current 2.2 version as soon as possible.
1) Is it safe to upgrade from Apache 1.3.37 to 2.2.4 on a Cpanel machine. I am worried that Cpanel won't like it.
2) Is Php4 still acceptable to use with Apache 2.2?
3) Can someone suggest a tutorial or guide for an upgrade to 2.2?
we've been running our software on apache 1.3 for years with no problems. We have a new server running apache2 and now none of our mod_rewrite works. Is there something extra that needs to be done with apache 2 to get mod_rewrite working? The module is definitely loaded (first thing I checked). If we turn on allowOverride from None to All in the httpd.conf we get completely blank pages. Our regular php pages work fine with allowoverride set to none, but they all break when it is set to all. Please help. This is the second time we have run into this on apache 2 servers.
I need to modify a web that is working in the server. I'd like to download it to my computer and test it. For this reason I have to change the htaccess file to change the redirects, but it doesn't work, appears 404 error
I have a home server set up with a couple of things going. Here is the weird thing that I can't figure out. I can access everything just fine from an INTERNET connection external to my LAN using my domain name, let's say "domain.com". So, if I type into my computer on my LAN www.domain.com, it searches without actually finding it's destination giving up after a period of time saying the server cannot be found.
But, if I type www.domain.com on my mobile phone using my data connection, it connects without a hitch and everything functions fine. I have done this set up before at a different home, but since I moved, I have come across this problem and either don't remember having this happen before or don't remember what I did to resolve it. What I should look for?
