• Announcements

    • d00p

      Major server crash   03/27/17

      Due to a major server crash, most of our services are currently not available. Sorry for any inconvenience. Sadly, the forums database could not be restored, so we are back to a database from mid-2016  Sorry


  • Content count

  • Joined

  • Last visited

  • Days Won


Slydder last won the day on January 26 2012

Slydder had the most liked content!

Community Reputation

1 Neutral

About Slydder

  • Rank
    Advanced Froxie
  • Birthday 12/27/68

Contact Methods

  • Website URL

Profile Information

  • Gender
    Not Telling
  • Location
    Schwerin, Germany
  1. Chrisv, If you want, we can speak on the matter. I have been running a 6 tier HA LB cluster stack hosting magento installs for about 3 years now with froxlor. There are a few things I have found out over the years regarding this issue and they may come of use to you. Chuck
  2. Hey, RFC 6781 "suggests" a minimum of 5 - 10 minute TTL for standard zone entries. Dynamic DNS was NOT conceptualized when that RFC was released. However, 1 second is a bit much. better would be 1 - 5 minutes. Irrespective of what the RFC states the TTL that is set in his script and the cronjob executing is in no way related other than the fact that the less frequent the cron run the longer the wait for the update. Nothing about the stock Froxlor DNS service is HA. It is an exercise left up to the implementing admin to actually install his/her slave servers and setup the transfers. If they have done this then all is good. if not then they have much larger problems that has nothing at all to do with this script. The IPv6 problem is a problem though. Chuck
  3. Hey all, I finally got a bit of time to get some more work done on the Stack/Cluster plugin I have been working on. You can see some shots here. https://www.itadmins.net/2016/06/13/745/#more-745
  4. correct (3 frox installs here in production with local mysql servers). however, this database CAN be on a remote server or cluster (such as by 12 of the frox servers we have in production atm).
  5. actually webserver, mysql-client and php are correctly required dependancies (otherwise froxlor is completely useless on the server) and smtp is pretty much a requirement of the server whether frox is installed or not. courier/dove/whatnot is a recommendation and not a dep. awstats/webalizer could be argued but for this sake let's just say they are viable deps. mysql-server is the ONLY dep that is NOT 100% needed locally on the server. but like I said. other than that bit, the package is great. keep up the good work.
  6. actually I do like it very much except for the fact that per default you are forced to install a mysql server. mysql server shouldn't be a "local" requirement and there for not a dependancy. The documentation could simply be changed from apt-get install froxlor to apt-get install froxlor mysql-server has the same effect and makes the package usable for everyone. but hey. your project and it's just an idea. take it or leave it. I can build my own packages to keep from having to use a tarball in production systems.
  7. basically because the situation is the same now as for 3 years.
  8. The major problem I have with the debian package is the mysql dependency. I run a galara cluster and do NOT want a local server installed. up till now I build my own frox packages after modifying the rules to get rid of the mysql server dependancy.
  9. Actually I am not a fan of an automated repair and optimization of mysql. As I have posted on my wiki (http://wiki.itadmins.net/doku.php?id=mysql:repair_and_optimization) it is best to do this per hand and only after you have stopped all services that access the server. Which means if you did this automatically you have to stop all services (automatically) do the repair/optimize and then start the services. Depending on what you have running against your DB this could take a while (depending on load and currently running queries).
  10. you're not really a sysadmin are you? not trying to rip on you. if not find someone that knows what they are doing a have them check the system. also which version of frox are you running on that box?
  11. what services do you have running? pull a copy of everything in /var/log to another system for ananlysis. do you know when this started happening?
  12. ein direkte integration. kein grund BackupPc neu zu erfinden.
  13. ich mag froxlor wirklich. aber das backup system kann ich nicht empfehlen. ich nutze nur BackupPc f?r alle mein servers und es gehts einwandfrei. ich hab bereits angefangen ein BackupPc module f?r Frox zu programmieren und hoffe das es bald fertig ist.
  14. diese fehler kann man oft wegen ein falsch eingestellt fcgi socket (rechte checkin) oder pfad ist falsch.
  15. rufst du denn script direkt auf? so: # /var/www/froxlor/scripts/jobs/cron_backup.php # PHP Fatal error: Call to undefined function openRootDB() in /var/www/froxlor/scripts/jobs/cron_backup.php on line 22