I am using single Apache HTTP Server (2.2.23) as a Load Balancer with two IBM Websphere application server nodes (other machines). I have deployed the simple text based helloWorld application and it works fine with load balancer. But When I deploy the real application that contains images,css file , java script file. It loads the page without images and show me simple text and gives me the following Exception on error_logs and similar kind of exceptions
[error] [client 192.217.71.77] File does not exist: /usr/local/apache2/htdocs/application, referer: http://192.168.141.17/application/faces/test.jsp
Interestingly, when I access the application without load balancer, it also works fine.
Which Event Handler gets fired when a subscription is created? I've tried both "Hosting settings created" and "Default domain (the first domain added to a subscription/webspace) created" but those don't seem to be firing when I create a new subscription. After creating the Event Handler the psa service was restarted each time. I have a script setup to just log the NEW_DOMAIN_NAME to a file, but that isn't happening.
I normally protect a given directory in the Plesk Contral Panel with a Username / Password. I would like to bypass the username and password for visitors from one IP.
Unable to read apache features from the service node: [Sat Jan 10 12:25:03.013856 2015] [so:warn] [pid 32541] AH01574: module actions_module is already loaded, skipping [Sat Jan 10 12:25:03.014058 2015] [so:warn] [pid 32541] AH01574: module auth_digest_module is already loaded, skipping [Sat Jan 10 12:25:03.014694 2015] [so:warn] [pid 32541] AH01574: module authz_user_module is already loaded, skipping
When I try to migrate from old server to new server, I get this error:
Warning: Deployer has been terminated by exception: Line 471 error: Element 'certificates': This element is not expected. Expected is one of ( sb-config, backup-settings, server-preferences, spamassassin, grey-listing, virusfilter, kav-settings, coldfusion, gapps-services, events ).
I have just upgraded linux VPS running ubuntu 10. I installed all of the latest plesk updates first and then went through the upgrade. There were no pre-upgrade warnings and message at the end said it was successful but i'm now getting the following error instead of the login page:
I'm currently experiencing a lot of problems, using Horde. Users are not able to log-in due to this error:
Code:
2014-10-09T10:00:54+02:00 EMERG: HORDE Uncaught exception 'Horde_Exception_PushApp' with message 'User xxx@yyy.tld is not authorized for Horde.' in /usr/share/psa-pear/pear/php/Horde/Registry.php:1555 Stack trace: #0 /usr/share/psa-pear/pear/php/Horde/Registry.php(1198): Horde_Registry->pushApp('horde', Array)
[Code] .....
I've already tried re-installing Horde, but without success.
There's an article in your KB, but `/var/lib/php/session` does not exist and `/var/lib/php5/sessions` has the required perms.
I've also tried to set session.save_path to `/var/lib/php5/sessions` in `/etc/psa-webmail/horde/horde/php.ini` and after a restart, sessions are written into that directory. But the problem still exists.
Code: _b|i:1412842564;_r|i:1412864164;horde|a:25:{s:11:"auth/authId";s:13:" xxx@yyy.tld";s:12:"auth/browser";s:110:" Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.101 Safari/537.36";s:16:"auth/credentials";s:4:" imp";s:15:"auth/remoteAddr";s:15:" my.ip.addr.ess";s:11:"auth/userId";s:13:"
I created a new 'Hosting settings created' event running as root and with the highest priority with this command: /var/www/move_some_files.sh
I created a new customer with to test it
But, is not running the script! If I try some command directly on the event like 'touch /var/www/new_file' it's created, so the event is running, but not my script.
Seems everythings is working normal when ignoring following error message, but everytime I add or change mail settings for a domain, I am getting this error:
Internal error.
ERROR: Uncaught exception 'Zend_Log_Exception' with message '"/var/log/plesk/panel.log" cannot be opened with mode "a"' in /usr/local/psa/admin/externals/Zend/Log/Writer/Stream.php:81 Stack trace: #0 /usr/local/psa/admin/plib/Plesk/Log.php(69): Zend_Log_Writer_Stream->__construct
PROBLEM DESCRIPTION When triggering the events 'Mail account created' or 'Mail account modified' the returned variable NEW_MAILBOX will always state TRUE regardless of the mailbox option being ticked or not ticked on the 'New mail account' option located on the 'Mail' tab of a subscription.
STEPS TO REPRODUCE 1: Log in to plesk. 2. Select 'Tools & Settings' 3: Select 'Event Manager' 4: Select 'Add New Event Handler' 5: Select Event 'Mail account updated' 6: Enter in '/usr/bin/php /root/scripts/dbmail/mail_mod.php' to the Command box.
[Code] ....
ACTUAL RESULT
[NEW_MAILBOX] => true
EXPECTED RESULT
[NEW_MAILBOX] => false
ANY ADDITIONAL INFORMATION
I submitted this with parallels support and they stated that the variable NEW_MAILBOX will always return as TRUE regardless of if the mailbox option is ticked or not. They also stated the NEW_MAILBOX variable will be true regardless of any action taken on the panel with mail accounts. The actual documentation on this variable is very sparse
Component name/description Old component value New component value Mailbox old_mailbox new_mailbox
We previously had some code that would trigger on this variable and would create a mail account on our mail server with or without a mailbox.
if (!strcmp(getenv('NEW_MAILBOX'),"true") && !strcmp(getenv('OLD_MAILBOX'),"false")){ //Create a mailbox on the external mail service } if (!strcmp(getenv('NEW_MAILBOX'),"false") && !strcmp(getenv('OLD_MAILBOX'),"true")){ //Create a mail forwarder on the external mail service }
At some point this variable has stopped working with newer versions of plesk. Having a variable that is always true regardless of what is done when creating a mail account seems pointless and requesting a new feature that was already there in older versions doesnt seem like something that should be requested on a new feature request.
QUESTION: Is there anyway to get this functionality restored other than requesting it gets re added via [URL] ....
I am running Plesk 11.5.30 on CentOS and trying to change the default permissions of the /httpdocs folder and the skeleton site that is in .skel/0/httpdocs that appears when a domain is created. I have failed to find the event that I need to use to trigger the command.
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.