[Support] jasonbean - Apache Guacamole


Message added by Taddeusz,

Before upgrading to 1.5.0 you need to have first upgraded to 1.4.0-3 of the container. I discovered that prior to 1.4.0-3 it was not shutting down MariaDB correctly and causing the database to be left in a dirty state.

 

If after upgrading to 1.5.0 you discover that MariaDB is stopping and the log mentions something about needing to open the database in an older version of MariaDB you should downgrade specifically to 1.4.0-3, start the container and make sure it's running correctly. Then you may upgrade to 1.5.0.

Recommended Posts

  • 3 weeks later...
1 hour ago, surfshack66 said:

Is it possible to install GhostScript to enable printing?

 

"Printing support requires GhostScript to be installed. If guacd cannot find the gs executable when printing, the print attempt will fail."

 

Ok, if you don't mind briefly running a test version I can push out one with gs included later today.

Link to comment

I have updated the the image to output Tomcat's catalina.out file /config/guacamole/log to help troubleshooting. I also changed the scripts to always update file permissions to try to mitigate a problem where it appears that the database can't be read.

 

Please let me know if you're having any issues.

Link to comment

Hello,

 

Just updated the container and cannot get to the login page any longer...

 

Error:

 

Starting guacd: SUCCESS

*** Booting runit daemon...

*** Runit started as PID 42

Database exists.

Database upgrade not needed.

Setting Database Directory Permissions

Starting MariaDB...

Jun 9 01:17:26 9b972d957350 syslog-ng[48]: syslog-ng starting up; version='3.5.6'

180609 01:17:26 mysqld_safe Logging to '/config/databases/9b972d957350.err'.

180609 01:17:26 mysqld_safe Starting mysqld daemon with databases from /config/databases

*** Shutting down runit daemon (PID 42)...

*** Killing all processes...

*** Running /etc/my_init.d/firstrun.sh...

Using existing properties file.

Using existing MySQL extension.

Updating user permissions.

*** Running /etc/rc.local...

* Starting Tomcat servlet engine tomcat8

...fail!

guacd[39]: INFO: Guacamole proxy daemon (guacd) version 0.9.14 started

Starting guacd: SUCCESS

*** Booting runit daemon...

*** Runit started as PID 42

Database exists.

Database upgrade not needed.

Setting Database Directory Permissions

Starting MariaDB...

Jun 9 01:30:54 9b972d957350 syslog-ng[48]: syslog-ng starting up; version='3.5.6'

 

Looks like there is now an issue starting Tomcat...

 

Any ideas?

 

Thanks!

 

Sent from my SM-N950U using Tapatalk

 

 

 

 

Link to comment

The fail message after starting tomcat has always been there. I’m not sure why it shows that. Does the page load but just shows nothing? If so, that means it can’t connect to your authentication source. Look at the catalina.out file and see if there are any errors there.

Link to comment
On 6/9/2018 at 11:34 AM, airbillion said:

Hello,

 

Just updated the container and cannot get to the login page any longer...

 

Error:

 

Starting guacd: SUCCESS

*** Booting runit daemon...

*** Runit started as PID 42

Database exists.

Database upgrade not needed.

Setting Database Directory Permissions

Starting MariaDB...

Jun 9 01:17:26 9b972d957350 syslog-ng[48]: syslog-ng starting up; version='3.5.6'

180609 01:17:26 mysqld_safe Logging to '/config/databases/9b972d957350.err'.

180609 01:17:26 mysqld_safe Starting mysqld daemon with databases from /config/databases

*** Shutting down runit daemon (PID 42)...

*** Killing all processes...

*** Running /etc/my_init.d/firstrun.sh...

Using existing properties file.

Using existing MySQL extension.

Updating user permissions.

*** Running /etc/rc.local...

* Starting Tomcat servlet engine tomcat8

...fail!

guacd[39]: INFO: Guacamole proxy daemon (guacd) version 0.9.14 started

Starting guacd: SUCCESS

*** Booting runit daemon...

*** Runit started as PID 42

Database exists.

Database upgrade not needed.

Setting Database Directory Permissions

Starting MariaDB...

Jun 9 01:30:54 9b972d957350 syslog-ng[48]: syslog-ng starting up; version='3.5.6'

 

Looks like there is now an issue starting Tomcat...

 

Any ideas?

 

Thanks!

 

Sent from my SM-N950U using Tapatalk

 

 

 

 

 

I have the same issue with the update, same errors,

 

Link to comment

For those having problems let me know what the exact problem is. Does the login form show or do you get a white page and no visible error? Do any errors show in your Docker log or catalina.out?

 

I believe there are problems with file permissions going on but I guess I'm not quite understanding the root of the problem.

Link to comment
On 6/10/2018 at 8:38 AM, Taddeusz said:

For those having problems let me know what the exact problem is. Does the login form show or do you get a white page and no visible error? Do any errors show in your Docker log or catalina.out?

 

I believe there are problems with file permissions going on but I guess I'm not quite understanding the root of the problem.

 

I can't access the webui either. No idea what caused it

Edited by jrdnlc
Link to comment
Just now, jrdnlc said:

 

No access to webui. I removed docker image and deleted app folder. Tried new install and same error

 

When I say exactly, I mean does the page load but it's just white with no errors. Or do you get a 404 or other error trying to load the page?

 

What permissions are on your ApacheGuacamole appdata folder?

Link to comment
1 minute ago, Taddeusz said:

 

When I say exactly, I mean does the page load but it's just white with no errors. Or do you get a 404 or other error trying to load the page?

 

What permissions are on your ApacheGuacamole appdata folder?

 

Default permissions when adding a docker on unRAID. Attached a screenshot of the page 

 

Screen Shot 2018-06-11 at 12.28.01 PM.png

Link to comment
1 hour ago, Taddeusz said:

I apologize for the problems. This time it's really fixed. Tomcat was really not starting when the /config/guacamole/log folder didn't exist. I had to change the point at which that folder was being created.

Is the update live yet? Still not fixed for me

Link to comment
20 minutes ago, Taddeusz said:

Ok, I finally really figured this out. Apparently when I split this to create a multi-stage build I inadvertently removed the line that made firstrun.sh executable. I have corrected the error and pushed a new build.

I hate to say but that didn’t fix it

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.