Menu
▾
▴
[linux-iscsi-devel] [ linux-iscsi-Bugs-955690 ] iscsi daemon is not started automatically after system boot
|
From: SourceForge.net <no...@so...> - 2004-05-20 08:49:13
|
Bugs item #955690, was opened at 2004-05-18 08:29 Message generated for change (Comment added) made by surekhap You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=387023&aid=955690&group_id=26396 Category: iscsi-drvr Group: 4.0.1 Status: Open Resolution: None Priority: 5 Submitted By: Shashi Kiran T.R. (shkiran) Assigned to: Surekha P.C (surekhap) Summary: iscsi daemon is not started automatically after system boot Initial Comment: Configuration : [root@linux-2 root]# uname -a Linux linux-2 2.6.5 #1 SMP Tue May 11 14:24:30 IST 2004 i686 i686 i386 GNU/Linux [root@linux-2 root]# iscsi-ls ****************************************** ************************************* SFNet iSCSI Driver Version ... 4:0.1.5 (16-May- 2004) ****************************************** ************************************* iscsi daemon is not started automatically when system comes up after a reboot. When iscsi service is started manually from command line the following messages are logged. This is misleading because "/udev/iscsictl" file is in fact getting created after some delay: ----------------------- May 18 13:33:42 linux-2 iscsid[2104]: version 4:0.1.5 variant (16-May-2004) May 18 13:33:42 linux-2 iscsid[2104]: cannot open /udev/iscsictl: No such file or directory May 18 13:33:42 linux-2 iscsid[2104]: could not open control device /udev/iscsictl. Make sure iscsi is loaded ----------------------- ---------------------------------------------------------------------- >Comment By: Surekha P.C (surekhap) Date: 2004-05-20 08:49 Message: Logged In: YES user_id=763349 The problem is with udev since udev daemon is not getting started after reboot. As a result /udev/iscsictl entry is not created, and driver fails to start. The above messages are logged since the iSCSI deamon is not able to open iscsi control device. Will check with latest udev package to see if the problem persists. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-05-20 08:45 Message: Logged In: NO The problem is with udev since udev daemon is not getting started after reboot. As a result /udev/iscsictl entry is not created, and driver fails to start. The above messages are logged since the iSCSI deamon is not able to open iscsi control device. Will check with latest udev package to see if problem persists. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=387023&aid=955690&group_id=26396 |