This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Error with Log Searching in PureMessage multi server deployment

Hi All,

I've logged a support case regarding this issue on the 26th but unfortunately fail to get any positive feedback so far so decided to try my luck here in this forum.

I'm configuring a PMX multy server deployment with Central server and 2 Edge servers (PMX version 5.5.9). I need help on configuring Logserching option in http://xxx.xxx.xxx.xxx:28443/groups interface. I have successfully use this option on single server deployments but this is the first time I'm tying this on a multi server setup. I have already increased the "remote_search_timeout" value in /opt/pmx/etc/logsearch.conf to prevent search timeouts. I have no connectivity issues between CSM & Edge servers as I can telnet on port 28443 for both directions. Please advice whether I need to perform additional configurations in my scenario. My CSM is using sendmail as the MTA but both Edge servers are running POSTFIX. When I try to search logs, it says " Note  Your search returned 0 results."

Kind regards,
Pubudu.

:1036


This thread was automatically locked due to age.
Parents
  • Hi Barney,

    If you see the 408 time-out error when running the pmx-logsearch command this is usually a sign that the communicaton between the PureMessage hosts are taking too long to answer and the logsearch command timing out.  You can adjust the time-out by looking in /opt/pmx/etc/logsearch.conf.  You can read more information about the logsearch.conf file by doing 'man logsearch.conf' as the pmx user.

    -Jason

    :16711
Reply
  • Hi Barney,

    If you see the 408 time-out error when running the pmx-logsearch command this is usually a sign that the communicaton between the PureMessage hosts are taking too long to answer and the logsearch command timing out.  You can adjust the time-out by looking in /opt/pmx/etc/logsearch.conf.  You can read more information about the logsearch.conf file by doing 'man logsearch.conf' as the pmx user.

    -Jason

    :16711
Children
No Data