Jump to content
Froxlor Forum

ripieces

Members
  • Content Count

    14
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by ripieces

  1. Looking (again / more properly) at the MasterCron.php code Froxlor already uses a locking mechanism based on the PID - however I think this is doomed to fail in my opinion, since cron jobs can run in parallel with different PIDs. (this is wrong info sorry) I tried to run two scripts in parallel, one that does the nss extrausers files and one that does the chown many times each, all went through without any error, so that must be s.th. else.
  2. froxlorlocal is the user we have for the PHP-FPM enabled froxlor-VHOST, hm.
  3. d00p pointed this out on GitHub, this is actually a very good question / fact :S I still think it's related to libnss-extrausers, but that's really weird.
  4. I opened an issue to track the problem on the issue tracker (I hope that is the right thing to do, I am not sure) https://github.com/Froxlor/Froxlor/issues/928 Also added notes about a solution there, but not sure if good. We could continue the discussion here to avoid spamming users that folow it there.
  5. I switched both servers to libnss-extrausers back then for the same reason, because libnss-mysql would make things eally slow and sometimes even stall a bit. This could be indeed the reason, since up to 4 tasks can run at the same time with the default /etc/cron.d/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 # */5 * * * * root /usr/bin/nice -n 5 /usr/bin/php -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --tasks
  6. Sadly it didn't help on the h2 one, it just happened again Edit: Just so you can see I really entered the commands: root@h2 ~ # grep -r froxlorlocal /etc /etc/subgid-:froxlorlocal:1279648:65536 /etc/subgid:froxlorlocal:1279648:65536 /etc/gshadow-:froxlorlocal:!::www-data /etc/passwd-:froxlorlocal:x:9999:9999:,,,:/home/froxlorlocal:/bin/false /etc/shadow:froxlorlocal:*:17141:0:99999:7::: /etc/subuid-:froxlorlocal:1279648:65536 /etc/gshadow:www-data:*::froxlorlocal /etc/gshadow:froxlorlocal:!::www-data /etc/shadow-:froxlorlocal:*:17141:0:99999:7::: /etc/php/7.3/fpm/pool.d/h2.vgstudios.
  7. Thank you very much for your reply. I will report back if it solved it in a few days (I have doubts and need to test it).
  8. We have a server with many "customers" (90+, because I tend to separate websites by customers when they are not related) and we get these errors very randomly by email and with about an average of 1 - 2 times per week I think (not every day at least): Subject: Cron <root@h2> /usr/bin/nice -n 5 /usr/bin/php -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --tasks 1> /dev/null Time:3/7/21, 6:40 PM Content: chown: invalid user: ‘froxlorlocal:froxlorlocal’ Edit: I also had it one time already where it failed with "invalid group" instead. It's driving
  9. For one of my friend's company this _could_ be interesting, if you have proper backups / depending on how those are handled. This is the biggest thing that keeps us from moving to other solutions, currently we use duplicity to backup encrypted on some cloud service(s) and moving elsewhere would mean usually a lot of drawbacks on the backups / backup retention time etc. But just see it as note, maybe many other customers have other problems / priorities and this won't be one with them maybe. Anyways: Good luck and success with your new project!
  10. Thank you very much for your help. Yes they were in there. I think that will solve it! (Used --remove instead of --delete.) Thank you!
  11. Yes sorry, I meant 0.10.17-1 (current latest). [Tue 26 May 2020 12:07:10 AM CEST] 3155.co.il:Verify error:Invalid response from https://3155.co.il/.well-known/acme-challenge/iySt9DPeykV5--MPZDoEbhBcdRhvDERKKhybpcJk7oo [2606:4700:3036::681f:4e4a]: [Tue 26 May 2020 12:07:10 AM CEST] Please add '--debug' or '--log' to check more details. [Tue 26 May 2020 12:07:10 AM CEST] See: https://github.com/acmesh-official/acme.sh/wiki/How-to-debug-acme.sh [Tue 26 May 2020 12:07:11 AM CEST] Error renew 3155.co.il. [Tue 26 May 2020 12:07:20 AM CEST] hasade.vagas.co.il:Verify error:DNS problem: NXDOMAIN l
  12. Hi. Since we are on 0.10.7-1 we get acme.sh errors from the cron for domains that we deleted quite some while ago from Froxlor or that we removed from Let's Encrypt SSL earlier. Is this a bug or normal? Anyone else with that problem? With kind regards
  13. I wanted to suggest providing Liberapay.com as option for donations to the Froxlor team. It also allows to have teams.
  14. Hello. This is just a suggestion (so free free to ignore it): Increasingly people seem to want to use Gmail MX or Outlook MX with their domains. For that to work properly, I need to uncheck "Emaildomain" of course (otherwise any sending email accounts on the local server won't find the target domain's accounts on the MX servers, since the domain gets resolved locally and it tells it there is no such mail box). In case Froxlor is ported to OpenDKIM, I'd like to suggest of thinking of this possibility from a DKIM perspective, since currently when you turn off "Emaildomain" then of
×
×
  • Create New...