Unable to access WebGL app as Azure Web App - azure

I'm trying to deploy a Unity WebGL app to Azure to run as a Web App. But I cannot get the app to deploy. I am using the latest version of Unity (2022.1.3f1).
I have built the app, and here are the contents of my `Build`` directory:
# Build> ll
-rw-r--r-- 1 DKS0510862 staff 3664517 Jun 9 11:12 DSG Westy Unity PoC.data.gz
-rw-r--r-- 1 DKS0510862 staff 78822 Jun 9 11:14 DSG Westy Unity PoC.framework.js.gz
-rw-r--r--# 1 DKS0510862 staff 20484 Jun 9 11:09 DSG Westy Unity PoC.loader.js
-rw-r--r-- 1 DKS0510862 staff 7390463 Jun 9 11:14 DSG Westy Unity PoC.wasm.gz
In VS Code, I am navigating to the Build directory, right-clicking on the directory, and then selecting Deploy to Web App. I am logged in to Azure, and I am prompted to select the App Service that I created in Azure, so my connection is okay.
The deployment seems to have run successfully.
4:02:14 PM innovation-unity-poc-dev: Starting deployment...
4:02:18 PM innovation-unity-poc-dev: Creating zip package...
4:02:22 PM innovation-unity-poc-dev: Zip package size: 10.9 MB
4:02:24 PM innovation-unity-poc-dev: Updating submodules.
4:02:24 PM innovation-unity-poc-dev: Preparing deployment for commit id '38620705e7'.
4:02:24 PM innovation-unity-poc-dev: Generating deployment script.
4:02:24 PM innovation-unity-poc-dev: Using the following command to generate deployment script: 'azure site deploymentscript -y --no-dot-deployment -r "C:\local\Temp\zipdeploy\extracted" -o "C:\home\site\deployments\tools" --basic --sitePath "C:\local\Temp\zipdeploy\extracted"'.
4:02:26 PM innovation-unity-poc-dev: Generating deployment script for Web Site
4:02:27 PM innovation-unity-poc-dev: Generated deployment script files
4:02:27 PM innovation-unity-poc-dev: Running deployment command...
4:02:27 PM innovation-unity-poc-dev: Command: "C:\home\site\deployments\tools\deploy.cmd"
4:02:30 PM innovation-unity-poc-dev: Handling Basic Web Site deployment.
4:02:30 PM innovation-unity-poc-dev: Creating app_offline.htm
4:02:30 PM innovation-unity-poc-dev: KuduSync.NET from: 'C:\local\Temp\zipdeploy\extracted' to: 'C:\home\site\wwwroot'
4:02:30 PM innovation-unity-poc-dev: Deleting file: 'hostingstart.html'
4:02:30 PM innovation-unity-poc-dev: Copying file: 'DSG Westy Unity PoC.data.gz'
4:02:30 PM innovation-unity-poc-dev: Copying file: 'DSG Westy Unity PoC.framework.js.gz'
4:02:30 PM innovation-unity-poc-dev: Copying file: 'DSG Westy Unity PoC.loader.js'
4:02:30 PM innovation-unity-poc-dev: Copying file: 'DSG Westy Unity PoC.wasm.gz'
4:02:30 PM innovation-unity-poc-dev: Deleting app_offline.htm
4:02:30 PM innovation-unity-poc-dev: Finished successfully.
4:02:30 PM innovation-unity-poc-dev: Running post deployment command(s)...
4:02:30 PM innovation-unity-poc-dev: Triggering recycle (preview mode disabled).
4:02:30 PM innovation-unity-poc-dev: Deployment successful.
4:03:18 PM: Deployment to "innovation-unity-poc-dev" completed.
However, when I try to connect to the app, in the browser I am seeing the error message "You do not have permission to view this directory or page".
I see the following in the Web Server logs, but these don't appear to be error messages.
022-06-09 20:08:09 ~1INNOVATION-UNITY-POC-DEV GET /api/logstream/http X-ARR-LOG-ID=bba7b8a4-5d1e-4616-8f43-5237acd8a969 443 - 199.30.194.254 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_15_7)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/102.0.5005.61+Safari/537.36 - - innovation-unity-poc-dev.scm.azurewebsites.net 200 0 64 2729 1541 180037
2022-06-09 20:08:20 INNOVATION-UNITY-POC-DEV GET / X-ARR-LOG-ID=628fa657-ed76-4252-a55d-c15b3f4150cf 443 - 199.30.194.254 Mozilla/5.0+(Macintosh;+Intel+Mac+OS+X+10_15_7)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/102.0.5005.61+Safari/537.36 ARRAffinity=22a7daa836b64a8ce56c907737553d08297ff2e76cd06a1f52c29956b9a85c17;+ARRAffinitySameSite=22a7daa836b64a8ce56c907737553d08297ff2e76cd06a1f52c29956b9a85c17 - innovation-unity-poc-dev.azurewebsites.net 403 14 0 422 1626 62
The only entry I am seeing in the Application Logs is a request to the logstream API.
I have no idea where to look to do any more troubleshooting. Is there some way I can see what the filesystem looks like for the app, to see if my files were deployed correctly?

Related

Azure functions on Premises - Error response from daemon: Cannot kill container

I am working with Azure Functions on Premises V2 (Runtime).
Trying to test a simple function that is executed each minute and write in logs.
However Function is not executed, and I am getting this error.
It is running on a Virtual Machine with Windows server 2016.
(what I think could be causing this problem).
I am new wiht Docker and Hyper-V, any help will be appreciated.
There are some command lets I can execute, to comprobate if Hyper V and
Docker are running well ?
Thank You in Advance.
This is the Log I'm getting.
3/14/2018 5:42:44 PM Welcome, you are now connected to log-streaming service.3/14/2018 5:41:48 PM [myteslaVM] Function App 'MyContainerFuncApp' is starting...3/14/2018 5:41:49 PM [myteslaVM] Pull container image azfuncrun/azure-functions-runtime:preview2-latest-nanoserver3/14/2018 5:41:50 PM [myteslaVM] preview2-latest-nanoserver: Pulling from azfuncrun/azure-functions-runtime3/14/2018 5:41:50 PM [myteslaVM] Digest: sha256:dfdb47a7638d0cdd1a42c603e3e59311ee0d229222f88329a7c561fc3d8b2ff33/14/2018 5:41:50 PM [myteslaVM] Status: Image is up to date for azfuncrun/azure-functions-runtime:preview2-latest-nanoserver
3/14/2018 5:41:50 PM [myteslaVM] The container image azfuncrun/azure-functions-runtime:preview2-latest-nanoserver has been pulled successfully!
3/14/2018 5:41:50 PM [myteslaVM] Provisioning container MyContainerFuncApp_03/14/2018 5:41:51 PM [myteslaVM] f2788b6c9c5d6115bba891f463759dd0df75c2344e6c217b0280a8b9f686fb32
3/14/2018 5:41:51 PM [myteslaVM] C:\Program Files\Azure Functions Runtime\docker\docker.exe: Error response from daemon: container f2788b6c9c5d6115bba891f463759dd0df75c2344e6c217b0280a8b9f686fb32
encountered an error during CreateContainer: failure in a Windows system call: No hypervisor is present on this system. (0xc0351000) extra info: {"SystemType":"Container","Name":"f2788b6c9c5d6115bba891f463759dd0df75c2344e6c217b0280a8b9f686fb32","Owner":"docker","IgnoreFlushesDuringBoot":true,"LayerFolderPath":"C:\\Program Files\\Azure Functions Runtime\\docker\\windows\\windowsfilter\\f2788b6c9c5d6115bba891f463759dd0df75c2344e6c217b0280a8b9f686fb32","Layers":[{"ID":"951f96e7-ad8c-5e5c-8533-4f70d49a4e6a","Path":"C:\\Program Files\\Azure Functions
"HostName":"f2788b6c9c5d","MappedDirectories":[{"HostPath":"c:\windows\temp\fwas\mycontainerfuncapp","ContainerPath":"c:\home","ReadOnly":false,"BandwidthMaximum":0,"IOPSMaximum":0,"CreateInUtilityVM":false}],"HvPartition":true,"EndpointList":["d6c4c527-5520-40f1-9c84-2f3d8a013900"],"HvRuntime":{"ImagePath":"C:\Program Files\Azure Functions Runtime\docker\windows\windowsfilter\545c1be2ad30f1933a07de48e4ffe611900bacafbf4b717de969b56fb8a725d6\UtilityVM"},"AllowUnqualifiedDNSQuery":true}.
3/14/2018 5:41:51 PM [myteslaVM] Issuing stop command to container: MyContainerFuncApp_
03/14/2018 5:41:52 PM [myteslaVM] Error response from daemon: Cannot kill container: MyContainerFuncApp_0: No such container: MyContainerFuncApp_03/14/2018 5:41:52 PM [myteslaVM] Stop complete for container: MyContainerFuncApp_03/14/2018 5:41:52 PM [myteslaVM] ExecuteCommand called with C:\Program Files\Azure Functions Runtime\docker\docker.exe returned 125.3/14/2018 5:42:03 PM [myteslaVM]
Function App 'MyContainerFuncApp' is starting...3/14/2018 5:42:04 PM [myteslaVM] Pull container image azfuncrun/azure-functions-runtime:preview2-latest-nanoserver3/14/2018 5:42:06 PM [myteslaVM] preview2-latest-nanoserver: Pulling from azfuncrun/azure-functions-runtime3/14/2018 5:42:06 PM [myteslaVM] Digest: sha256:dfdb47a7638d0cdd1a42c603e3e59311ee0d229222f88329a7c561fc3d8b2ff3
3/14/2018 5:42:06 PM [myteslaVM] Status: Image is up to date for azfuncrun/azure-functions-runtime:preview2-latest-nanoserver3/14/2018 5:42:06 PM [myteslaVM] The container image azfuncrun/azure-functions-runtime:preview2-latest-nanoserver has been pulled successfully!3/14/2018 5:42:06 PM [myteslaVM] Provisioning container MyContainerFuncApp_13/14/2018 5:42:07 PM [myteslaVM] 10dfbab15acef64780c34d5d01ded776a10d074500b33ba916b032920404d1d13/14/2018 5:42:07 PM [myteslaVM] C:\Program Files\Azure Functions Runtime\docker\docker.exe:
Researching more on the subject, I realized that it does not work for Basic Plan (SKU) for
virtual Machines.
Only works for SKU in Standard plan.
Applies for both Windows Pro and Windows Server 2016.
After some research I did next steps in order to try to resolve this error.
1.Windows Server 2016 Configuration
https://app.pluralsight.com/player?course=installing-windows-server-2016&author=greg-shields&name=installing-windows-server-2016-m2&clip=5&mode=live
--Install Features and Roles.
2.Install Hyper-V
https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/get-started/install-the-hyper-v-role-on-windows-server
To check Hyper-V installed, run this cmd let in Power Shell.
Get-WindowsFeature -ComputerName <computer_name>
Get-WindowsFeature -ComputerName MyteslaVM
To Install Hyper-V
Add-WindowsFeature –name RSAT-Hyper-V-Tools
https://social.technet.microsoft.com/Forums/windows/en-US/f750d5e3-69f8-4cbd-a7aa-98e2fd41c618/need-to-install-hyperv-management-tools-on-server-2012-vm?forum=winserverhyperv
3.Execute Docker version.
4.Execute Dockerd "Daemon" .
https://www.bountysource.com/issues/40602674-can-t-start-docker-service-on-windows-server-vm
dockerd --debug
Stop-service docker
Get-ContainerNetwork | Remove-ContainerNetwork -Force
Start-service docker
5.
Get-VM | Set-VMProcessor -ExposeVirtualizationExtensions $true
https://github.com/Azure/Azure-Functions/issues/359
6.Install Docker
https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/quick-start-windows-server
Install-Module -Name DockerMsftProvider -RequiredVersion 1.0.0.3
Install-Module -Name DockerMsftProvider -Repository PSGallery -Force
Install-Package -Name docker -ProviderName DockerMsftProvider
7.Install The latest azure-functions-core-tools:
npm i -g azure-functions-core-tools#core
Run npm i -g npm **to update
Install .NET Core 2.0
https://www.microsoft.com/net/download/windows
9.To enable nested virtualization, you need to run the following cmdlet in the Hyper-V host:
Get-VM | Set-VMProcessor -ExposeVirtualizationExtensions $true
10.Run Script
https://github.com/moby/moby/issues/19685
11.Download azure-functions-runtime:2.0.0-nanoserver
docker pull microsoft/azure-functions-runtime:2.0.0-nanoserver-1709
12.One of the Hyper-V components is not running
https://social.technet.microsoft.com/Forums/en-US/b4d0761d-6048-4cb8-9a1f-1a2544b4ceb2/one-of-the-hyperv-components-is-not-running?forum=win10itprovirt
13.Disable Windows defender.
https://www.windowscentral.com/how-permanently-disable-windows-defender-windows-10
It seems as Azuer Function runtime component is not working for Windows Server 2016,
because containers.
I tried it with a new Virtual Machine, with Windows 10 Pro. And it is now working.
Steps:
Create Virtual Machine, with Windows 10 Pro
Install/enable Hyper-V
Install and configure Component for Azure Functions.
see image for Azure Function Running

Unable to connect to artifactory after service restart on CentOS7

I'm a total linux newbie and I'll drop the story here so hopefully someone knows what's going on.
I have a linux box running CentOS and I have artifactory running as a service. After I restarted the server everything started back up but I'm no longer able to connect to artifactory. I checked the artifactory log and everything says it started fine
artifactory.log
2017-02-09 22:15:12,149 [art-init] [INFO ] (o.a.s.ArtifactoryApplicationContext:360) - Artifactory application context is ready.
2017-02-09 22:15:12,152 [art-init] [INFO ] (o.a.w.s.ArtifactoryContextConfigListener:225) -
###########################################################
### Artifactory successfully started (7.122 seconds) ###
###########################################################
Then I checked the tomcat log to make sure that that started fine
catalina.log
INFO: Starting service Catalina
Feb 09, 2017 10:25:42 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.56
Feb 09, 2017 10:25:42 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor /opt/jfrog/artifactory/tomcat/conf/Catalina/localhost/artifactory.xml
Feb 09, 2017 10:25:47 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deployment of configuration descriptor /opt/jfrog/artifactory/tomcat/conf/Catalina/localhost/artifactory.xml has finished in 4,865 ms
Feb 09, 2017 10:25:47 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/jfrog/artifactory/tomcat/webapps/ROOT
Feb 09, 2017 10:25:47 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /opt/jfrog/artifactory/tomcat/webapps/ROOT has finished in 246 ms
Feb 09, 2017 10:25:47 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8081"]
Feb 09, 2017 10:25:47 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8019"]
I'm at a point where I'm not even sure what to check. When I try to connect to the page I just get the "The Connection has time out".
If anyone knows anything I can check I'd be extremely grateful.
edit:
Running a netstat -tulnp it shows the ports as open
tcp6 0 0 127.0.0.1:8015 :::* LISTEN 3538/java
tcp6 0 0 :::8081 :::* LISTEN 3538/java
tcp6 0 0 :::8019 :::* LISTEN 3538/java
Turns out I had a firewall on.
Since this is an internal site I disabled it by
systemctl stop firewalld
Would it be worth my time to just allow those ports access?

Docker volumes on CentOS 7

I have run into a problem on CentOS 7 when attempting to map a volume to the host in a tomcat container. This happens with the public tomcat images as well as an image I have created (based on centos instead of debian).
instantiating a container as follows will succeed:
docker run -it -d tomcat:8
instantiating a container as follows will succeed, but with errors in the log and logs are not written to the host:
docker run -it -d -v /usr/local/tomcat:/usr/local/tomcat tomcat:8
[wpackard#eagle2 tomcat]$ dkr run -it -d -v
/usr/local/tomcat:/usr/local/tomcat tomcat:8
34075701b1436f83a24212170b4d2113ae698df244c449203b1c9af9814485c9
[wpackard#eagle2 tomcat]$ dkr ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
34075701b143 tomcat:8 "catalina.sh run" 5 seconds ago Up 4 seconds 8080/tcp sharp_einstein
[wpackard#eagle2 tomcat]$ dkr logs sharp_einstein
Using CATALINA_BASE: /usr/local/tomcat
Using CATALINA_HOME: /usr/local/tomcat
Using CATALINA_TMPDIR: /usr/local/tomcat/temp
Using JRE_HOME: /usr
Using CLASSPATH: /usr/local/tomcat/bin/bootstrap.jar:/usr/local/tomcat/bin/tomcat-juli.jar
java.util.logging.ErrorManager: 4
java.io.FileNotFoundException: /usr/local/tomcat/logs/catalina.2015-03-31.log (Permission denied)
...
31-Mar-2015 15:32:04.088 SEVERE [Catalina-startStop-1] org.apache.catalina.startup.HostConfig.start Unable to create directory for deployment: /usr/local/tomcat/conf/Catalina/localhost
31-Mar-2015 15:32:04.097 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory /usr/local/tomcat/webapps/ROOT
31-Mar-2015 15:32:04.468 WARNING [localhost-startStop-1] org.apache.catalina.core.StandardContext.postWorkDirectory Failed to create work directory [/usr/local/tomcat/work/Catalina/localhost/ROOT] for context []
31-Mar-2015 15:32:05.966 SEVERE [localhost-startStop-1] org.apache.jasper.EmbeddedServletOptions.<init> The scratchDir you specified: /usr/local/tomcat/work/Catalina/localhost/ROOT is unusable.
31-Mar-2015 15:32:06.042 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory /usr/local/tomcat/webapps/ROOT has finished in 1,929 ms
31-Mar-2015 15:32:06.043 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory /usr/local/tomcat/webapps/docs
31-Mar-2015 15:32:06.093 WARNING [localhost-startStop-1] org.apache.catalina.core.StandardContext.postWorkDirectory Failed to create work directory [/usr/local/tomcat/work/Catalina/localhost/docs] for context [/docs]
31-Mar-2015 15:32:06.216 SEVERE [localhost-startStop-1] org.apache.jasper.EmbeddedServletOptions.<init> The scratchDir you specified: /usr/local/tomcat/work/Catalina/localhost/docs is unusable.
31-Mar-2015 15:32:06.219 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory /usr/local/tomcat/webapps/docs has finished in 176 ms
31-Mar-2015 15:32:06.220 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory /usr/local/tomcat/webapps/examples
31-Mar-2015 15:32:06.272 WARNING [localhost-startStop-1] org.apache.catalina.core.StandardContext.postWorkDirectory Failed to create work directory [/usr/local/tomcat/work/Catalina/localhost/examples] for context [/examples]
31-Mar-2015 15:32:07.952 SEVERE [localhost-startStop-1] org.apache.jasper.EmbeddedServletOptions.<init> The scratchDir you specified: /usr/local/tomcat/work/Catalina/localhost/examples is unusable.
[wpackard#eagle2 tomcat]$
Exec'ing to the container and attempting to write also fails.
[wpackard#eagle2 tomcat]$ dkr ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
34075701b143 tomcat:8 "catalina.sh run" 5 minutes ago Up 5 minutes 8080/tcp sharp_einstein
[wpackard#eagle2 tomcat]$ dkr exec -it sharp_einstein /bin/bash
root#34075701b143:/usr/local/tomcat# ls -l
total 96
-rw-rw-r--. 1 root root 56977 Jan 23 11:59 LICENSE
-rw-rw-r--. 1 root root 1397 Jan 23 11:59 NOTICE
-rw-rw-r--. 1 root root 6779 Jan 23 11:59 RELEASE-NOTES
-rw-rw-r--. 1 root root 16204 Jan 23 11:59 RUNNING.txt
drwxrwxr-x. 2 root root 4096 Mar 31 12:14 bin
drwxrwxr-x. 2 root root 4096 Jan 23 11:59 conf
drwxrwxr-x. 2 root root 4096 Mar 31 12:14 lib
drwxrwxr-x. 2 root root 6 Jan 23 11:56 logs
drwxrwxr-x. 2 root root 29 Mar 31 12:14 temp
drwxrwxr-x. 7 root root 76 Jan 23 11:57 webapps
drwxrwxr-x. 2 root root 6 Jan 23 11:56 work
root#34075701b143:/usr/local/tomcat# cd logs
root#34075701b143:/usr/local/tomcat/logs# echo "test" > test.log
bash: test.log: Permission denied
I have created an instance of the postgresql container on centos and that successfully maps and uses the volume, verified by creating a db, stopping the instance and then re-running the container.
[wpackard#eagle2 ~]$ uname --all
Linux eagle2 3.10.0-123.20.1.el7.x86_64 #1 SMP Thu Jan 29 18:05:33 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[wpackard#eagle2 ~]$
dkr is an alias to docker, I have created a docker group and added myself to the group to eliminate the need for sudo.
The volume mapping seems to work correctly on ubuntu. On CentOS I have tried both the package version (as below), and also updating it to 1.5.
[wpackard#eagle2 ~]$ dkr --version
Docker version 1.3.2, build 39fa2fa/1.3.2
[wpackard#eagle2 ~]$
How do I make volumes work on CentOS?
I think your volumes are working :-) You have a permission problem. I run into this fairly often with the mapping of user id between the host and the container. On your host, if you look at /usr/local/tomcat (ls -ld), you will see a owner, group and the permissions. You probably have something like 0755 (read/write/exec by owner, read/exec by group, read/exec by world. You can test this theory easily, simple remember the current settings for /usr/local/tomcat/logs, then do:
chmod 777 /usr/local/tomcat/logs
from the docker host (not the container). Then run your test on the container, the Permission denied should evaporate.
This is NOT a good fix, though. I don't know what the community says about user id mapping for docker. One thing you could do is figure out the user and group in your host for that directory. Then, when you create your image (or at run time) create a user with the same id and a group with the same id in the container. Then run your tomcat service using that user in the container.
This is due to SELinux.
You must attach correct type to host directory:
host$ chcon -Rt svirt_sandbox_file_t /usr/local/tomcat

Nothing happens when I tried to run liferay 6.1.1. on a existing Tomcat 7 server

Any help will be welcome.
I followed this tutorial steps, trying to run liferay 6.1.1. on a existing tomcat, but nothing happens when I launch tomcat server.
Server's log message (see), seems to be normal, but every tomcat default app is loaded, except liferay's war file. When I hit localhost:8080/, all I receive is a nice 404 status!
//Tomcat logs:
Nov 14, 2012 3:10:22 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /Users/cbs_sp/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.
Nov 14, 2012 3:10:23 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Nov 14, 2012 3:10:23 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Nov 14, 2012 3:10:23 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1991 ms
Nov 14, 2012 3:10:23 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Nov 14, 2012 3:10:23 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.32
Nov 14, 2012 3:10:23 PM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor /Cesar/Profissional/Projetos/Meu/Java/Liferay/Server/liferay_home/apache-tomcat-7.0.32/conf/Catalina/localhost/ROOT.xml
Nov 14, 2012 3:10:26 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /Cesar/Profissional/Projetos/Meu/Java/Liferay/Server/liferay_home/apache-tomcat-7.0.32/webapps/docs
Nov 14, 2012 3:10:26 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /Cesar/Profissional/Projetos/Meu/Java/Liferay/Server/liferay_home/apache-tomcat-7.0.32/webapps/examples
Nov 14, 2012 3:10:27 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /Cesar/Profissional/Projetos/Meu/Java/Liferay/Server/liferay_home/apache-tomcat-7.0.32/webapps/host-manager
Nov 14, 2012 3:10:27 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /Cesar/Profissional/Projetos/Meu/Java/Liferay/Server/liferay_home/apache-tomcat-7.0.32/webapps/manager
Nov 14, 2012 3:10:27 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Nov 14, 2012 3:10:27 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Nov 14, 2012 3:10:27 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 4691 ms
Any idea about what might be happening?
Or, where I can start?
Thanks in advance,
*** Additional info added ****
//Terminal:
[Cesars-Computer: apache-tomcat-7.0.32] $ cd webapps/
[Cesars-Computer: webapps] $ ls -la
total 0
drwxr-xr-x# 7 cbs_sp admin 238 Oct 3 04:52 .
drwxr-xr-x# 13 cbs_sp admin 442 Nov 7 17:09 ..
drwxr-xr-x# 4 cbs_sp admin 136 Nov 13 12:53 ROOT
drwxr-xr-x# 52 cbs_sp admin 1768 Oct 3 04:52 docs
drwxr-xr-x# 7 cbs_sp admin 238 Oct 3 04:52 examples
drwxr-xr-x# 7 cbs_sp admin 238 Oct 3 04:52 host-manager
drwxr-xr-x# 8 cbs_sp admin 272 Oct 3 04:52 manager
[Cesars-Computer: webapps] $ cd ROOT
[Cesars-Computer: ROOT] $ ls -la
total 348080
drwxr-xr-x# 4 cbs_sp admin 136 Nov 13 12:53 .
drwxr-xr-x# 7 cbs_sp admin 238 Oct 3 04:52 ..
-rw-r--r--# 1 cbs_sp admin 6148 Nov 13 12:53 .DS_Store
-rw-r--r--# 1 cbs_sp admin 178206477 Nov 7 14:46 liferay-portal-6.1.1-ce-ga2-20120731132656558.war
Solved!
If anyone faced this same problem, just change the name of the .war to ROOT.war, and put it under webapps/ directory, it will work fine!
And If you are following the steps from Liferay site, as I did. At some point the tutorial will tell you to create a ROOT.xml, when you do that, just add the Context parent node, which, until the moment I wrote this, was not mentioned in the tutorial example's snippet.
My ROOT.xml:
[Cesars-Computer: apache-tomcat-7.0.32] $ cd conf/Catalina/localhost/
[Cesars-Computer: localhost] $ cat ROOT.xml
<Context path="" crossContext="true">
</Context>
Thanks and success to everyone,

file upload in JSF using myfaces component

I am creating a JSF application where file uploading functionality is required.I have added all the required jar files in my /WEB-INF/lib folder.
jsf-api.jar
jsf-impl.jar
jstl.jar
standard.jar
myfaces-extensions.jar
commons-collections.jar
commons-digester.jar
commons-beanutils.jar
commons-logging.jar
commons-fileupload-1.0.jar
but still when trying to deploy the application on apache 6.0.29 i am getting the following error.
org.apache.catalina.core.StandardContext
addApplicationListener
INFO: The listener "com.sun.faces.config.ConfigureListener" is already
configured for this context. The duplicate definition has been ignored.
org.apache.catalina.core.StandardContext start
SEVERE: Error listenerStart
PM org.apache.catalina.core.StandardContext start
SEVERE: Context [/jsfApplication] startup failed due to previous errors
org.apache.catalina.loader.WebappClassLoader
clearReferencesJdbc
The web application [/jsfApplication] registered the JBDC driver
[com.mysql.jdbc.Driver] but failed to unregister it when the web
application was stopped. To prevent a memory leak, the JDBC Driver has been
forcibly unregistered.
org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [/jsfApplication] appears to have started a thread
named [Timer-0] but has failed to stop it. This is very likely to create a
memory leak.
org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [/jsfApplication] appears to have started a thread
named [MySQL Statement Cancellation Timer] but has failed to stop it. This
is very likely to create a memory leak.
log4j:ERROR LogMananger.repositorySelector was null likely due to error in
class reloading, using NOPLoggerRepository.
i am using also using hibernate and spring framework for this application.
please help.
thanks,
Update:
This is the complete error message which I am getting whenever I am adding myFaces-extension.jar file to my /WEB-INF/lib folder.
Using CATALINA_BASE: /home/prt/Desktop/apache-tomcat-6.0.29 Using CATALINA_HOME: /home/prt/Desktop/apache-tomcat-6.0.29 Using CATALINA_TMPDIR: /home/prt/Desktop/apache-tomcat-6.0.29/temp Using JRE_HOME: /usr/jdk1.6.0_20 Using CLASSPATH: /home/prt/Desktop/apache-tomcat-6.0.29/bin/bootstrap.jar 8 Jan, 2011 7:08:54 PM org.apache.catalina.core.AprLifecycleListener init INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/jdk1.6.0_20/jre/lib/i386/client:/usr/jdk1.6.0_20/jre/lib/i386:/usr/jdk1.6.0_20/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib 8 Jan, 2011 7:08:54 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 8 Jan, 2011 7:08:54 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 643 ms 8 Jan, 2011 7:08:54 PM org.apache.catalina.core.StandardService start INFO: Starting service Catalina 8 Jan, 2011 7:08:54 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.29 8 Jan, 2011 7:08:54 PM org.apache.catalina.startup.HostConfig deployDescriptor INFO: Deploying configuration descriptor host-manager.xml 8 Jan, 2011 7:08:55 PM org.apache.catalina.startup.HostConfig deployDescriptor INFO: Deploying configuration descriptor manager.xml 8 Jan, 2011 7:08:55 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive jsfApplication.war 8 Jan, 2011 7:08:55 PM org.apache.catalina.loader.WebappClassLoader validateJarFile INFO: validateJarFile(/home/prt/Desktop/apache-tomcat-6.0.29/webapps/jsfApplication/WEB-INF/lib/servlet-api.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class 8 Jan, 2011 7:08:55 PM org.apache.catalina.core.StandardContext addApplicationListener INFO: The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored. 8 Jan, 2011 7:08:58 PM org.apache.catalina.core.StandardContext start SEVERE: Error listenerStart 8 Jan, 2011 7:08:58 PM org.apache.catalina.core.StandardContext start SEVERE: Context [/jsfApplication] startup failed due to previous errors 8 Jan, 2011 7:08:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: The web application [/jsfApplication] registered the JBDC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. 8 Jan, 2011 7:08:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/jsfApplication] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak. 8 Jan, 2011 7:08:58 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/jsfApplication] appears to have started a thread named [MySQL Statement Cancellation Timer] but has failed to stop it. This is very likely to create a memory leak. log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository. 8 Jan, 2011 7:08:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory examples 8 Jan, 2011 7:08:58 PM org.apache.catalina.loader.WebappClassLoader loadClass INFO: Illegal access: this web application instance has been stopped already. Could not load java.net.BindException. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact. java.lang.IllegalStateException at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1531) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1491) at com.mysql.jdbc.CommunicationsException.(CommunicationsException.java:161) at com.mysql.jdbc.MysqlIO.send(MysqlIO.java:2759) at com.mysql.jdbc.MysqlIO.quit(MysqlIO.java:1410) at com.mysql.jdbc.Connection.realClose(Connection.java:4947) at com.mysql.jdbc.Connection.cleanup(Connection.java:2063) at com.mysql.jdbc.Connection.finalize(Connection.java:3403) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83) at java.lang.ref.Finalizer.access$100(Finalizer.java:14) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160) 8 Jan, 2011 7:08:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory docs 8 Jan, 2011 7:08:58 PM org.apache.catalina.startup.HostConfig deployDirectory INFO: Deploying web application directory ROOT 8 Jan, 2011 7:08:58 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on http-8080 8 Jan, 2011 7:08:58 PM org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009 8 Jan, 2011 7:08:58 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/24 config=null 8 Jan, 2011 7:08:58 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 3905 ms
I got also problems with myfaces-extensions using x tags. The conflict is due to the fact that myfaces is a very old solution and if your other libraries are uptodate the versions won't match. As posted at tomahawk inputfileupload uploaded file is null in my answer you should use tomahawk t tag and libraries related to it. Actual solution is posted in the main answer of that very same link.
I'm pretty sure this will do the thing. Tick my answer if the post included the answer to your question in its wiki-link :)

Resources