Current audit.log/wso2carbon.log only seems to have logs after the
incident. Earlier logs (wso2carbon.log.2016-07-03) seems to ends with;
> org.apache.qpid.pTID: [-1234] [] [2016-07-03 00:53:07,213] ERROR
> {org.wso2.carbon.registry.core.dataaccess.TransactionManager} - Failed to
> start new registry transaction.
> {org.wso2.carbon.registry.core.dataaccess.TransactionManager}
> org.h2.jdbc.JdbcSQLException: IO Exception: "java.io.IOException: No space
> left on device";
> "/home/ladmin/cloud_setup/wso2das-3.0.1/repository/database/WSO2CARBON_DB.h2.db"
> [90031-140]
May be it couldn't log the incident, since there's No space left on device.
On Mon, Jul 4, 2016 at 2:39 PM, Dulanja Liyanage <[email protected]> wrote:
> What was getting printed on the logs?
>
> Thanks,
> Dulanja
>
> On Mon, Jul 4, 2016 at 2:11 PM, Grainier Perera <[email protected]> wrote:
>
>> Hi All,
>>
>> I was trying to access Carbon Management Console (of DAS 3.0.1) with
>> correct credentials and it kept returning "Login failed! Please recheck the
>> username and password and try again.". Then I checked disk usage of that
>> node and it was at 100% (/dev/sda1 29G 29G 0 100% /). After cleaning some
>> logs and artifacts, I tried to log back in with the same credentials, and
>> this time it worked. Is this the expected behavior?
>>
>> Regards,
>> --
>> Grainier Perera
>> Software Engineer
>> Mobile : +94716122384
>> WSO2 Inc. | http://wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> Thanks & Regards,
> Dulanja Liyanage
> Lead, Platform Security Team
> WSO2 Inc.
>
--
Grainier Perera
Software Engineer
Mobile : +94716122384
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
