![]() ![]() To invalidate the cache aka "force the server to recalculate all ACLs for a client" the server has a clearACLCache(User*) method.The server has a cache system for permissions aka ACLs, probably implemented to reduce the number of expensive computations and database lookups.Somewhere within this method the channel remember feature is computed and applied to the client. ![]() The msgAuthenticate in murmur/Messages.cpp method parses the content of the user connection msg and sets everything up. In 1.5 RC you can even observe the issue visually by looking at the lock icons for channels with ACL specified as above. I sent the sqlite file via e-mail to your e-mail address within the git logs.Īlright so I found the cause of this issue. I tried to compile server 1.3.4 via docker for testing, but it failed to compile. I also tested on server v1.4.230 via docker compiled image and client 1.5.0, and the bug still occurred. I removed all the spaces and apostrophe, retested on client 1.5.0 and docker image 1.5.420, and the problem still occurs. The root channel contained letters, spaces, and an apostrophe. Whether the channel required an access token or its name had special characters didn't matter, no channel location was saved upon reconnecting.Īll of my channel names contain just letters and spaces. The problem is reproducible with any arbitrary channel on the server. Upon upgrading to the 1.4.287 docker image the problem started. I switched OS to Ubuntu 22.04 so I could run docker and upgrade to 1.4.287. ![]() On 1.3.4 I never observed this problem regardless of client used. Maybe this is the reason.īefore 1.4.287, the server ran 1.3.4 on Redhat 8. The 1.4 server which also triggered the error for me has the following special characters in some channel names However any advice on how to fix my sqlite file? I would prefer not having to rebuild all my channels and permissions. ![]() With this in mind, I understand if it is not worth investigating and fixing the backwards compatibility. My sqlite database dates back to 1.2, maybe earlier. Therefore it seems the 1.4.287 server update broken backwards compatibility with server sqlite files made in earlier versions. The bug occurred and it would not remember my last channel. Then I used the same server and client, but loaded my old sqlite file. I tested this multiple times to confirm it worked. Upon reconnecting, the server remembered the channel I was in. Then I made some channels to test, added an access token to my client, 1.5 from master, entered a channel and then disconnected. I allowed my mumble server, 1.5.420, a docker image from master, to generate a new sqlite file. 17:36:10.810 Server attempted state change on nonexistent channel 17:36:10.810 Server attempted state change on nonexistent channel 17:36:10.810 Server attempted state change on nonexistent channel 17:36:10.810 Server attempted state change on nonexistent channel 17:36:10.810 Server attempted state change on nonexistent channel 17:36:10.810 Server attempted state change on nonexistent channel 17:36:10.810 Server attempted state change on nonexistent channelīased on all the above, I decided to try generating a new sqlite file for the server. However when connecting with an access toke, the terminal that launches the client contains the below warnings that are not present when connecting without an access token. it seems running a 1.5 client and 1.5 server does not fix the issue. I connected to my mumble server 1.5.420, a docker image from master, and confirmed that when a token is set, it is still not saving the last channel I was connected too. I confirmed the client is reporting a version of 1.5.0. I managed to build the Linux client on my Ubuntu computer from master. ![]()
0 Comments
Leave a Reply. |