Sure, I can certainly do that! I'm busy tonight but I'll get everything together tomorrow and send it over.
On Thu, Sep 7, 2017 at 7:05 PM Nicholas Couchman <[email protected]> wrote: > Glad to hear it! Any chance you could summarize the circumstances under > which the problem exists - exact version and build of ESX, which network > adapter type, and what version of Linux you're running (including kernel > build)? I see some of that info throughout the thread, but it would be > nice to have the rest and have it all in one place. > > -Nick > > On Sep 7, 2017, at 18:36, austin wonderly <[email protected]> wrote: > > The esxi update ended up doing the trick! Guacamole is functioning without > any issues now. > > On Thu, Sep 7, 2017 at 3:19 PM, austin wonderly <[email protected]> > wrote: > > it might be an ESXI bug. I'm going to see if there are any updates >> available, will provide an update soon. >> >> https://bugzilla.kernel.org/show_bug.cgi?id=191201 >> > On Thu, Sep 7, 2017 at 2:48 PM, austin wonderly <[email protected]> >> wrote: >> > I had to change the network adapter type from vmnet3 to e1000e. Apparently >>> this can cause other issues though, so I'm going to keep playing around >>> with it and see if I can get it working with the vmnet3 adapter again. >>> >> On Thu, Sep 7, 2017 at 2:36 PM, Mike Jumper <[email protected]> >>> wrote: >>> >> For future reference, what did you try specifically that ultimately >>>> solved things? The answers on SO may well change order, get edited, etc. >>>> over time. >>>> >>> On Sep 7, 2017 11:31, "austin wonderly" <[email protected]> wrote: >>>> >>> actually I tried the first answer found on this page >>>>> https://serverfault.com/questions/859095/why-does-my-debian-server-freeze/859118, >>>>> and for some reason that did the trick >>>>> >>>> On Thu, Sep 7, 2017 at 2:23 PM, austin wonderly <[email protected] >>>>> > wrote: >>>>> >>>> Is it possible that ESXI could be causing problems? I tried perform a >>>>>> similar installation in workstation today, and was able to get things >>>>>> running properly. I then tried taking the same exact steps in ESXI and >>>>>> encountered the unresponsive problem again. >>>>>> >>>>> On Wed, Sep 6, 2017 at 10:33 PM, austin wonderly < >>>>>> [email protected]> wrote: >>>>>> >>>>> Here are some screenshots of what I get when accessing guacamole: >>>>>>> >>>>>>> Login screen comes up properly: >>>>>>> >>>>>> <Screen Shot 2017-09-06 at 10.30.49 PM.png> >>>>>>> >>>>>> SSH terminal shows up after I've authenticated, at which point the >>>>>>> system immediately becomes unresponsive: >>>>>>> >>>>>> >>>>>>> <Screen Shot 2017-09-06 at 10.31.02 PM.png> >>>>>>> >>>>>>> >>>>>> >>>>>>> On Wed, Sep 6, 2017 at 10:25 PM, austin wonderly < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> thanks for your help with this. >>>>>>>> >>>>>>>> I'm going to try installing guacamole manually tomorrow. Regarding >>>>>>>> the responsiveness of the server, when this issue occurs, the server >>>>>>>> will >>>>>>>> stop responding to pings, the console will become unresponsive, and >>>>>>>> esxi >>>>>>>> will report a spike in CPU usage for the host. Guacamole's interface >>>>>>>> will >>>>>>>> no longer respond either due to the loss of network connectivity. >>>>>>>> >>>>>>>> On Wed, Sep 6, 2017 at 10:20 PM, Mike Jumper < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> On Wed, Sep 6, 2017 at 7:13 PM, austin wonderly < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> hello, >>>>>>>>>> >>>>>>>>>> I'm trying to set up guacamole to allow html5 ssh access to my >>>>>>>>>> server. so far I've done the following: >>>>>>>>>> >>>>>>>>>> 1. apt-get install guacamole >>>>>>>>>> >>>>>>>>> >>>>>>>>> Though this is unlikely to be related to your problem, I would >>>>>>>>> recommend installing a recent release of Guacamole following the >>>>>>>>> manual, >>>>>>>>> rather than installing packages via apt-get. >>>>>>>>> >>>>>>>>> >>>>>>>>>> ... >>>>>>>>>> >>>>>>>>>> 3. Restarted Guacd and tomcat >>>>>>>>>> >>>>>>>>>> After doing all of this, I'll be able to login to guacamole's web >>>>>>>>>> interface and get presented with "Login:" on guacamole's web terminal >>>>>>>>>> interface, but then my debian installation (clean install aside from >>>>>>>>>> guacamole, open-vm-tools, and ssh) just becomes completely >>>>>>>>>> unresponsive and >>>>>>>>>> won't respond again until I perform a hard reboot. I'm running Linux >>>>>>>>>> kingston 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u2 (2017-06-26) >>>>>>>>>> x86_64 >>>>>>>>>> GNU/Linux. >>>>>>>>>> >>>>>>>>> >>>>>>>>> Does the lack of response correlate to logging in to Guacamole? >>>>>>>>> >>>>>>>>> When the system is unresponsive, does the Guacamole interface >>>>>>>>> respond (page can be reloaded, you can log out / back in successfully, >>>>>>>>> etc.)? >>>>>>>>> >>>>>>>>> To what degree is the system unresponsive? Does the server respond >>>>>>>>> to input via a hardware keyboard? Does the server respond to pings? >>>>>>>>> >>>>>>>>> Is there something in my configuration that's incorrect? I checked >>>>>>>>>> syslog and catalina.log, but they both just stop logging at the same >>>>>>>>>> time >>>>>>>>>> that my system becomes unresponsive. >>>>>>>>>> >>>>>>>>> >>>>>>>>> It's unlikely that anything in Guacamole could cause your system >>>>>>>>> to go entirely down like this. Since "unresponsive" can mean many >>>>>>>>> things, I >>>>>>>>> think the first step here is to determine exactly what condition >>>>>>>>> occurs on >>>>>>>>> the server to result in that behavior. >>>>>>>>> >>>>>>>>> - Mike >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>
