1

Topic: Ubuntu 14.04 Install - Stuck on php.ini config

==== Required information ====
- iRedMail version: 0.9.0
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): LDAP
- Linux/BSD distribution name and version: Ubuntu 14.04
- Related log if you're reporting an issue:
====

During the configuration, it seems to get stuck right after trying to create the php.ini for fpm; I've run it twice now after a full reinstall of the OS on the VPS, same result.  It's been sitting over an hour now, top shows that aptget is taking up about 9% of the CPU while this is happening.





Creating config file /etc/php5/mods-available/curl.ini with new version
php5_invoke: Enable module curl for apache2 SAPI
php5_invoke: Enable module curl for fpm SAPI
php5_invoke: Enable module curl for cli SAPI
Setting up php5-fpm (5.5.9+dfsg-1ubuntu4.6) ...

Creating config file /etc/php5/fpm/php.ini with new version
php5_invoke pdo: already enabled for fpm SAPI
php5_invoke curl: already enabled for fpm SAPI
php5_invoke opcache: already enabled for fpm SAPI




1863 root      20   0   94288  54564  41668 S  8.9  2.1   3:15.38 apt-get
1869 root      20   0  105632   4316   3252 S  0.3  0.2   0:04.65 sshd
1900 root      20   0   24976   1692   1132 R  0.3  0.1   0:11.82 top
    1 root      20   0   33372   2688   1408 S  0.0  0.1   0:02.64 init
    2 root      20   0       0      0      0 S  0.0  0.0   0:00.00 kthreadd
    3 root      20   0       0      0      0 S  0.0  0.0   0:00.06 ksoftirqd/0



First time through I left it for longer and eventually it got to a point where it errored out, and nothing after that worked.  Couldn't connect to any of the services, web server was there but no pages existed for the admin panels, etc.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Ubuntu 14.04 Install - Stuck on php.ini config

Got it working, wiped my VPS back to 14.04 standard then did apt-get update and upgrade.  After that the install took, so I'm betting there was something in the basic OS image from my VPS host that needed to be upgraded before the install was done.