Defect #451

Locks bei Demuxer

Added by mj0 over 2 years ago. Updated over 2 years ago.

Status:Erledigt Start date:06/04/2009
Priority:Dringend Due date:
Assignee:zooey % Done:

100%

Category:tools
Target version:Ver. 5.0
Resolution:fixed

Description

Der Demuxer lockt immer alle systeme, gibt sie aber erst nach dem Durchlauf frei. So locken sich NFS und SQFS gegenseitig. Interessanterweise klappt der Durchlauf, wenn man den Demuxer mit einem system startet welches diesen Lock verursacht.
Bsp: ubuntu-9.04-clone::nfs und ubuntu-9.04-clone::sqfs-nbd

Demuxer wird bei einem der Systeme locken, außer man wählt es explizit, also slxconfig-demuxer ubuntu-9.04-clone::nfs

this happened the first time yesterday evening. During the demuxer run I
get a lock of a system. When I remove the lock an error occurs:

--------------
linking demuxed system 14 : ubuntu-9.04-clone::sqfs-nbd into bootloader menu
waiting for "ubuntu-9.04-clone"-lock ...................ok
!   setting kernel of system 'ubuntu-9.04-clone::sqfs-nbd' to
'vmlinuz-2.6.28-11-generic'!
Can't locate object method "new" via package
"OpenSLX::BootEnvironment::Preboot::CD" at
/opt/openslx/bin/../lib/OpenSLX/Basics.pm line 627

ls -la /export/sqfs/
-rwx------ 1 root root 3402924032 2009-05-23 12:47 ubuntu-9.04-clone
lrwxrwxrwx 1 root root         17 2009-05-23 12:44 ubuntu-9.04-clone at nbd
-> ubuntu-9.04-clone
-------------

And it seems that nothing is running except the NBD server.

Associated revisions

Revision 2efbbd9e
Added by zooey over 2 years ago

  • fixed pretty stupid bug that involved mixed use of bufferd/non-buffered IO
    which caused locks to hang even in the same process-group (for which they
    should be recursable) - closes #451

git-svn-id: http://svn.openslx.org/svn/openslx/openslx/trunk@2943 95ad53e4-c205-0410-b2fa-d234c58c8868

History

Updated by mj0 over 2 years ago

So hier mal ein paar Beispiele:

Lock bei ubuntu-9.04-clone::sqfs-nbd:

root@archive:~# slxconfig-demuxer suse-11.1-default::nfs

linking demuxed system 1 : ubuntu-8.04-default::nfs into bootloader menu
!   setting kernel of system 'ubuntu-8.04-default::nfs' to 'vmlinuz-2.6.24-23-server'!

linking demuxed system 3 : suse-10.2-main::nfs into bootloader menu

linking demuxed system 5 : scilin-4.7-default::nfs into bootloader menu
!   setting kernel of system 'scilin-4.7-default::nfs' to 'vmlinuz-2.6.9-78.0.1.EL.cern'!

demuxing system 6 : suse-11.1-default::nfs
!   uclibc-rootfs for system 'suse-11.1-default::nfs' may not be up-to-date - consider updating the vendor-OS!
active plugins: syslog,xserver,desktop,vmchooser,vmware,bootsplash,x11vnc
creating boot environment for preboot
creating boot environment for pxe

linking demuxed system 7 : suse-11.0-default::nfs into bootloader menu

linking demuxed system 8 : ubuntu-8.10-default::nfs into bootloader menu
!   setting kernel of system 'ubuntu-8.10-default::nfs' to 'vmlinuz-2.6.27-11-server'!

linking demuxed system 10 : ubuntu-9.04-clone::nfs into bootloader menu
!   setting kernel of system 'ubuntu-9.04-clone::nfs' to 'vmlinuz-2.6.28-11-generic'!

linking demuxed system 14 : ubuntu-9.04-clone::sqfs-nbd into bootloader menu
waiting for "ubuntu-9.04-clone"-lock ............ok
!   setting kernel of system 'ubuntu-9.04-clone::sqfs-nbd' to 'vmlinuz-2.6.28-11-generic'!

linking demuxed system 15 : suse-11.0-locktest::nfs into bootloader menu

creating CD-image for client preboot (based on ubuntu-9.04-clone::nfs) ...

creating CD-image for client pbexternal (based on ubuntu-9.04-clone::nfs) ...

wrote 1 system-specific and 4 client-specific configurations
2 initramfs were created
all systems ok
all boot-environments ok

Kein Lock:

root@archive:~# slxconfig-demuxer ubuntu-9.04-clone::nfs

linking demuxed system 1 : ubuntu-8.04-default::nfs into bootloader menu
!   setting kernel of system 'ubuntu-8.04-default::nfs' to 'vmlinuz-2.6.24-23-server'!

linking demuxed system 3 : suse-10.2-main::nfs into bootloader menu

linking demuxed system 5 : scilin-4.7-default::nfs into bootloader menu
!   setting kernel of system 'scilin-4.7-default::nfs' to 'vmlinuz-2.6.9-78.0.1.EL.cern'!

linking demuxed system 6 : suse-11.1-default::nfs into bootloader menu

linking demuxed system 7 : suse-11.0-default::nfs into bootloader menu

linking demuxed system 8 : ubuntu-8.10-default::nfs into bootloader menu
!   setting kernel of system 'ubuntu-8.10-default::nfs' to 'vmlinuz-2.6.27-11-server'!

demuxing system 10 : ubuntu-9.04-clone::nfs
!   setting kernel of system 'ubuntu-9.04-clone::nfs' to 'vmlinuz-2.6.28-11-generic'!
!   uclibc-rootfs for system 'ubuntu-9.04-clone::nfs' may not be up-to-date - consider updating the vendor-OS!
active plugins: xserver,desktop,x11vnc,syslog,bootsplash,profile,vmchooser,vmware
creating boot environment for preboot
creating boot environment for pxe

linking demuxed system 14 : ubuntu-9.04-clone::sqfs-nbd into bootloader menu
!   setting kernel of system 'ubuntu-9.04-clone::sqfs-nbd' to 'vmlinuz-2.6.28-11-generic'!

linking demuxed system 15 : suse-11.0-locktest::nfs into bootloader menu

creating CD-image for client preboot (based on ubuntu-9.04-clone::nfs) ...

creating CD-image for client pbexternal (based on ubuntu-9.04-clone::nfs) ...

wrote 1 system-specific and 4 client-specific configurations
2 initramfs were created
all systems ok
all boot-environments ok

slxconfig-demuxer ohne System läuft auch durch, auch wenn es auch schon mal nicht der Fall war, glaube ich zumindest.

Updated by zooey over 2 years ago

Bei obigem Beispiel mit Lock - wie kommt der Demuxer dann an das Lock, nachdem er ausgibt, dass er darauf wartet? Greifst Du da manuell ein, oder passiert das automatisch nach einer gewissen Zeit?

Updated by mj0 over 2 years ago

Ja ich lösche es dann immer manuell. Keine Ahnung wie lange ich sonst warten müsste. Aber habe auch schon 3 Zeilen mit Punkten vollgemalt gesehen bis ich das Lock gelöscht hatte.

Updated by zooey over 2 years ago

  • Status changed from Neu to Gelöst
  • % Done changed from 0 to 100
  • Resolution set to fixed

Das eigentliche Problem war klein (r2943), aber dahinter versteckte sich auch ein großes (r2944) :-)

Updated by mj0 over 2 years ago

  • Status changed from Gelöst to Erledigt

Getestet, geht wieder. kann somit geschlossen werden.

Also available in: Atom PDF