[sles-beta] Lots of basic service failing to start with SLES12B8

urs.frey at post.ch urs.frey at post.ch
Fri Jun 13 01:03:10 MDT 2014


Hi Darren

Yes the same here

h063ur:~ # journalctl | grep failed
Jun 10 11:18:56 localhost kernel: acpi PNP0A08:00: ACPI _OSC support notification failed, disabling PCIe ASPM
Jun 10 11:19:08 h063ur systemd[1]: Unit plymouth-start.service entered failed state.
Jun 10 11:19:10 h063ur systemd[1]: Unit plymouth-start.service entered failed state.
Jun 10 11:19:19 h063ur systemd[1]: Unit kdump.service entered failed state.
Jun 10 11:19:19 h063ur boot.kdump[1775]: ..failed

regards

Urs Frey
Post CH AG
Informationstechnologie
IT Betrieb
Webergutstrasse 12
3030 Bern (Zollikofen)
Telefon : ++41 (0)58 338 58 70
FAX     : ++41 (0)58 667 30 07
E-Mail:   urs.frey at post.ch<mailto:urs.frey at post.ch>

Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Darren Thompson
Gesendet: Thursday, June 12, 2014 11:18 PM
An: SUSE Linux Enterprise High Availability Authorized Beta Program; sles-beta at lists.suse.com
Betreff: Re: [sles-beta] Lots of basic service failing to start with SLES12B8

oops

Actually left out the most important bit of log, where udev failes...

node1:~ # journalctl | grep failed
Jun 13 07:08:54 localhost kernel: tsc: Fast TSC calibration failed
Jun 13 07:08:54 localhost kernel: tsc: Marking TSC unstable due to check_tsc_sync_source failed
Jun 13 07:08:54 localhost kernel: acpi PNP0A03:00: ACPI _OSC support notification failed, disabling PCIe ASPM
Jun 13 07:08:54 localhost systemd[1]: Unit plymouth-start.service entered failed state.
Jun 13 07:09:02 node1 systemd[1]: Unit plymouth-start.service entered failed state.
Jun 13 07:09:02 node1 systemd[1]: Unit systemd-udev-settle.service entered failed state.

Darren

On 13 June 2014 07:15, Darren Thompson <darrent at akurit.com.au<mailto:darrent at akurit.com.au>> wrote:
Team

I am seeing lots of basic services failing to start under SLES12B8

The udev in particular seems to have nasty flow-on effects (seems to stop multipath working, which stops clustering)...

here is an extract from the startup/journalctl

node1:~ # journalctl | grep failed
Jun 13 07:08:54 localhost kernel: tsc: Fast TSC calibration failed
Jun 13 07:08:54 localhost kernel: tsc: Marking TSC unstable due to check_tsc_sync_source failed
Jun 13 07:08:54 localhost kernel: acpi PNP0A03:00: ACPI _OSC support notification failed, disabling PCIe ASPM
Jun 13 07:08:54 localhost systemd[1]: Unit plymouth-start.service entered failed state.
Jun 13 07:09:02 node1 systemd[1]: Unit plymouth-start.service entered failed state.

These were "in-place upgraded" from SLES12B7 so tis could be a unique error due to not being clean installed (hence no automatic SR).

I'm planning on rebuilding my cluster clean on SLES12B8 over weekend (nothing better to do with my free time;-)

Is anyone else seeing these errors (if yes then I'll raise the SR's now) if not then let me know...

Darren

--

Darren Thompson

Professional Services Engineer / Consultant

 [cid:image001.jpg at 01CB7C0C.6C6A2AE0]

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au<mailto:steve at akurit.com.au>
Web: www.akurit.com.au<http://www.akurit.com.au/>



--

Darren Thompson

Professional Services Engineer / Consultant

 [cid:image001.jpg at 01CB7C0C.6C6A2AE0]

Level 3, 60 City Road

Southgate, VIC 3006

Mb: 0400 640 414

Mail: darrent at akurit.com.au<mailto:steve at akurit.com.au>
Web: www.akurit.com.au<http://www.akurit.com.au/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140613/730bbcb0/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 3692 bytes
Desc: image001.jpg
URL: <http://lists.suse.com/mailman/private/sles-beta/attachments/20140613/730bbcb0/attachment.jpg>


More information about the sles-beta mailing list