http://bugs.skolelinux.org/show_bug.cgi?id=1371
--- Comment #38 from Petter Reinholdtsen <[email protected]> 2009-12-13 21:00:37 --- I've investigated some more, trying to figure out what the problem is. I believe the problem is that several processes talk to the debconf backend in parallel, and this is the cause of the race condition. I've been able to reproduce this error, and also was able to get one successful installation. Here is an interesting part from the diff of the installation log between the two installation. (-) marks the hanging installation and (+) the non-hanging. in-target: invoke-rc.d nfs-kernel-server reload in-target: info: LTSP client installation completed successfully debconf: --> PROGRESS STOP -main-menu[1067]: (process:26991): /bin/debconf-get: -main-menu[1067]: (process:26991): return: -main-menu[1067]: (process:26991): line 4: -main-menu[1067]: (process:26991): Illegal number: d-i -main-menu[1067]: (process:26991): -main-menu[1067]: INFO: Priority changed externally, setting main-menu default to 'medium' (O K) debconf: <-- 0 OK -debconf: --> GET debconf/priority GET debconf/priority X_SAVE METAGET debian-installer/ethde tect/title Description GET auto-install/enable +main-menu[1067]: (process:27031): /bin/debconf-get: +main-menu[1067]: (process:27031): return: +main-menu[1067]: (process:27031): line 4: +main-menu[1067]: (process:27031): Illegal number: d-i +main-menu[1067]: (process:27031): +main-menu[1067]: INFO: Priority changed externally, setting main-menu default to 'medium' (O K) +debconf: --> GET debconf/priority +debconf: <-- 0 critical +debconf: --> GET debconf/priority X_SAVE METAGET debian-installer/ethdetect/title Descriptio n debconf: <-- 20 Incorrect number of arguments +debconf: --> GET auto-install/enable +debconf: <-- 0 false debconf: --> METAGET debian-installer/localechooser/title Description debconf: <-- 0 Velg språk/Choose language I am pretty sure the X_SAVE action come from a exiting debconf client, and thus that several processes are talking to debconf at the same time and on the same pipe. I've been unable to locate exactly which processes are involved. I tested to see if the problem was that that the postinst process for ltsp-client-builder udeb would exit before the ltsp-build-client process called from it, but adding a wait call before "db_progress STOP" did not solve the problem. I've written a new tool pipegraph in debian-edu-config to see if I can use it to locate the processes talking to the debconf backend at the same time. Not sure if it will lead to anything, but worth a try. -- Configure bugmail: http://bugs.skolelinux.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are watching all bug changes. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
