Public bug reported:
do-release-upgrade produces:
Calculating the changes
Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade.
This can be caused by:
* Upgrading to a pre-release version of Ubuntu
* Running the current pre-release version of Ubuntu
I am running maas-*-1.7.1 and I am still getting this on machines when
trying to commission them. These machines used to commission just fine,
maybe before the last update. Now nothing commissions. What kinds of
logs are useful and from which machines, the maas server or the client
machines
I am running maas-*-1.7.1 and I am still getting this on machines when
trying to commission them. These machines used to commission just fine,
maybe before the last update. Now nothing commissions. What kinds of
logs are useful and from which machines, the maas server or the client
machines
Public bug reported:
wakeonlan uses a tcp socket to wake up the server and can run as the
maas user. ether_wake uses a udp socket to wake up the server and must
run as root for it to work.
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
The fix for this is ato add the following line to /etc/sudoers.d/99
-maas-sudoers:
maas ALL= NOPASSWD: /usr/sbin/etherwake
and edit /etc/maas/templates/power/ether_wake.template to change:
/usr/sbin/etherwake $mac_address
to:
sudo /usr/sbin/etherwake $mac_address
If the network that you need
The fix for this is ato add the following line to /etc/sudoers.d/99
-maas-sudoers:
maas ALL= NOPASSWD: /usr/sbin/etherwake
and edit /etc/maas/templates/power/ether_wake.template to change:
/usr/sbin/etherwake $mac_address
to:
sudo /usr/sbin/etherwake $mac_address
If the network that you need
Public bug reported:
wakeonlan uses a tcp socket to wake up the server and can run as the
maas user. ether_wake uses a udp socket to wake up the server and must
run as root for it to work.
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Public bug reported:
We upgraded to the 3.2.0-45-generic kernel on a pair of 64 but vms and
now the server gets lots of errors with connectoins with CLOSED_WAIT
status. This eventually fills up the connection tables and new work
stops happening. We have removed any iptables firewalls from the
** Package changed: nginx (Ubuntu) = pound (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1189764
Title:
Pound server get too many CLOSE_WAIT sessions and fails
To manage notifications
*** This bug is a duplicate of bug 516854 ***
https://bugs.launchpad.net/bugs/516854
After upgrading to Lucid I made certain that I had openvpn, network-
manager-openvpn, and network-manager-openvpn-gnome, but it still didn't
work. It would start thousands of openvpn processes. I finally
Public bug reported:
Binary package hint: python-virtinst
Ubuntu 9.10
python-virtinst 0.400.3-4ubuntu1
I expected it to convert a vmware vm to something that could be used by
kvm
virt-convert -i vmx -o virt-image iMKS_Build-383/iMKS.vmx imksvm
Generating output in 'virt-image' format to
11 matches
Mail list logo
