I have compiled an fastcgid example program along-with libfcgid files using visual studio 10 compiler. The exe file works correctly. But when I try to open the exe file using a browser through apache server, after much delay the following is displayed in the browser.
Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
The apache log file contains the following errors:
[error] (OS 2)The system cannot find the file specified. : mod_fcgid: can't run C:/Program
[warn] (OS 2)The system cannot find the file specified. : mod_fcgid: spawn process C:/Program Files/Apache Software Foundation/Apache2.2/htdocs/test/fcgitest.exe error
[warn] [client 127.0.0.1] mod_fcgid: can't apply process slot for C:/Program Files/Apache Software Foundation/Apache2.2/htdocs/test/fcgitest.exe
I have noticed the error occurs when I include the following line in httpd.conf
SetHandler fcgid-script
Can anyone help me solve this issue? Thanks in advance.
Initially, I installed apache in path 'C:program files'. It has a space character in path. It was the reason for this error. So I uninstalled apache and re-installed in c drive so that the installation folder is C:apache2.2. This solved the error.
Related
I have to migrate my prestashop 1.7 to another sever because the OVH crash.
but i have blank page in back and front office.
No error display with debug mode.
PHP version : 7.1 (apache server with plesk)
any idea ?
warning :
mod_fcgid: stderr: PHP Warning: include(): Failed opening '/var/www/vhosts/xxxxx.be/httpdocs/vendor/composer/../psr/log/Psr/Log/LogLevel.php' for inclusion (include_path='/var/www/vhosts/xxxxx.be/httpdocs/tools/htmlpurifier/standalone:/var/www/vhosts/xxxxx.be/httpdocs/vendor/pear/pear_exception:/var/www/vhosts/xxxxx.be/httpdocs/vendor/pear/console_getopt:/var/www/vhosts/xxxxx.be/httpdocs/vendor/pear/pear-core-minimal/src:/var/www/vhosts/xxxxx.be/httpdocs/vendor/pear/archive_tar:.:/opt/plesk/php/7.1/share/pear') in /var/www/vhosts/xxxxx.be/httpdocs/vendor/composer/ClassLoader.php on line 444
mod_fcgid: stderr: PHP Fatal error: Class 'Psr\Log\LogLevel' not found in /var/www/vhosts/xxxxx.be/httpdocs/vendor/symfony/symfony/src/Symfony/Component/Debug/Debug.php on line 56
mod_fcgid: stderr: PHP Warning: include(/var/www/vhosts/xxxxx.be/httpdocs/vendor/composer/../psr/log/Psr/Log/LogLevel.php): failed to open stream: No such file or directory in /var/www/vhosts/xxxxx.be/httpdocs/vendor/composer/ClassLoader.php on line 444
What version of Prestashop ?
The error is clear, a core Prestashop file is missing :
/vendor/psr/log/Psr/Log/LogLevel.php
You have to restore it by taking it from the ZIP of the same version.
My two cents: you are restoring on a backup where "log*" was excluded and this caused the files containing the word log not to be backed up... so check that everything else is intact!
While upgrading my Artifactory server (free OSS version) from the version 5.2.0 to the latest 5.4.5, I was hit by an ARTIFACTORY_PID problem.
After migrating from 5.3.2 to 5.4.0, the Artifactory server did not want to start anymore complaining about
PID file /var/opt/jfrog/run/artifactory.pid not readable (yet?) after start.
I found the only way around it is to remove the line export CATALINA_PID=$ARTIFACTORY_PID from the setenv.sh of the tomcat.
Note that upgrade from 5.2.0 to 5.3.2 went smoothly.
However, after upgrading from 5.4.0 to the latest 5.4.5 this trick does not work anymore. Now I get an error:
Job for artifactory.service failed because a configured resource limit was exceeded. See "systemctl status artifactory.service" and "journalctl -xe" for details.
And when executing service artifactory status, I get:
● artifactory.service - Setup Systemd script for Artifactory in Tomcat Servlet Engine
Loaded: loaded (/usr/lib/systemd/system/artifactory.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: resources) since Tue 2017-07-25 09:40:10 CEST; 4s ago
Process: 31912 ExecStart=/opt/jfrog/artifactory/bin/artifactoryManage.sh start (code=exited, status=0/SUCCESS)
Jul 25 09:40:10 linux systemd[1]: Failed to start Setup Systemd script for Artifactory in Tomcat Servlet Engine.
Jul 25 09:40:10 linux systemd[1]: Unit artifactory.service entered failed state.
Jul 25 09:40:10 linux systemd[1]: artifactory.service failed.
In fact Artifactory is now running showing version 5.4.5, but I am not happy about all those errors above.
Plus I am a bit failing to understand the purpose of CATALINA_PID and/or ARTIFACTORY_PID. Why the tomcat was failing on the startup because of this file? What was wrong with the permissions? I think I did no extra actions before.
The only difference that before it was installed from an official downloaded rpm. But now using an official remote yum repo.
If I try to create an empty /var/opt/jfrog/run/artifactory.pid file, while Artifactory is running, it gets deleted. Who is deleting this file and why? Is it a standard tomcat behavior?
OS: CentOS 7, up to date.
In my case (in a slow virtual machine) the error message from the command artifactoryManage.sh start was:
ERROR: Artifactory Tomcat server did not start in 60 seconds. Please check the logs
The log file told that the only problem was slowness (/var/opt/jfrog/artifactory/logs/artifactory.log):
### Artifactory successfully started (64.802 seconds) ###
The problem was solved by adding a longer timeout to the service definition at /etc/systemd/system/artifactory.service:
[Service]
Environment=START_TMO=120
After editing the service definition, as you know, systemctl daemon-reload was needed.
Run this script:
/opt/jfrog/artifactory/bin/artifactoryManage.sh start
It will show the exact error to you.
In my case it was java version not updated. So I updated to java 1.8.
I have encountered a problem with running Jboss as service on Fedora. Here is the log I have after using command: systemctl status jboss-as.service
Here is the log I have been receiving:
jboss-as.service - SYSV: JBoss AS Standalone
Loaded: loaded (/etc/rc.d/init.d/jboss-as)
Active: failed (Result: resources) since Thu 2014-01-16 09:31:54 CET; 46min ago
Process: 501 ExecStart=/etc/rc.d/init.d/jboss-as start (code=exited, status=0/SUCCESS)
Jan 16 09:31:22 servername.domain systemd[1]: Starting SYSV: JBoss AS Standalone...
Jan 16 09:31:23 servername.domain jboss-as[501]: Starting jboss-as: chown: missing operand after ‘/var/run/jboss-as’
Jan 16 09:31:23 servername.domain jboss-as[501]: Try 'chown --help' for more information.
Jan 16 09:31:54 servername.domain jboss-as[501]: [ OK ]
Jan 16 09:31:54 servername.domain systemd[1]: PID file /var/run/jboss-as/jboss-as-standalone.pid not readable (yet?) after start.
Jan 16 09:31:54 servername.domain systemd[1]: Failed to start SYSV: JBoss AS Standalone.
Jan 16 09:31:54 servername.domain systemd[1]: Unit jboss-as.service entered failed state.
First, I tried to find a solution for the chown: missin operand after ... problem and found something: here but it did not help. And also, I was looking for the answer for the PID file problem but it does not even exist in in the location: var/run/jboss-as/
This is because the startup script uses the variable $JBOSS_USER but it is not defined inside the script.
Please put in the file /etc/jboss-as/jboss-as.conf the following line:
JBOSS_USER=root
(change the root with other dedicated linux user e.g. jboss-as)
It looks like the service startup script expects to be able to write to the /var/run/jboss-as directory but doesn't have permissions to do so.
In your place I'd ensure that this directory is owned by the user that runs JBoss and that it is writable.
Check that there aren't other errors (particularly missing or incorrect paths) in your /etc/rc.d/init.d/jboss-as file (I assume you copied it from the jboss install folder to create a startup script.
I had the same issue until I fixed a completely unrelated link in that script, then it went away.
In Centos 7, if you straight way copying the jboss-as-standalone.sh in /etc/rc.d/init.d/, ensure JBOSS_CONF and JBOSS_HOME path is correct.
For me, it was with systemd. When I set the service y put wrong the PID File.
Example:
In the service was like
/var/run/jboss-as/jboss-as-standalone.pid
But in the script was like
/var/run/jboss-as/jboss-as.pid
Very strange errors in my apache log on a new server, obviously I have no *.php file.
[Mon Feb 18 08:02:32 2013] [error] [client ::1] script '/var/www/html/*.php' not found or unable to stat
Suggestions are welcome.
Unable to stat just means the file doesn't exist.
Check your code, and make sure there's no place trying to require this *.php. It's somewhat hard to debug without any actual code.
I have an Apache tomcat 7.0.5 Server on a Windows R2 Server and I've deployed a webApp ( java JSF) on it, everything was working fine, but it suddenly stopped and won't run again. when I try to run it, it tells me "Error 1067: The Process terminated unexpectedly" and In the logs I get these files:
tomcat7-stdout.2012-08-08.log
2012-08-08 18:00:06 Commons Daemon procrun stdout initialized
commons-daemon.2012-08-08.log
[2012-08-08 19:02:30] [info] Commons Daemon procrun finished
[2012-08-08 19:13:02] [info] Commons Daemon procrun (1.0.4.0 64-bit) started
[2012-08-08 19:13:02] [info] Running 'Tomcat7' Service...
[2012-08-08 19:13:02] [info] Starting service...
[2012-08-08 19:13:02] [error] CreateJavaVM Failed
[2012-08-08 19:13:03] [info] Service started in 1000 ms.
[2012-08-08 19:13:03] [info] Run service finished.
[2012-08-08 19:13:03] [info] Commons Daemon procrun finished
tomcat7-stderr.2012-08-08.log
2012-08-08 18:00:06 Commons Daemon procrun stderr initialized
Please use CMSClassUnloadingEnabled in place of CMSPermGenSweepingEnabled in the future
Unrecognized VM option '+HeapDumpOnOutOfMemoryError '
since I was having some 'perm gen' memory error I added some stuff to my apache Tomcat properties, folowing this link how to handle Perm Gen
so my Java Options look like this:
-Dcatalina.home=C:\Program Files\Apache Software Foundation\Tomcat 7.0
-Dcatalina.base=C:\Program Files\Apache Software Foundation\Tomcat 7.0
-Djava.endorsed.dirs=C:\Program Files\Apache Software Foundation\Tomcat 7.0\endorsed
-Djava.io.tmpdir=C:\Program Files\Apache Software Foundation\Tomcat 7.0\temp
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=C:\Program Files\Apache Software Foundation\Tomcat 7.0\conf\logging.properties
-XX:+CMSClassUnloadingEnabled
-XX:+CMSPermGenSweepingEnabled
-XX:PermSize=256m
-XX:MaxPermSize=256m
-XX:+HeapDumpOnOutOfMemoryError
Any ideas as to why the server won't start anymore? THANKS!
~Myy
After spending hours trying to figure this out, I finally found it. I had an extra space at the end of VM command.
'+HeapDumpOnOutOfMemoryError '
which was giving me the Unrecognized VM option.....
Thanks for reading, hopefully when you get this error, you can take extra precautions to verify the syntax.
to manage the memory you need to set some Xms and Xmx parameter
Xms manages the initial heap size
Xmx manages the maximum heap size
Thus try to add :
-Xms=256m -Xmx=256m
regards
The error is on option "HeapDumpOnOutOfMemoryError" which is not even listed in your post. Can you post a screen print of the "Java" tab from the "tomcat" service screen (similar to the link you have provided) ? This will tell us the actual options you are using and also the memory you have set.
copy the file msvcr71.dll from the bin dir of your java installation, to the bin dir of the tomcat installation.