Ubuntu

systemd: bad; vendor preset: enabled

Asked by Battant

Hello,

My configuration :
uname -a
Linux mparchet-W240EU-W250EUQ-W270EUQ 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
 lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
My question :
If I enter a command like this in a termial
systemctl status apache2.service
I have this result :
● apache2.service - LSB: Apache2 web server
   Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
  Drop-In: /lib/systemd/system/apache2.service.d
           └─apache2-systemd.conf
   Active: active (running) since dim. 2016-04-24 15:14:16 CEST; 5h 42min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1559 ExecStart=/etc/init.d/apache2 start (code=exited, status=0/SUCCE
    Tasks: 7 (limit: 512)
   CGroup: /system.slice/apache2.service
           ├─ 1781 /usr/sbin/apache2 -k start
           ├─ 1790 /usr/sbin/apache2 -k start
           ├─ 1791 /usr/sbin/apache2 -k start
           ├─ 1792 /usr/sbin/apache2 -k start
           ├─ 1793 /usr/sbin/apache2 -k start
           ├─ 1794 /usr/sbin/apache2 -k start
           └─11912 /usr/sbin/apache2 -k start
and with this service
systemctl status mysql.service
● mysql.service - LSB: Start and stop the mysql database server daemon
   Loaded: loaded (/etc/init.d/mysql; bad; vendor preset: enabled)
   Active: active (running) since dim. 2016-04-24 15:14:16 CEST; 5h 48min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1560 ExecStart=/etc/init.d/mysql start (code=exited, status=0/SUCCESS
    Tasks: 27 (limit: 512)
   CGroup: /system.slice/mysql.service
           ├─1618 /bin/bash /usr/bin/mysqld_safe
           ├─1619 logger -p daemon err -t /etc/init.d/mysql -i
           ├─1768 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plu
           └─1769 logger -t mysqld -p daemon error

and calandarserver :

systemctl status calendarserver.service
● calendarserver.service - LSB: Calendar and Contacts Server
   Loaded: loaded (/etc/init.d/calendarserver; bad; vendor preet:s enabled)
   Active: active (exited) since dim. 2016-04-24 15:14:14 CEST; 5h 50min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1558 ExecStart=/etc/init.d/calendarserver start (code=exited, status=
    Tasks: 0 (limit: 512)

I have this recurrent message :

bad; vendor preet:s enabled

Could you help me please to fix this issue ?

Best regards

Battant

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Manfred Hampl (m-hampl) said : 		#1

What is the problem?
The message as such?
Do apache2 and MySQL work as desired?

Revision history for this message
Battant (mparchet) said : 		#2

Hello,

I twill try to explain you more clearly :

I have installed ubuntu 16.04 whith these packages :

1. apache2:
  Installed: 2.4.18-2ubuntu3
  Candidate: 2.4.18-2ubuntu3
  Version table:
 *** 2.4.18-2ubuntu3 500
        500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status
     2.4.18-1ubuntu1 500
        500 http://archive.ubuntu.csg.uzh.ch/ubuntu xenial/main amd64 Packages

2. apt-cache policy mariadb-server
mariadb-server:
  Installed: 10.0.24-7
  Candidate: 10.0.24-7
  Version table:
 *** 10.0.24-7 500
        500 http://ch.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
        500 http://ch.archive.ubuntu.com/ubuntu xenial/universe i386 Packages
        100 /var/lib/dpkg/status
     10.0.23-2 500
        500 http://archive.ubuntu.csg.uzh.ch/ubuntu xenial/universe amd64 Packages
        500 http://archive.ubuntu.csg.uzh.ch/ubuntu xenial/universe i386 Packages

3. apt-cache policy calendarserver
calendarserver:
  Installed: 7.0+dfsg-2
  Candidate: 7.0+dfsg-2
  Version table:
 *** 7.0+dfsg-2 500
        500 http://ch.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
        100 /var/lib/dpkg/status
     7.0+dfsg-1 500
        500 http://archive.ubuntu.csg.uzh.ch/ubuntu xenial/universe amd64 Packages

Question : when I run a systemd command like this

systemctl status apache2.service

i get this message :

bad; vendor preset: enabled

This situation is the same for all the package.

I hop hop that you have understand the situation.

Could you help me to fix this issues ?

Best regards

Battant

Revision history for this message
Manfred Hampl (m-hampl) said : 		#3

I still do not understand your problem.

Does the apache2 service run as desired?

Revision history for this message
Battant (mparchet) said : 		#4

Hello,

To answer your above questions :

The apache2 is running and works. but I am surprised to see the following message "bad; vendor preset: enabled)"

Mariadb does not work (see the bellow error message) and I also get the same message as for apache2

[Note] InnoDB: Highest supported file format is Barracuda.
[Note] InnoDB: 128 rollback segment(s) are active.
[Note] InnoDB: Waiting for purge to start
[Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.28-76.1 started; log sequen
[Note] Plugin 'FEEDBACK' is disabled.
[Note] Server socket created on IP: '127.0.0.1'.
[Note] /usr/sbin/mysqld: ready for connections.
4-MariaDB-7' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Ubuntu 16.04

Any Idea concerning the message "bad; vendor preset: enabled" ?

Could you help me please for the issue concerning mariadb ?

Thank you very much

Best regards

Battant

Revision history for this message
Manfred Hampl (m-hampl) said : 		#5

If apache is working well, then I would not take that message "bad; vendor preset: enabled" too serious.

I do not see anything wrong with mariadb ("ready for connections"), which "bellow error message" are you referring to?

Revision history for this message
Marc Vanhoomissen (mvh) said : 		#6

I think this message 'bad: vendor preset' is very confusing to see when you try to understand where a problem is located. Right now, I investigate why bacula softare does not run anymore since upgrade to ubunut 16.04. I saw the 'Bad: vendor preset'when checking the status of the bacula-dir. I took me a while to understand that this information is not relevant.

I am convinced many people will stumble on that message. So my advice is either remove it from the information given in the status or make it understandable.

Revision history for this message
Barry Onizak (bonizak) said : 		#7

I stumbled upon this message as I worked to fix my tomcat8 installation after upgrading to 16.04.
I too found this 'bad' state for the the unit-files field, to be confusing until I read http://askubuntu.com/questions/836059/sudo-service-status-includes-bad. It is described quite well here and lead me to determine, like you, that the state is irrelevant.
I agree the state could be better worded.

Can you help with this problem?

Provide an answer of your own, or ask Battant for more information if necessary.

To post a message you must log in.