[Bug 645575] Re: udev rules for mdadm cause boot hangs and md array malfunctions
I am not sure if they should be marked as duplicates, but see also https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1335642 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/645575 Title: udev rules for mdadm cause boot hangs and md array malfunctions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/645575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1335642] Re: mdadm runs into infinite loop and prevents initrd/initramfs phase to finish on boot
I came across this while purposely breaking my sw RAID array to test if booting through the mirror disk or degraded array was OK. Comment #4 worked for me. ls /dev/mapper on the initram shell really showed that my root device (which is on LVM) was not available before running that udevadm command. There was another catch that took me over an hour: I starting this by physically removing the sda disk. But later I reinserted it, and keep debugging like that most of the time, without resyncing the arrays, 'cause I wanted it to come up fine in that state. So I when I ran update-initramfs only the files in sdb got updated. *It took me a while to realize that the boot process was reading the initramfs files from the un-updated re-inserted sda disk.* I then re- synced my /boot and the workaround (#4) worked, duh. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1335642 Title: mdadm runs into infinite loop and prevents initrd/initramfs phase to finish on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1335642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1335642] Re: mdadm runs into infinite loop and prevents initrd/initramfs phase to finish on boot
Forgot to add that I am using Ubuntu 14.04 on an IBM x3630 M4 hardware. 12.04 apparently didn't manifested this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1335642 Title: mdadm runs into infinite loop and prevents initrd/initramfs phase to finish on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1335642/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278193] Re: logrotate skip the rotation of many files under /var/log due to bad group ownership
I've went through this problem just now. The changes described in #5 solved the problem for me as well. The fix released in LP: #1258202 (logrotate version 3.8.6-1ubuntu2) adds those lines to the default logrotate.conf file, but I got some custom configs in mine and so I had to manually change it. Of course it only works when it reads logrotate.conf, which I guess is not the case when you run this way: logrotate -df /etc/logrotate.d/rsyslog Running either /etc/cron.daily/logrotate or "/usr/sbin/logrotate /etc/logrotate.conf" works fine. Maybe the config "su root syslog" should be the compile-time-default in Ubuntu so to avoid this situation. Don't know if it is possible. Also, from what I understand reading man logrotate.conf, the "su root syslog" line only changes the user/group that the process of rotation will run as, which does not (necessarily) affect the owner and group of the log files: that is defined by the "create" directive (see the logrotate.conf man for that directive). That's why you don't see any files with group syslog, Uwe. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278193 Title: logrotate skip the rotation of many files under /var/log due to bad group ownership To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1278193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000770] Re: In Ubuntu installer, LVM device nodes are not created in time
I've hit this bug even tough I've applied the fix discussed in comment #6 of bug #964957. Specifically I've built partman-auto-lvm_42ubuntu2+dannf2_all.udeb from the 38th revision of https://code.launchpad.net/~dannf/partman-auto-lvm /precise-fixes, and installed that udeb using an early command. I've also confimed that /bin/perform_recipe_by_lvm contains the update-dev --settle line. It happened for me just as in Sgifford reported, but with swap partition instead of root. I'm preseeding the partitioning. The workaround he suggested (running vgscan --mknodes) works for me too. ** Changed in: partman-auto-lvm (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000770 Title: In Ubuntu installer, LVM device nodes are not created in time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto-lvm/+bug/1000770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 859319] Re: preseeded partition attempts to proceed too fast
This is probably the same as #964957, isn't it? Maybe should be marked as duplicate? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/859319 Title: preseeded partition attempts to proceed too fast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/859319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 522509] Re: [FFE] tftpd-hpa doesn't start on boot
> Also why does service say it is running when it isn't? Yeah, I saw the same thing. Didn't investigate it enough to make any comments. > Anything else I can try to make tftpd-hpa work from boot? Maybe starting tftpd as an "up" line on the interface definition (/etc/network/interface, man interfaces for more info). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/522509 Title: [FFE] tftpd-hpa doesn't start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/522509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 522509] Re: [FFE] tftpd-hpa doesn't start on boot
Hello Allen, As you may already know, the tftpd-hpa daemon is started on boot by the upstart system, as configured in the file /etc/init/tftpd-hpa.conf. This file contains a line beggining with "start on", which gives the *condition* in which upstart will start the daemon (by running the script that is defined in the same file). The error message "cannot resolve local IPv4 bind address: 0.0.0.0, Name or service not known" tells us that there is no configured IP address when tftpd is started. In my case, that happened because of the NIC bonding (multiple physical NICs configured as one logical NIC) configuration. The original "start on" condition (on lucid) is "start on (filesystem and net-device-up IFACE!=lo)". So when bondX gets up, that condition is satisfied, tftpd starts, but all the physical interfaces which are part of bondX are not ready yet, which gives the error, and makes tftpd exit. I changed the condition (in a non-generic, not even good way) so tftpd gets started later. It worked Do you use nic bonding too? I've just checked now that in Precise they changed the condition to "start on runlevel [2345]". I guess that should work even with bonding, don't remember if I tried that... Could it be another network configuration problem in your setup, maybe? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/522509 Title: [FFE] tftpd-hpa doesn't start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/522509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 522509] Re: [FFE] tftpd-hpa doesn't start on boot
I have the same problem, using lucid latest package (5.0-11ubuntu2.1). I have many interfaces configured in this machine, and nic bonding configured. Upstart seems to raise tftp when the first bond interface starts: syslog.2.gz:Jun 13 14:17:02 kernel: [3.923760] bnx2: eth1: using MSI syslog.2.gz:Jun 13 14:17:02 kernel: [3.924441] bonding: bond0: Warning: failed to get speed and duplex from eth1, assumed to be 100Mb/sec and Full. syslog.2.gz:Jun 13 14:17:02 kernel: [3.924451] bonding: bond0: enslaving eth1 as an active interface with an up link. syslog.2.gz:Jun 13 14:17:02 kernel: [3.925317] bonding: bond0: setting mode to 802.3ad (4). syslog.2.gz:Jun 13 14:17:02 kernel: [3.925348] bonding: bond0: Setting MII monitoring interval to 100. syslog.2.gz:Jun 13 14:17:02 kernel: [3.925395] bonding: bond0: Setting LACP rate to fast (1). syslog.2.gz:Jun 13 14:17:02 in.tftpd[842]: cannot resolve local IPv4 bind address: 0.0.0.0, Name or service not known syslog.2.gz:Jun 13 14:17:02 init: tftpd-hpa main process (842) terminated with status 66 syslog.2.gz:Jun 13 14:17:02 init: tftpd-hpa main process ended, respawning syslog.2.gz:Jun 13 14:17:02 kernel: [4.129433] 802.1Q VLAN Support v1.8 Ben Greear syslog.2.gz:Jun 13 14:17:02 kernel: [4.129436] All bugs added by David S. Miller syslog.2.gz:Jun 13 14:17:02 kernel: [4.134009] bonding: bond0: link status definitely down for interface eth0, disabling it syslog.2.gz:Jun 13 14:17:02 kernel: [4.134012] bonding: Warning: bond0: link status changed for uninitialized port on eth0 syslog.2.gz:Jun 13 14:17:02 kernel: [4.134017] bonding: bond0: now running without any active interface ! The "status tftpd-hpa" says the job is running, when it's not (should THAT happen?). stop/start raises the program just fine. I tried to change the condition to "(filesystem and and started networking)", but that seems to start it even earlier. I've changed it to "(filesystem and net-device-up IFACE=bond0.80)" (bond0.80 is the last bond interface) and then it worked. But the problem may actually be that bondX is !=lo, and it may come up before any of its slaves be available, resulting in the "cannot resolve local IPv4 bind address: 0.0.0.0" error. Should I open a new bug? If so, should it be on tftpd-hpa, or some other package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/522509 Title: [FFE] tftpd-hpa doesn't start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/522509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 153623] Re: bootsplash ubuntu gusty RC with mobility radeon x700
I was having the same problem in my laptop (Dell 131L with radeon xpress 1100, widescreen display). I've solved it by correcting the resolution in the /etc/usplash.conf file and running "sudo update-initramfs -u -k `uname -r`". The resolution was wrong: 1280x1024 while the native for my display is 1280x800. -- bootsplash ubuntu gusty RC with mobility radeon x700 https://bugs.launchpad.net/bugs/153623 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
