|
Bugzilla – Full Text Bug Listing |
| Summary: | Upgrading from openSUSE 11.4 to openSUSE 12.1 breaks third-party LSB-compliant System V style init scripts | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Bart Van Assche <bart.vanassche> |
| Component: | Basesystem | Assignee: | Frederic Crozat <fcrozat> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
dmesg output
System log since boot |
||
|
Description
Bart Van Assche
2011-12-22 13:41:57 UTC
Filed this as a new bug as asked in comment 28 of http://bugzilla.novell.com/show_bug.cgi?id=725917. could you check /var/log/messages for error message ? what is the output of systemctl status scst ? Haven't found any error messages in /var/log/messages. Regarding the systemctl output: # systemctl status scst Failed to issue method call: Unit name scst is not valid. try systemctl status scst.service # systemctl status scst.service
scst.service - LSB: SCST - A Generic SCSI Target Subsystem
Loaded: loaded (/etc/init.d/scst)
Active: inactive (dead)
CGroup: name=systemd:/system/scst.service
could you reboot with adding "systemd.log_level=debug systemd.log_target=kmsg" on your kernel command line and attach dmesg output after rebooting ? After having run "zypper update" I see different behavior than what was reported in #0: without systemd the script still works fine and with systemd it does now something but still not what it should do. # SYSTEMD_NO_WRAP=true /etc/init.d/scst stop; echo $? Stopping SCST done 0 # SYSTEMD_NO_WRAP=true /etc/init.d/scst start; echo $? Loading and configuring SCST done 0 # /etc/init.d/scst stop; echo $? redirecting to systemctl 0 # /etc/init.d/scst start; echo $? redirecting to systemctl Job failed. See system logs and 'systemctl status' for details. 1 Created attachment 472342 [details]
dmesg output
The attached file is the output of:
# SYSTEMD_NO_WRAP=true /etc/init.d/scst stop; dmesg -c >/dev/null; /etc/init.d/scst start; dmesg -c > dmesg-scst.txt
I need the full log of dmesg, since your system was started (and it would be great if you could ensure SYSTEMD_NO_WRAP is not set when you reboot, so the trace would be complete when dmesg is called the first time). Created attachment 472349 [details]
System log since boot
System log since boot, with SYSTEMD_NO_WRAP not set.
Regarding the kernel I'm running: it's a 3.2.1 kernel + srp-ha patches + scst_exec_req_fifo-3.2.patch + 3.3-rc1 commit 625cbfa + 3.3-rc1 commit 2cd094f. The reported issue also occurs with SUSE's kernel-desktop-3.1.0-1.2.1.x86_64 kernel by the way. it seems scst wasn't started at startup, since I don't see it at all in the trace you posted. Please, make sure the service was started before doing dmesg and don't compress the trace when attaching it to bugzilla. Correct, SCST wasn't started at startup - I start that service manually. The /etc/init.d/scst script seems to work now with the latest openSUSE 12.1 userspace packages. It's still not clear to me though what has been causing the failure. I'll keep an eye on this, and thanks for looking into this. there were some changes in 12.1 maintenance update for systemd, which might have fixed scst script handling. Let's close this as "fixed", feel free to reopen if you have the issue. |