Posts by Nuxwin

Hello ;

This thread is intended to clarify how i-MSCP manages the php.ini files, according the way you are running PHP.

I. i-MSCP frontEnd (control panel) php.ini file

The i-MSCP control panel runs it own instance of PHP FPM. Its php.ini file is located at /usr/local/etc/imscp_panel/php.ini and its FPM pool configuration file at /usr/local/etc/imscp_panel/php/php-fpm.conf

Note that these files only apply to the control panel. For the customer sites, see below.

Important: If you modify one of these files, don't forget to restart the imscp_panel service.

II. Customers sites

I Apache2 with MPM ITK

When using Apache with the MPM ITK (therefore, with mod_php), only one php.ini file located at /etc/php5/apache2/php.ini or /etc/php/<version>/apache2/php.ini is relevant for all your customers. If you change a parameter in this file, it will apply to all your customers. However you must note that any parameter defined in the vhost file take precedence over those set in the php.ini file.

You can also edit (override) some parameters via the i-MSCP PHP Editor. These parameters are defined in the Apache vhost file of the customer for which you are acting.

Important: When you modify a parameter manually in the php.ini file, you must restart the Apache2 service.

II. Apache2 with Fcgid

When using Apache with Fcgid, PHP is running as CGI program. Each customer has its own php.ini file located at /var/www/fcgi/<domain.tld>/php<version>/php.ini

You can change some parameters via the i-MSCP PHP Editor. These parameters are defined in the php.ini file of the customer for which you are acting.

Note: This "mode" also allows to have more than one php.ini file per customer:

- per_user: each customer will have only one php.ini file
- per_domain: each domain / domain alias will have its own php.ini file
- per_vhost: each vhost for domain, domain alias, subdomain and subdomain alias will have its own php.ini file

Important: When you modify a parameter manually in a php.ini file, you must restart the Apache2 service.

III. Apache2 with PHP-FPM

When using Apache with php-fpm, only one php.ini file located at /etc/php5/fpm/php.ini or /etc/php/<version>/fpm/php.ini is relevant for all your customers. If you change one parameter in this file, it will apply to all your customers.

However each customer has a least one php-fpm pool configuration file located under /etc/php5/fpm/pool.d or /etc/php/<version>/fpm/pool.d, in which you can override PHP parameters (read the documentation about php-fpm carefully).

You can also change some parameters via the i-MSCP PHP Editor. These parameters are defined in the customer php-fpm pool file.

Note: This "mode" also allows to have more than one php.ini file per customer:

- per_user: each customer will have only one pool
- per_domain: each domain / domain alias will have its own pool
- per_site: each site will have its own pool

Important: When you modify a parameter manually in the php.ini file or a php-fpm pool file, you must restart the php5-fpm service.

Hello ;

See http://forum.i-mscp.net/Thread…i-MSCP?pid=10724#pid10724

Thank you for using i-MSCP

Quote from tom

Ich hab Deinen Text nicht verstanden - koenntest Du das bitte noch einmal in Deutsch senden? Ist ja German-Corner hier. Danke.

gruss tom

Hello ;

I try to help our users only... I've already warned you few days ago about your behavior. You do not want understand. Well you get banned for a week.

We don't like spoilsport here.

BTW: You treat the founders of this project in a funny way. You are expecting what exactly?

Thanks

Quote from funnymob

Hallo zusammen,

ich wollte OwnCloud als Paket über die Softwareverwaltung meinen Kunden zur Verfügung stellen. Das Paket ist eine bz2-Datei owncloud-4.5.6.tar.bz2.
iMSCP läßt leider nur tar.gz Dateien zu.

Ich kann natürlich die Datei entpacken und in eine tar.gz wieder einpacken. Allerdings muss ich das dann immer händisch wiederholen, wenn ich neue Versionen hochladen will

Ist es möglich den Upload von bz2-Dateien ebenfalls zu gestatten, oder ist das ein größerer act?
Macht es vielleicht auch Sinn das OwnCloud in die default SW-Liste mit aufzunehmen?

Danke
Gruß
funnymob

Display More

Hello ;

Any 3rd party software should be re-packaged specifically for i-MSCP. Any archive (even if it's a tar.gz) uploaded in the i-MSCP software installer pool without any modification will not work.

To resume, when you want make a software compatible with the i-MSCP software installer, you must repack it to add the needed i-MSCP installer files. Therefore, you will so have to do:

1. Download the upstream archive
2. Unpack the archive
3. Add specific iMSCP software installer files
4. Repack the archive with i-MSCP software installer files included in it
5. Upload the new archive in the i-MSCP software installer pool

So here, at the step 4, you must just repack it has tar.gz

BTW: Maybe I missed some steps here. Ask TheCry for more detail.

I close the related ticket as worksform.

Thank you for using i-MSCP

Quote from biologist

http://lmgtfy.com/?q=howto+cron

http://lmgtfy.com/?q=php+howto+cron+using+wget

Hello ;

All will be regenerated from scratch. I recommend to make a backup and restore your custom parameters after.

Thank for using i-MSCP

Well, ok

I 've received you PM. I'm now waiting for needed data.

Thank you for using i-MSCP

Quote from dzchimp

Yes, Nuxwin, my VPS control panel is Solusvm. However I have removed sendmail:

Code

1. sudo apt-get purge postfix exim4 sendmail sendmail-bin

And reinstalled i-mscp. Now, sending email works and smtp is shown as active. Once again, I cant receive email.

Are you sure that the sendmail MTA process is not there ? Sometime, only a purge don't really stop it... Stange but true...

Quote from dzchimp

That most certainly seems to have been the case here.

Thank you! I seem to be turning blind. I missed that line in grep!

Removed sendmail, updated i-mscp, and now smtp service is running. So we're back to the initial issue. Mail sent from the server goes through fine. But the server cant receive mail.

Code

1. Delivery to the following recipient failed permanently: [email protected] details of permanent failure:Google tried to deliver your message, but it was rejected by the server for the recipient domain joel.co.in by r2d2.joel.co.in. [50.7.228.37].The error that the other server returned was:550 5.1.1 <[email protected]>: Recipient address rejected: User unknown in local recipient table

Dig of my MX record yields this:

Code

1. joel.co.in. 14400 IN MX 10 r2d2.joel.co.in.

The FQDN of my server as set on the VPD panel is r2d2.droidzone.in. Is this what is supposed to be set up?

Other records are as follows:

Code

1. ;; QUESTION SECTION:;joel.co.in. IN ANY;; ANSWER SECTION:joel.co.in. 14400 IN TXT "google-site-verification=hOLP1HhkutllGmRUDs5gkQMMWKAV7f5T7AyBBQ_y-Po"joel.co.in. 86400 IN NS ns101.dnsever.com.joel.co.in. 86400 IN NS ns108.dnsever.com.joel.co.in. 86400 IN NS ns77.dnsever.com.joel.co.in. 3600 IN SOA ns77.dnsever.com. root.joel.co.in. 1360417469 10800 3600 604800 3600joel.co.in. 14400 IN MX 10 r2d2.joel.co.in.joel.co.in. 14400 IN A 50.7.228.37;; ADDITIONAL SECTION:ns108.dnsever.com. 86400 IN A 121.254.188.108ns77.dnsever.com. 85404 IN A 121.254.188.77ns101.dnsever.com. 85404 IN A 121.254.188.101r2d2.joel.co.in. 13197 IN A 50.7.228.37;; Query time: 364 msec;; SERVER: 127.0.1.1#53(127.0.1.1);; WHEN: Sun Feb 10 17:50:49 2013;; MSG SIZE rcvd: 321

Is there a mistake somewhere?

Latest mail logs are again uploaded. I've got to solve this somehow.

Are PTR records essential? I've submitted a request to my VPS host to turn on rDNS for me, but apparently the request needs to be sent through their main data centre to get activated.

My postfix config:
main.cf

Code

1. # Postfix directory settings; These are critical for normal Postfix MTA functionallitycommand_directory = /usr/sbindaemon_directory = /usr/lib/postfix# Some common configuration parametersinet_protocols = ipv4, ipv6inet_interfaces = allmynetworks_style = hostmyhostname = joel.co.inmydomain = joel.co.in.localmyorigin = $myhostnamesmtpd_banner = $myhostname ESMTP i-MSCP 1.1.0-rc1.4 Managedsetgid_group = postdrop# Receiving messages parametersmydestination = $myhostname, $mydomainappend_dot_mydomain = noappend_at_myorigin = yeslocal_transport = localtransport_maps = hash:/etc/postfix/imscp/transportrelay_domains = hash:/etc/postfix/imscp/relay_domainsalias_maps = hash:/etc/aliasesalias_database = hash:/etc/aliases# Delivering local messages parametersmail_spool_directory = /var/mail# Mailboxquota# => 0 for unlimited# => 104857600 for 100 MBmailbox_size_limit = 0mailbox_command = procmail -a "$EXTENSION"# Message size limit# => 0 for unlimited# => 104857600 for 100 MBmessage_size_limit = 0biff = norecipient_delimiter = +local_destination_recipient_limit = 1local_recipient_maps = unix:passwd.byname $alias_database# i-MSCP Autoresponder parametersimscp-arpl_destination_recipient_limit = 1# Delivering virtual messages parametersvirtual_mailbox_base = /var/mail/virtualvirtual_mailbox_limit = 0virtual_mailbox_domains = hash:/etc/postfix/imscp/domainsvirtual_mailbox_maps = hash:/etc/postfix/imscp/mailboxesvirtual_alias_maps = hash:/etc/postfix/imscp/aliasesvirtual_minimum_uid = 999virtual_uid_maps = static:999virtual_gid_maps = static:8# SASL parameterssmtpd_sasl_auth_enable = yessmtpd_sasl_security_options = noanonymousbroken_sasl_auth_clients = yessmtpd_sasl_authenticated_header = yessmtpd_helo_required = yessmtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_invalid_helo_hostname, reject_non_fqdn_helo_hostnamesmtpd_sender_restrictions = reject_non_fqdn_sender, reject_unknown_sender_domain, permit_mynetworks, permit_sasl_authenticatedsmtpd_recipient_restrictions = reject_non_fqdn_recipient, reject_unknown_recipient_domain, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, reject_unlisted_recipient, check_policy_service inet:127.0.0.1:12525, check_policy_service inet:127.0.0.1:10023, permitsmtpd_data_restrictions = reject_multi_recipient_bounce, reject_unauth_pipelining# TLS parameters#smtpd_tls_security_level = may#smtpd_tls_loglevel = 2#smtpd_tls_cert_file = /etc/imscp/joel.co.in.pem#smtpd_tls_key_file = /etc/imscp/joel.co.in.pem#smtpd_tls_auth_only = no#smtpd_tls_received_header = yes# AMaViS parameters; activate, if available/used#content_filter = amavis:[127.0.0.1]:10024# Quota support; activate, if available/used#virtual_create_maildirsize = yes#virtual_mailbox_extended = yes#virtual_mailbox_limit_maps = mysql:/etc/postfix/mysql_virtual_mailbox_limit_maps.cf#virtual_mailbox_limit_override = yes#virtual_maildir_limit_message = "The user you're trying to reach is over mailbox quota."#virtual_overquota_bounce = yessmtpd_sasl_local_domain =virtual_transport = virtual

Mailboxes:

Code

1. root@r2d2:/etc/postfix# cat /etc/postfix/imscp/mailboxes## MTA Managment Mailboxes List;## Please do NOT edit it manually;#[email protected] joel.co.in/joel/

Code

1. root@r2d2:/etc/postfix# cat /etc/postfix/imscp/aliases
2. #
3. # MTA Managment Virtual Aliases List;
4. #
5. # Please do NOT edit it manually;
6. #
7. [email protected] [email protected]
8. [email protected] [email protected]
9. [email protected] [email protected]

Display More

Hello ;

Well, you are using openvz or something like this ?

You must kill and purge the sendmail MTA packages and rerun the i-MSCP installer.

I can assist you via teamviewer if you want. Just PM me

Thank you for using i-MSCP.

Quote from c0urier

I'm pretty sure it's installed as default on some debian machines, all depending on your selections during installation. And if it's a VPS they prob. use a standard mirror with sendmail as a standard package.

The sendmail MTA is installed with many openvz images. I ran with such problemes with many users during support sessions...