[Bug 746699] Re: failure trying to install from Debian 4.0 (kernel 2.6.18-5)
I had forgotten I even filed this a decade ago. I don't really have such a system to test with anymore, and it's not clear what more recent versions of things would be worth testing with. I suspect this can just be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/746699 Title: failure trying to install from Debian 4.0 (kernel 2.6.18-5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/746699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923416] [NEW] Installer crash in 20.10 in new VirtualBox VM on OS-X
Public bug reported: Installing 20.10 in new VirtualBox VM on OS-X, zfs selected ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 00:52:45 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923416 Title: Installer crash in 20.10 in new VirtualBox VM on OS-X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1923416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612517] Re: Server fails to start after upgrade because of customized config and obsolete/renamed directives
This failure also occurs because "log_slow_queries" has become "slow_query_log", but the installer does not handle this change automagically. Like the OP's error, nothing specific to it is mentioned in the installation failure message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612517 Title: Server fails to start after upgrade because of customized config and obsolete/renamed directives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1612517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1339607] Re: Unencrypted private keys are insecure message is vague and unhelpful
I confirm the same behavior that Dmitri sees. I have an encrypted private key configured with its password within the Network Manager which belongs to a wifi connection. When that connection is found at boot time, I receive this warning message regardless of whether the key is encrypted, or not. This is quite misleading. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1339607 Title: Unencrypted private keys are insecure message is vague and unhelpful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1339607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1163513] [NEW] dbus/udev send NFS client connection out out the wrong interface
Public bug reported: I apologize for being vague , but I am not certain which package is responsible for this bug. Both dbus and udev are the most likely candidates as both contain recent change logs that mention Interface 00 binding. Both were upgraded during the application of all waiting system updates for Ubuntu Server 12.04.2 LTS on 03/22/2013, and the previous patch application before that was mid-December 2012. After applying all waiting updates on 03/22 we began to notice that MPI jobs were failing on our HPC clusters. This behavior was traced down to NFS (which was not updated in this patch cycle) clients improperly routing traffic. These clients use NFS on a VLAN that is unique to each cluster, which is only accessible to each node on their eth1 interface. On the nodes that would still work we noticed that the NFS mount had bound to the client address (clientaddr) of eth1, and on the nodes that were no longer functioning they had bound to '0.0.0.0' instead. This behavior was proven by finding a high count of discarded packets at hop 1, as the upstream router is not aware of each cluster's internal VLAN. I could not get this behavior to change simply by remounting, but it can definitely change after a reboot. For one 'up' cycle the NFS mount may bind to eth1, and on the next it may bind to 0.0.0.0 instead. Manually configuring each node's NFS mounts in /etc/fstab to use the client address of eth1 (clientaddr=eth1's address) corrects the issue, but this extra configuration has never been needed in the past, nor can I find any documentation regarding this change. Here is the complete list of what was updated in this patch cycle: dmsetup apparmor apport apt apt-transport-https apt-utils base-files bind9-host dnsutils dpkg gir1.2-gudev-1.0 gnupg gpgv grub-common grub-pc grub-pc-bin grub2-common initramfs-tools initramfs-tools-bin iptables isc-dhcp-client isc-dhcp-common language-pack-en language-pack-en-base language-selector-common libapt-inst1.4 libapt-pkg4.12 libbind9-80 libdbus-glib-1-2 libdevmapper1.02.1 libdns81 libdrm-intel1 libdrm-nouveau1a libdrm-radeon1 libdrm2 libfreetype6 libgnutls26 libgudev-1.0-0 libisc83 libisccc80 libisccfg82 liblwres80 libmysqlclient18 libnih-dbus1 libnih1 libpciaccess0 libplymouth2 libssl1.0.0 libudev0 libxml2 linux-headers-server linux-image-server linux-server man-db mountall mysql-common openssl perl perl-base perl-modules plymouth Plymouth-theme-ubuntu-text postfix puppet puppet-common python-apport python-problem-report sudo ubuntu-minimal ubuntu-standard udev upstart x11-common ** Affects: dbus (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/1163513 Title: dbus/udev send NFS client connection out out the wrong interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1163513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361992] Re: HostAliases ignored
Hello, This issue has been resolved thanks to the help of Jean-Luc of the awstats team. Some changes that came in v6.5.x broke the way that we were using awstats. To make our configurations compatible with v6.5.x we had to change the following: 1) LogSeparator= became \s+ as one of our log entries is double- spaced and the newer awstats versions use a single space explicitly. 2) LogFormat 4 no longer recognizes anything beyond the end of its expected string. We now use this custom string instead: LogFormat = %host %other %logname %time1 %methodurl %code %bytesd %refererquot %uaquot %virtualname 3) Any HostAlias entries that looked like a-product-name had to be changed to REGEX[\a-product-name\$] in order to be recognized within the %virtualname variable. Please close this bug, and thanks again for being willing to get involved. -- HostAliases ignored https://bugs.launchpad.net/bugs/361992 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361992] Re: HostAliases ignored
Hello, I apologize for my delay but I stopped watching this after it didn't get answered for a few weeks. This is on the server edition of Ubuntu 6.06.x LTS (Dapper), but it is important to note that this issue persists in all versions of awstats from 6.54.x onward. -- HostAliases ignored https://bugs.launchpad.net/bugs/361992 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361992] Re: HostAliases ignored
Typo: The version in my last comment should have been 6.5.x. -- HostAliases ignored https://bugs.launchpad.net/bugs/361992 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361992] [NEW] HostAliases ignored
Public bug reported: Ubuntu 6.06.2 LTS (Dapper) Upgrading to any awstats version from 6.5-1 onward (I have tried both awstats_6.5-1ubuntu1.3_all.deb from dapper and awstats_6.6+dfsg- 1ubuntu0.1_all.deb from gutsy) breaks the HostAliases directive. Prior to this upgrade our awstats installation had been running fine for more than a year. In a specific configuration file (let's call it myconf) we have: LogFormat = 4 LogSeparator= SiteDomain=mydomain.com HostAliases=REGEX[\a-product-name\$] Long ago we learned that the HostAliases directive was the only way to get awstats to differentiate things with our logging structure (due to adding on the app-name and a-product-name entries). A sample web log line looks like this: 1.1.1.1 - - [13/Apr/2009:23:59:29 -0700] POST /gateway/httpservlet HTTP/1.1 200 520 - app-name a-product-name In the past this line would have been included when statistics were run against the myconf configuration (e.g. '/usr/lib/cgi-bin/awstats.pl -update -config=myconf') but not when any other config was run that looked for a different a-product-name as defined in its HostAliases. Since updating awstats all records in any of our weblogs get included when any configuration is used, regardless whether its HostAliases directive matches or not. ** Affects: awstats (Ubuntu) Importance: Undecided Status: New -- HostAliases ignored https://bugs.launchpad.net/bugs/361992 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361992] Re: HostAliases ignored
Here is the output of updating against myconf. You can see that every parsed record is counted as a new qualified record when only about 40% of the actual log lines pertain to the HostAliases in the coinfiguration. # /usr/lib/cgi-bin/awstats.pl -update -config=myconf Create/Update database for config /etc/awstats/awstats.myconf.conf by AWStats version 6.6 (build 1.887) From data in log file /logarchive/request.log.w1.mydomain.com.2009_04_13... Phase 1 : First bypass old records, searching new record... Direct access after last parsed record (after line 5) Warning: awstats has detected that some hosts names were already resolved in your logfile /logarchive/request.log.w1.mydomain.com.2009_04_13. If DNS lookup was already made by the logger (web server), you should change your setup DNSLookup=1 into DNSLookup=0 to increase awstats speed. Jumped lines in file: 5 Found 5 already parsed records. Parsed lines in file: 50305 Found 0 dropped records, Found 0 corrupted records, Found 0 old records, Found 50305 new qualified records. -- HostAliases ignored https://bugs.launchpad.net/bugs/361992 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
