Has any one seen this behavior on FC4 systems, and know what to do about it?
You go into a text terminal and wan to change to init level 3, so you execute the command init 3. The machine hangs. (more about this later)
So just to try something you enter init 1 instead of init 3. The machine goes to init level 1. Aha you say. I know what to do and you type init 3 The machine not to be bested by a mere user changes to init level 5.
A kind of work around>
If you go into a terminal and you type init 3 and it hangs in various places depending on how long you wait and whether you hit return. Now you hit ctrl-alt-f7 the screen goes black. You then hit ctl-alt-f1 and eureka you are in init level 3. Is that obscure enough a procedure for you. I tried this on three machines and it worked every time.
What is happening here? Does any one know?
On Mon, 2005-08-29 at 16:31 -0500, akonstam@trinity.edu wrote:
Has any one seen this behavior on FC4 systems, and know what to do about it?
You go into a text terminal and wan to change to init level 3, so you execute the command init 3. The machine hangs. (more about this later)
So just to try something you enter init 1 instead of init 3. The machine goes to init level 1. Aha you say. I know what to do and you type init 3 The machine not to be bested by a mere user changes to init level 5.
A kind of work around>
If you go into a terminal and you type init 3 and it hangs in various places depending on how long you wait and whether you hit return. Now you hit ctrl-alt-f7 the screen goes black. You then hit ctl-alt-f1 and eureka you are in init level 3. Is that obscure enough a procedure for you. I tried this on three machines and it worked every time.
What is happening here? Does any one know?
--
======================================================================= I hope you're not pretending to be evil while secretly being good. That would be dishonest.
Aaron Konstam Computer Science Trinity University telephone: (210)-999-7484
Aaron,
Does hitting return in the virtual terminal return a prompt after you enter runlevel 3?
I have seen what you describe on FC3. I think the prompt after typing init 3 is getting lost. I just reproduced it on an x86_64 machine and I see on an i386 machine as well. Maybe a bug report is in order.
Bob...
On Mon, Aug 29, 2005 at 06:15:54PM -0400, Bob Chiodini wrote:
On Mon, 2005-08-29 at 16:31 -0500, akonstam@trinity.edu wrote:
Has any one seen this behavior on FC4 systems, and know what to do about it?
You go into a text terminal and wan to change to init level 3, so you execute the command init 3. The machine hangs. (more about this later)
So just to try something you enter init 1 instead of init 3. The machine goes to init level 1. Aha you say. I know what to do and you type init 3 The machine not to be bested by a mere user changes to init level 5.
A kind of work around>
If you go into a terminal and you type init 3 and it hangs in various places depending on how long you wait and whether you hit return. Now you hit ctrl-alt-f7 the screen goes black. You then hit ctl-alt-f1 and eureka you are in init level 3. Is that obscure enough a procedure for you. I tried this on three machines and it worked every time.
What is happening here? Does any one know?
--
Aaron,
Does hitting return in the virtual terminal return a prompt after you enter runlevel 3?
I have seen what you describe on FC3. I think the prompt after typing init 3 is getting lost. I just reproduced it on an x86_64 machine and I see on an i386 machine as well. Maybe a bug report is in order.
Bob...
No prompt is returned. The machine has hung. However, I think what you are describing is the behavior on earlier versions. When you ran init 3 some lines appeared but after the line anacron appeared you had to hit return to get the prompt.
In out case , either the screen goes black and hangs or sometimes you get as far as the line anacron but hitting return does nothing.
On Tuesday 30 August 2005 12:38, akonstam@trinity.edu wrote:
No prompt is returned. The machine has hung. However, I think what you are describing is the behavior on earlier versions. When you ran init 3 some lines appeared but after the line anacron appeared you had to hit return to get the prompt.
In out case , either the screen goes black and hangs or sometimes you get as far as the line anacron but hitting return does nothing.
Does this still happen if you try the 'vesa' X driver?
-Andy
On Tue, Aug 30, 2005 at 12:40:26PM +0100, Andy Green wrote:
On Tuesday 30 August 2005 12:38, akonstam@trinity.edu wrote:
No prompt is returned. The machine has hung. However, I think what you are describing is the behavior on earlier versions. When you ran init 3 some lines appeared but after the line anacron appeared you had to hit return to get the prompt.
In out case , either the screen goes black and hangs or sometimes you get as far as the line anacron but hitting return does nothing.
Does this still happen if you try the 'vesa' X driver?
-Andy
As I keep telling my students you need to ask even it shows your ignorance. Maybe it is the early hour but I don't know how to try the 'vesa' X driver or even what the 'vesa' X driver is. I would like to know what it is if it potentially will solve our problem. Could you clarify?
--
------------------------------------------- Aaron Konstam Computer Science Trinity University telephone: (210)-999-7484
On Tue, 2005-08-30 at 06:38 -0500, akonstam@trinity.edu wrote:
On Mon, Aug 29, 2005 at 06:15:54PM -0400, Bob Chiodini wrote:
On Mon, 2005-08-29 at 16:31 -0500, akonstam@trinity.edu wrote:
Has any one seen this behavior on FC4 systems, and know what to do about it?
You go into a text terminal and wan to change to init level 3, so you execute the command init 3. The machine hangs. (more about this later)
So just to try something you enter init 1 instead of init 3. The machine goes to init level 1. Aha you say. I know what to do and you type init 3 The machine not to be bested by a mere user changes to init level 5.
A kind of work around>
If you go into a terminal and you type init 3 and it hangs in various places depending on how long you wait and whether you hit return. Now you hit ctrl-alt-f7 the screen goes black. You then hit ctl-alt-f1 and eureka you are in init level 3. Is that obscure enough a procedure for you. I tried this on three machines and it worked every time.
What is happening here? Does any one know?
--
Aaron,
Does hitting return in the virtual terminal return a prompt after you enter runlevel 3?
I have seen what you describe on FC3. I think the prompt after typing init 3 is getting lost. I just reproduced it on an x86_64 machine and I see on an i386 machine as well. Maybe a bug report is in order.
Bob...
No prompt is returned. The machine has hung. However, I think what you are describing is the behavior on earlier versions. When you ran init 3 some lines appeared but after the line anacron appeared you had to hit return to get the prompt.
In out case , either the screen goes black and hangs or sometimes you get as far as the line anacron but hitting return does nothing.
--
Hey Aaron,
Two things come to mind on this....
1) Are we really, really sure it is "hung"? Sometimes with the death of X, it leaves me on tty7, and simply hitting Ctrl-Alt-F1 or Ctrl-Alt-F2 brings me to my text based login prompt.
2) I thought I remembered reading something about one or more of the X video drivers causing problems going back and forth to text mode virtual consoles. Perhaps trying a "more generic" video driver in your X configuration (system-config-display - Hardware Tab).
Of course, another test would be to try to connect to the machine remotely after dropping it to runlevel 3 - you could try ssh'ing into it to test whether it is truly hung or just a console thing...
HTH,
--Rob
On Tuesday 30 August 2005 13:44, akonstam@trinity.edu wrote:
As I keep telling my students you need to ask even it shows your ignorance. Maybe it is the early hour but I don't know how to try the 'vesa' X driver or even what the 'vesa' X driver is. I would like to know what it is if it potentially will solve our problem. Could you clarify?
Yep. X is the graphical display system, it keeps its configuration in /etc/X11/xorg.conf.
If you make a backup of that, then have a look in there, you'll see it is made up of various stanzas which talk about your keyboard, mouse, monitor, display adapter and "screens", which are the association of these other things into a single monitor.
You want to look for this:
Section "Device" ... Driver "mydriver" ... EndSection
mydriver is the name of your current X video driver. Comment out the old Driver line with a #
# Driver "mydriver"
and add in the vesa driver instead
Driver "vesa"
underneath it. Then save the file and restart X (Ctrl-Alt-Backspace will do it if you saved your stuff and are on VT7 (Ctrl-Alt-F7)).
Now you should come up reasonably as before, but you are using a very boring, 'safe' driver with no real accelleration. If the behaviours that you don't like persist, now you can rule out the X display driver as the source. But perhaps the behaviours will be gone, in which case you know it is likely coming from your old X display driver, whatever that was.
-Andy
On Wed, Aug 31, 2005 at 06:54:09PM +0100, Andy Green wrote:
On Tuesday 30 August 2005 13:44, akonstam@trinity.edu wrote:
As I keep telling my students you need to ask even it shows your ignorance. Maybe it is the early hour but I don't know how to try the 'vesa' X driver or even what the 'vesa' X driver is. I would like to know what it is if it potentially will solve our problem. Could you clarify?
Yep. X is the graphical display system, it keeps its configuration in /etc/X11/xorg.conf.
If you make a backup of that, then have a look in there, you'll see it is made up of various stanzas which talk about your keyboard, mouse, monitor, display adapter and "screens", which are the association of these other things into a single monitor.
You want to look for this:
Section "Device" ... Driver "mydriver" ... EndSection
mydriver is the name of your current X video driver. Comment out the old Driver line with a #
# Driver "mydriver"
and add in the vesa driver instead
Driver "vesa"underneath it. Then save the file and restart X (Ctrl-Alt-Backspace will do it if you saved your stuff and are on VT7 (Ctrl-Alt-F7)).
Now you should come up reasonably as before, but you are using a very boring, 'safe' driver with no real accelleration. If the behaviours that you don't like persist, now you can rule out the X display driver as the source. But perhaps the behaviours will be gone, in which case you know it is likely coming from your old X display driver, whatever that was.
-Andy
I could try this but the same behavior occurs on machines that have a wide variety of drivers being used (nvidea, intel, etc). For example my machine has a ATI Technologies Inc. R128 video card and uses the r128 driver. It is hard to believe all these drivers have the same bug.
On Wed, 2005-08-31 at 08:31 -0400, Robert Locke wrote:
On Tue, 2005-08-30 at 06:38 -0500, akonstam@trinity.edu wrote:
On Mon, Aug 29, 2005 at 06:15:54PM -0400, Bob Chiodini wrote:
On Mon, 2005-08-29 at 16:31 -0500, akonstam@trinity.edu wrote:
Has any one seen this behavior on FC4 systems, and know what to do about it?
You go into a text terminal and wan to change to init level 3, so you execute the command init 3. The machine hangs. (more about this later)
So just to try something you enter init 1 instead of init 3. The machine goes to init level 1. Aha you say. I know what to do and you type init 3 The machine not to be bested by a mere user changes to init level 5.
A kind of work around>
If you go into a terminal and you type init 3 and it hangs in various places depending on how long you wait and whether you hit return. Now you hit ctrl-alt-f7 the screen goes black. You then hit ctl-alt-f1 and eureka you are in init level 3. Is that obscure enough a procedure for you. I tried this on three machines and it worked every time.
What is happening here? Does any one know?
--
Aaron,
Does hitting return in the virtual terminal return a prompt after you enter runlevel 3?
I have seen what you describe on FC3. I think the prompt after typing init 3 is getting lost. I just reproduced it on an x86_64 machine and I see on an i386 machine as well. Maybe a bug report is in order.
Bob...
No prompt is returned. The machine has hung. However, I think what you are describing is the behavior on earlier versions. When you ran init 3 some lines appeared but after the line anacron appeared you had to hit return to get the prompt.
In out case , either the screen goes black and hangs or sometimes you get as far as the line anacron but hitting return does nothing.
--
Hey Aaron,
Two things come to mind on this....
- Are we really, really sure it is "hung"? Sometimes with the death of
X, it leaves me on tty7, and simply hitting Ctrl-Alt-F1 or Ctrl-Alt-F2 brings me to my text based login prompt.
- I thought I remembered reading something about one or more of the X
video drivers causing problems going back and forth to text mode virtual consoles. Perhaps trying a "more generic" video driver in your X configuration (system-config-display - Hardware Tab).
Of course, another test would be to try to connect to the machine remotely after dropping it to runlevel 3 - you could try ssh'ing into it to test whether it is truly hung or just a console thing...
HTH,
--Rob
As I see it, ctrl-alt-F7 is the graphics console and has no definition in runlevel 3.
I have seen the same behavior as was reported where the console seemed to 'hang' when switching to runlevel 3 from runlevel 5. The simple expediency of using ctrl-alt-F2 gets me to a text console, and sure enough I find that the X windows system is not running.
I put the 'problem' down to the fact that it is the terminal definition that goes away as X gets shutdown but the console is still set to a now undefined terminal. Switching to a terminal that is defined (F1 - F6) gets me past that every time.
Am Do, den 01.09.2005 schrieb Daniel Vogel um 1:58:
Please do not hijack foreign maillist threads. And please do not send HTML formatted list mails, especially if your mail client sends HTML only and no plain text part too.
http://www.fedoraproject.org/wiki/MailingListRules
After finishing my work on a server, some changes were made and i just cannot connect to my email through squirrelmail, IMAP error.
For giving valuable help it would be good if you provide the real, verbose error messages.
I checked some things and decided to re install cyrus, but i think im missing 2 things:
Certificate and database wich i cannot find out how to set them up.
The example certificate is build by Cyrus-IMAPd package install and the databases initialize during installation too.
It's weird to install it from scratch and cannot make them work.
You do not use the rpms?
...i feel noober each time, but...can someone tell me what to do? when i restart cyrus-imapd daemon, it fails when the database is getting prepared.
Provide log entries and error messages.
Daniel Vogel
Alexander
-
akonstam＠trinity.edu -
Alexander Dalloz -
Andy Green -
Bob Chiodini -
Daniel Vogel -
Jeff Vian -
Robert Locke