over the past days I've checked everything and tried to optimize apache, mysql unfortunately without success.
Would it be possible to order a payable investigation?
Posts by fulltilt
-
-
Such error should not occurs with Serie 1.4.x because we don't use auxprop.
Content of your /etc/postfix/sasl/smtpd.conf is?
you're right, my mistake ... I have copied the old smtpd_sender_restrictions without comparing .... beat me
-
- IMSCP: 1.4.3
- Distribution: Debian 8.6
- Proftpd
- PHP FCGID
- MariaDB 10.0
- Courier
- Roundcube
- Pydio
- Plugins:
PanelRedirect 1.1.5, PMA Captcha 1.1.1, RoundCubePlugins 2.0.1, SpamAssassin 1.1.1 , LetsEncrypt 3.0.0a few days ago I have already reported about apache and nginx timeout issues, after the update (1.3.16 > 1.4.3) nothing has changed.
these are local timeouts that only affect apache, nginx and the monit server.
So I need to use monit for restarts:
if failed host localhost port 80 protocol http then exec "/usr/sbin/apachectl graceful"
I also run curl response tests via cron (1min) from my local system, sometimes it works for many hours but usually there are interruptions.
Following response outputs were generated while monit restart were deactivated:Lookup time: 0,012
Connect time: 0,025
PreXfer time: 0,199
StartXfer time: 0,216
Total time: 0,216Lookup time: 0,012
Connect time: 1,021
PreXfer time: 1,214
StartXfer time: 1,261
Total time: 1,261Lookup time: 0,012
Connect time: 64,387
PreXfer time: 64,559
StartXfer time: 64,576
Total time: 64,576Lookup time: 0,014
Connect time: 64,857
PreXfer time: 65,024
StartXfer time: 65,042
Total time: 65,042Lookup time: 0,012
Connect time: 15,454
PreXfer time: 15,632
StartXfer time: 15,649
Total time: 15,649Code- monit[18344]: 'apache2' failed protocol test [HTTP] at INET[localhost:80] via TCP -- HTTP: Error receiving data
- Sun May 07 11:34:49.006270 2017] [suexec:notice] [pid 21049:tid 140091504371584] AH01232: suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
- [Sun May 7 11:34:49 2017] [notice] vlogger: caught TERM, shutting down
- [Sun May 7 11:34:49 2017] [notice] vlogger: DBI usage tracker dump interval set to 30 seconds
- [Sun May 7 11:34:49 2017] [notice] vlogger: started CustomLog Handler -- resuming normal operations
- [Sun May 07 11:34:50.013632 2017] [mpm_event:notice] [pid 21052:tid 140091504371584] AH00489: Apache/2.4.10 (Debian) OpenSSL/1.0.1t mod_fcgid/2.3.9 configured -- resuming normal operations
- [Sun May 07 11:34:50.013677 2017] [core:notice] [pid 21052:tid 140091504371584] AH00094: Command line: '/usr/sbin/apache2'
- [Sun May 07 11:40:59.785147 2017] [mpm_event:notice] [pid 21052:tid 140091504371584] AH00493: SIGUSR1 received. Doing graceful restart
- [Sun May 7 11:40:59 2017] [notice] vlogger: caught TERM, shutting down
- [Sun May 7 11:41:00 2017] [notice] vlogger: DBI usage tracker dump interval set to 30 seconds
- [Sun May 7 11:41:00 2017] [notice] vlogger: started CustomLog Handler -- resuming normal operations
- [Sun May 07 11:41:01.009412 2017] [mpm_event:notice] [pid 21052:tid 140091504371584] AH00489: Apache/2.4.10 (Debian) OpenSSL/1.0.1t mod_fcgid/2.3.9 configured -- resuming normal operations
- [Sun May 07 11:41:01.009427 2017] [core:notice] [pid 21052:tid 140091504371584] AH00094: Command line: '/usr/sbin/apache2'
- [Sun May 07 11:41:01.009441 2017] [mpm_event:warn] [pid 21052:tid 140091504371584] AH00488: long lost child came home! (pid 21055)
during a timeout apache, nginx and monit server could also re-activated by service imscp_panel restart ....
-
- IMSCP: 1.4.3
- Distribution: Debian 8.6
- Proftpd
- PHP FCGID
- MariaDB 10.0
- Courier
- Roundcube
- Pydio
- Plugins:
PanelRedirect 1.1.5, PMA Captcha 1.1.1, RoundCubePlugins 2.0.1, SpamAssassin 1.1.1 , LetsEncrypt 3.0.0update went well without any problems but now I see many auxpropfunc error in journalctl
-
I see many thousands of /autodiscover/autodiscover.xml requests in my panel logs, does it come from the roundcube plugin and could this lead to problems with apache or nginx interruption?
proxy:https://admin.host2.myhost.tld…discover/autodiscover.xml -
it seems sometimes there are conflicts w/ nginx and or php5-fpm, if I restart nginx and php5-fpm, apache2 is also back online ...
and sometimes an nginx restart shows this error message:
Code- ● nginx.service - A high performance web server and a reverse proxy server
- Loaded: loaded (/lib/systemd/system/nginx.service; enabled)
- Active: failed (Result: exit-code) since Wed 2017-05-03 11:41:58 CEST; 21s ago
- Process: 27052 ExecStop=/sbin/start-stop-daemon --quiet --stop --retry QUIT/5 --pidfile /run/nginx.pid (code=exited, status=1/FAILURE)
- Process: 5855 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=1/FAILURE)
- Process: 5851 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
- Main PID: 24339 (code=exited, status=0/SUCCESS)
- May 03 11:41:57 host2 nginx[5855]: nginx: [emerg] bind() to xx.xx.xxx.xx:8443 failed (98: Address already in use)
- May 03 11:41:57 host2 nginx[5855]: nginx: [emerg] bind() to [::]:8443 failed (98: Address already in use)
- May 03 11:41:57 host2 nginx[5855]: nginx: [emerg] bind() to xx.xx.xxx.xx:8880 failed (98: Address already in use)
- May 03 11:41:57 host2 nginx[5855]: nginx: [emerg] bind() to [::]:8880 failed (98: Address already in use)
- May 03 11:41:57 host2 nginx[5855]: nginx: [emerg] bind() to xx.xx.xxx.xx:8443 failed (98: Address already in use)
- May 03 11:41:57 host2 nginx[5855]: nginx: [emerg] bind() to [::]:8443 failed (98: Address already in use)
- May 03 11:41:58 host2 nginx[5855]: nginx: [emerg] still could not bind()
- May 03 11:41:58 host2 systemd[1]: nginx.service: control process exited, code=exited status=1
- May 03 11:41:58 host2 systemd[1]: Failed to start A high performance web server and a reverse proxy server.
- May 03 11:41:58 host2 systemd[1]: Unit nginx.service entered failed state.
-
CPU load looks good ... no zombies and nothing special in our error logs, v3.16 was always very reliable so far ...
for testing I have set a higher value for fs.file-max = 4097152 and reduced open-files limits in my.cnf
there were no problems at night, but I guess it starts over when customers working on their applications### edit ###
yep, have to update - looks like the vlogger issueCode- [Wed May 03 08:37:23.925425 2017] [mpm_worker:notice] [pid 24236:tid 140630988191616] AH00295: caught SIGTERM, shutting down
- [Wed May 3 08:37:23 2017] [notice] vlogger: caught TERM, shutting down
- [Wed May 3 08:37:25 2017] [notice] vlogger: DBI usage tracker dump interval set to 30 seconds
- [Wed May 3 08:37:25 2017] [notice] vlogger: started CustomLog Handler -- resuming normal operations
-
### Note ###
I will not be able to do the update until the weekend ...
But I recognized that a certain error message appears in the daemon logs before it freezes:Access denied for user 'web757'@'localhost' (using password: YES)
after that I see also a DBI connection error for the imscp_user connection
and mostly the panel is also frozen so I have to restart nginx, panel and apache.The system has been running smoothly for about 5 months without any problems, so it could be caused by a customer script ...
above database connection access for web757'@'localhost') was set to % by the customer -
OK, I have restored the plugin from a backup ...
so I guess that means I should update the roundcube plugin after upgrading imSCP, right? -
- IMSCP: 1.3.16 (Build: 20170107)
- Distribution: Debian 8.6
- Proftpd
- PHP FCGID
- MariaDB 10.0
- Courier
- Roundcube
- Pydio
- Plugins:
PanelRedirect 1.1.5, PMA Captcha 1.1.1, RoundCubePlugins 1.2.6, SpamAssassin 1.1.1 , LetsEncrypt 3.0.1because of a planned imSCP upgrade I updated my plugins first ... letsencrypt went well but roundcube plugins did not ...
should I re-install the previous version of RoundCubePlugins 1.2.6 or is there any other way to fix this?
Before I can run my imSCP upgrade I have to do some testing in a V-Box ... is there any soltution for a quick fix?Code- Plugin::RoundcubePlugins::_installComposerPackages:
- [Symfony\Component\Console\Exception\RuntimeException]
- The "--no-suggest" option does not exist.
- require [--dev] [--prefer-source] [--prefer-dist] [--no-progress] [--no-update] [--no-scripts] [--update-no-dev] [--update-with-dependencies] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--] []...