package libapache2-mod-php7.0 7.0.18-0ubuntu0.16.04.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

Bug #1703537 reported by Yurij
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
php7.0 (Ubuntu)
Fix Released
Undecided
Yurij

Bug Description

AFTER APT-GET UPDATE; APT-GET UPGRADE. FOUND ERRORS IN LIBAPACHE UPDATE PROCESS. IT'S NO CRITICAL ERROR

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libapache2-mod-php7.0 7.0.18-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.9
Architecture: amd64
Date: Tue Jul 11 10:12:24 2017
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.20
SourcePackage: php7.0
Title: package libapache2-mod-php7.0 7.0.18-0ubuntu0.16.04.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Yurij (itshi32) wrote :
Revision history for this message
Joshua Powers (powersj) wrote :

Thank you for taking the time to file a bug report.

I am unable to reproduce this in a container. Is there anything special
about your configuration?

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

Changed in php7.0 (Ubuntu):
status: New → Incomplete
Revision history for this message
Yurij (itshi32) wrote :

I have fixed the bug. there are my steps

  #create backup tar.gz of /etc/apache especially for sites-* and mod-*
  sudo apt-get install libapache2-mod-fastcgi php-fpm # not shure that this is needfull step
  #i remove completly my installation as described in there https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1597315/comments/2
 rm -r /etc/apache2/ /etc/php/
  sudo apt-get purge apache2* php libapache2-mod-php php7.0
  sudo apt-get install apache2 libapache2-mod-php php7.0 --reinstall
  #restart ubuntu
   gksu nemo&

   cd sites-available/

   mv 000-default.conf 000-default.conf.bak

  # unpack from backup sites-available my conf (000-default.conf)
   cd sites-enabled/
  # unpack from backup sites-available my conf (symlink to 000-default.conf)
  # unpack the previously installed mods (i had 2 manually added)
   service apache2 force-reload
#Now my apache2 is running, so could close the bug please.

Yurij (itshi32)
Changed in php7.0 (Ubuntu):
status: Incomplete → Opinion
assignee: nobody → Yurij (itshi32)
Revision history for this message
Yurij (itshi32) wrote :

Finally, got all in order by installing php7.1-fpm https://launchpad.net/~ondrej
sudo a2enconf php7.1-fpm
Enabling conf php7.1-fpm.
service apache2 restart
systemctl status php7.1-fpm.service
● php7.1-fpm.service - The PHP 7.1 FastCGI Process Manager
   Loaded: loaded (/lib/systemd/system/php7.1-fpm.service; enabled; vendor preset: enabled)
   Active: active (running) since Вт 2018-02-13 16:55:25 MSK; 5min ago
     Docs: man:php-fpm7.1(8)
 Main PID: 3008 (php-fpm7.1)
   Status: "Processes active: 0, idle: 2, Requests: 0, slow: 0, Traffic: 0req/sec"
   CGroup: /system.slice/php7.1-fpm.service
           ├─3008 php-fpm: master process (/etc/php/7.1/fpm/php-fpm.conf)
           ├─3011 php-fpm: pool www
           └─3012 php-fpm: pool www

фев 13 16:55:25 xerus systemd[1]: Starting The PHP 7.1 FastCGI Process Manager...
фев 13 16:55:25 xerus systemd[1]: Started The PHP 7.1 FastCGI Process Manager.

Changed in php7.0 (Ubuntu):
status: Opinion → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.