It's the normal builtin NIC on a headless server. Tried with different
hardware as well:
*-network
description: Ethernet interface
product: 82574L Gigabit Network Connection
vendor: Intel Corporation
*-network
description: Ethernet interface
pro
I tried your suggested settings on fresh installs including all updates but
this still regularly fails to bind the address. I have those servers running as
virtual machines with Qemu/KVM.
If I do the same thing on bare metal, the binding will succeed in like 95% of
boots.
/var/log/openvpn.log
Public bug reported:
unstable while loading before finished
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: unity-schemas 7.4.0+16.04.20160906-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
Uname: Linux 4.4.0-116-generic i686
.tmp.unity_support_test.0:
ApportVersio
** Description changed:
OpenVPN intermittently fails to bind to local address during boot on
Ubuntu Server 16.04.2 LTS. Sometimes it succeeds, sometimes it does not.
/var/log/openvpn.log
Wed May 10 15:42:02 2017 OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)]
[LZO] [EPOLL] [PKCS11]
Public bug reported:
OpenVPN intermittently fails to bind to local address during boot on
Ubuntu Server 16.04.2 LTS. Sometimes it succeeds, sometimes it does not.
/var/log/openvpn.log
Wed May 10 15:42:02 2017 OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)]
[LZO] [EPOLL] [PKCS11] [MH] [IPv6] b
Unfortunately I have to confirm, that I no longer have the hardware to
test it on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616107
Title:
Kernel oops + system freeze on network-bridge shutdown
I'll have the servers for another ~2 weeks for testing. After that
they're going off to the customer with Ubuntu 14. Please tell me now if
you need more testing done.
Cheers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
The #17 kernel has no oops. Network and bridge are brought up after
boot, however there is no network connectivity on the bridge. "sudo
service networking restart" fixes that and after that everything works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
4.4 final shows the same oops.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616107
Title:
Kernel oops + system freeze on network-bridge shutdown
To manage notifications about this bug go to:
http
More test results:
v4.5 mainline build -> No oops, no problems
v4.5-rc1 mainline build -> No oops, no problems
v4.4.21 mainline build -> Same oops
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16161
So I tested a couple of them:
v4.4.19 mainline build -> Same oops
v4.6.4 mainline build -> No oops
Remark: Bridge is up after boot but without network connection. "sudo service
networking restart" fixes that.
v4.6.7 mainline build -> No oops
Remark: Bridge is up after boot but without network c
Some more information:
On Ubuntu 16.04 LTS:
- The above error occurs in all Ubuntu 16.04 LTS versions since the beta and up
to Ubuntu 16.04.1 LTS with kernel 4.4.0-36-generic #55-Ubuntu
- It does NOT occur in Ubuntu 16.04.1 LTS with manually installed kernel
"v4.8-rc3 mainline build"
- bridge-ut
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: kernel-fixed-upstream
** Description changed:
A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
This error does not ap
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1616107/+attachment/4726885/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16161
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1616107/+attachment/4726886/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616107
apport information
** Tags added: apport-collected
** Description changed:
A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
This error does not appear in Ubuntu 14.04 however.
The error is reprodu
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1616107/+attachment/4726884/+files/ProcEnviron.txt
** Description changed:
A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2
** Package changed: ubuntu => linux (Ubuntu)
** Also affects: bridge-utils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1616107
Title:
Kernel o
** Description changed:
A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
This error does not appear in Ubuntu 14.04 however.
The error is reproducible whenever issuing the commands "shutdown",
"se
Public bug reported:
A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is
brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver.
This error does not appear in Ubuntu 14.04 however.
The error is reproducible whenever issuing the commands "shutdown",
"service networkin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/879744
Title:
outline of every 3x3 square difficult to see
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome
Public bug reported:
The frames changed after upgrade to 11.10
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-sudoku 1:3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu3
Archit
** Attachment added: "partman"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/800046/+attachment/2176617/+files/partman
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/800046
Title:
insta
** Attachment added: "/var/log/syslog"
https://bugs.launchpad.net/bugs/800046/+attachment/2176616/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/800046
Title:
installation failure
T
Public bug reported:
Binary package hint: ubiquity
Installing Dual boot (Win MCE, Mythbuntu) on computer with 2 drives.
1st drive has NTFS partition, then 15G root, 4G swap. 2nd drive first
partition is JFS and labeled /var (best I could do for media drive with
installer), then final partition i
** Attachment added: "logs.tar.gz"
http://launchpadlibrarian.net/38346251/logs.tar.gz
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/38346252/AlsaDevices.txt
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/38346253/ArecordDevices.txt
** Att
Public bug reported:
I was performing a large file transfer off this machine. The network
stalled. Neither source nor destination could ping either other, but
after a few minutes I could ping the gateway from the affected machine.
I was SSH'd into this laptop and it took 2-3 minutes for the term
27 matches
Mail list logo
