> I'm sorry Scott, I've been side-tracked onto some other work for a bit. > I want to get back onto this but it will have to wait a little. Hi, it's me, I'm back. :)
Reading back through this thread, it now seems obvious that I had two problems. One was the infamous 2nd login issue. I have updated lbuscd. Although I haven't done any extensive testing, it does seem fixed. But the other problem is still haunting me. > > > > When I plug in my usb drive, I get the icon on the Desktop and it gets > > > > mounted on Drives/usb. > > > > When I unplug the drive, the icon disappears and gets unmounted. > > > > When I plug it in again nothing happens although on the terminal dmesg says it got plugged in. > > 1) exactly what device is this? verbatim 512 pendrive > > Could you please provide me with a dump > > of lsusb on a full linux box? lsusb Bus 005 Device 001: ID 0000:0000 Bus 004 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 001 Device 002: ID 08ec:0015 M-Systems Flash Disk Pioneers Bus 001 Device 001: ID 0000:0000 Here I go through the troubleshooting process twice. All from the same session. The first run though is the first plugin. The second run though corresponds to the seconf plugin in. Step 1: Disable X on the workstation. SCREEN_01 = shell ok Step 2: Are you running LTSP 4.2? cat /etc/version VERSION=4.2 ok Step 3: Determining if LOCAL_STORAGE is on. On the workstation, execute the command ps -ef | grep lbuscd. ok Step 4: Does your workstation know its name? At the command prompt, type the command "hostname". ws055.ltsp Step 5: Do you have devices in your fstab? cat /etc/fstab /dev/fd0 /tmp/drives/readwrite auto rw,noatime 0 0 If you're trying to get USB plugging going, plug in a device now. new full speed UDB device uhci_hcd and address 2 ........ ........ sda: sda1 sd 0:0:0:0: Attached scsi removable disk sda cat /etc/fstab /dev/scsi/host0/bus0/target0/lun0/part1 /tmp/drives/lapiz auto rw,noatime 0 0 /dev/fd0 /tmp/drives/readwrite auto rw,noatime 0 0 Step 6: Booting X. startx Log in as the user, and open up an xterm. Step 7: Is the user in the fuse group? At the xterm prompt, type the command id. ok Step 8: Is lbussd running? As the user, check that lbussd is running. You can check this with ps -ef | grep lbussd. ok Step 9: Is the fuse module loaded? Execute the following command: lsmod | grep fuse. The fuse module should appear. ok As well, in your /dev directory, you should have a /dev/fuse file, owned by root, and group owned by fuse, with permissions 660. crw-rw---- 1 root fuse 10, 229 2006-06-29 12:04 fuse Step 10: Does your $DISPLAY variable match the terminal's hostname? Execute the following command: echo $DISPLAY. ws055.ltsp:0.0 The bit before the colon (the hostname part) must EXACTLY match the hostname that the terminal thinks it has back in step 3. ok Here I can open the usbdevice "lapiz" and use it. :) Step 11: is the lbus_event_handler firing? A quick verification that the whole LtspFS system is working, is to try to manually fire up a mount. /usr/sbin/lbus_event_handler.sh add block /tmp 1024 Temp An icon should pop up on the desktop, called "Temp", ok and browsing it should reveal the /tmp directory on your client. No If not, check to see if a "tmp" folder is created in your $HOME/Drives directory, ~/Drives$ ls lapiz readwrite tmp ~/Drives$ ls -l ls: tmp: No such file or directory and that a "Temp.desktop" file appears in your $HOME/Desktop folder. yes As well, the command mount should show an ltspfs mount in your home directory, similar to this: ltspfs on /home/sbalneav/Drives/tmp type fuse (rw,nosuid,nodev,user=sbalneav) ok To remove the mount, type the following: /usr/sbin/lbus_event_handler.sh remove block /tmp 1024 Temp ok The icon should disappear, as well as the directory in $HOME/Drives. As well, the mount command should not show the ltspfs mount anymore. ok If there are any errors printed out by the lbus_event_handler.sh script, save them, and check on the IRC channel or the mailing list. They are important, and will help the people there to help you. ************************ I pull out the usb device. The icon disappears. The mount command should not show the usbdevice ltspfs mount anymore. The mount point in the Drives directory is removed. On the terminal The usb entry in fstab is removed. The usbdevice directory /tmp/drives/lapiz is removed Now I plug the usbdevice in for a second time on the same session. Step 3: Determining if LOCAL_STORAGE is on. On the workstation, execute the command ps -ef | grep lbuscd. ok Step 4: Does your workstation know its name? At the command prompt, type the command "hostname". ws055.ltsp Step 5: Do you have devices in your fstab? cat /etc/fstab /dev/fd0 /tmp/drives/readwrite auto rw,noatime 0 0 If you're trying to get USB plugging going, plug in a device now. new full speed UDB device uhci_hcd and address 2 ........ ........ sda: sda1 sd 1:0:0:0: Attached scsi removable disk sda note: on the first plug in this was sd 0:0:0:0: Attached scsi removable disk sda cat /etc/fstab /dev/fd0 /tmp/drives/readwrite auto rw,noatime 0 0 No scsi entry! Step 6: Booting X. startx Log in as the user, and open up an xterm. (note: no usbdevice icon or directory in ~/Drives) Step 7: Is the user in the fuse group? At the xterm prompt, type the command id. ok Step 8: Is lbussd running? As the user, check that lbussd is running. You can check this with ps -ef | grep lbussd. ok Step 9: Is the fuse module loaded? Execute the following command: lsmod | grep fuse. The fuse module should appear. ok As well, in your /dev directory, you should have a /dev/fuse file, owned by root, and group owned by fuse, with permissions 660. crw-rw---- 1 root fuse 10, 229 2006-06-29 12:04 fuse Step 10: Does your $DISPLAY variable match the terminal's hostname? Execute the following command: echo $DISPLAY. ws055.ltsp:0.0 The bit before the colon (the hostname part) must EXACTLY match the hostname that the terminal thinks it has back in step 3. ok Step 11: is the lbus_event_handler firing? A quick verification that the whole LtspFS system is working, is to try to manually fire up a mount. /usr/sbin/lbus_event_handler.sh add block /tmp 1024 Temp An icon should pop up on the desktop, called "Temp", ok and browsing it should reveal the /tmp directory on your client. No If not, check to see if a "tmp" folder is created in your $HOME/Drives directory, ~/Drives$ ls lapiz readwrite tmp ~/Drives$ ls -l ls: tmp: No such file or directory and that a "Temp.desktop" file appears in your $HOME/Desktop folder. yes As well, the command mount should show an ltspfs mount in your home directory, similar to this: ltspfs on /home/sbalneav/Drives/tmp type fuse (rw,nosuid,nodev,user=sbalneav) ok To remove the mount, type the following: /usr/sbin/lbus_event_handler.sh remove block /tmp 1024 Temp ok The icon should disappear, as well as the directory in $HOME/Drives. As well, the mount command should not show the ltspfs mount anymore. ok ******************* > > The client sends some > > messages via logger() to the server. Could you please check in /var/log > > on the server, and send me what udev's sending to the server. Now I boot the terminal and watch /var/log/syslog on the server Jun 30 12:03:55 ws055.ltsp root: usbcore: registered new driver usbfs Jun 30 12:03:55 ws055.ltsp root: usbcore: registered new driver hub Jun 30 12:03:55 ws055.ltsp root: USB Universal Host Controller Interface driver v2.3 Jun 30 12:03:55 ws055.ltsp root: PCI: Found IRQ 10 for device 0000:00:07.2 Jun 30 12:03:55 ws055.ltsp root: uhci_hcd 0000:00:07.2: UHCI Host Controller Jun 30 12:03:55 ws055.ltsp root: uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1 Jun 30 12:03:55 ws055.ltsp root: uhci_hcd 0000:00:07.2: irq 10, io base 0x0000de00 Jun 30 12:03:55 ws055.ltsp root: usb usb1: configuration #1 chosen from 1 choice Jun 30 12:03:55 ws055.ltsp root: hub 1-0:1.0: USB hub found Jun 30 12:03:55 ws055.ltsp root: hub 1-0:1.0: 2 ports detected Jun 30 12:03:55 ws055.ltsp root: ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) Jun 30 12:03:55 ws055.ltsp root: usbcore: registered new driver usbmouse Jun 30 12:03:55 ws055.ltsp root: drivers/usb/input/usbmouse.c: v1.6:USB HID Boot Protocol mouse driver Jun 30 12:03:55 ws055.ltsp root: usbcore: registered new driver usbkbd Jun 30 12:03:55 ws055.ltsp root: drivers/usb/input/usbkbd.c: :USB HID Boot Protocol keyboard driver Jun 30 12:03:57 ws055.ltsp root: udev detected add of floppy Jun 30 12:03:57 ws055.ltsp /bin/ltspfsd[963]: Program started Jun 30 12:03:57 ws055.ltsp init: Entering runlevel: 5 #note: Here I plug in the usbdevice Jun 30 12:04:49 ws055.ltsp root: udev detected add of disk #note: Here I unplug it Jun 30 12:05:37 ws055.ltsp root: udev detected remove of disk Jun 30 12:05:37 ws055.ltsp root: udev detected remove of floppy #note: here I plug it in again. Jun 30 12:05:50 ws055.ltsp root: udev detected add of none Jun 30 12:05:50 ws055.ltsp lbuscd: new_block_device: Invalid number of args Jun 30 12:05:50 ws055.ltsp lbuscd: Expecting: 'AddBlockDevice|sharename|blockdev|Removeable|size|desc' This doesn't seem to be right, does it? Any ideas please? Cheers. Chris. On 5/4/06, Chris Fanning <[EMAIL PROTECTED]> wrote: > I'm sorry Scott, I've been side-tracked onto some other work for a bit. > I want to get back onto this but it will have to wait a little. > I'll post back here with those questions answered as soon as I can. > > Thanks. > Chris. > > > On 5/4/06, Scott Balneaves <[EMAIL PROTECTED]> wrote: > > On Wed, May 03, 2006 at 01:39:55PM +0200, Chris Fanning wrote: > > > Hi Scott, > > > > > > I hope I'm not bashing you too much on this. > > > Here is something else I've noticed that may help narrow things down. > > > > > > On a second login at the terminal (kde), the floppy doesn't get > > > mounted (no icon either) > > > but this doesn't alwasys happen on the second login, maybe on the the > > > third or fourth. > > > When this happens, nothing else gets mounted either. ie. cdrom and > > > pendrive. > > > > > > What tests can I do? > > > > First of all: > > > > 1) exactly what device is this? Could you please provide me with a dump > > of lsusb on a full linux box? > > > > 2) You say it gets added the first time on the client's fstab? When you > > pull it out, I'm assuming the fstab gets removed? The client sends some > > messages via logger() to the server. Could you please check in /var/log > > on the server, and send me what udev's sending to the server. > > > > If things are failing at step 4, then lbuscd or lbussd has nothing to do > > with it: udev is having problems with the device. > > > > Scott > > > > -- > > Scott L. Balneaves | "Looking beyond the embers of bridges glowing behind us > > Systems Department | To a glimpse of how green it was on the other side..." > > Legal Aid Manitoba | -- Pink Floyd "High Hopes" > > > > > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.1 (GNU/Linux) > > > > iD8DBQFEWh2qcJo/YDt+FuERArXAAJ0R/hiRKDHsUTHHGfoja0wxCGjnvQCfVU59 > > zzj/gv5c6eo4HcNELrhuknc= > > =1mtN > > -----END PGP SIGNATURE----- > > > > > > > Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
