In fact, when I only connect to linux via ssh or rdp to windows, there is
no problem.

The problem only occurs when I connect to the linux system through rdp or
vnc. Maybe it is a problem with xrdp and vncserver. Maybe it is a problem
with my configuration, but there is actually no configuration.
I wonder if it may be that the connection has not been closed since the
connection was opened, and it directly appears that the resources have not
been released.

I'm still looking for a solution

Michael Ballard <[email protected]> 于2020年2月24日周一 下午9:32写道:

> I may have had a similar problem. After a few days/weeks, connections
> through guacamole would take a long time. I could connect directly to the
> computers via ssh or rdp just fine from a different computer in my lan.
>
> I realized RAM usage on my server hosting guacamole was very high, and it
> looked to not be directly related to guacamole processes. I restarted. And
> it's been working fine for months.
>
> My guacamole server is inside a virtual machine, this guest is also my web
> server, the host is also serving several different guests.
>
> I've monitored ram use periodically since, and it has remained at a
> reasonable level and I have not seen the problem return.  I do not think it
> was a guacamole-specific issue.
>
> On Sun, Feb 23, 2020, 21:49 benchu yao <[email protected]> wrote:
>
>> Install xrdp and vncserver on centos7, and then use the rdp or vnc
>> protocol to connect remotely many times,after that  the centos server login
>> becomes difficult.
>> It used to take 2s to log in successfully through the ssh protocol, but
>> now it may take 60s. The rdp and vnc protocols can no longer be used, and
>> often need to restart the virtual machine to resolve
>>
>> When I say that I have logged in to the centos7 system through the rdp
>> and vnc protocols many times, it means no more than 50 times, maybe only 20
>> times, and each time does not exceed half an hour.
>>
>>  Of course, I connected via guacamole
>>
>> I want to ask if you have such a problem. Is it a problem with my
>> operating system?
>>
>

Reply via email to