Search results

Thank you!

Nothing wrong. It's in your list of things which require a DA license. I think my question was very clear. In other words, why should blockcracking stop working without DA license? I'm no scripter so maybe it's something in one of the files, hence the question.

Not there indeed, but I thought you were talking about the /var/log/httpd and /var/log/httpd/domains logs. But are they still generated in the /home/user when DA is not running anymore? If yes, they can be put manually in the logrotate.d section. What about blockcracking?

The apache (webserver) log rotation is done via normal logrotate. The file for that is /etc/logrotate.d/apache so DA is not required for that if I'm correct. Blockcracking is called from within exim.conf. So existing configs should also still work right?

I've seen this with a friend of mine, who due to some error his license got expired. But also messages from DA itself stating services won't stop. You could also send them a mail or contact form, they won't bite. :) Doublecheck the cronjobs that they are present in the OS so the OS will trigger...

You might want to have a look at my guide (click) to setup a seperate DNS record for your hostname. That works with it's own SOA and SPF records.

Lately our customers are getting a lot of spam. Problem is that we can not block it the normal way, as they are coming via Google. We report every instance, but they keep coming, it looks like this: eceived: from server.mycompany.nl by server.mycompany.nl with LMTP id...

This is still going on? I thought since last post was from january this was already fixed. Do you have a legacy license or normal? With normal license you could send in a ticket. Also check your /usr/local/directadmin/data/templates/custom for entries and what they contain. Which version DA...

Thanks but I don't need to know. It should be working correctly when CB is updating MariaDb. I can't help that anyway. So as long as the user makes his backups, he's fine.

AAAAAAAAAAAARGGGGHHHH 🫨🫨🥴🥴 Darn... I trusted you, forgot to read the fine print. :( ... thinking of counter measures.... We can't make any statements about this.🫢 I'm sure they are already monitoring this and things will be taken care of when it gets too far. Which might indeed be now.

Thanks for your insights, but as you could read, it only happens with the mysqldump command, either when custombuild is doing the backup when upgrading MariaDB or when issueing the command manually. I always to CB updates at early night time and we almost never have a high load then. Also when...

FOR THAT MACHINE. Unless you buy a retail license. You did not buy a DA retail license. I'm going to start baking pies quickly, the combi deal with @sysdev suddenly brought in a lot of orders again. :)

Thank you for the tip, but there are 2 thoughts with that idea. His passwords does not start with ! and we have more passwords with a ! or # in them which don't give issues. Second thing is that even if this would work in shell, it still would not work during the custombuild update of MariaDB as...

He didn't say that it was. :ROFLMAO: One never knows. I can understand benefits for some so I hope they will decide in favor of you.

Might be nice, but I think DA won't do that. Too much fuzz with customers paying a yearly license and the for whatever reason they use it shorter and start demanding money back because they didn't use it the full year. No you, but if I see how crazy some people get on what lifetime should be...

Yes that's what I also said. DA is using a different method. But during update the mysqldump command is used and there WF blocks things. NP user can make backups himself then. It's clear to me that this is a WF issue, so I don't worry about it anymore then. Sleep well, thank you!

I don't get out put here: select * from INFORMATION_SCHEMA.PROCESSLIST where db = 'user_wp979'; Not sure what you mean, I don't do anything special, just like always. da build update da build update_versions

During update/install mysql it's using the same as any other license. Custombuild update. I use it via commandline but that makes no difference Normal admin backup or user backup is working normally yes.

I don't know about that one, have legacy license. So don't know where to look.

That also works well until line 226 as above. Beginning: Enter password: -- Connecting to localhost... -- Starting transaction... -- Setting savepoint... -- Retrieving table structure for table wp_actionscheduler_actions... -- Sending SELECT query... -- Retrieving rows... -- Rolling back to...