Bug#606192: [Solved] Re: system boot sometimes stuck with "waiting for /dev to be fully populated."
On 3/1/11 2:19 PM, Maria Mckinley wrote: On 3/1/11 10:44 AM, Maria Mckinley wrote: I am having this problem after upgrading from Lenny to Squeeze. It is stuck on this screen for a few minutes, and then goes into some strange state where the screen is not getting a signal, but the machine appears to be doing something, and I have to reset the power to get it to reboot. I can boot into previous kernels still. Tried installing firmware-linux-nonfree, but this did not help. thanks, maria Some more info... I was following the directions on how to upgrade described here: http://www.debian.org/releases/squeeze/amd64/release-notes/ch-upgrading.en.html I had upgraded the kernel and udev, and had rebooted when the problem occurred. I decided to boot into the Lenny kernel, and do apt-get dist-upgrade there to see if that would help. Unfortunately, it did not. I noticed that when I was booting into the earlier kernel, there was a message about mounting none on /dev/failed, and something about devtmpfs not available. This was early enough in the boot process, that I couldn't find anything about it in the logs, however, and I did not see these messages in the latest kernel that fails to boot. thanks, maria Booted into single user mode, and saw that it seemed to be having problems with the nvidia card, so I installed nvidia-xconfig, and reconfigured udev. Then I was able to boot without any problems. ~maria -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#606192: system boot sometimes stuck with "waiting for /dev to be fully populated."
On 3/1/11 10:44 AM, Maria Mckinley wrote: I am having this problem after upgrading from Lenny to Squeeze. It is stuck on this screen for a few minutes, and then goes into some strange state where the screen is not getting a signal, but the machine appears to be doing something, and I have to reset the power to get it to reboot. I can boot into previous kernels still. Tried installing firmware-linux-nonfree, but this did not help. thanks, maria Some more info... I was following the directions on how to upgrade described here: http://www.debian.org/releases/squeeze/amd64/release-notes/ch-upgrading.en.html I had upgraded the kernel and udev, and had rebooted when the problem occurred. I decided to boot into the Lenny kernel, and do apt-get dist-upgrade there to see if that would help. Unfortunately, it did not. I noticed that when I was booting into the earlier kernel, there was a message about mounting none on /dev/failed, and something about devtmpfs not available. This was early enough in the boot process, that I couldn't find anything about it in the logs, however, and I did not see these messages in the latest kernel that fails to boot. thanks, maria -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#606192: system boot sometimes stuck with "waiting for /dev to be fully populated."
I am having this problem after upgrading from Lenny to Squeeze. It is stuck on this screen for a few minutes, and then goes into some strange state where the screen is not getting a signal, but the machine appears to be doing something, and I have to reset the power to get it to reboot. I can boot into previous kernels still. Tried installing firmware-linux-nonfree, but this did not help. thanks, maria -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#555966: avelsieve: Cannot modify header information
Hi Hauke, I had put this problem on the back burner, and recently looked into it again. Turns out that somehow an extra blank line had been inserted into the top of managesieve.lib.php. I guess this happened somehow when I was moving the web site from the old server. No idea how, but making be the first line in the file, instead of a blank line, made everything work just fine again. cheers, maria Jan Hauke Rahm wrote: tags 555966 + moreinfo unreproducible thanks Hi Maria, you found the right config file (sorry for being unspecific) but I can't seem to find the reason for the bug you reported. On Mon, Nov 16, 2009 at 04:00:53PM -0800, Maria McKinley wrote: When a user tries to make any changes to filters from the squirrelmail filters interface, then he/she gets the following sorts of errors (depending on what changes he/she is trying to make): Warning: Cannot modify header information - headers already sent by (output started at /usr/share/squirrelmail/plugins/avelsieve/include/managesieve.lib.php:2) in /usr/share/squirrelmail/plugins/avelsieve/edit.php on line 136 Warning: Cannot modify header information - headers already sent by (output started at /usr/share/squirrelmail/plugins/avelsieve/include/managesieve.lib.php:2) in /usr/share/squirrelmail/plugins/avelsieve/table.php on line 124 managesieve.lib.php contains only comments in line 2 unless you changed it. There shouldn't be any output at all. I'm sorry, I can't see how to help you here. Hauke -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#555966: avelsieve: Cannot modify header information
Jan Hauke Rahm wrote: Hi Maria, thanks for your report. It seems you've found reportbug quite usefull, huh? :) On Thu, Nov 12, 2009 at 02:27:47PM -0800, Maria Mckinley wrote: When a user tries to make any changes to filters from the squirrelmail filters interface, then he/she gets the following sorts of errors (depending on what changes he/she is trying to make): Warning: Cannot modify header information - headers already sent by (output started at /usr/share/squirrelmail/plugins/avelsieve/include/managesieve.lib.php:2) in /usr/share/squirrelmail/plugins/avelsieve/edit.php on line 136 Warning: Cannot modify header information - headers already sent by (output started at /usr/share/squirrelmail/plugins/avelsieve/include/managesieve.lib.php:2) in /usr/share/squirrelmail/plugins/avelsieve/table.php on line 124 That doesn't sound right and I can't reproduce that here. Can you for a start send me the output of grep "\$plugins\[[0-9]\+\]" $SM_CONFIG | cut -d "'" -f2 and dpkg -l | egrep "(squirrelmail|avelsieve)" I'll have a look into that later. Thanks! Hauke PS: Please always keep the bug address in CC. Hope I checked the right config file... ella:/etc/squirrelmail# grep "\$plugins\[[0-9]\+\]" config.php | cut -d "'" -f2 calendar delete_move_next abook_take message_details preview_pane squirrel_logger bug_report squirrelspell avelsieve ella:/etc/squirrelmail# dpkg -l | egrep "(squirrelmail|avelsieve)" ii avelsieve 1.9.7-6+lenny1 Sieve mail filters plugin for SquirrelMail ii squirrelmail2:1.4.15-4+lenny2 Webmail for nuts ii squirrelmail-compatibility 2.0.12-1 SquirrelMail plugin: Let other plugins work with older/newer S ii squirrelmail-locales1.4.13-20071220-1 Translations for the SquirrelMail Webmail package ii squirrelmail-logger 2.2-1 SquirrelMail plugin: Add logging functionality to your webmail cheers, maria -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#555966: avelsieve: Cannot modify header information
Package: avelsieve Version: 1.9.7-6+lenny1 Severity: normal When a user tries to make any changes to filters from the squirrelmail filters interface, then he/she gets the following sorts of errors (depending on what changes he/she is trying to make): Warning: Cannot modify header information - headers already sent by (output started at /usr/share/squirrelmail/plugins/avelsieve/include/managesieve.lib.php:2) in /usr/share/squirrelmail/plugins/avelsieve/edit.php on line 136 Warning: Cannot modify header information - headers already sent by (output started at /usr/share/squirrelmail/plugins/avelsieve/include/managesieve.lib.php:2) in /usr/share/squirrelmail/plugins/avelsieve/table.php on line 124 thanks, maria -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages avelsieve depends on: ii debconf1.5.24Debian configuration management sy ii squirrelmail 2:1.4.15-4+lenny2 Webmail for nuts avelsieve recommends no packages. Versions of packages avelsieve suggests: ii cyrus-imapd-2.2 2.2.13-14+lenny3 Cyrus mail system (IMAP support) -- debconf information: avelsieve/no_purge: * avelsieve/runconfig: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#482817: initscripts: No longer mounts NFS filesystems at startup
Oops, hit send too soon. I was able to get portmap working using the older version (etch portmap 5-26), but statd still did not start up. It complains that: Opening /var/run/rpc.statd.pid failed: Read-only file system. Which seems crazy, as the whole point of this is to have / mounted over nfs, and it has to be read-only until statd starts running, yes? Note this is the message I got when I tried to start statd after the system had booted, the boot message went by too quickly to see if it complained about the same thing at boot. thanks, maria -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#482817: initscripts: No longer mounts NFS filesystems at startup
I am having a similar problem, and portmap 6.0-9 does not solve my problem either. On my setup, rpc.statd does not start because portmap does not start, so my nfs mounts do not happen. I end up booting with the read only file system mounted by initrd. I did also try adding ASYNCMOUNTNFS=no to /etc/default/rcS regards, maria I tried installing the previous version of portmap (etch portmap 5-26), and it still does not start. What does portmap depend on, ie. need to have running, in order to start? Could it be something further up stream preventing it from starting? I cannot get it running at all, even once the system is booted and I have a command line. thanks, maria -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#482817: initscripts: No longer mounts NFS filesystems at startup
I am having a similar problem, and portmap 6.0-9 does not solve my problem either. On my setup, rpc.statd does not start because portmap does not start, so my nfs mounts do not happen. I end up booting with the read only file system mounted by initrd. I did also try adding ASYNCMOUNTNFS=no to /etc/default/rcS regards, maria -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
