Bug 24392

Summary:	Tomoyo linux does'nt work from boot up
Product:	Mageia	Reporter:	Andrew Brewster <ab.kde>
Component:	RPM Packages	Assignee:	Thomas Backlund <tmb>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	cjw, marja11, ouaurelien
Version:	6
Target Milestone:	Mageia 7
Hardware:	x86_64
OS:	Linux
See Also:	https://bugs.mageia.org/show_bug.cgi?id=13015
Whiteboard:
Source RPM:	tomoyo-tools-2.5.0-7.mga6	CVE:
Status comment:
Attachments:	tomoyo-auditd.service unit file from docs

Description Andrew Brewster 2019-02-20 22:55:37 CET

Created attachment 10772 [details]
tomoyo-auditd.service unit file from docs

Tomoyo always fails to start up on boot properly, lots of examples in boot log, same as the last one shown here, machine name {xxxx} removed.

journalctl --unit=tomoyo-auditd

Feb 20 19:20:07 {xxxx} systemd[1]: Starting LSB: TOMOYO Linux MAC logging daemon...
Feb 20 19:20:07 {xxxx} tomoyo-auditd[5092]: Starting ccs-auditd: tomoyo-auditd [remote_ip:remote_port]
Feb 20 19:20:07 {xxxx} tomoyo-auditd[5092]:   See /etc/tomoyo/tools/auditd.conf for configuration.
Feb 20 19:20:07 {xxxx} tomoyo-auditd[5092]: [FAILED]
Feb 20 19:20:08 {xxxx} systemd[1]: tomoyo-auditd.service: Control process exited, code=exited status=1
Feb 20 19:20:08 {xxxx} systemd[1]: Failed to start LSB: TOMOYO Linux MAC logging daemon.
Feb 20 19:20:08 {xxxx} systemd[1]: tomoyo-auditd.service: Unit entered failed state.
Feb 20 19:20:08 {xxxx} systemd[1]: tomoyo-auditd.service: Failed with result 'exit-code'.

systemctl -l status tomoyo-auditd.service - returns disabled
● tomoyo-auditd.service - TOMOYO Linux Auditing Daemon
   Failed: loaded (/usr/lib/systemd/system/tomoyo-auditd.service; disabled; vendor preset: enabled)

The current installation provides an init script
/etc/rc.d/init.d/tomoyo-auditd
but MGA 6 uses systemd, and should use a service file

test out by disabling init script, avoid potential conflicts
cd /etc/rc.d/init.d
chmod -x tomoyo-auditd

add new unit file 
/usr/lib/systemd/tomoyo-auditd.service
see attachment, copied from Tomoyo docs at
http://tomoyo.osdn.jp/2.5/chapter-4.html.en

enable service
systemctl enable tomoyo-auditd.service

reboot

journalctl -b --unit=tomoyo-auditd

Feb 20 20:40:26 {xxxx} systemd[1]: Starting TOMOYO Linux Auditing Daemon...
Feb 20 20:40:26 {xxxx} tomoyo-auditd[4292]: Started.
Feb 20 20:40:26 {xxxx} systemd[1]: Started TOMOYO Linux Auditing Daemon.

check status
systemctl -l status tomoyo-auditd.service
● tomoyo-auditd.service - TOMOYO Linux Auditing Daemon
   Loaded: loaded (/usr/lib/systemd/system/tomoyo-auditd.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-02-20 20:40:26 GMT; 30min ago
  Process: 4243 ExecStart=/usr/sbin/tomoyo-auditd (code=exited, status=0/SUCCESS)
 Main PID: 4292 (tomoyo-auditd)
   CGroup: /system.slice/tomoyo-auditd.service
           └─4292 /usr/sbin/tomoyo-auditd


Swap the unit file for the init script for Mageia 7

Comment 1 Andrew Brewster 2019-02-20 22:57:43 CET

new unit file should be
/usr/lib/systemd/system/tomoyo-auditd.service

not
/usr/lib/systemd/tomoyo-auditd.service

Comment 2 Marja Van Waes 2019-02-21 14:34:02 CET

Assinging to the registered maintainer, CC'ing a cauldron tomoyo-tools submitter.

Assignee: bugsquad => tmb
CC: (none) => cjw, marja11

Comment 3 Aurelien Oudelet 2020-08-16 22:35:26 CEST

Does this still apply to Mageia 7 or Cauldron ?

CC: (none) => ouaurelien

Comment 4 Aurelien Oudelet 2020-08-26 11:34:43 CEST

Since we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
Resolution: (none) => OLD