DirectAdmin 1.46.1 has been released

Hi guys....
so everything seems okay with DA 1.46.2?
I have waited a bit to update:rolleyes:
 
Last edited:
Hi all,

I updated version 1.454 to 1.462 and receive the following error message:

/usr/lib64/libmysqlclient.so.18: no version information available

/lib64/libc.so.6: version `GLIBC_2.14' not found

I use CentOS 6.5, How do I fix this?
 
I've seen this error on two different server and another post on this forum.

Apparently the update to latest version doesnt work pretty well, a re-update can fix this issue.

Try: /usr/local/directadmin/custombuild/build update_da

Regards
 
Last edited:
If I want

try_files $uri $uri/ /index.php?q=$uri&$args;

in

location / {


}

nginx virtualhost I can use custom httpd for that? I know about custom vhost templates but I want this only for single domain (IPB Board need this to work properly)
 
interfasys said:
Could we get more details on CUSTOMX? http://www.directadmin.com/features.php?id=1654

It doesn't seem to work to customise a domain.
I've added some directives to the CUSTOM4 field and nothing seems to have been written to httpd.conf
Click to expand...
Make sure you're not using custom templates.
If you are using custom templates, ensure they have all of the |CUSTOM_| tokens added.

If you want, I've been adding a few more features to it to help clarify what you're using... it will now show you the raw template being used, and if it's custom or not:
http://www.directadmin.com/features.php?id=1666

In the pre-release binaries if you'd like to try it out.

The actual functionality of the CUSTOM4 token is fairly straightforward.
1) Your changes should be saved into
Code: 
/usr/local/directadmin/data/users/username/domains/domain.com.cust_httpd.1
2) Upon any httpd.conf rewrites, the contents of that domain.com.cust_httpd.1 is added into the |CUSTOM4| token, which is just before the last </VirtualHost> entry in all 4 VirtualHosts. Use if-then-else statements to control more fine details as to when you want it used.

John
 
brtkm said:
If I want

try_files $uri $uri/ /index.php?q=$uri&$args;

in

location / {


}

nginx virtualhost I can use custom httpd for that? I know about custom vhost templates but I want this only for single domain (IPB Board need this to work properly)
Click to expand...
It would depend on if you're using the proxy setup or not.

I'm going to assume you're using a stand-alone setup, without the nginx/apache proxy setup (the proxy already has a / location, so it would need a different procedure)
In any case, if you only want that to show up in the http://domain.com and https://domain.com servers, and *not* any subdomains, then it might look like this:
Add to CUSTOM3:
Code: 
|*if !SUB|
location / {
        try_files $uri $uri/ /index.php?q=$uri&$args;
}
|*endif|
and see if that works for you.

If you are running the proxy setup, then it gets more complicated for the location / case.

John
 
I would like to add that with proxy setup Apache rewrites (config or .htaccess) should be enough to do the URL rewriting.
 
is there ANY chance this (or the 1.46) could cause GD issues on websites?
I had working setup, upgraded php 5.5.14 to 5.5.17 and then update directadmin.
since then GD not creating/displaying thumbnails.
today I fully reinstalled the server and directadmin using php 5.5.14 and apache 2.4.9 with NO caching methods.

GD still not creating thumbnails.
php info shows it loaded but its not working, and the only thing I did was update php and directadmin. and I know the sites were working fine 30 minutes prior to update.
I caught the issue about 5 hours after I updated, forgot to check that one item after updating.

the 1.46 series updates is only commonality I cannot rule out myself and of course new install gets 1.46.2.
 
Last edited:
ok heres the problem, system says (after DA and CB installed) that GD is installed and yum install gd also states that.
but there is NO gd.so file on the server.
none.
nowheres.
yum reinstall gd (is same version) and it works now.

I am not sure if this is a DA issue or a CB issue.
something in either DA or CB during last update caused gd.so to disappear.
 
Last edited:
dmacleo said:
ok heres the problem, system says (after DA and CB installed) that GD is installed and yum install gd also states that.
but there is NO gd.so file on the server.
none.
nowheres.
yum reinstall gd (is same version) and it works now.

I am not sure if this is a DA issue or a CB issue.
something in either DA or CB during last update caused gd.so to disappear.
Click to expand...
This has got nothing to do with DA. Have you tried downgrading PHP?
 
yes had tried downgrading.
like I said, tried downgrading php and apache.
did a full server reinstall and still saw it.
tried php and apache downgrade again again and did not solve it.
running yum reinstall fixed it.
145 install with CB 2 did not have the issue.
upgrading to 146 created the issue.
146 fresh install with CB 2 has the issue.
I have no way of seeing if its a DA or a CB issue but it IS one of those 2.
a fresh install of DA with stock CB settings ( was php 5.5.17 and apache 2.4.10 ) shows GD as installed yet no gd.so located on server.
 
Definitly is not depending on DA side since this will not affect PHP in any way.

Probably somehow a bug on PHP installation/upgrade from CB 2, smtalk would maybe have to look into your box or have a better reply.

Sayd that, if was a PHP upgrade issue, the downgrade should solve.. if not.. rarely should be a PHP issue.

Definitly, apache have nothing to do with that at all.

Regards
 
yeah if it actually was php issue the multiple tries at downgrading should have fixed it.
I tried apache also as I wanted to get it to a point where php/apache versions were versions I know for a fact did work.
I would tend to think it was CB issue but the issue appearing after only upgrading to 146 with no known CB updates troubles me. the issue appearing on fresh install being a CB issue makes sense, but the problem happening after upgrading to 146 is odd.
could be pure coincidence but where issue did crop up after upgrading I figured I should mention it.
really only way to test at this point it so do a fresh install again and that would cost me money so I cannot. unless I could install on a vps for a day (I don't own license) to see.
 
That is nothing DA related, because gd.so is a PHP extension, it must have been installed by you. Because CustomBuild compiled PHP with built-in GD support (meaning no gd.so on the system).
 
well multiple gd powered site worked on 145 and didn't work after update to 146
same sites didn't work on fresh install of 146
so I check to see if gd is installed using yum install gd and it is. I have not installed it or anything else myself at this point.
sites still don't work.
run yum reinstall and everything works

there still is no gd.so listed on my setup, even after doing reinstall, that was just something I was looking towards for clues to the issue and to possibly narrow down the issue. as it turned out that wasn't as important as I initially thought.

since it wasn't listed, gd listed as installed, and NOTHING worked I then decided to try yum reinstall which worked. this is the whole point, I had to actually reinstall to make it work.

so tell me how this is due to something I have done as I cannot see how? the fresh install and sites not working is key I think.
I will see if I can upgrade friends server to 146 today and see if his gd sites stop working but that unit due to be taken down this weekend so I may not get a chance.
 
Last edited:
You must log in or register to reply here.
Back
Top