Jump to content
Froxlor Forum

ind

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ind

  • Rank
    Froxie

Profile Information

  • Location
    Berlin
  1. ind

    Apache2 runs, but fell inactive

    solved changed in envars export APACHE_PID_FILE=/var/run/apache2$SUFFIX.pid into: export APACHE_PID_FILE=/var/run/apache2/apache2$SUFFIX.pid
  2. ind

    Apache2 runs, but fell inactive

    I had to change the lockfile settings from default /var/lock/apache2/accept.lock to Mutex file:${APACHE_LOCK_DIR} default. With the original setting apache wouldn't start Might be there is an error in the mutex configuration which is # Since there is no sane way to get the parsed apache2 config in scripts, some # settings are defined via environment variables and then used in apache2ctl, # /etc/init.d/apache2, /etc/logrotate.d/apache2, etc. export APACHE_RUN_USER=www-data export APACHE_RUN_GROUP=www-data # temporary state file location. This might be changed to /run in Wheezy+1 export APACHE_PID_FILE=/var/run/apache2/apache2$SUFFIX.pid export APACHE_RUN_DIR=/var/run/apache2$SUFFIX export APACHE_LOCK_DIR=/var/lock/apache2$SUFFIX # Only /var/log/apache2 is handled by /etc/logrotate.d/apache2. export APACHE_LOG_DIR=/var/log/apache2$SUFFIX any helpful hints are appreciated....
  3. ind

    Apache2 runs, but fell inactive

    -- Logs begin at Thu 2018-11-08 15:31:09 CET, end at Wed 2018-11-14 16:14:11 CET. -- Nov 14 16:13:38 srvxx dovecot[30185]: lda(root): msgid=<20181114145503.7359F21E0270@ssrvxx>: save failed to INBOX: Read-only mbox Nov 14 16:13:38 srvxx postfix/local[30184]: 7359F21E0270: to=<root@srvxx>, orig_to=<root>, relay=local, delay=1116, delays=1115/0.01/0/0.16, dsn=4.3.0, status=deferred (temporary failure) Nov 14 16:13:45 srvxxsrvxxsrvxx systemd[1]: Stopped LSB: Apache2 web server. -- Subject: Unit apache2.service has finished shutting down -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apache2.service has finished shutting down. Nov 14 16:13:51 srvxx systemd[1]: Starting LSB: Apache2 web server... -- Subject: Unit apache2.service has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apache2.service has begun starting up. Nov 14 16:13:51 srvxx apache2[30226]: Starting web server: apache2httpd (pid 29324) already running Nov 14 16:14:11 srvxx apache2[30226]: failed! Nov 14 16:14:11 srvxx apache2[30226]: The apache2 instance did not start within 20 seconds. Please read the log files to discover problems ... (warning). Nov 14 16:14:11 srvxxsrvxx systemd[1]: apache2.service: control process exited, code=exited status=1 Nov 14 16:14:11 srvxx systemd[1]: Failed to start LSB: Apache2 web server. -- Subject: Unit apache2.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit apache2.service has failed. -- -- The result is failed. Nov 14 16:14:11 srv087 systemd[1]: Unit apache2.service entered failed state.
  4. ind

    Apache2 runs, but fell inactive

    Yep root@srvxx /var/www $ /etc/init.d/apache2 stop [ ok ] Stopping apache2 (via systemctl): apache2.service. root@srvxx /var/www $ /etc/init.d/apache2 start [....] Starting apache2 (via systemctl): apache2.serviceJob for apache2.service failed. See 'systemctl status apache2.service' and 'journalctl -xn' for details. failed! root@srvxx/var/www
  5. Hi, I upgraded from debian 7 to 8 (yeah - quite late) and so from apache2.4 to 2.4, before i go for debian 9 I need some help for this issue: when I start apache I get this: Nov 14 15:20:32 srv087 apache2[27920]: Starting web server: apache2 failed! Nov 14 15:20:32 srv087 apache2[27920]: The apache2 instance did not start within 20 seconds. Please read the log files to discover problems ... (warning). Nov 14 15:20:32 srv087 systemd[1]: apache2.service: control process exited, code=exited status=1 Nov 14 15:20:32 srv087 systemd[1]: Failed to start LSB: Apache2 web server. Nov 14 15:20:32 srv087 systemd[1]: Unit apache2.service entered failed state. but the server with the ID is running: 27934 root 15:20 /usr/sbin/apache2 -k start 27937 www-data 15:20 /usr/sbin/apache2 -k start 27938 www-data 15:20 /usr/sbin/apache2 -k start 27939 www-data 15:20 /usr/sbin/apache2 -k start in the error log I get this: [Wed Nov 14 15:20:12.229256 2018] [core:warn] [pid 27934] AH00098: pid file /var/run/apache2.pid overwritten -- Unclean shutdown of previous Apache run? [Wed Nov 14 15:20:12.235164 2018] [mpm_prefork:notice] [pid 27934] AH00163: Apache/2.4.10 (Debian) OpenSSL/1.0.1t configured -- resuming normal operations [Wed Nov 14 15:20:12.235224 2018] [core:notice] [pid 27934] AH00094: Command line: '/usr/sbin/apache2' I would like to have apache in normal state ... , any suggestions?
  6. Hat sich gerade erledigt - hatte die Fehlermeldung falsch interpretiert.. eine Auswahlliste der Begriffe für das Feld (AuthName):wäre vielleicht hifreich..
  7. Bei mir taucht das gleiche Problem auf. Egals was ich eingebe: Fehlermeldung Der Wert des Feldes "directory_authname" hat nicht das erwartete Format. PHP-Version: 5.6.30-1~dotdeb+7.1 MySQL-Server-Version: 5.6.36-1~dotdeb+7.1-log Webserver-Interface: APACHE2HANDLER Speicherauslastung: MemTotal: 16340016 kB MemFree: 2110292 kB System-Auslastung: 1.35 / 1.58 / 1.68 Kernel: 3.2.0-4-amd64 (x86_64) 0.9.38.7
  8. ind

    Erstellen von Konfigurationsdateien

    Hm - There is already a Cronjob in progress. Exiting... Take a look into the contents of /var/run/froxlor_froxlor_master_cronjob-tasks.lock-* for more information! ich glaube das war was ich ?bersehen hatte...
  9. ind

    Erstellen von Konfigurationsdateien

    bei: /usr/bin/nice -n 5 /usr/bin/php5 -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --tasks 1> /dev/null werden die ausszehenden Konfigurations?nderungen nicht durchgef?hrt bei /usr/bin/nice -n 5 /usr/bin/php5 -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --force l?ft er durch... Ausstehende Cron-Aufgaben: Zur Zeit gibt es keine ausstehenden Aufgaben f?r Froxlor
  10. ind

    Erstellen von Konfigurationsdateien

    Crond f?r Froxlor: # automatically generated cron-configuration by froxlor # do not manually edit this file as it will be re-generated periodically. PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin # */8 * * * * root /usr/bin/nice -n 5 /usr/bin/php5 -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --tasks 1> /dev/null 0 0 */2 * * root /usr/bin/nice -n 5 /usr/bin/php5 -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --traffic 1> /dev/null 7 0 1 * * root /usr/bin/nice -n 5 /usr/bin/php5 -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --used_tickets_reset 1> /dev/null 14 0 1 * * root /usr/bin/nice -n 5 /usr/bin/php5 -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --ticketarchive 1> /dev/null 5 0 * * * root /usr/bin/nice -n 5 /usr/bin/php5 -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --usage_report 1> /dev/null 0 */6 * * * root /usr/bin/nice -n 5 /usr/bin/php5 -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --mailboxsize 1> /dev/null cron log: Jul 28 13:24:01 srv087 /USR/SBIN/CRON[17109]: (root) CMD (/usr/bin/nice -n 5 /usr/bin/php5 -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --tasks 1> /dev/null) aber: Ausstehende Cron-Aufgaben: Neuerstellung der Webserver-Konfiguration Neuerstellung der Bind-Konfiguration
  11. Die Erstellen von Konfigurationsdateien h?ngt bei meiner Installation. Mit --force kann ich es durchf?hren, aber in der "normaklen Konfiguration bleibt er beim letzten"force" Durchlauf h?ngen. Hat da jemand eine Idee???
  12. ind

    update syscp to froxlor

    I tried to get the update documentation - but even after succesfully logged in, still this: Sorry, you don't have enough rights to continue. Perhaps you forgot to login? So I'm still looking for that update information - Thx
×