Re: lug-bg: Speshno: Ne boot-va.

[danchev@xxxxxxxxx (George Danchev)]

Zna4i: 
popitaj google.co za tvoq problem:

Id "1" respawning too fast: disabled for 5 minutes

[note: respawNing, a ne respawHing]

vizh linkovete ima i specialno za suse,  i stava vypros 4e nqkoj init script 
se opitva da startira nqkoj damn display manager kato xdm, gdm, kdm, wdm, 
etc... 

> Ne vyrvi prevklujchvaneto nito kato single,nito kato probvam normalno da
> vljaza i zabie. Kato zabie sled $ init x poluchavam redovete s
> "respawning..." i spira. Ne umira syvsem, na vseki 5 minuti bylva 6 reda,
> respawning ot 1 do 6. Alt-F2 i drugite mi davat prazen ekran, nishto. Na
> F1 moga pone s PageUp da si razgledjdam kernel syobshtenijata do
> trygvaneto na init.

taka e zastoto  v multi user mode izpadash v edno polozhenie na neprestanni 
opiti display managera  da zapusne X-sa i pri neuspeh go repeat-va sled edi 
kolko si minuti, nito si na tty nito X-sa e zapusnat. Kernela e zdrav, prav i 
korav - nqma gutane ! 

a tezi problemi, vsystnost maj ne sa problemi

> Local ACPI disabled by BIOS -- reenabling
BIOS-a ne enable-va, OK kernela reenable-va... no probs ?

> Could not enable APIC!
ok, vse edno 4e e podadena boot opciq noapic, nqma nuzhda izrishno da se dava 
v slu4aq, ima smisyl ako kernel enable-va APIC, a pyk nie ne iskame tova ?

Vse pove4e si mislq 4e update-a na BIOS-a ne e pri4inata za problema, osven 
tova v edin ot starite ti postingi 4eta 4e vrystaneto na stariq bios systo ne 
pomagalo. Nesto e pipano i omazano po init scriptovete, ili konfiguracionnite 
fajlove na display managera - xdm ili xfre86... ili ti ili nqkoj neposlushna 
i/ili bugava instalaciq na nqkoq programa. 
nqma li na4in da reinstalirash tova xdm, kdm ili tam kyfto displey manager 
imash, ako trqbva deinstall i posle install. Siguren sym 4e  nqmash backup na 
/etc-to, no nqma li na4in da backup-nesh segashnoto systoqnie na tvoito /etc, 
i da reinstall-nesh ot rpm package "sysvinit"-a, vsystnost taka se kazva 
package pri debian, pri suse neznam kak e. Nabozil si si init scriptovete - 
tova e moqta diagnoza - ne kazvam 4e sym 100% prav, no neka nqkoj po-advanced 
user kojto ima suse pod ryka da si dade mnenieto za diagnoza i le4enie. 

Eto problemite koito mu dava init-a:
[mnogo problemi, mnogo nesto, nqkoj ili nesto e bozil/bozilo mnogo qko tuka]
-------------------------------------------------------------------------------------------------

DHCLIENT: The device  eth0 is not available at the moment.
DHCLIENT: Please check if the driver is set up correctly.

/etc/rc.d/dhclient says:
No devices available/configured to start dhcp client on
 7 [1A 8DHCLIENT: DHCP for PCMCIA devices is normally handled directly by the 
card
DHCLIENT: manager. Use "cardctl eject/insert" or eject/insert the card 
manually.
DHCLIENT: You can also use this script if you give the device name the a
DHCLIENT: second argument.
No devices available/configured to start dhcp client on
 7 [1A 8

Here I finished with run level 3. Then I did YAST and configured
(tried to) the dhpclient and the PCMCIA card. Yast said ok but could
not finish, cycling non-stop with the message:
/bin/ls: Argument list too long
/sbin/conf.d/SuSEconfig.gdm: Argument list too long
/usr/bin/manpath: Argument list too long

So I did Ctr-C to interrupt YAST and continued to test the services of
runlevel 5. Now I even started the xemacs to make use of its eshel and
term mode. To be on the safe side I repeated starting processes and
daemons that were already running from the previous exercise in
runlevel 3.

Runlevel 5 

These messages appear suddenly after I did M-x term in xemacs:
(1) (error/warning) Error in process filter: (error /etc/X1/ is not a 
directory)

(2) (error/warning) Error in process filter: (error /etc/X1/ is not a 
directory)

DHCLIENT: DHCP for PCMCIA devices is normally handled directly by the card
DHCLIENT: manager. Use "cardctl eject/insert" or eject/insert the card 
manually.
DHCLIENT: You can also use this script if you give the device name the a
DHCLIENT: second argument.
No devices available/configured to start dhcp client on
 7 [1A 8

 # /etc/rc.d/i4l start
/dev/isdninfo: No such device

(none):/tmp # /etc/rc.d/hotplug start
Starting hotplugging services [ pci** can't synthesize pci hotplug events
 usb ] 7  [80C [10D [1;32mdone [m  8

(none):/tmp # /etc/rc.d/dictd start
Starting DICTDdictd (main): dictd already running with pid 4161
   remove /var/run/dictd.pid or use -f to force startup
startproc:  exit status of parent of /usr/sbin/dictd: 1
 7  [80C [10D [1;31mfailed [m  8

(none):/tmp # /etc/rc.d/lpd start
Starting lpd2002-04-08-00:55:01.886 Get_local_host: hostname '(none)' bad
2002-04-08-00:55:01.985 Get_local_host: hostname '(none)' bad
 7  [80C [10D [1;31mfailed [m  8

(none):/tmp # /etc/rc.d/xntpd start
Starting network time protocol daemon (NTPD) 7  [80C [10D [1;32mdone [m  8
(none):/tmp # /etc/rc.d/ypbind start
Starting ypbindLocal domain name not set
  [80C [10D [1;33mskipped [m 

(none):/tmp # /etc/rc.d/fam start
Starting File Access Monitoring Daemonfam[26062]: can't register with 
portmapper.
startproc:  exit status of parent of /usr/sbin/fam: 1
 7  [80C [10D [1;31mfailed [m  8

(none):/tmp # /etc/rc.d/ksysguardd start
Starting remote monitor daemon for ksysguard /usr/bin/ksysguardd: error while 
loading shared libraries: libsensors.so.1: cannot open shared object file: No 
such file or directory
startproc:  exit status of parent of /usr/bin/ksysguardd: 127
 7  [80C [10D [1;31mfailed [m  8

(none):/tmp # /etc/rc.d/nfsserver start
Starting kernel based NFS serverstartproc:  exit status of parent of 
/usr/sbin/rpc.mountd: 1
 7  [80C [10D [1;31mfailed [m  8

(none):/tmp # /etc/rc.d/xdm

And there we go, kde2 started and I logged in as a normal user.

Click on YAST and then Konsole gave me:
"DCOP communication error (Konsole)
There was an error setting up inter-process communications for
KDE. The message returned by the system was:
Authentication rejected, reason: None of the authentication protocols
specified are supported and host-based authentication failed. Please,
check that the "dcopserver" program is running."

Now a check gives /opt/kde2/bin/dcopserver running.

An attemt to umount with a mouse click the windows partition /dev/hda5
(still mounted by the single user, was needed to write the log
messages during the diagnostic process) gives me:
"Could not start process, can't talk to Klauncher"
-----------------------------------------------------------------------

S mnogo greshki i ugovorki se dobirash do runlevel 5 kudeto ve4e zapo4va tozi 
neprestanen cykyl s opitite na display manager-a, i syotvetno ti izpluva 
redovete:

Id "1" respawning too fast: disabled for 5 minutes
Id "2" respawning too fast: disabled for 5 minutes

Eto edin podoben problem:
http://lists.suse.com/archive/suse-sparc/2001-Apr/0108.html
[zavaliqta e pokazal kernel tasks, vmesto startiranite ot init procesi]
S otgovor:
http://lists.suse.com/archive/suse-sparc/2001-Apr/0109.html

P.S. i bglinux mozhe bi nqma nisto obsto s tova prestyplenie
P.S.S ako iskash da pokazvash mnogo mnogo golemi outputs na files po dobre gi 
ka4vaj nqkude na web, stoto edin url < ot samiq text na output-a ;-)
P.S.S.S sorry za dylgiq mail, no taka maj kartinata e po-qsna, nadqvam se 
4astite ot maila na koito ne se davat otgovori i komentari ste bydat triti.


-- 
Greets,
fr33zb1
===========================================================================
A mail-list of Linux Users Group - Bulgaria (bulgarian linuxers)
http://www.linux-bulgaria.org/ Hosted by Internet Group Ltd. - Stara Zagora