Mailinglist Archive: opensuse-bugs (4292 mails)

< Previous Next >
[Bug 1037012] New: Service doesn't start because of unknown runlevel
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 01 May 2017 14:05:38 +0000
  • Message-id: <bug-1037012-21960@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=1037012


Bug ID: 1037012
Summary: Service doesn't start because of unknown runlevel
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: All
OS: Other
Status: NEW
Severity: Critical
Priority: P5 - None
Component: Basesystem
Assignee: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
Reporter: petr.m@xxxxxxxxx
QA Contact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---

I upgraded my TW
and I found out that "bind" doesn't start during boot. If I start it later by
command "systemctl start named" service is starting without problem.
A few second after boot the result of "runlevel" command is unknown.

# systemctl is-enabled named
named.service is not a native service, redirecting to systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install is-enabled named
Can't determine current runlevel
disabled



But a minute later the result of "runlevel" command is N 3.

# systemctl is-enabled named
named.service is not a native service, redirecting to systemd-sysv-install.
Executing: /usr/lib/systemd/systemd-sysv-install is-enabled named
enabled

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
This Thread
  • No further messages