Posts by itscz.org

Ja, ging aber nicht so einfach. War damals beim Setup nur nen Auftragsserver und nicht mein Eigener, dann liefen zuviele Criticals drauf als dass ich ein Debian Update gewagt hätte, zwischendurch hatte ich im anderen Rahmen i-MSCP kennengelernt aber auch das war mir zu heiß, es dort upzudaten, zumal es dafür keinen richtigen Bedarf gab, lediglich die Server-Software wurde einfach zu alt, vor allem PHP und OpenSSL. Nun habe ich am Ende aber den alten Server aus Firmenumstrukturierungen geerbt und naja, wollte dann rasch davon weg

Ich habe es tatsächlich geschafft meinen letzten ispCP auf Debian 6 mit PHP 5.2 und einem ssllabs Rating mit tiefrotem F und lauter anderen Sackgassen auf einen nagelneue Kiste mit i-MSCP 1.3.7 zu ziehen

Da ich weder ispCP auf der neuen Kiste installieren konnte noch mich getraut habe, mit iMSCP auf der alten Kiste anzufangen (zuuuuuuu lange in Betrieb, zuuuuuuuu viele Dateien von Hand editiert), habe ich tatsächlich jeden User einzeln angeschrieben, mit ihm einen Umzugstermin vereinbart und alles VON HAND mit neuen Kennwörtern neu angelegt, mit mysqldump und rsync und courier-to-dovecot migration alles rübergezogen, DNS angepasst (leider noch voll extern) und voila. ApacheBenches jenseits der 500% Boost und alle sind (bisher) zufrieden.

Ich genieße etwas die neuen Einstellungsmöglichkeiten für SSL (ja, ich hab in ispCP die ganzen apache sites von hand dafür editiert...) und externe mailserver (unter ispcp schön in den postfix domains rumgefummelt) und ein paar andere goodies wie shared mountpoints für domain aliase (GEIL!). Mit ein paar anderen dingen habe ich noch zu knabbern wie DNS hidden primary setup, php error log und jailed domain crons - aber das wird schon.

Danke an alle die an iMSCP wie auch immer beteiligt waren, echt geiles Teil und ein (Web-)Root OHNE das geht absolut gar nicht mehr!

Wollte ich nur mal loswerden

Same here. What i am missing most is configuring php error log, i am totally confused that such an important thing is turned OFF by default.

On ispCP i changed the template file so each domain got its log unter its "logs" subdirectory.

On iMSCP this doesn't work anymore because the domain's log dir is now owned by root, but php runs under vuXXXX. I tried to put it under domain root folder then but there is simply happening nothing. It may be a permission thingy i don't know yet. I saw there is some php error printing within the apache? error log but that is not enough. Think about call traces that are printed or even more using XDEBUG.

Of course if a new log is added, it should be part of rotation as well

I saw there are listener files for pool config override but that's too static and unsexy. I also don't know a good error log store location yet because of that root-thingy.

It would be nice if the customer (or the reseller configuring a customer) can add custom logrotation configs.
Currently i maintain one file in /etc/logrotate.d/ to setup rotation for my magento customers like this:

# Customer: xxx: Magento Logs
/var/www/virtual/xxx/htdocs/var/log/*.log {
su vu2009 vu2009
weekly
missingok
rotate 4
compress
delaycompress
notifempty
mail my@mail
mailfirst
sharedscripts
}

If there would be a textarea for editing this... wooooooooooa
For customer level configs the su directive should be forbidden / set automatically of course

What you think?

For now if i configure a space quota i have to define a total mail quota as well and a quota for each mail account.
This is very annoying.

I would like to:

1. Leave email quota unlimited while a space quota is definied, then mail may be counted for statistics, but is not calculated for quota (i think that is ispCP behaviour)

2. Define an overall mail quota but NOT for each account, so quota is shared accross them. I've seen a config option that should act like this, but it has no affect or didn't understand it right. Leaving a zero at account setup is denied if mail quota is configured.

Thanks.

1. Config Option for default email address behaviour for customers:
- always show
- default show
- default hide
- always hide

If default, they should have a toggle button on the list.
For resellers and admin only default options should be possible.
I know it was there similary in ispCP and early iMSCP, don't know why it was removed, but i like to have it back

2. Default total list length including ALL (for all lists :))

3. I also would like to configure each default address or at least keep them in sync, because now they are created differently:
- For main domains, abuse, hostmaster and postmaster is forwarded to reseller or admin address, but webmaster to the customer address
- For alias domains, all four are forwarded to the customer address
Why is this so different?

Output of findmnt -lo source,target,propagation

The initial cron i configured was (JAILED):
* * * * * ls -l /

Here are the exact steps:

- Change into customer acc
- Try to remove cronjob
- Page is reloaded and it says update in progress
- This log entry appears:

==> /var/log/imscp/Modules::Plugin_CronJobs.log <==
[Fri Oct 28 21:00:46 2016] [fatal] iMSCP::DbTasksProcessor::_process: Modules::Plugin::_call: Could not delete /var/chroot/CronJobs/jail/var/www/virtual/ufo-base.de: problem unlinking /var/chroot/CronJobs/jail/var/www/virtual/ufo-base.de: cannot remove directory: Device or resource busy

I click the Cronjob page again for refresh and now its an 400 Bad Request, because the plugin is instantly in error state and the page inaccessible.

The only thing i could do so far is restart the server, then disable the CronJobs plugin. I can also re-enable it and add and edit crons, but i cannot delete this first one.

I can give you panel and root ssh access if that will help...

How can i unblock this manually?

I stopped everything so that the output of "lsof | grep /var/chroot/" is empty now, but it still says device or resource is busy.

EDIT: I managed to get both plugins enabled again by restarting the server. Now i tried to remove the jailed test cron again and i get an 400 Bad Request in https://xxx:8443/client/cronjobs - The plugin is then in error state again

Hi,

i just installed both plugins on a fresh i-MSCP 1.3.7 on Debian Jessie 8.6 Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u1 (2016-09-03) x86_64 GNU/Linux

Testing was fine with SSH and Jobs (Jailed), now i tried to remove the ssh user from my test customer and it hangs in update in progress state.
I then tried to go further with removing the permissions from that reseller and now both SSH and CronJob plugins are in error state:

Modules::Plugin::_call: Could not delete /var/chroot/InstantSSH/shared_jail/var/www/virtual/xxx: problem unlinking /var/chroot/InstantSSH/shared_jail/var/www/virtual/xxx: cannot remove directory: Device or resource busy

What can i do?

EDIT: The test cron is still running