PDA

View Full Version : clean FreeBSD 5.3 work with DA?


SeFlow
11-30-2004, 02:58 PM
hi,
i read some posts about freebsd 5.3 and da. i need to setup 3 new servers with freebsd and DA, anyone know if i can install DA normally (as for 5.2) with freebsd 5.3?

i read guido for upgading to 5.2.1 to 5.3, but if i have clean installation i must touch something, or i just write /setup.sh ?

Regards, Matteo

Chrysalis
11-30-2004, 08:18 PM
the FreeBSD 5.1 DA should work fine, you may run into issues if your named is chrooted otherwise you should be fine.

mattbates
12-06-2004, 05:35 PM
I'm in the same position. I need to install two DA servers next week and I'm intending to use FreeBSD 5.3.

Would I be advised to take the safe supported option of 5.1 or use the FreeBSD latest release with DA?

Thanks,
Matt B

blueice
12-08-2004, 01:49 PM
any info from official directadmin support team?
in how many time directadmin official support 5.3?

Chrysalis
12-08-2004, 05:59 PM
FreeBSD 5.2.1 is fully compatible and is a better option then 5.1, if you are nervous about trying 5.3 then use 5.2.1 for now.

blueice
12-09-2004, 11:27 AM
Originally posted by Chrysalis
FreeBSD 5.2.1 is fully compatible and is a better option then 5.1, if you are nervous about trying 5.3 then use 5.2.1 for now.
5.2.1 stop updates in 20 days :(
So the only real good option for freebsd and dual xeons is the 5.3.
I thing it is good time for a official info about the status of 5.3

bjseiler
12-09-2004, 02:13 PM
I have a shiny new dell 1750 sitting here waiting for an operating system....... Should I go 4.10 or 5.3 -- what do you guys think?

Chrysalis
12-09-2004, 07:32 PM
blueice yes you are right then this is a big issue that needs addressing by directadmin, 5.3 does work with directadmin but only with changes made it wont out of the box. So I guess unless you are really fluent with FreeBSD then go with 4.10.

mattbates
12-09-2004, 07:52 PM
Thanks for your replies.

I'd really like to use FreeBSD 5.3 if I can.

What modifications are necessary?

Matthew

Chrysalis
12-09-2004, 07:57 PM
read here

http://www.directadmin.com/forum/showthread.php?s=&threadid=5735

motobrandt
12-10-2004, 10:35 AM
Maybe a good way to get this going is for a few of us to get a FreeBSD 5.3 box up and running and then have DA do their free install on it.

This might clue them in that they could/should make a 5.3 release with only those minor mods that are posted in that other thread.

I'm in for one box.:D

anyone else?

bjseiler
12-10-2004, 10:36 AM
I am installing 5.3 today and will take it over to the data center and install DA tomorrow. Fingers crossed.

mattbates
12-10-2004, 10:58 AM
Keep us updated, if you can.

I'm installing Monday.

Matt

mattbates
12-10-2004, 11:00 AM
Yep, me too. I've got a spare box that I'd be willing to put forward.

Originally posted by motobrandt
Maybe a good way to get this going is for a few of us to get a FreeBSD 5.3 box up and running and then have DA do their free install on it.

This might clue them in that they could/should make a 5.3 release with only those minor mods that are posted in that other thread.

I'm in for one box.:D

anyone else?

Chrysalis
12-10-2004, 06:52 PM
I have sent an email to john with links to both threads.

DirectAdmin Support
12-11-2004, 02:13 AM
Hello,

Thanks for the email. We've just purchased a few more build systems for the office and we'll do an official 5.3 compile/installer. (Other one is for fedora 3).

The current release of DA for freebsd 5.x *is* setup to fit on a 5.3 system, but the binary itself is still compiled for a 5.1 machine, hence we're going to start fresh to iron out the kinks.

I know a few people have got it to work with the current release, so it is possible.

John

wdv
12-11-2004, 07:23 AM
John, do you have any ETA on the new FreeBSD 5.3 packages? I want to upgrade my FreeBSD 5.2.1 boxes to 5.3 as soon as possible, however it'd be nice if we could use binaries compiled for 5.3 (especially of DA itself) :)

bjseiler
12-11-2004, 09:46 AM
Here are the problems so far.

MySQL is not running after installation. It looks like it did not get installed at all as there is no conf file or executeable. I can't find any error logs telling me why it failed though......

It also looks like I will have ftp and dns issues based on these logs.

Dec 11 10:22:50 www9 named[2800]: starting BIND 9.3.0
Dec 11 10:22:50 www9 named[2800]: none:0: open: /etc/namedb/rndc.key: file not found
Dec 11 10:22:50 www9 named[2800]: couldn't add command channel 127.0.0.1#953: file not found
Dec 11 10:22:50 www9 named[2800]: none:0: open: /etc/namedb/rndc.key: file not found
Dec 11 10:22:50 www9 named[2800]: couldn't add command channel ::1#953: file not found
Dec 11 10:22:50 www9 named[2800]: zone 0.0.127.IN-ADDR.ARPA/IN: loading master file master/localhost.rev: file not found
Dec 11 10:22:50 www9 named[2800]: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA/IN: loading master file master/localhost-v6.rev: file not found
Dec 11 10:22:50 www9 named[2800]: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT/IN: loading master file master/localhost-v6.rev: file not found
Dec 11 10:23:00 www9 proftpd[2811]: www9.leadasp.com - ProFTPD 1.2.9 (stable) (built Mon Jan 19 16:05:43 MST 2004) standalone mode STARTUP
Dec 11 10:23:20 www9 proftpd[2836]: www9.leadasp.com - Failed binding to 0.0.0.0, port 21: Address already in use
Dec 11 10:23:20 www9 proftpd[2836]: www9.leadasp.com - Check the ServerType directive to ensure you are configured correctly.

bjseiler
12-12-2004, 06:19 AM
I am at the give up stage with installing on 5.3. Mysql did not get installed at all and unless I am blind, there are no logs showing me why. I guess I will wait until DA figures out a 5.3 version because I know I can install mysql through ports and make it work, but that would just make me nervous later on when upgrading.

mattbates
12-12-2004, 09:54 AM
Are you going to revert to 5.2.1? I've noticed that is supported.

I presume it is possible to upgrade to 5.3 later, when it's officially supported?

bjseiler
12-12-2004, 11:08 AM
No, I am not going to revert to 5.2.1. I am just going to keep the fingers crossed that DA has enough time to figure it out this week.

jmstacey
12-12-2004, 04:02 PM
I suggest installing either 5.1 or 5.21 not 4.10 because there is no active development on it anymore to my knowledge. Only bug/security fixes. And a reinstall is required to get from 4.10 to 5.x so you might as well put an older version of the 5.x line on and then upgrade later on since thats easy enough with cvsup.

werwin01
12-12-2004, 04:53 PM
Does 5.3 work with DA v1.232?

dan35
12-12-2004, 09:08 PM
Originally posted by motobrandt
Maybe a good way to get this going is for a few of us to get a FreeBSD 5.3 box up and running and then have DA do their free install on it.

This might clue them in that they could/should make a 5.3 release with only those minor mods that are posted in that other thread.

I'm in for one box.:D

anyone else?

I"m in :)

werwin01
12-12-2004, 10:57 PM
I'll setup a box this week with a fresh install of 5.3.
I'm in

Chrysalis
12-13-2004, 12:57 AM
jmstacey actually 4.10 is a better bet then both 5.1 and 5.2.1, the problem is 5.2.1 is EOL this month and I think 5.1 is already EOL. This means they wont be security patched and directadmin wont install on them since the directadmin install script uses pkg_add -r (once EOL this stops working because the packages for that release are removed from the ftp site) and directadmin fails.

RELENG_4_8 4.8-RELEASE Extended April 3, 2003 March 31, 2005
RELENG_5_2 5.2.1-RELEASE Early adopter February 25, 2004 December 31, 2004
RELENG_4_10 4.10-RELEASE Extended May 27, 2004 May 31, 2006
RELENG_5 n/a n/a n/a October 31, 2006
RELENG_5_3 5.3-RELEASE Extended November 6, 2004 October 31, 2006

there is the current releases and EOL dates.

matthewventura
12-13-2004, 05:04 PM
Im not very experienced with freebsd and da, but why do you need updates to freebsd if your os/da/box allready works (besides security updates)?

jmstacey
12-13-2004, 08:13 PM
I'm just thinking of a longer run. If you install 4.10, thats all good and nice, but as far as I know there is no upgrade path to 5.3 from 4.x. So in another month or so when DA fully supports 5.3 (or 4.10 EOL comes around) you will have to do another fresh install whereas if you install 5.2.1 now and have DA working they will most likely have most of the bugs fixed so you can upgrade to 5.3 easily with cvsup saving some time and hassle. But thats just my opinion :)

Chrysalis
12-13-2004, 08:27 PM
well 4.10 has over half a year to go yet and there is still 4.11 to come so the EOL is a long way off, 5.3 also has a long life but isnt yet fully compatible with Directadmin, both 5.1 and 5.2.1 will be EOL come end of this month and that means no security patches and no remote package fetching.

matthewventura
12-13-2004, 08:57 PM
since I'm new to this, what is the downside to having 4.10 come to EOL? I know a lot of servers that run 4.4 still.

Chrysalis
12-14-2004, 03:30 AM
did you read my post before you replied?

"will be EOL come end of this month and that means no security patches and no remote package fetching."

mainly meaning insecure kernel and base utils, and the inability to use pkg_add -r. Incidently if pkg_add -r fails then directadmin installer fails as it relies on this.

matthewventura
12-14-2004, 10:20 AM
viaverio.com still uses 4.7 on it's virtual servers...

4.7-RELEASE-p27 FreeBSD 4.7-RELEASE-p27 #33: Mon Jun 14 16:36:44 MDT 2004

---

So now my question is, does DA interact seamlessly with new versions of FreeBSD?

I've heard there are issues?

matthewventura
12-14-2004, 10:22 AM
btw, I am looking for a system where you don't have to apply new patches all the time, so older might be better for me.

---

after installed does DA require any updates?

or can I just setup FREEBSD and DA to my satisfaction and just let it run?

HH-Steve
12-15-2004, 01:58 AM
4.10 EOL is estimated at May 31, 2006 according to the FreeBSD team:

http://www.freebsd.org/security/

If your not using multiple cpu's 4.x works great and by the time it is EOL your probably due for a server upgrade anyway so get a fresh install of the latest version of FreeBSD done then.

Anyway, thats what I would do.

HH-Steve
12-15-2004, 02:02 AM
@matthewventura

You will always have to update software on your server no matter which version of FreeBSD you choose. For example:

FreeBSD
Directadmin
Exim
MySQL
ProFTPD
phpmyadmin
squirrelmail
etc...

Thats part of being a server admin.

Chrysalis
12-15-2004, 02:07 AM
matthewventura then I wouldn't want to use viaverio.com, as HH-Steve said admins should pro actively be updating software as security holes get found etc. This also applies for the kernel and of course FreeBSD 4.7 security holes no longer get patched.

matthewventura
12-15-2004, 04:23 PM
viaverio is huge, maybe they do their own updates?

Dillard
12-18-2004, 04:12 PM
Hello all!

I'm new to DirectAdmin and just finished my first installation (on an fresh FreeBSD 5.3).

I'll give my remarks for this:

1) On my box perl was installed under /usr/local/bin/perl. Since DA is looking at /usr/bin/perl this didn't work. So I created a symlink (" ln -s /usr/local/bin/perl /usr/bin/perl") to solve this

2) Since perl was not "available" during the initial installation I had to recompile apache. ("cd /usr/local/directadmin/scripts; ./customapache.sh")

3) Somehow MySQL was installed but I never entered a password, nor did it respond to the already existing passwords. So i did ("cd /usr/local/directadmin/scripts; ./mysql.sh rootpass da_user da_userpass") to solve this. Since there were no databases it's harmless.

4) Don't forget to add your setup user (the one you created during FreeBND install) to /etc/ssh/sshd_config BEFORE you reboot otherwise you will be looked out.

That's all i came across for the moment, everything seems to work fine now. I will hand over the server to my client and if something comes up I will report back on this forum.

Chrysalis
12-19-2004, 03:11 AM
when Installing perl on FreeBSD you should use the ported version and after installation run use.perl ports, this will create the symlink for you. I have also came across the same mysql issue's even on FreeBSD 4.x, I am wondering if John starts needing to spend serious time on the FreeBSD stuff because things are looking shaky at the moment, the FreeBSD 4.8 version should be renamed FreeBSD 4.10 or 4.x as it causes people to think they have to use 4.8 which is outdated, and likewise the FreeBSD 5.1 should be FreeBSD 5.3 version or 5.x and the binaries need to be recompiled to stop the zombie processes that have been discovered, and this forum needs to be categorised since FreeBSD 5 is now a STABLE release.

bjseiler
12-21-2004, 07:42 AM
DA Team -- It would really help me (and I suppose others) a ton if you could let me know how the 5.3 progress is coming. I've got a machine just kind of sitting now waiting for the word on 5.3 and 4 more machines coming today that I need to set up and buy licenses for.

If you think it will be another month, no problem, I will just load 4.10 on them. I just want to know what we're looking at here for a timeframe.

Chrysalis
12-21-2004, 02:10 PM
Well I think there are just 2 things they need to do.

1 - Recompile the Direct Admin binaries on a 5.3 machine to stop the zombie processes.

2 - Change the install procedure for mysql and to support chrooted bind.

I guess they are just too busy right now, I see them rolling out debian and fedora core 3 support.

matthewventura
12-23-2004, 11:25 PM
Im getting conflicting info from this post.

Conflicting info:

(1) 4.10 is eol.
(2) 4.10 is eol in may 2006

(3) there are no security patches for 4.10
(4) 4.10 will have support until well into the year 2006

~
DA support says that 4.10 would be their choice.

~
From the freebsd.com website:

http://www.freebsd.org/releases/5.3R/migration-guide.html

"The next release from CURRENT will likely be 6.0-RELEASE, created from CVS HEAD. There is no firm date for 6.0, as of the 5.3 release date, although it is expected sometime in 2006.

A limited amount of development will continue on the 4-STABLE development branch, with at least one more release (4.11) planned at some point after 5.3-RELEASE. For especially conservative users, it may be reasonable to continue using the 4.X releases for a time. The Security Officer Team <security-officer@FreeBSD.org> will continue to support releases made from the 4-STABLE branch in accordance with their published policies, which can be found on the Security page on the FreeBSD web site."

This tells me that I won't have to upgrade for a long time.

Reading the above, can anyone give a good reason not to stay with 4.x?

Chrysalis
12-24-2004, 02:57 AM
matthewventura I dont know who said 4.10 is EOL but it wasn't me.

Never use CURRENT for production server's it is the equivelent to cvs, cutting edge code.

There are 2 STABLE branches at this time 4.x and 5.x.

4.10 is NOT EOL and is good until may 2006 and there will be a 4.11 which means at that time you can switch to 4.11 and I expect 4.11 to be a extended release so it should take you to January 2007 at the earliest.

5.1 is EOL, 5.2.1 will be EOL by the end of this month, 5.3 is NOT EOL and is the first 5.x STABLE release.

As of right now there is no 6.0 Release it is just a CURRENT branch in development.

motobrandt
12-24-2004, 03:57 PM
Originally posted by Chrysalis
Well I think there are just 2 things they need to do.

1 - Recompile the Direct Admin binaries on a 5.3 machine to stop the zombie processes.

2 - Change the install procedure for mysql and to support chrooted bind.

I guess they are just too busy right now, I see them rolling out debian and fedora core 3 support.

Aren't there also some issues with named or DNS in general?

matthewventura
12-24-2004, 09:18 PM
so the options seem to be

4.10

and

5.3

since they are the only "stable" versions...

however didnt freebsd stay they were not going to use the term stable anymore? and just use the word current?

jmstacey
12-24-2004, 11:47 PM
Originally posted by matthewventura
however didnt freebsd stay they were not going to use the term stable anymore? and just use the word current?

If they did, I never get that memo. ;)

bjseiler
12-29-2004, 10:07 AM
DA...... update on a DirectAdmin FreeBSD 5.3 build??? Please, for Christmas :-)

matthewventura
12-29-2004, 12:36 PM
Originally posted by jmstacey
If they did, I never get that memo. ;)

yeah, my mistake, I misread...

bjseiler
01-03-2005, 10:20 AM
DA...... update on a DirectAdmin FreeBSD 5.3 build??? Please, for New Year's :-)

If it is going to be March or June, please, just say something. I don't mind using 4.10 (or 4.11 soon), but I would like to know when a stable 5.3 might be ready. Just say something please.

werwin01
01-03-2005, 12:15 PM
Originally posted by bjseiler
If it is going to be March or June, please, just say something. I don't mind using 4.10 (or 4.11 soon), but I would like to know when a stable 5.3 might be ready. Just say something please.

Email support and link them to this thread if you want a response

DirectAdmin Support
01-03-2005, 03:32 PM
Hello,

As everyone is getting back from holidays, they're sending a huge surge of support issues.. Currently working through them.

I'll start downloading the 5.3 isos now. Still not positive if it's needed ... the current binaries "work", but just with the zombie issue. If the new build system doesn't change anything, then we'll continue to use the old binaries (I hope it does fix the zombie issue)

If you'd like to use 5.3, but are just holding back because we havn't declared DA as "stable" (or current ;)) for it yet, you can install 5.3, install DA on it and use it until we get the new binary compiled. I'm not sure any of the current issues are "fatal", but just ask someone who's using it right now to see how it affects the operation of the system.

We are working on several OS's right now, so hopefully I can get it installed/compiled in a week or 2. (email me if I'm not done by then ;))

John

Chrysalis
01-04-2005, 08:27 AM
John I have noticed when using the DA dns interface on a 5.3 box the changes arent applied, I guess this might be related to the HUP issue with named on 5.3 boxes, a workaround is to either issue /etc/rc.d/named restart or rndc reload.

For now I am probably going to cron named to restart every hour so if any changes are made they will be applied at most 1 hour after the change.

blueice
01-23-2005, 01:04 PM
Originally posted by DirectAdmin Support
Hello,

As everyone is getting back from holidays, they're sending a huge surge of support issues.. Currently working through them.

I'll start downloading the 5.3 isos now. Still not positive if it's needed ... the current binaries "work", but just with the zombie issue. If the new build system doesn't change anything, then we'll continue to use the old binaries (I hope it does fix the zombie issue)

If you'd like to use 5.3, but are just holding back because we havn't declared DA as "stable" (or current ;)) for it yet, you can install 5.3, install DA on it and use it until we get the new binary compiled. I'm not sure any of the current issues are "fatal", but just ask someone who's using it right now to see how it affects the operation of the system.

We are working on several OS's right now, so hopefully I can get it installed/compiled in a week or 2. (email me if I'm not done by then ;))

John
Hi,
it is gone 20 days after your post.
Can you please inform us about the status for freebsd 5.3? This delay is because have problems?

interfasys
01-25-2005, 04:15 PM
Files have started to appear on their repository, but there is no FreeBSD5.3 bundle yet.

Chrysalis
01-26-2005, 08:11 PM
yep noticed but gonna send john an email he has perl56.tbz there instead of perl.tbz, and 5.3 uses perl 5.8.5 as default so it could mess things up because it would effectively downgrade perl.

Yikes2000
03-05-2005, 12:44 AM
Any update on this issue of installing DA on a clean FreeBSD 5.3?

existenz
03-14-2005, 07:21 PM
Just did it a few times. Had a few issues with BIND, found a few little things like Zend and SpamAssassin. Everything seems to work, I did send John a bunch of little items that hopefully he may incorporate into the installer that would fix these issues.