Ubuntu-fr

joHNkHaN

J'ai casser ma config Apache en installant php7.1

Bonjour les libristes
Je travaille comme Dev junior dans une petite boite, sur un laptop avec Ubuntu 16.04.
Depuis que j'ai installer les paquet php7.1 de Sergej mon localhost ne fonctionne plus (cela n'as peut-être aucun rapport mais c'est arrivé précisément à ce moment)..

Les log

journalctl | tail

me retourne

mysql-systemd-start[27571]: my_print_defaults: [ERROR] Fatal error in defaults handling. Program aborted! mysqld[27583]: mysqld: [ERROR] Found option without preceding group in config file /etc/mysql/my.cnf at line 24!

La ligne 24 de my.cnf contient

datadir=D:/ProgramData/MySQL/MySQL Server 5.6/Data

Le diag

apache2ctl configtest

me retourne

apache2: Syntax error on line 222 of /etc/apache2/apache2.conf: Could not open configuration file /etc/phpmyadmin/apache.conf: No such file or directory Action 'configtest' failed. The Apache error log may have more information.

En effet mon fichier apache2.conf a carrément disparu...
J'ai donc voulu réinstaller Apache

sudo apt-get -o DPkg::Options::="--force-confmiss" --reinstall install apache2

L'installation me retourne un échec

Job for apache2.service failed because the control process exited with error code. See "systemctl status apache2.service" and "journalctl -xe" for details.
invoke-rc.d: initscript apache2, action "start" failed.
● 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: failed (Result: exit-code) since ven. 2018-03-23 14:51:24 CET; 10ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 4365 ExecStart=/etc/init.d/apache2 start (code=exited, status=1/FAILURE)
mars 23 14:51:24 than-HP-ProBook-470-G2 apache2[4365]:  *
mars 23 14:51:24 than-HP-ProBook-470-G2 apache2[4365]:  * The apache2 configtest failed.
mars 23 14:51:24 than-HP-ProBook-470-G2 apache2[4365]: Output of config test was:
mars 23 14:51:24 than-HP-ProBook-470-G2 apache2[4365]: apache2: Syntax error on line 222 of /etc/apache2/apache2.conf: Could not open configuration file /etc/phpmyadmin/... directory
mars 23 14:51:24 than-HP-ProBook-470-G2 apache2[4365]: Action 'configtest' failed.
mars 23 14:51:24 than-HP-ProBook-470-G2 apache2[4365]: The Apache error log may have more information.
mars 23 14:51:24 than-HP-ProBook-470-G2 systemd[1]: apache2.service: Control process exited, code=exited status=1
mars 23 14:51:24 than-HP-ProBook-470-G2 systemd[1]: Failed to start LSB: Apache2 web server.
mars 23 14:51:24 than-HP-ProBook-470-G2 systemd[1]: apache2.service: Unit entered failed state.
mars 23 14:51:24 than-HP-ProBook-470-G2 systemd[1]: apache2.service: Failed with result 'exit-code'.

Je suis débutant sur Ubuntu, un petit coup de main serais le bienvenu
D'ici la je vous souhaite une bonne journée.

Alex10336

Re : J'ai casser ma config Apache en installant php7.1

B'soir,

mysql-systemd-start[27571]: my_print_defaults: [ERROR] Fatal error in defaults handling. Program aborted! mysqld[27583]: mysqld: [ERROR] Found option without preceding group in config file /etc/mysql/my.cnf at line 24!

La ligne 24 de my.cnf contient

datadir=D:/ProgramData/MySQL/MySQL Server 5.6/Data

sympa la ligne: "D:/ProgramData/MySQL/MySQL Server 5.6/Data"
Modification piqué d'un tuto windope ?

mon my.cnf:

#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

#
# * IMPORTANT: Additional settings that can override those from this file!
#   The files must end with '.cnf', otherwise they'll be ignored.
#

!includedir /etc/mysql/conf.d/
!includedir /etc/mysql/mysql.conf.d/

pour le /etc/apache2/apache2.conf, possible de montrer les lignes avant et après la 222 ?

Dernière modification par Alex10336 (Le 23/03/2018, à 19:56)

---

« On ne répond pas à une question par une autre question. » (moi ;-) )

joHNkHaN

Re : J'ai casser ma config Apache en installant php7.1

Merci beaucoup pour votre réponse rapide ,

sympa la ligne: "D:/ProgramData/MySQL/MySQL Server 5.6/Data"
Modification piqué d'un tuto windope ?

En effet ça parait délirant j'avais pas vus Voici le lien du site que je suivait.. , le but étais de migrer de php 7.0 à 7.1...

pour le /etc/apache2/apache2.conf, possible de montrer les lignes avant et après la 222 ?

Voici les ligne 220 à 22 du fichier apache2.conf ( qui ne contient que 222 lignes ):

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
Include /etc/phpmyadmin/apache.conf

Et si utile, le fichier en entier:

# This is the main Apache server configuration file.  It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
#	/etc/apache2/
#	|-- apache2.conf
#	|	`--  ports.conf
#	|-- mods-enabled
#	|	|-- *.load
#	|	`-- *.conf
#	|-- conf-enabled
#	|	`-- *.conf
# 	`-- sites-enabled
#	 	`-- *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
#   together by including all remaining configuration files when starting up the
#   web server.
#
# * ports.conf is always included from the main configuration file. It is
#   supposed to determine listening ports for incoming connections which can be
#   customized anytime.
#
# * Configuration files in the mods-enabled/, conf-enabled/ and sites-enabled/
#   directories contain particular configuration snippets which manage modules,
#   global configuration fragments, or virtual host configurations,
#   respectively.
#
#   They are activated by symlinking available configuration files from their
#   respective *-available/ counterparts. These should be managed by using our
#   helpers a2enmod/a2dismod, a2ensite/a2dissite and a2enconf/a2disconf. See
#   their respective man pages for detailed information.
#
# * The binary is called apache2. Due to the use of environment variables, in
#   the default configuration, apache2 needs to be started/stopped with
#   /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
#   work with the default configuration.


# Global configuration
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE!  If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the Mutex documentation (available
# at <URL:http://httpd.apache.org/docs/2.4/mod/core.html#mutex>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
Mutex file:${APACHE_LOCK_DIR} default

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5


# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here.  If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the severity of messages logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
# "LogLevel info ssl:warn"
#
LogLevel warn

# Include module configuration:
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf

# Include list of ports to listen on
Include ports.conf


# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
	Options FollowSymLinks
	AllowOverride None
	Require all denied
</Directory>

<Directory /usr/share>
	AllowOverride None
	Require all granted
</Directory>

<Directory /var/www/>
	Options Indexes FollowSymLinks
	AllowOverride None
	Require all granted
</Directory>

#<Directory /srv/>
#	Options Indexes FollowSymLinks
#	AllowOverride None
#	Require all granted
#</Directory>




# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
	Require all denied
</FilesMatch>


#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf

# vim: syntax=apache ts=4 sw=4 sts=4 sr noet
Include /etc/phpmyadmin/apache.conf

joHNkHaN

Re : J'ai casser ma config Apache en installant php7.1

Je viens de corriger my.conf pour le faire pointer vers le bon répertoire et j'ai récupéré mon localhost merci

Par contre il semble que j'ai plus accès a phpMyAdmin... Je vais faire encore quelque recherche...

Dernière modification par joHNkHaN (Le 24/03/2018, à 11:57)

Alex10336

Re : J'ai casser ma config Apache en installant php7.1

phpmyadmin est un truc lourdingue, essaye " https://www.adminer.org/ "

tu peux supprimer la ligne " Include /etc/phpmyadmin/apache.conf ", elle ne devrait pas y être. mais plutot dans le conf-available d'apache

Dernière modification par Alex10336 (Le 25/03/2018, à 13:46)

---

« On ne répond pas à une question par une autre question. » (moi ;-) )

joHNkHaN

Re : J'ai casser ma config Apache en installant php7.1

Pas encore fini réparation

 #2002 - No such file or directory<br />Le serveur ne répond pas (ou l'interface de connexion vers le serveur MySQL local n'est pas correctement configurée).
La connexion au controluser tel que défini dans votre configuration a échoué.

Sympa adminer ^^ je l'utiliserais pour des projet perso.. Bon faut quand même que je répare le myadmin(pour la boite ou je bosse) je vais continuer mes recherches...

                          ####################################RESOLU####################################

https://stackoverflow.com/questions/370 … -specified

Dernière modification par joHNkHaN (Le 25/03/2018, à 20:30)

krodelabestiole

Re : J'ai casser ma config Apache en installant php7.1

le but étais de migrer de php 7.0 à 7.1...

pour quoi faire ?

migrer de version de php en ajoutant un ppa, c'est une méthode très sale. donc si c'est inutile, mieux vaut éviter.
et si c'est indispensable, alors mieux utiliser une version de son os qui supporte la version de php dont on a besoin, ou utiliser docker https://github.com/nextcloud/docker

---

nouveau forum ubuntu-fr on en parle là : refonte du site / nouveau design
profil - sujets récurrents

bruno

Re : J'ai casser ma config Apache en installant php7.1

migrer de version de php en ajoutant un ppa, c'est une méthode très sale.

+1
On ne compte plus, sur ce forum et ailleurs, les utilisateurs ayant « cassé » leur système en utilisant ce ppa en particulier.