You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Atanu Mishra (JIRA)" <ji...@apache.org> on 2015/08/14 01:49:46 UTC

[jira] [Closed] (TRAFODION-142) LP Bug: 1246870 - Trafodion doesn't provide logging facility

     [ https://issues.apache.org/jira/browse/TRAFODION-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Atanu Mishra closed TRAFODION-142.
----------------------------------
    Resolution: Fixed
      Assignee:     (was: Sandhya Sundaresan)

> LP Bug: 1246870 - Trafodion doesn't provide logging facility
> ------------------------------------------------------------
>
>                 Key: TRAFODION-142
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-142
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: sql-general
>            Reporter: Matt Brown
>            Priority: Critical
>             Fix For: 1.0 (pre-incubation)
>
>
> Hi Matt,
> Narendra and I were discussing this yesterday.
> Here are a few ideas…
> As of RH6 – we no longer have evlog.
> With Trafodion, there’s no seapilot.
> To look at /var/log/messages, you have to be root.
> Syslog seemed like a good idea yesterday.
> $MY_SQROOT/export/include/seabed/logalt.h – SBX_log_write allows you to do that:
> void SBX_log_write(int                     log_type,
>                    const char             *log_file_dir,
>                    const char             *log_file_prefix,
>                    int                     comp_id,
>                    int                     event_id,
>                    posix_sqlog_facility_t  facility,
>                    posix_sqlog_severity_t  severity,
>                    const char             *name,
>                    const char             *msg_prefix,
>                    const char             *msg,
>                    const char             *snmptrap_cmd,
>                    const char             *msg_snmptrap,
>                    char                   *msg_ret,
>                    size_t                  msg_ret_size);
> We also discussed rolling our own – but then you have to worry about the logs filling up
> and the whole log management thing.
> -dave.
> From: Brown, Matt (SeaQuest R&D) 
> Sent: Thursday, October 24, 2013 10:08 AM
> To: George, Dave
> Cc: Omanski, Zbigniew; Tharaknath, Capirala; Kakarlamudi, Rao; Hegde, Anuradha
> Subject: Question about logging 
> Hi Dave,
> In new Trafodion environment do you know where event logs are located? Our product is still logging to QPid but I have no idea where these events are going. I don’t even see anything in monitor logs any longer. Dave B. said you might have some insight.
> Thanks,
> Matt



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)