Freeaqingme
commented
3 years ago I figured I might be able to attach a debugger to see what's going on. However, unfortunately, gdb doesn't know what to do with Go. Also, Delve complains that it "could not open debug info" (presumably because of missing DWARF headers).
Having said that, for one reason or another* everything just seems to have resolved.
I realize this issue reads a little like a support issue, but I think that the fact that the socket can become unresponsive and make anything that connects to it unresponsive is a bit of a bug. But it may be quite difficult to find out what was causing it.
There was one thing that I changed. I have this script running every 1 second to transfer some files to my VM:
#!/bin/bash
vmName=puppet1
status=$(lxc info $vmName)
if [ $? != 0 ]; then
# vm not running
exit
fi
codePath=/etc/puppetlabs/code/environments/dev
lastModifiedTimestamp=$(find $codePath -type f -printf '%T@ %p\n' | \
sort -n | tail -1 | cut -d'.' -f1)
lastFewSecondsTimestamp=$(echo $(date +%s)-5 | bc)
if (( $lastModifiedTimestamp > $lastFewSecondsTimestamp )); then
echo "Files modified in last 5 seconds, syncing..."
tar zcf - -C $codePath . | lxc exec $vmName -- tar zxvf - -C $codePath >/dev/null
echo "Syncing complete!"
fiThe issue seemed to resolve itself right when I put an 'exit 0' statement on line 2. Perhaps that may or may not give a hint as to where the issue originates?
stgraber
I'm not entirely sure if this issue pertains to LXC or LXD. I just wanted to enter a VM using
lxc exec <vmName> bash. That command hangs consistently without any output shown.lxc lsalso hangs with no output whatsoever (unless in debug mode):I think that for a command like this there could/should be a timeout on the call to the unix.socket, but that obviously wouldn't fix the problem. How should I go about fixing it and making things responsive again? It's a test environment so I could easily just reboot something, but as it is a lab set up for a future production environment I'd like to be able to fix it in a way I would also do on production in the future.
Required information
I
Information to attach
lxd.log: