Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

olat_1 | /bin/bash: /entrypoint.sh: Permission denied #1

Open
mclark4386 opened this issue Jun 8, 2020 · 7 comments
Open

olat_1 | /bin/bash: /entrypoint.sh: Permission denied #1

mclark4386 opened this issue Jun 8, 2020 · 7 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@mclark4386
Copy link

I'm guessing that the script isn't set to executable in the repo? just tried pulling it from docker hub and running it with this docker-compose file to try it out:

version: "3.1"

services: 
  olat:
    image: blackrose01/openolat:latest
    environment:
      DB_TYPE: postgresql
      DB_HOST: db
      DB_NAME: olat
      DB_USER: postgres
      DB_PASS: postgres
    ports:
      - "8088:8088"
    volumes:
      - ./olat_data:/opt/openolat/olatdata

  db:
    image: postgres:11.6-alpine
    environment:
      POSTGRES_DB: olat
      POSTGRES_PASSWORD: postgres
    ports:
      - "5432:5432"
    volumes:
      - ./db_data:/var/lib/postgresql/data

If I'm doing it wrong would love to know how! Thanks!^^

@BlackRose01
Copy link
Owner

Hello,

there could be several reasons why your openolat container is not starting up. First I would say that the user permissions on your volume is not correct. Another reason could be a misconfiguration of the openolat.config.

@mclark4386
Copy link
Author

Set the folder to 777. What are you thinking the issue would be with the openolat.config?

@BlackRose01
Copy link
Owner

maybe there are some misconfigurations in the file but do you have any logfiles from the container?

@pheraph
Copy link

pheraph commented Jun 19, 2020

I'm gonna hang on to this one. First of all, thanks for the container! I'm currently also failing to start the container successfully. I have taken the docker-compose.yml from @mclark4386 as starting point, where I also get the error bin/bash: /entrypoint.sh: Permission denied. I then cloned this github repository, run a chmod +x on the entrypoint.sh and the shell script could be called. But then Tomcat could not be loaded (TOMCAT_VERSION = latest):

Cannot find tomcat release with Tomcat Version: 9.0.34. So your passes TOMCAT_VERSION is wrong.

After I manually set it to the available version 9.0.36, Tomcat was downloaded, but then I get pages and pages of warnings which I'm not sure about. Do you have any ideas?

olat_1  | Create necessary folders for OpenOlat in: /opt/openolat
olat_1  | mkdir: cannot create directory '/opt/openolat/olatdata': File exists
olat_1  | Download OpenOlat Version: 1428
olat_1  | Download Tomcat Version: 9.0.36
olat_1  | Unpack downloaded files to installation directory (this can be take some time)
olat_1  | Create necessary Symlinks/Move files
olat_1  | Create database configuration for OpenOlat
olat_1  | Update OpenOlat configuration file
olat_1  | Create environment file for tomcat
olat_1  | Set global environment variables
olat_1  | Clean up
olat_1  | rm: cannot remove '/tmp/*.service': No such file or directory
olat_1  | Write installation information
olat_1  | Start OpenOlat
olat_1  | NOTE: Picked up JDK_JAVA_OPTIONS:  --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
olat_1  | Jun 19, 2020 8:24:19 AM org.apache.coyote.AbstractProtocol init
olat_1  | INFO: Initializing ProtocolHandler ["http-nio-8088"]
olat_1  | Jun 19, 2020 8:24:19 AM org.apache.catalina.startup.Catalina load
olat_1  | INFO: Server initialization in [947] milliseconds
olat_1  | Jun 19, 2020 8:24:19 AM org.apache.catalina.core.StandardService startInternal
olat_1  | INFO: Starting service [Catalina]
olat_1  | Jun 19, 2020 8:24:19 AM org.apache.catalina.core.StandardEngine startInternal
olat_1  | INFO: Starting Servlet engine: [Apache Tomcat/9.0.36]
olat_1  | Jun 19, 2020 8:24:19 AM org.apache.catalina.startup.HostConfig deployDescriptor
olat_1  | INFO: Deploying deployment descriptor [/opt/openolat/conf/Catalina/localhost/ROOT.xml]
olat_1  | Jun 19, 2020 8:24:19 AM org.apache.catalina.startup.HostConfig deployDescriptor
olat_1  | WARNING: The path attribute with value [] in deployment descriptor [/opt/openolat/conf/Catalina/localhost/ROOT.xml] has been ignored
olat_1  | Jun 19, 2020 8:24:19 AM org.apache.catalina.startup.SetContextPropertiesRule begin

....

olat_1  | WARNING: The web application [ROOT] appears to have started a thread named [Abandoned connection cleanup thread] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
olat_1  |  [email protected]/java.lang.Object.wait(Native Method)
olat_1  |  [email protected]/java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:155)
olat_1  |  com.mysql.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:64)
olat_1  |  [email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
olat_1  |  [email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
olat_1  |  [email protected]/java.lang.Thread.run(Thread.java:834)
olat_1  | Jun 19, 2020 8:24:31 AM org.apache.catalina.startup.HostConfig deployDescriptor
olat_1  | INFO: Deployment of deployment descriptor [/opt/openolat/conf/Catalina/localhost/ROOT.xml] has finished in [12,640] ms
olat_1  | Jun 19, 2020 8:24:31 AM org.apache.coyote.AbstractProtocol start
olat_1  | INFO: Starting ProtocolHandler ["http-nio-8088"]
olat_1  | Jun 19, 2020 8:24:32 AM org.apache.catalina.startup.Catalina start
olat_1  | INFO: Server startup in [12,766] milliseconds
olat_1  | Jun 19, 2020 8:24:35 AM org.apache.catalina.loader.WebappClassLoaderBase checkStateForResourceLoading
olat_1  | INFO: Illegal access: this web application instance has been stopped already. Could not load []. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
olat_1  | java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load []. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
olat_1  | 	at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1385)
olat_1  | 	at org.apache.catalina.loader.WebappClassLoaderBase.getResource(WebappClassLoaderBase.java:1038)
olat_1  | 	at com.mysql.jdbc.AbandonedConnectionCleanupThread.checkContextClassLoaders(AbandonedConnectionCleanupThread.java:90)
olat_1  | 	at com.mysql.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:63)
olat_1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
olat_1  | 	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
olat_1  | 	at java.base/java.lang.Thread.run(Thread.java:834)
olat_1  | 

@BlackRose01
Copy link
Owner

Thank you for your the tip and I changed the default value. I see that Apache removed the Tomcat version from there Website.

Could you try to delete the volume entry in the compose file. Maybe there are some problems with the different file systems but I will try it within the next days.

@BlackRose01
Copy link
Owner

Short update from my side. I tested it on my Synology DS918+ and it worked. I will test it on my other homeserver but I need a new fan. So the final test and repair will start at the weekend. I hope that's ok.

@BlackRose01
Copy link
Owner

I came up to the following result: I cannot run openolat with docker-compose at all. I receive always the same errors like you but when I pull the repository and build it then I didn't get any errors and I can run it. So please currently don't use docker-compos but I will continue to search the problem. If there are any other mistakes please report it to me and I will look forward to fix them. :D

@BlackRose01 BlackRose01 added bug Something isn't working enhancement New feature or request labels Jul 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants