H i Supun, This is because, patch related log properties have been set to print only to carbon cosole and patches.log file, Will change this to log wso2carbon.log too. But patches.log file should have these logs, could you confirm it?
Thanks, shameera. On Mon, Jul 8, 2013 at 8:27 AM, Supun Malinga <[email protected]> wrote: > Shameera, > > I am aware what "start" does.. :) > But if its properly logged it should appear in the wso2carbon.log.. > > thanks, > > > On Mon, Jul 8, 2013 at 8:24 AM, Shameera Rathnayaka <[email protected]>wrote: > >> Hi Supun, >> >> If you use "start" parameter then output get directed to /dev/null , >> Hence you will not see any output in startup console, following is the >> command which runs inside the script if you start server with "start" >> parameter, >> >> "nohup bash $CARBON_HOME/bin/wso2server.sh $args > /dev/null 2>&1 &" >> >> Thanks, >> Shameera. >> >> >> On Mon, Jul 8, 2013 at 8:06 AM, Supun Malinga <[email protected]> wrote: >> >>> Hi Shameera, >>> >>> I couldn't see the patch mgmt logs. I start the server as "wso2server.sh >>> start". Please check. >>> >>> thanks, >>> >>> >>> On Mon, Jul 8, 2013 at 12:41 AM, Shameera Rathnayaka >>> <[email protected]>wrote: >>> >>>> Hi Azeez, >>>> >>>> On Sun, Jul 7, 2013 at 11:48 PM, Afkham Azeez <[email protected]> wrote: >>>> >>>>> I think you should check the MD5 of the jars too & reapply patches if >>>>> they have changed. >>>>> >>>> >>>> If that so we have to maintain another file which keeps MD5 sum of most >>>> latest jars available in patches and check against it to identify jar >>>> changes. This will add another IO access to server startup hope that is >>>> fine. >>>> >>>> Cheers, >>>> Shameera. >>>> >>>> >>>>> >>>>> >>>>> On Sun, Jul 7, 2013 at 6:41 PM, Shameera Rathnayaka <[email protected] >>>>> > wrote: >>>>> >>>>>> Hi Supun, >>>>>> >>>>>> We are checking patch changes in directory level not in jar level. >>>>>> But you will get md5 checksum warning if there any mismatch with most >>>>>> latest patches jar and the same jar in plugins directory. If there is any >>>>>> waring then you will see message like "Patch verification process >>>>>> complete >>>>>> with warnings" in server startup console. You can see these waring in >>>>>> patches.log file where all patch related log messages print. >>>>>> >>>>>> In your case you have to remove the previous patch first and then >>>>>> apply again with updated patch, Yes this is bit ugly but we don't >>>>>> recommend >>>>>> to update the jars comes with patches. For the easy of development we can >>>>>> introduce a way to force the patch application process(again we have to >>>>>> use >>>>>> a startup parameter). >>>>>> >>>>>> thanks, >>>>>> Shameera. >>>>>> >>>>>> >>>>>> On Sun, Jul 7, 2013 at 1:17 AM, Supun Malinga <[email protected]>wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Noticed that after you updated a jar in a patch directory, it won't >>>>>>> get reapplied.. >>>>>>> Are we not checking the md5?. >>>>>>> >>>>>>> thanks, >>>>>>> -- >>>>>>> Supun Malinga, >>>>>>> >>>>>>> Senior Software Engineer, >>>>>>> WSO2 Inc. >>>>>>> http://wso2.com >>>>>>> http://wso2.org >>>>>>> email - [email protected] <[email protected]> >>>>>>> mobile - 071 56 91 321 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Software Engineer - WSO2 Inc.* >>>>>> *email: shameera AT wso2.com <[email protected]> , shameera AT >>>>>> apache.org <[email protected]>* >>>>>> *phone: +9471 922 1454* >>>>>> * >>>>>> * >>>>>> *Linked in : * >>>>>> http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >>>>>> *Twitter : *https://twitter.com/Shameera_R >>>>>> >>>>>> _______________________________________________ >>>>>> Dev mailing list >>>>>> [email protected] >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Afkham Azeez* >>>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>> * <http://www.apache.org/>** >>>>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>>> twitter: >>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>>> * >>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>>> * >>>>> * >>>>> *Lean . Enterprise . Middleware* >>>>> >>>> >>>> >>>> >>>> -- >>>> *Software Engineer - WSO2 Inc.* >>>> *email: shameera AT wso2.com <[email protected]> , shameera AT >>>> apache.org <[email protected]>* >>>> *phone: +9471 922 1454* >>>> * >>>> * >>>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >>>> *Twitter : *https://twitter.com/Shameera_R >>>> >>> >>> >>> >>> -- >>> Supun Malinga, >>> >>> Senior Software Engineer, >>> WSO2 Inc. >>> http://wso2.com >>> http://wso2.org >>> email - [email protected] <[email protected]> >>> mobile - 071 56 91 321 >>> >> >> >> >> -- >> *Software Engineer - WSO2 Inc.* >> *email: shameera AT wso2.com <[email protected]> , shameera AT >> apache.org<[email protected]> >> * >> *phone: +9471 922 1454* >> * >> * >> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >> *Twitter : *https://twitter.com/Shameera_R >> > > > > -- > Supun Malinga, > > Senior Software Engineer, > WSO2 Inc. > http://wso2.com > http://wso2.org > email - [email protected] <[email protected]> > mobile - 071 56 91 321 > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com <[email protected]> , shameera AT apache.org<[email protected]> * *phone: +9471 922 1454* * * *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
