Install thinks Fbsd 5.3 is Redhat?

isnoop

Verified User
Joined
Jan 12, 2006
Messages
6
The install starts off well enough until it starts talking about up2date, which I believe is only for RedHat. Here's the output:

Code:
DirectAdmin will now be install on: FreeBSD 5.3
beginning pre-checks, please wait...
adding gd ...
Fetching [url]http://files.directadmin.com/services/packages-5.3-release/Latest/gd.tbz...[/url] Done.
pkg_add: package bsdpan-Compress-Zlib-1.41 has no origin recorded
pkg_add: package bsdpan-DB_File-1.811 has no origin recorded
pkg_add: package bsdpan-Time-HiRes-1.66 has no origin recorded
pkg_add: package bsdpan-libwww-perl-5.805 has no origin recorded
pkg_add: package bsdpan-mod_perl-1.29 has no origin recorded
pkg_add: package 'gd-2.0.25,1' or its older version already installed
--01:57:32--  [url]https://www.directadmin.com/cgi-bin/daupdate?uid=2298&lid=11741[/url]
           => `/usr/local/directadmin/update.tar.gz'
Resolving [url]www.directadmin.com...[/url] 66.51.122.131
Connecting to [url]www.directadmin.com[/url]|66.51.122.131|:443... connected.
WARNING: Certificate verification error for [url]www.directadmin.com:[/url] unable to get local issuer certificate
HTTP request sent, awaiting response... 200 OK
Length: 4,548,861 (4.3M) [application/x-gzip]

100%[========================================================================================>] 4,548,861   1007.71K/s    ETA 00:00

01:57:37 (938.77 KB/s) - `/usr/local/directadmin/update.tar.gz' saved [4548861/4548861]

Cannot find /etc/sysconfig/rhn/up2date... up2date may break things.
*** Cannot find the /etc/shadow file used for passwords ***
*** bison is required for compiling, please install bison (up2date -u bison)***
*** cannot the find webalizer binary, please install webalizer (up2date -u webalizer)***
Installation didn't pass, halting install.
Anyone have any advice on this?
 
This looks like a first, lucky you :(

Since this is happening during the install, I would suggest contacting [email protected]

I no longer have FreeBSD on any servers, however everything looks right up until that point.

While your waiting, you could always run through the shell script and see why it's trying up2date, but that's just me. I have quite a bit of spare time on my hands. :p
 
Last edited:
Well, I was just about to troubleshoot, but it looks like they fixed it! The install script is running right now.
 
Back
Top