[Bug 4880] New: koha-remove sometimes fails because user is logged int
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4880 Summary: koha-remove sometimes fails because user is logged int Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Packaging AssignedTo: lars@catalyst.net.nz ReportedBy: lars@catalyst.net.nz QAContact: koha-bugs@lists.koha-community.org Estimated Hours: 0.0 I have not been able to reproduce this, but sometimes koha-remove fails because the user is logged in. I have no idea how that happens, since the instance-specific user cannot log in at all, and there is no trace of them being logged in. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4880 Lars Wirzenius <lars@catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|lars@catalyst.net.nz |robin@catalyst.net.nz -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4880 Simon Story <simon.story@catalyst-eu.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon.story@catalyst-eu.net --- Comment #1 from Simon Story <simon.story@catalyst-eu.net> 2011-11-18 14:05:14 UTC --- Perhaps deluser/userdel are complaining that the user is logged in because the zebra daemon still running as that user. Maybe the daemon has not finished shutting down by the time the deluser command is run? -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4880 Jared Camins-Esakov <jcamins@cpbibliography.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |6684 -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4880 MJ Ray (software.coop) <mjr@software.coop> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mjr@software.coop --- Comment #2 from MJ Ray (software.coop) <mjr@software.coop> --- I think the daemon has not finished shutting down by the time the deluser command is run. Could a wait, pkill or sleep be put before the deluser? -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4880 MJ Ray (software.coop) <mjr@software.coop> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|koha-remove sometimes fails |koha-remove sometimes fails |because user is logged int |because user is logged in -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4880 --- Comment #3 from Robin Sheat <robin@catalyst.net.nz> --- hmm, this sounds quite plausible. I think a ps -u instance-koha test loop with (say) a 5 second sleep might be a useful solution here. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4880 Magnus Enger <magnus@enger.priv.no> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |magnus@enger.priv.no --- Comment #4 from Magnus Enger <magnus@enger.priv.no> --- Not sure if this really adds anything, but here goes: I have been moving some instances around today, and done some koha-removes. In the beginning I was getting errors because the koha user for the given instance was logged in. Now I have tried several times to run koha-stop-zebra before I run koha-remove, and now I'm not getting the error about the logged in user. At least that seems to confirm the theory from comment #2. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org