ZCS 6.0.1 ported to FreeBSD7

[ausfeldj]

well I am familiar with i386 vs amd64. I am trying to get this running on a total old - a$$ piece of $hit. 6.4 is the only freebsd I can actually get to run on my hardware. So I am working with what I have.

I am only familiar with the 601 main download. (~380 mb). Then the only patch that works with it is 601. The wiki clearly states there is more patches 605 etc but only one download 601. So I have only downloaded the 601 main fileset and have not checked to see if there are more options. If there are matching files sets with the patches then I understand why you are trying your best to not be rude but the wiki is not clear. Please help get this running.

I do not have any useful debug output now. The last thing I saw was gmake:***[/usr/home/public/p4/GNR-601/ZimbraBuild/corebuild/opt/zimbra/cyrus-sasl-2.1 .23.3z] Error 1.

But I was away during the build and that is all that is left from the screen which is of any use. I defn installed cyrus-sasl and it seemed to work ok but I do not know if I got a "SUCCESS" from the initial build screen.

[ausfeldj]

I also do not have a zcs-6.0* anywhere easy to find.

[solko]

Originally Posted by ausfeldj

well I am familiar with i386 vs amd64. I am trying to get this running on a total old - a$$ piece of $hit. 6.4 is the only freebsd I can actually get to run on my hardware. So I am working with what I have.

I am only familiar with the 601 main download. (~380 mb). Then the only patch that works with it is 601. The wiki clearly states there is more patches 605 etc but only one download 601. So I have only downloaded the 601 main fileset and have not checked to see if there are more options. If there are matching files sets with the patches then I understand why you are trying your best to not be rude but the wiki is not clear. Please help get this running.

I do not have any useful debug output now. The last thing I saw was gmake:***[/usr/home/public/p4/GNR-601/ZimbraBuild/corebuild/opt/zimbra/cyrus-sasl-2.1 .23.3z] Error 1.

But I was away during the build and that is all that is left from the screen which is of any use. I defn installed cyrus-sasl and it seemed to work ok but I do not know if I got a "SUCCESS" from the initial build screen.

ausfeldj,
the wiki is quite very clear to state this in bold:
Please, always check zimbra FreeBSD thread for the latest news!
which covers pretty much everything, hehe. but yes, i failed to look at the wiki from the user view and pretty much expected everything to be self-explanatory. mea culpa, i have updated the wiki to reflect current situation concerning new versions.
furthermore, there was/is always a list of available packages related to a zimbra version - rest is source only.
furthermore2, i have uploaded the 605 source (check wiki) - there was always an option to download it via perforce (check wiki).

as for the building itself. it's really kinda no go to use 605 patch with 601 source.. i hoped people would figure that out by themselves but then i always expect people to at least know zimbra a little prior to coming to this thread.

please, try these steps:
0) check zimbra.imladris.sk download area for all the available files,
1) follow the wiki for i386 from 'Getting the source from zimbra.imladris.sk' (install build dependencies by yourself).

the build itself logs to a file, check that one out. there may be multiple issues with 6.x and i am really not going to cover this topic. 6.x is way too old - it should work flawlessly but there is always a 'but', isn't it?

i will try to clean the wiki up, possibly adding step by step instructions for 8.x when 606 is out.

i am always available on icq/skype for interactive help.

[solko]

i have updated the 605 patch to account for memcached freebsd 8 i386 linking issue (after reading Nullfork's wiki update - many thanks).

since i don't use i386 myself i had no idea and noone told me .

[fantom_smert]

Greetings I live in Russia!
Has decided to establish zimbra on freebsd!
At a configuration the error takes off.
In what a problem???

Initializing ldap...failed. (512)

ERROR

Configuration failed

[phoenix]

Originally Posted by fantom_smert

In what a problem???

Initializing ldap...failed. (512)

ERROR

Configuration failed

That's usually a problem with your /etc/hosts file or your DNS isn't correct. Check the Quick Start Installation Guide and if you're behind a NAT router (or firewall) you will need a Split DNS set-up - further details in the forums if you do a search, this subject has been covered many times.

[fantom_smert]

But,
grandkavkaz# cat /etc/hosts
::1 localhost localhost.grandkavkaz.net
127.0.0.1 localhost localhost.grandkavkaz.net
192.168.1.254 grandkavkaz.net

-irsD or -c command or -O shopt_option (invocation only)
-abefhkmnptuvxBCHP or -o option
MX: 192.168.1.254.grandkavkaz.net (192.168.1.254)

Interface: 192.168.1.254
Interface: 127.0.0.1
192.168.1.254
done.
Checking for port conflicts


At me lifted the DNS-Server

[phoenix]

Originally Posted by fantom_smert

But,
grandkavkaz# cat /etc/hosts
::1 localhost localhost.grandkavkaz.net
127.0.0.1 localhost localhost.grandkavkaz.net
192.168.1.254 grandkavkaz.net

That format is incorrect, check the documentation or forums for the correct format.

Originally Posted by fantom_smert

-irsD or -c command or -O shopt_option (invocation only)
-abefhkmnptuvxBCHP or -o option
MX: 192.168.1.254.grandkavkaz.net (192.168.1.254)

Interface: 192.168.1.254
Interface: 127.0.0.1
192.168.1.254
done.
Checking for port conflicts

At me lifted the DNS-Server

Run the following commands on the Zimbra server and post the output:

cat /etc/resolv.conf
dig yourdomain.com mx
dig yourdomain.com any
host `hostname` <- use that exact command with backticks not single quotes

You can also search the forums for details of the expected output of these commands.

[fantom_smert]

grandkavkaz# cat /etc/resolv.conf
nameserver 127.0.0.1
domain grandkavkaz.net

grandkavkaz# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.1.254 mail.grandkavkaz.net mail

grandkavkaz# dig grandkavkaz.net mx

; <<>> DiG 9.4.3-P2 <<>> grandkavkaz.net mx
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60387
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;grandkavkaz.net. IN MX

;; ANSWER SECTION:
grandkavkaz.net. 38400 IN MX 10 mail.grandkavkaz.net.

;; AUTHORITY SECTION:
grandkavkaz.net. 38400 IN NS 127.0.0.1.grandkavkaz.net.

;; ADDITIONAL SECTION:
mail.grandkavkaz.net. 38400 IN A 192.168.1.254

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Apr 6 11:32:19 2010
;; MSG SIZE rcvd: 94

grandkavkaz# dig grandkavkaz.net any

; <<>> DiG 9.4.3-P2 <<>> grandkavkaz.net any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9251
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; QUESTION SECTION:
;grandkavkaz.net. IN ANY

;; ANSWER SECTION:
grandkavkaz.net. 38400 IN MX 10 mail.grandkavkaz.net.
grandkavkaz.net. 38400 IN SOA grandkavkaz.net. admin.grandkavkaz.net. 10124 43200 3600 3600000 2592000
grandkavkaz.net. 38400 IN NS 127.0.0.1.grandkavkaz.net.
grandkavkaz.net. 38400 IN A 192.168.1.254

;; ADDITIONAL SECTION:
mail.grandkavkaz.net. 38400 IN A 192.168.1.254

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Apr 6 11:33:07 2010
;; MSG SIZE rcvd: 152

grandkavkaz# host `hostname`
mail.grandkavkaz.net has address 192.168.1.254

All the same the error stands out.

Setting local config values...done.
Setting up CA...done.
Deploying CA to /opt/zimbra/conf/ca ...done.
Creating SSL certificate...done.
Installing mailboxd SSL certificates...done.
Initializing ldap...failed. (512)

ERROR
Configuration failed

Please address the error and re-run /opt/zimbra/libexec/zmsetup.pl to
complete the configuration.

Errors have been logged to /tmp/zmsetup.04062010-110122.log

What do I do not so?

[HidX]

Originally Posted by fantom_smert

What do I do not so?

Хм... вроде всё верно. Проверь /etc/hostname и записи в DNS ещё раз.

Initializing ldap...failed - Говорит о том что есть ошибки в сетевой конфигурации сервера.