sorry I thought you were looking for a log file

usermod: no changes
----------------------
User UID: 99
User GID: 100
----------------------
Using existing properties file.
Using existing MySQL extension.
No permissions changes needed.
Database exists.
Database upgrade not needed.
2023-02-16 08:49:03,512 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2023-02-16 08:49:03,512 INFO Set uid to user 0 succeeded
2023-02-16 08:49:03,515 INFO supervisord started with pid 26
2023-02-16 08:49:04,517 INFO spawned: 'guacd' with pid 29
2023-02-16 08:49:04,519 INFO spawned: 'mariadb' with pid 30
2023-02-16 08:49:04,522 INFO spawned: 'tomcat' with pid 31
guacd[29]: INFO:        Guacamole proxy daemon (guacd) version 1.4.0 started
guacd[29]: INFO:        Listening on host 0.0.0.0, port 4822
2023-02-16 08:49:05,725 INFO success: guacd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-02-16 08:49:05,725 INFO success: mariadb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-02-16 08:49:05,725 INFO success: tomcat entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

@Electrohacker I'm not sure what's going on. It may be that the MySQL extension or one of its lib dependencies has gotten corrupted. What I would suggest doing is to stop the container. Go to the guacamole/extensions folder and delete the guacamole-auth-jdbc-mysql jar file (not the exact name, there's a version number there too). Also go to the guacamole/lib folder and delete the two mysql-connector files. Then restart the container. It should re-copy those files.

 

Other than that there might be database corruption?

didnt work.  Same error.  Where do I start with the database?

1.5.0 has dropped.

1 hour ago, kaiguy said:

1.5.0 has dropped.

Yes, I’ve been working on it when I can.

On 2/22/2023 at 5:12 AM, Taddeusz said:

Yes, I’ve been working on it when I can.

Any News? Any way I / we can help?

On 3/6/2023 at 9:30 AM, CryoRig said:

Any News? Any way I / we can help?

 

Sorry, it's been a busy few weeks and my brain just hasn't been able to focus. I'm going to put in effort this weekend to try and get it out.

I have an update. I'm not quite ready to push 1.5.0 out due to a problem I've found with the 1.4.0 container. Apparently using mysqld_safe does not shut the process down cleanly so the database was being left in a dirty state. I discovered this when I ran the newer MariaDB in Alpine it was complaining that the database needed to be opened and closed in an earlier version of MariaDB.

 

So, I've pushed out a new version of 1.4.0 that works as it should, starting mysqld directly so that it shuts the database down correctly.

 

Honestly, this might explain some of the database problems some of you have reported.  I'll give it a day or two and then push out 1.5.0 when I feel it's ready.

Edited March 19, 20233 yr by Taddeusz

Let me also say that I'm a little excited about 1.5.0. Due to switching from a Debian base to an Alpine base the containers are about half the size.

While you're active on the 1.5.0 uplift with Alpine, would you consider a possible tweak to the guacamole deployment?

I have a minor cosmetic issue with Guacamole and the mouse pointer which is corrupted. The issue is reported fixed in 1.6.0 but a minor patch could resolve issues with Ubuntu 22.04 RDP mouse corruption. guacamole releases are reasonably slow so i am hoping a patch might get us through their release cycle.

 

See below:

 

 

https://issues.apache.org/jira/browse/GUACAMOLE-1717

 

 

@codyrat I'm sorry, I take the guacamole server (guacd) binary as it is. It would take a lot of work to make a custom build to back port that one fix. I know that report says that the fix version will be 1.6.0 but it appears that they are going to do a 1.5.1 release. The change was merged 2 hours ago.

@codyrat I would suggest making a comment and asking if they could push the change to 1.5.1.

Ok, I have promoted 1.5.0 to be "latest". Please be aware of the big red message at the top. You MUST have upgraded to 1.4.0-3 before upgrading to 1.5.0.

Working great so far. Thanks @Taddeusz! Supper happy I can now use ed25519 keys.

Working great. Thankyou!

Edited March 21, 20233 yr by Zeroeth

On 3/20/2023 at 11:00 AM, Taddeusz said:

@codyrat I would suggest making a comment and asking if they could push the change to 1.5.1.

Thanks for replying. I'll take your advice and comment on the issue thread and see if I can convince the team to promote the defect fix earlier. Thanks for the great container!

Hi!

 

I'm getting the following issue on printing through RDP connection after upgrading to 1.5.0.

 

If I check on the 1.4.0-3 version, printing works without any issues.

 

Any ideas what this might be related to?

 

ApacheGuacamole Log

-------------------------------------------------------------------

guacd[4661]: INFO:      User "@1ef25a0a-eeb9-4bb7-98ba-d887a463c0bf" joined connection "$87a093cc-718b-44be-be2f-274a6d743162" (1 users now present)
guacd[4661]: INFO:      Loading keymap "base"
guacd[4661]: INFO:      Loading keymap "en-us-qwerty"
guacd[4661]: INFO:      Connected to RDPDR 1.13 as client 0x0005
guacd[4661]: INFO:      Connected to RDPDR 1.13 as client 0x000a
guacd[4661]: INFO:      RDPDR user logged on
guacd[4661]: INFO:      Print job created
guacd[4661]: INFO:      Created PDF filter process PID=4817
guacd[4817]: INFO:      Running gs
GPL Ghostscript 10.00.0: Unrecoverable error, exit code 1
guacd[4661]: INFO:      Print job closed

-------------------------------------------------------------------

 

Also, I have checked this on 1.4.0-3 on another docker instance since if I try to downgrade from 1.5.0 back to 1.4.0-3 then mariaDB won't start.

 

Thanks in advance!

Edited March 22, 20233 yr by Zeroeth

@Zeroeth I've reproduced the problem. I'll have to do some testing to see if it's a bug with guacd or with my implementation.

@Zeroeth I've tested with their guacd container and get the same error. In fact, it's actually worse because once GhostScript fails once it apparently never closes the print job and I end up with an error in my remote Windows which I wasn't getting from my own guacd. I'll put in a bug report if there isn't one already.

37 minutes ago, Taddeusz said:

@Zeroeth I've tested with their guacd container and get the same error. In fact, it's actually worse because once GhostScript fails once it apparently never closes the print job and I end up with an error in my remote Windows which I wasn't getting from my own guacd. I'll put in a bug report if there isn't one already.

 

Thankyou @Taddeusz! I have this running on one of my instances for testing and yes the printer that is mapped goes offline on the remote windows VM.

 

For my other instances, I was able to restore the previous version 1.4.0-3 from my backups since downgrading was causing an issue with mariaDB from starting. 

Edited March 22, 20233 yr by Zeroeth

just updated docker now, wish  i didn't to be honest (is it me or is updating dockers these days is becoming very hit and miss with issues)??

 

anyway i'm getting issues in logs and it's broke 

 

2023-03-24 02:05:13,819 INFO exited: mariadb (exit status 1; not expected)
2023-03-24 02:05:14,821 INFO spawned: 'mariadb' with pid 251
2023-03-24 02:05:15,844 INFO success: mariadb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-03-24 02:05:15,845 INFO exited: mariadb (exit status 1; not expected)
2023-03-24 02:05:16,848 INFO spawned: 'mariadb' with pid 256
2023-03-24 02:05:17,875 INFO success: mariadb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-03-24 02:05:17,875 INFO exited: mariadb (exit status 1; not expected)
2023-03-24 02:05:18,878 INFO spawned: 'mariadb' with pid 261
2023-03-24 02:05:19,903 INFO success: mariadb entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2023-03-24 02:05:19,903 INFO exited: mariadb (exit status 1; not expected)
2023-03-24 02:05:20,905 INFO spawned: 'mariadb' with pid 266
2023-03-24 02:05:21,934 INFO success: mariadb entered RUNNING state, process 

 

 

how do i down grade back to the previous version which was working great ( i have now removed the plugin that auto updates dockers...i wished i stuck with manual updating).

 

 

what do i do to go back wo the working one?

 

EDIT

 

i done "jasonbean/guacamole:1.4.0-3"

 

it downgraded and working great, i will leave this alone now, and stop auto updating dockers!

Edited March 24, 20233 yr by Registered55
solution

Hi, I have done the 1.4.0-3 upgrade to 1.5 as I had Mysql errors when doing the docker upgrade via the auto update docker feature. 

 

Guacamole now loads and can be used, however NONE of my VNC connections work any more

I have about 6 physical machines (NOT VM's) that was working perfect before with WOL. 

 

Any idea why they all stopped working with 1.5?

 

Unfortunately it does not look like you can downgrade from 1.5 to previous versions again as I get Mysql errors again when trying to go back to 1.4.0-3

Edited March 24, 20233 yr by nik82

@nik82 Are there any errors in the log?

@nik82 I've just pushed a small update. There was a guacd dependency I missed. I've not had any problems with VNC connections. The ones I've tried are to Docker containers.

I also have issues with VNC connections. It's as if guac didnt even try to connect. Just said connection failed.

 

Immediate failure. Not like when something times out etc.

 

guacd[171]: ERROR:      Unable to connect to VNC server.
guacd[171]: INFO:       User "@c" disconnected (0 users remain)
guacd[171]: INFO:       Last user of connection "$d" disconnected
guacd[24]: INFO:        Connection "$d" removed.

 

Connection from another machine with the same VNC details works as it should

 

Guac to the same machine via RDP works so not a VLAN/Network issue. Just not VNC, since latest update.

Edited March 26, 20233 yr by Urbanpixels