Bug 21559

Summary:	systemctl status mdmonitor.service returns failed
Product:	Mageia	Reporter:	peter lawford <petlaw726>
Component:	RPM Packages	Assignee:	Thomas Backlund <tmb>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, ouaurelien
Version:	6
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	mdadm	CVE:
Status comment:
Attachments:	return of mdadm --detail --scan -v return of journalctl -xe

Description peter lawford 2017-08-18 13:59:47 CEST

Description of problem:I have 4 raid volumes on my system, and they seem to be recognized by mageia 6:

see return of the command mdadm --detail --scan -v on the attached file

but:

[root@magaux alain4]# systemctl status mdmonitor.service
● mdmonitor.service - Software RAID monitoring and management
   Loaded: loaded (/usr/lib/systemd/system/mdmonitor.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since ven. 2017-08-18 10:54:23 CEST; 2h 52min ago

août 18 10:54:23 magaux systemd[1]: Starting Software RAID monitoring and management...
août 18 10:54:23 magaux mdadm[12228]: mdadm: No mail address or alert command - not monitoring.
août 18 10:54:23 magaux systemd[1]: mdmonitor.service: Control process exited, code=exited status=1
août 18 10:54:23 magaux systemd[1]: Failed to start Software RAID monitoring and management.
août 18 10:54:23 magaux systemd[1]: mdmonitor.service: Unit entered failed state.
août 18 10:54:23 magaux systemd[1]: mdmonitor.service: Failed with result 'exit-code'.
running systemctl start mdmonitor.service
doesn't change the situation:

[root@magaux alain4]# systemctl start mdmonitor.service
Job for mdmonitor.service failed because the control process exited with error code.
See "systemctl status mdmonitor.service" and "journalctl -xe" for details.

see attached files



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Comment 1 peter lawford 2017-08-18 14:01:55 CEST

Created attachment 9610 [details]
return of mdadm --detail --scan -v

Comment 2 peter lawford 2017-08-18 14:02:48 CEST

Created attachment 9611 [details]
return of journalctl -xe

Comment 3 Marja Van Waes 2017-08-18 16:17:55 CEST

Assinging to the mdadm maintainer.

Source RPM: (none) => mdadm
CC: sysadmin-bugs => marja11
Component: Release (media or process) => RPM Packages

Marja Van Waes 2017-08-18 16:18:06 CEST

Assignee: bugsquad => tmb

Comment 4 Thomas Backlund 2017-08-18 16:45:32 CEST

You need to configure the service as the error states:

août 18 10:54:23 magaux mdadm[12228]: mdadm: No mail address or alert command - not monitoring.

Comment 5 peter lawford 2017-08-18 23:19:23 CEST

(In reply to Thomas Backlund from comment #4)
> You need to configure the service as the error states:
> 
> août 18 10:54:23 magaux mdadm[12228]: mdadm: No mail address or alert
> command - not monitoring.

sorry, I'm not a specialist of linux, only an honest user; tell me exactly what I have to do.
my mageia6 comes from migration from mageia5, and I had never such trouble with this latter version

Comment 6 peter lawford 2017-08-30 21:39:33 CEST

(In reply to Thomas Backlund from comment #4)
> You need to configure the service as the error states:
> 
> août 18 10:54:23 magaux mdadm[12228]: mdadm: No mail address or alert
> command - not monitoring.

I'am always awaiting your reply to comment 5
thank you

Comment 7 peter lawford 2017-09-19 16:13:07 CEST

SOLVED: echo "MAILADDR root" >> /etc/mdadm.conf

Comment 8 Aurelien Oudelet 2020-08-05 16:15:42 CEST

This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as FIXED, see Comment #7.(EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => FIXED
CC: (none) => ouaurelien