DaSilva
-
Posts
42 -
Joined
-
Last visited
Posts posted by DaSilva
-
-
Dieser LE DNS Check kann dafür verantwortlich sein?
Ich nehme mal die LE Option bei der Domain raus und untersuche das nochmal 24 Std.
-
Hallo,
Ja, leider steht nicht wirklich etwas darin, was auf einen Fehler hinweisen könnte.
[information] TasksCron: Searching for tasks to do [information] Running Let's Encrypt cronjob prior to regenerating webserver config files [information] Checking for LetsEncrypt client upgrades before renewing certificates: [Do 29. Okt 10:46:08 CET 2020] Already uptodate! [Do 29. Okt 10:46:08 CET 2020] Upgrade success! [Do 29. Okt 10:46:08 CET 2020] Installing cron job 3 0 * * * "/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh" > /dev/null [information] Requesting 1 new Let's Encrypt certificates [information] Creating certificate for domain.tld [information] Adding common-name: domain.tld [information] Adding SAN entry: www.domain.tld [information] Validating DNS of domain.tld [warning] Skipping Let's Encrypt generation for domain.tld due to no system known IP address via DNS check [information] Validating DNS of www.domain.tld [warning] Skipping Let's Encrypt generation for www.domain.tld due to no system known IP address via DNS check [information] Updated Let's Encrypt certificate for [information] Updated Let's Encrypt certificate for [information] Updated Let's Encrypt certificate for [information] Updated Let's Encrypt certificate for [information] Updated Let's Encrypt certificate for [information] Updated Let's Encrypt certificate for [information] Updated Let's Encrypt certificate for [information] Updated Let's Encrypt certificate for [error] Could not find file 'domain.tld.cer' in '/root/.acme.sh/domain.tld/' [error] Could not find file 'ca.cer' in '/root/.acme.sh/domain.tld/' [error] Could not find file 'fullchain.cer' in '/root/.acme.sh/domain.tld/' [error] Could not get Let's Encrypt certificate for domain.tld: [information] Updated Let's Encrypt certificate for [information] Updated Let's Encrypt certificate for [information] Updated Let's Encrypt certificate for [information] Updated Let's Encrypt certificate for [information] Updated Let's Encrypt certificate for [information] Let's Encrypt certificates have been updated [information] apache::createIpPort: creating ip/port settings for x.x.x.x:80 [debug] x.x.x.x:80 :: inserted vhostcontainer [information] apache::createIpPort: creating ip/port settings for x.x.x.x:443 [debug] x.x.x.x:443 :: inserted vhostcontainer [information] apache::createVirtualHosts: creating vhost container for domain 57, customer [information] apache::createVirtualHosts: creating vhost container for domain 55, customer [information] apache::createVirtualHosts: creating vhost container for domain 56, customer [information] apache::createVirtualHosts: creating vhost container for domain 45, customer [information] apache::createVirtualHosts: creating vhost container for domain 16, customer [information] apache::createVirtualHosts: creating vhost container for domain 80, customer [information] apache::createVirtualHosts: creating vhost container for domain 54, customer [information] apache::createVirtualHosts: creating vhost container for domain 22, customer [information] apache::createVirtualHosts: creating vhost container for domain 38, customer [information] apache::createVirtualHosts: creating vhost container for domain 28, customer [information] apache::createVirtualHosts: creating vhost container for domain 48, customer [information] apache::createVirtualHosts: creating vhost container for domain 74, customer [information] apache::createVirtualHosts: creating vhost container for domain 47, customer [information] apache::createVirtualHosts: creating vhost container for domain 14, customer [information] apache::createVirtualHosts: creating vhost container for domain 72, customer [information] apache::createVirtualHosts: creating vhost container for domain 52, customer [information] apache::createVirtualHosts: creating vhost container for domain 58, customer [information] apache::createVirtualHosts: creating vhost container for domain 31, customer [information] apache::createVirtualHosts: creating vhost container for domain 76, customer [information] apache::createVirtualHosts: creating vhost container for domain 44, customer [information] apache::createVirtualHosts: creating vhost container for domain 67, customer [information] apache::createVirtualHosts: creating vhost container for domain 81, customer [information] apache::createVirtualHosts: creating vhost container for domain 69, customer [information] apache::createVirtualHosts: creating vhost container for domain 68, customer [information] apache::createVirtualHosts: creating vhost container for domain 53, customer [information] apache::createVirtualHosts: creating vhost container for domain 15, customer [information] apache::createVirtualHosts: creating vhost container for domain 30, customer [information] apache::createVirtualHosts: creating vhost container for domain 79, customer [information] apache::createVirtualHosts: creating vhost container for domain 34, customer [information] apache::createVirtualHosts: creating vhost container for domain 26, customer [information] apache::createVirtualHosts: creating vhost container for domain 37, customer [information] apache::createVirtualHosts: creating vhost container for domain 66, customer [information] apache::createVirtualHosts: creating vhost container for domain 29, customer [information] apache::createVirtualHosts: creating vhost container for domain 25, customer [information] apache::createVirtualHosts: creating vhost container for domain 70, customer [information] apache::createVirtualHosts: creating vhost container for domain 71, customer [information] apache::createVirtualHosts: creating vhost container for domain 13, customer [information] apache::createVirtualHosts: creating vhost container for domain 73, customer [information] apache::createVirtualHosts: creating vhost container for domain 46, customer [information] apache::createVirtualHosts: creating vhost container for domain 49, customer [information] apache::createVirtualHosts: creating vhost container for domain 20, customer [information] apache::createVirtualHosts: creating vhost container for domain 21, customer [information] apache::createVirtualHosts: creating vhost container for domain 64, customer [information] apache::createVirtualHosts: creating vhost container for domain 65, customer [information] apache::createVirtualHosts: creating vhost container for domain 51, customer [information] apache::createVirtualHosts: creating vhost container for domain 50, customer [information] apache::createVirtualHosts: creating vhost container for domain 59, customer [information] apache::createVirtualHosts: creating vhost container for domain 23, customer [information] apache::createVirtualHosts: creating vhost container for domain 75, customer [information] apache::createVirtualHosts: creating vhost container for domain 3, customer [information] apache::writeConfigs: rebuilding /etc/apache2/sites-enabled/ [information] apache::writeConfigs: rebuilding /etc/apache2/htpasswd/ [information] apache::writeConfigs: rebuilding /etc/apache2/sites-enabled/ [information] Froxlor\Cron\Http\ApacheFcgi::reload: running service php7.0-fpm restart [information] Froxlor\Cron\Http\ApacheFcgi::reload: running service php7.1-fpm restart [information] Froxlor\Cron\Http\ApacheFcgi::reload: fpm config directory "/etc/php/5.6/fpm/pool.d/" is empty. Creating dummy. [information] Froxlor\Cron\Http\ApacheFcgi::reload: running service php5.6-fpm restart [information] Froxlor\Cron\Http\ApacheFcgi::reload: running service php7.2-fpm restart [information] Froxlor\Cron\Http\ApacheFcgi::reload: fpm config directory "/etc/php/7.3/fpm/pool.d/" is empty. Creating dummy. [information] Froxlor\Cron\Http\ApacheFcgi::reload: running service php7.3-fpm restart [information] Froxlor\Cron\Http\ApacheFcgi::reload: reloading Froxlor\Cron\Http\ApacheFcgi [notice] Creating passwd file [notice] Writing 24 entries to passwd file [notice] Succesfully wrote passwd file [notice] Creating group file [notice] Writing 23 entries to group file [notice] Succesfully wrote group file [notice] Creating shadow file [notice] Writing 24 entries to shadow file [notice] Succesfully wrote shadow file [notice] Checking system's last guid -
So,
Es gab nun keine weiteren "attempt to connect to Unix domain" Fehlermeldungen in der error.log der Kunden auf dem Server. Ich denke damit kann man sagen, dass die Fehler durch den Froxlor Cronjob hervorgerufen werden. Welche Daten kann ich übergeben um dies weiter zu analysieren?
-
Ich War der Meinung, dass diese Datei neu angelegt wird "no matter what" Hab ich mich wohl geirrt. Nagut, dann mach ich das so. Am Ende kommt's aufs gleiche raus
-
Ich habe es mit einem chmod 000 auf /var/www/froxlor/scripts/froxlor_master_cronjob.php versucht, der Cronjob lief aber weiterhin durch und es gab wieder socket Fehler um Wed Oct 28 03:50:05.357330, Wed Oct 28 04:05:04.981422 und Wed Oct 28 07:25:05.767229. Ich habe jetzt in den Cron Einstellungen den php Befehl mal auf /bin/false gestellt und teste es nochmal 24 Stunden.
-
Hab jetzt mal das Forum nach "attempt to connect to Unix domain" durchsucht und konnte da nur Probleme finden, welche nicht auf mein problem anzuwenden sind. Die meisten Probleme beziehen sich auf Einrichtung von PHP-FPM (Was ja generell bei mir funktioniert) oder Probleme mit nscd, welches nicht auf diesem Server existiert, es wird extrausers verwendet. Probleme dieser Art im Bezug auf den Froxlor Cronjob konnte ich auch nur finden im direkten Bezug zu der initialen Einrichtung von PHP-FPM.
Es ist halt sehr merkwürdig, dass alles wie butter läuft und es ab und an durch einen Froxlor Cronjob zu diesen socket Fehlern kommt, diese dann z.B. durch einen Weiteren Cronjob wieder behoben werden. Es scheint fast so, als könnte der Froxlor Cronjob manchmal nicht alles abarbeiten, was er wollte. Dieses Problem tritt mehrmals täglich auf, also auch nicht bei jedem oder jedem 2. cronjob. Manchmal hällt der Fehler auch ne Stunde oder länger an bis ein automatischer Cronjob den Fehler wieder behebt.
-
Hallo liebe Leute,
ich habe ein Phänomen, welches auf ein paar Servern mit sehr starken Zugriffszahlen auftritt.
Ich sehe auf diesen Servern vermehrt diese Fehlermeldungen:
[Sun Oct 25 16:00:04.209734 2020] [proxy:error] [pid 35780:tid 139952056231680] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/lib/apache2/fastcgi/6-[user-domain]-php-fpm.socket (*) failed
Problem ist, dass der Socket in jedem Fall vorhanden ist. Dieses Problem kann durch einen manuellen oder weiteren automatischen "Froxlorcron" gelöst werden.
Das Problem tritt zu 99% immer zur 5 Minute auf also zu Zeiten in denen der Froxlor Cronjob durch läuft.
Weitere Cronjobs auf dem Server welche diese Zeiten erklären könnten gibt es nicht. Hatte schon einmal jemand diese Probleme?
Ich habe es nun mit "ondemand" und "dynamic" probiert, ondemand wirft in jedem Fall mehr Fehler, dynamic ist jedoch auch nicht fehlerfrei. Die gleiche Konfiguration läuft auf anderen Servern ohne Probleme, da könnte es aber auch an wenig Traffic liegen.
Welche Logs soll ich bereit stellen? Ich bin leider mit meinem Latein am ende :(
Vielen Dank!
-
Hey,
is there the possibility with the 2FA function to hide/disable the email option completely?
And to set purely to QR Code? E-Mail is too insecure for our structure and I do not recommend it. Especially because the admin mail is not accessible for the users.
2FA will lock it out.
Is there any way we could do that? Could we adapt this in any config file?
-
Could be an option, that has to be enabled with caution, like /bin/bash for FTP users. We will fiddle with this idea and see what we can do to help prevent most of the bad things, that customers can do. Maybe limit it to curl/wget and stuff, without execute permissions for piped commands or strip them entirely.
-
20 minutes ago, d00p said:
what more features in the API??? We're at release-candidate level
That's correct and i dont mean it in any bad way.
The API Should be able to add/modify/remove/sanity-check Cronjobs on Customer Level. We are now also working on such a function, as this is the main reason we have to do anything Froxlor related, except updates. Would be a massive convenience. Are you interested in this function when we have it up and running?
-
Very well, the system runs flawlessly for now.
We are setting it up in an semi-production environment and can not wait for more features in the API (cronjobs are very high on our wish list). we are testing this release and will report any major bugs or changes that we made to the code(pull request).
Thank you so much!
-
Woks like a charm the second time!
i had to manually set the parameters in the Froxlor panel settings (e.g. libnss-extrausers flag). Is this intended or should i have run the Froxlor master cronjob for the changes to take effect?
-
Can i just repeat the step?
edit: Btw. there is no reported error in the mysql error.log, very strange.
-
Wonderfull, works like a Charm.
Now i wanted to test the configuration Script:
Here is what i did:
php /var/www/froxlor//install/scripts/config-services.php --froxlor-dir=/var/www/froxlor/ --create
this is the json i got:
{"distro":"buster","http":"apache24","dns":"x","smtp":"postfix_dovecot","mail":"dovecot_postfix2","ftp":"proftpd","system":["cron","awstats","libnssextrausers","logrotate","php-fpm"]}All went well until php fpm, here is the output:
php7.3-fpm (7.3.4-2) wird eingerichtet ... Creating config file /etc/php/7.3/fpm/php.ini with new version NOTICE: Not enabling PHP 7.3 FPM by default. NOTICE: To enable PHP 7.3 FPM in Apache2 do: NOTICE: a2enmod proxy_fcgi setenvif NOTICE: a2enconf php7.3-fpm NOTICE: You are seeing this message because you have apache2 package installed. Created symlink /etc/systemd/system/multi-user.target.wants/php7.3-fpm.service → /lib/systemd/system/php7.3-fpm.service. php-fpm (2:7.3+69) wird eingerichtet ... Trigger für systemd (241-7~deb10u1) werden verarbeitet ... PHP Warning: Error while sending QUERY packet. PID=22149 in /var/www/froxlor/lib/Froxlor/Database/Database.php on line 83 froxlor[22149]: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away froxlor[22149]: --- DEBUG: #0 /var/www/froxlor/lib/Froxlor/Database/Database.php(83): PDOStatement->execute(Array) #1 /var/www/froxlor/lib/Froxlor/Settings.php(109): Froxlor\Database\Database::pexecute(Object(PDOStatement), Array) #2 /var/www/froxlor/lib/Froxlor/Settings.php(179): Froxlor\Settings::storeSetting('panel', 'is_configured', '1') #3 /var/www/froxlor/lib/Froxlor/Cli/Action/ConfigServicesAction.php(298): Froxlor\Settings::Set('panel.is_config...', '1', true) #4 /var/www/froxlor/lib/Froxlor/Cli/Action/ConfigServicesAction.php(41): Froxlor\Cli\Action\ConfigServicesAction->applyConfig() #5 /var/www/froxlor/lib/Froxlor/Cli/Action/ConfigServicesAction.php(19): Froxlor\Cli\Action\ConfigServicesAction->validate() #6 /var/www/froxlor/lib/Froxlor/Cli/CmdLineHandler.php(64): Froxlor\Cli\Action\ConfigServicesAction->run() #7 /var/www/froxlor/lib/Froxlor/Cli/CmdLineHandler.php(47): Froxlor\Cli\CmdLineHandler->__construct(2, Array) #8 /var/www/froxlor/install/scripts/config-services.php(28): Froxlor\Cli\CmdLineHandler::processParameters(2, Array) #9 {main} We are sorry, but a MySQL - error occurred. The administrator may find more information in the sysloghere are the last few lines from the syslog:
Sep 17 12:46:41 froxlorimage systemd[1]: Starting The PHP 7.3 FastCGI Process Manager... Sep 17 12:46:41 froxlorimage systemd[1]: Started The PHP 7.3 FastCGI Process Manager. Sep 17 12:46:41 froxlorimage systemd[1]: Reloading. Sep 17 12:46:41 froxlorimage systemd[1]: /lib/systemd/system/dovecot.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/dovecot/master.pid → /run/dovecot/master.pid; please update the unit file accordingly. Sep 17 12:46:42 froxlorimage systemd[1]: Stopping The Apache HTTP Server... Sep 17 12:46:42 froxlorimage systemd[1]: apache2.service: Succeeded. Sep 17 12:46:42 froxlorimage systemd[1]: Stopped The Apache HTTP Server. Sep 17 12:46:42 froxlorimage systemd[1]: Starting The Apache HTTP Server... Sep 17 12:46:42 froxlorimage systemd[1]: Started The Apache HTTP Server. Sep 17 12:46:42 froxlorimage froxlor[22149]: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away Sep 17 12:46:42 froxlorimage froxlor[22149]: --- DEBUG: #0 /var/www/froxlor/lib/Froxlor/Database/Database.php(83): PDOStatement->execute(Array) #1 /var/www/froxlor/lib/Froxlor/Settings.php(109): Froxlor\Database\Database::pexecute(Object(PDOStatement), Array) #2 /var/www/froxlor/lib/Froxlor/Settings.php(179): Froxlor\Settings::storeSetting('panel', 'is_configured', '1') #3 /var/www/froxlor/lib/Froxlor/Cli/Action/ConfigServicesAction.php(298): Froxlor\Settings::Set('panel.is_config...', '1', true) #4 /var/www/froxlor/lib/Froxlor/Cli/Action/ConfigServicesAction.php(41): Froxlor\Cli\Action\ConfigServicesAction->applyConfig() #5 /var/www/froxlor/lib/Froxlor/Cli/Action/ConfigServicesAction.php(19): Froxlor\Cli\Action\ConfigServicesAction->validate() #6 /var/www/froxlor/lib/Froxlor/Cli/CmdLineHandler.php(64): Froxlor\Cli\Action\ConfigServicesAction->run() #7 /var/www/froxlor/lib/Froxlor/Cli/CmdLineHandler.php(47): Froxlor\Cli\CmdLineHandler->__construct(2, Array) #8 /var/www/froxlor/install/scripts/config-services.php(28): Froxlor\Cli\CmdLineHandler::processParameters(2, Array) #9 {main}Thanks for all your work!
-
4 minutes ago, d00p said:
No, normally the installer does this for you. What version are you testing with, latest git-master?
I downloaded froxlor-0.10.0-rc2.tar.gz from your first post. Should i pull the current git?
Thanks!
-
Hi,
is set up a new Server with Debian Buster. The Wiki install guide provides no guidance whatsoever on what the server needs to start the web-installer, would be nice to have a complete install guide when there is no LAMP Stack in place.i now get this error message during the installation:
Checking MySQL-root access... OK Creating backup of old database... OK (/tmp/froxlor_backup_201909171108.sql) Preparing database... OK Creating database and username... OK Testing if database and user have been created correctly... SQLSTATE[HY000] [1045] Access denied for user 'froxlor'@'localhost' (using password: YES) SQLSTATE[HY000] [1045] Access denied for user 'froxlor'@'localhost' (using password: YES)
mysql> use mysql;
Database changed
mysql> select user from user;
+------------------+
| user |
+------------------+
| mysql.infoschema |
| mysql.session |
| mysql.sys |
| root |
+------------------+
4 rows in set (0,00 sec)I am Using:
mysql 8.0.17-1debian10 (With mysql native password)
php 7.3.4-2
apache 2.4
Kernel 4.9.0-3i hope you can help with this.
Should i create the user and Database manually? -
Great, I really hadn't thought of that! They were really missing. For others, these variables have to be entered in Froxlor.
php_admin_flags
opcache.file_cache_only
opcache.enable_cli
opcache.enable_file_overridephp_admin_values
opcache.file_cache -
13 minutes ago, d00p said:
mod_php or fcgid or PHP-FPM? For mod_php you need to edit the one and only php.ini or use .htaccess
Sorry, I forgot. It's PHP-FPM. And in the Froxlor GUI it doesn't work.
The variable in Froxlor is in the screenshot only as an example. Unfortunately it doesn't work there.
Here the screenshots as I mean it.
-
Hi, I currently have the problem that certain php variables are not loaded by Froxlor. Only when I write them into the Conf.
For example, I wanted to set this variable.
opcache.file_cache = """
This only works if I enter it in this file.
/etc/php/7.3/mods-available/opcache.ini
Do you have any idea why?
Socket Fehler bei PHP-FPM (Froxlor Cronjob bedingt?!)
in German / Deutsch
Posted
Ich kann mir absolut nicht erklären, warum ein LE DNS Check zu einem PHP-FPM Socket Fehler führen sollte, aber seitdem die Domain von LE befreit wurde, gab es bisher keine weiteren Socket Fehler.
Könntest du erläutern, wie das durch einen LE DNS Check passieren könnte?