On 2013-07-30 06:18, Michael Wessel wrote:

 OK, here goes: Most of the hoops were my own fault (the major one
being that I had SELinux enabled without realizing it for some time
which resulted in all sorts of strange behavior...)

I'll include in the docs to disable SElinux on CentOS/Redhat. Or it
would be great if you had the chance to figure out some selinux rules
to make piler work with it without disabling it.


 I did a fresh install of CentOS6.4 Minimum install, so what I was
missing is based on that install.

 I used the PDF documentation from the website which I later saw
seems dated. The requirements have changed some compared to the
on-line documentation and there is no reference to the helpful "make
postinstall" in the PDF. So updating the PDF would be a good thing.

yes, it's in my head for a long time. I'll remove it until it's updated.

 I installed epel and rpmforge repos and then used the following yum
to install all the dependencies I was missing (I pieced this together
through several compile attempts):

 yum install man vim telnet net-snmp cronie sysstat rsync ntp wget
make gcc db4-devel patch zip unzip mysql mysql-server mysql-devel
gcc-devel php php-xml php-mysql libzip libzip-devel tre tre-devel
tcp_wrappers tcp_wrappers-libs tcp_wrappers-devel catdoc unrtf poppler
poppler-devel

thanks, I'll add this to the install docs.

 I did an rpm install of sphinx and had to edit
/usr/local/src/piler-0.1.23/init.d/rc.searchd and change
 ## Change the line (line 10):
 su piler -c '/usr/local/bin/searchd' 
 ##to this
 su piler -c '/usr/bin/searchd' 

perhaps it's better to specify on "su piler -c searchd" only, and add
PATH=/usr/bin:/usr/local/bin to the beginning of the script.

 After that I had 2 other gotchas. One was that I had to create
/etc/ld.so.conf.d/piler.conf and add to it: /usr/local/lib
 Then run ldconfig

hmm, isn't /usr/local/lib in the default path?


 Finally in /usr/local/etc/piler.conf I had to set the database host
to 127.0.0.1 (as opposed to localhost). Using localhost piler was not
able to connect to the database. Haven't looked into that yet to find

I think because the default path to socket (mysqlsocket) is /tmp/mysql.sock.
Try fixing it, and it will work. Perhaps it' enough to set it to empty
string and it will use the mysql library default, ie.

mysqlsocket=

out why. Probably a permission problem since localhost will use a
socket and 127.0.0.1 TCP/IP.

 At that point everything started working.

great!


 Thanks very much for this, I'll play around with both and see what
will work out best once I have a substantial amount of mail in the
archive (which won't take very long).

 And a minor issue - the health monitor permanently shows a red bar
 and no text for the CPU usage. The cron job is set up and seem

   %guest      %idle
 09:09:09 PM    all        0.23    0.00      0.10     0.58         
0.00    0.00        0.00        0.00           99.09

fix the cron entry to extract the last value, so change $11 to eg. $12
(not sure, the lines are wrapped in my mailer)

 And one additional minor thing, the SMTP Status shows "piler: Error"
even though it's running. I do have it listen on a port other than 25,
is that why?

set the correct port in config-site.php:

$config['PILER_PORT'] = 1234;

Janos


Reply via email to