Okay, sorry to pester list,
but I jumped and fell short on an active mail machine, about 6 hours ago.
I knew doing this on a cyrus-imapd server was insane....
I "Upgraded" from i386 openbsd 4.0 to amd64 openbsd 4.0
So if someone experienced with cyrus-imapd on amd64
can send me some suggestions, can be off list,
I would appreciate because I've getting stumped
and tired and have users waiting.
I have a real fear the dbd and cyrus database stuff may have squirreled
going form i386 to amd64 - please tell me I am wrong...
I promise to do a write up of the fubar for others
who may need to google
in the future...
........
I had deleted all the ports prior, and added same ones
back as amd64 after.
THE database for openldap was toast, since I knew
how to get that up faster, I used my
backup ldiff to reload it... I have a fear that
the berkeley dbd is different for amd64 than i386.....
with that experience......
so...
I got sendmail to work with saslauthd and openldap
to authenticate, and other parts...
So now the authentication with ldap should be working,
I can test it with
testsaslautd
but cyrus-imapd is not working yet.
And the log is not even getting to authentication,
so that is not the issue I think...
from /var/log/imapd.log
Mar 5 08:22:48 mail master[13640]: process started
Mar 5 08:22:48 mail master[1831]: about to exec
/usr/local/libexec/cyrus-imapd/ctl_cyrusdb
Mar 5 08:22:48 mail master[13640]: process 1831 exited, signaled to death
by 11
Mar 5 08:22:48 mail master[13640]: ready for work
Mar 5 08:22:48 mail master[6753]: about to exec
/usr/local/libexec/cyrus-imapd/ctl_cyrusdb
Mar 5 08:23:21 mail master[19218]: about to exec
/usr/local/libexec/cyrus-imapd/pop3d
Mar 5 08:24:13 mail master[15189]: about to exec
/usr/local/libexec/cyrus-imapd/imapd
I see the bad message "signaled to death by 11"
And if I telnet to pop3 or imapd they just don't refuse,
just never finish answering,
Connected to localhost.
Escape character is '^]'
and it just will timeout...
Perhaps I need to repair mailboxes?
geez I am getting fuzzy here... may need to take
a break even though the server is down.
Crazy,,,, I am going through all the configuration
files I can think of, I have an rsync of the i386
setup so I can look at files from yesterday and did remember to put
back the /usr/local/lib/sasl2/Cyrus.conf
I fear I am seeing trees, not the forest..
tia.
