Search results

Ran into this problem today. Your script worked like a charm. I did need to build rewrite_confs after switching PHP versions. But after that the default version changed and the older version was running successfully at the php4_selector. No need to rebuild PHP versions as they where already...

I agree. But why does that executable file exist if it causes conflicts and is actually replaced?

That could be a good reason to stop the process after an update. Thanks for the link. I should update my server monitoring according to this. My question now is if manually starting /usr/local/directadmin/da-popb4smtp messes things up?

Because a restart means downtime. da-popb4smtp is a simple process that should not require a full restart to be functional.

A few days ago one of my servers noticed me about the process da-popb4smtp which had stopped working. I looked into it and found that it was not service but just a process being run by DirectAdmin. I don't know how this process is started or restarted and could not find any documentation about...

No answers on david's question 2,5 years ago? I'm facing the same problem. This is my current Curl version: # curl -V curl 7.29.0 (x86_64-redhat-linux-gnu) libcurl/7.29.0 NSS/3.53.1 zlib/1.2.7 libidn/1.28 libssh2/1.8.0 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3...

Good question. I would also like to know if this will break a server. Or does DA simply stop releasing updates for it. What webalizer concerns, I think this is a handy tool for quickly scanning the some basic statistics. I never used Awstats so I cannot comment on that as an alternative. Can I...

I installed a new server and have set the license I bought to auto-detect the IP address. After installation I can see there is 1 session on the license and it shows a IPv6 address. The server works like it should, no problems there. In the DirectAdmin controlpanel under licensing there is a...

I perfectly understand. My reaction was just because jamgames2 said it "already" had been fixed. It sounded like this bug was just introduced in the last version and the fix was here before anyone noticed it. I didn't report this bug by the way so its a total coincidence that I'm just posting...

"Already" after several months. I found the same problem on a server I installed 5 months ago. Didn't notice it because those clients never used Webalizer.

I took a gamble and installed libgd-dev on a server with few clients. After that Webalizer installed good. Added a tally task to Task.queue and the stats seem to be generating like they should. Problem solved.

I see that there is a libgd-dev package in Debian. But this is a development version. Is there also a non-development version? Like a stable production version? And does Webalizer work with this libgd-dev version?

My webalizer statistics don't update. The DirectAdmin Task Queue Log tells me the following: Which is a little weird since this is a newly installed server. It is running Debian 11 (Bullseye). I installed DirectAdmin on a fresh Debian installation with this command: bash <(curl -fsSL...

Meanwhile all my servers have changed from Apache to Nginx to return the default page. This must have something to do with an update that changes something in the Nginx_apache configuration. Not all of my servers update at the same time so that is why not all of them fail at the same time. I...

No, not using that.

This is the result: # ./build set webserver nginx_apache webserver is already set to nginx_apache

On a few ones. Last night, 3 servers changed from Apache to Nginx.

I understand what you mean. But I still would like to know why a Nginx_apache setup sometimes changes from Nginx first to Apache first or the other way around. It doesn't seem logical.

I assumed that this was a fixed page answer. :) I mean, why would the answer ever change? In a Nginx_apache configuration it is always the same webserver that should answer your request right? Until it doesn't of course, like now.

Why would this be bugs if everything works normally. The only thing that seems to change is the webserver that answers the request.