centos 6.3 piler not starting

Issue #21 resolved
Former user created an issue

When I follow your installation instructions.....

sh init.d/rc.piler start

The script executes but there is no piler process running.

Comments (8)

  1. Janos SUTO repo owner

    please show me the output of piler -V, and the maillog entries. Please try to run "piler -d" manually to see what happens.

  2. capullon

    Hi, I have the following results.

    [root@GOLD63FULL init.d]# /usr/local/sbin/piler -d [root@GOLD63FULL init.d]# ps -ef | grep piler root 2521 2477 0 09:49 pts/0 00:00:00 grep piler

    [root@GOLD63FULL init.d]# /usr/local/sbin/piler -V piler 0.1.19, Janos SUTO <sj@acts.hu>

    Build Date: Tue Jul 24 20:05:17 BST 2012 Configure command: ./configure --enable-memcached --localstatedir=/var

    [root@GOLD63FULL init.d]#

  3. capullon

    Hi, just noticed the request for the maillog.

    It's below:

    Aug 2 09:45:26 localhost postfix/postfix-script[1760]: starting the Postfix mail system Aug 2 09:45:26 localhost postfix/master[1761]: daemon started -- version 2.6.6, configuration /etc/postfix Aug 2 09:49:51 localhost piler[2518]: cannot connect to mysql server Aug 2 09:49:51 localhost piler[2518]: ERR: cannot bind to port Aug 2 09:49:51 localhost piler[2518]: piler has been terminated Aug 2 09:58:25 localhost postfix/postfix-script[2641]: stopping the Postfix mail system Aug 2 09:58:25 localhost postfix/master[1761]: terminating on signal 15 Aug 2 11:04:25 localhost postfix/postfix-script[1759]: starting the Postfix mail system Aug 2 11:04:25 localhost postfix/master[1760]: daemon started -- version 2.6.6, configuration /etc/postfix Aug 2 11:07:29 localhost postfix/postfix-script[10068]: stopping the Postfix mail system Aug 2 11:07:29 localhost postfix/master[1760]: terminating on signal 15 Aug 2 11:09:00 localhost postfix/postfix-script[4961]: starting the Postfix mail system Aug 2 11:09:00 localhost postfix/master[4962]: daemon started -- version 2.6.6, configuration /etc/postfix

  4. capullon

    My fault.....was following your instructions blindly....looks like stopping postfix fixed it.

    Now.... I'll follow the rest of the instructions to see if I can get it working fully.

    thanks

  5. capullon

    Seeing the following mysql error

    Aug  2 18:28:15 localhost piler[6680]: sending signal to child (pid: 6681)
    Aug  2 18:28:15 localhost piler[6680]: sending signal to child (pid: 6682)
    Aug  2 18:28:15 localhost piler[6680]: sending signal to child (pid: 6683)
    Aug  2 18:28:15 localhost piler[6680]: sending signal to child (pid: 6684)
    Aug  2 18:28:15 localhost piler[6680]: sending signal to child (pid: 6685)
    Aug  2 18:28:15 localhost piler[6680]: sending signal to child (pid: 6686)
    Aug  2 18:28:15 localhost piler[6680]: sending signal to child (pid: 6687)
    Aug  2 18:28:15 localhost piler[6680]: sending signal to child (pid: 6688)
    Aug  2 18:28:15 localhost piler[6680]: sending signal to child (pid: 6689)
    Aug  2 18:28:15 localhost piler[6680]: sending signal to child (pid: 6690)
    Aug  2 18:28:15 localhost piler[6680]: piler has been terminated
    Aug  2 18:28:16 localhost piler[6782]: cannot connect to mysql server
    Aug  2 18:28:16 localhost piler[6782]: piler 0.1.19 starting
    Aug  2 18:28:16 localhost piler[6789]: forked a child (pid: 6789)
    Aug  2 18:28:16 localhost piler[6789]: child (pid: 6789) started main()
    Aug  2 18:28:16 localhost piler[6788]: forked a child (pid: 6788)
    Aug  2 18:28:16 localhost piler[6788]: child (pid: 6788) started main()
    Aug  2 18:28:16 localhost piler[6790]: forked a child (pid: 6790)
    Aug  2 18:28:16 localhost piler[6790]: child (pid: 6790) started main()
    Aug  2 18:28:16 localhost piler[6791]: forked a child (pid: 6791)
    Aug  2 18:28:16 localhost piler[6791]: child (pid: 6791) started main()
    Aug  2 18:28:16 localhost piler[6792]: forked a child (pid: 6792)
    Aug  2 18:28:16 localhost piler[6792]: child (pid: 6792) started main()
    Aug  2 18:28:16 localhost piler[6787]: forked a child (pid: 6787)
    Aug  2 18:28:16 localhost piler[6787]: child (pid: 6787) started main()
    Aug  2 18:28:16 localhost piler[6793]: forked a child (pid: 6793)
    Aug  2 18:28:16 localhost piler[6793]: child (pid: 6793) started main()
    Aug  2 18:28:16 localhost piler[6794]: forked a child (pid: 6794)
    Aug  2 18:28:16 localhost piler[6795]: forked a child (pid: 6795)
    Aug  2 18:28:16 localhost piler[6794]: child (pid: 6794) started main()
    Aug  2 18:28:16 localhost piler[6795]: child (pid: 6795) started main()
    Aug  2 18:28:16 localhost piler[6786]: forked a child (pid: 6786)
    Aug  2 18:28:16 localhost piler[6786]: child (pid: 6786) started main()
    [root@GOLD63FULL util]# vim /usr/local/etc/piler.conf 
    [root@GOLD63FULL util]# sh -x /root/piler-0.1.19/init.d/rc.piler restart
    
  6. Janos SUTO repo owner

    well, it's my fault that I haven't elaborated why you need postfix (or another MTA) as a smarthost. Now I extended the installation intstructions how to configure mail relay for piler.

    Basicaly the piler webui uses the mail relay server (it can be either on the piler host or on another host) to deliver users' emails from the archive to their mailbox.

    Please note that according to your logs piler cannot connect to the mysql server. Perhaps you should review the mysql* parameters in piler.conf. Without the sql server piler will temp fail the emails.

    If you made sure that piler was processing the emails properly, you may reduce the verbosity level.

  7. Janos SUTO repo owner

    One more thing: if you decided to run postfix on 127.0.0.1:25/tcp, then you should set the following in config.php:

    define('SMARTHOST', '127.0.0.1'); define('SMARTHOST_PORT', 25);

  8. Log in to comment