hmm, i just noticed that backups are now running as bzip and not pbzip. i know when i've done recent fresh installs of 1.1.0-rc1.4 it is pbzip... something seems off here. I even did an install --reconfigure, no good changes...
Posts by anarking
-
-
Hey guys, just wanted to see if anyone else has come across this... I upgraded my main 1.0.3 to 1.1.0-rc1.4 the other day, and ever since, my Proftpd will use 100% cpu (single thread) whenever someone tries to connect, and it will timeout while trying to login.
I have disabled IPv6, disabled TLS, made it not load TLS, etc. and it still happens. Have you seen this before, or any ideas of what it could be? Everything was fine and fast before the upgrade. I'm going to start running traces I guess, to see where the CPU usage is going...
Debian 6.0.6, and it shows ProFTPD as 1.3.3a.
-
Ahhh I see, new interface, then must Activate and provide MX servers. It all makes sense now, I believe it works as intended, no issue. Thanks nux.
-
Hey guys, before I make a bug ticket, I just want to see if anyone else can reproduce this...
I just upgraded a 1.0.3 server to 1.1.0-rc1.4 and when I go to set a domain to Mail External, it does not. I see nothing modified in relay, transport, or DNS files, neither working nor system files.
I just checked, and it does not work on my other systems running fresh installs of 1.1.0-rc1.4 either.
I thought this was working as of rc1, am I missing something?
Also, can we no longer make MX records from the Custom DNS records function?
-
this is very nice. having this as a configurable option in the custom section of the Vhost file for domains in i-MSCP would be a very awesome feature. hmm...
-
you need to update the corresponding entries in /etc/imscp/bind/parts as well
-
perhaps look at fcgid and php settings for max processes, etc. to optimize throughput. use "htop" to look at server resource usage and watch the processor, as a P4 is very slow. also, you may want to consider caching/varnish as a setup for the server.
-
thanks, good guide. this and the changing of IP for NAT setups is very helpful for some people.
QuoteWith the next release, you will only have to do
Code:
# cd /var/www/imscp/engine/setup
# perl imscp-setup --reconfigure ipsthat's awesome, nux
-
When running /var/www/imscp/engine/setup/set-engine-permissions
I imagine it has to do with these being handled by the package manager now. May be completely harmless, just thought I should let you know, if no one else has noticed. Fresh install of 1.1.0-rc1.4.
Other than that I really have found 0 errors with rc1.4 so far. I don't particularly like that a domain HAS to have a hosting plan to be created, but oh well Everything is Awesome
-
how do you mean? currently, new domain is added, and a "parking" default index.html page is put there. what are you wishing for? domain parking (with no hosting for the domain)? i have been thinking about a way to enable domain parking...