# How do I use --logLevel?

**URL:** <https://forum.liquibase.org/t/how-do-i-use-loglevel/3729>\
**Category:** Community Answers\
**Created:** [March 7, 2019, 8:37pm UTC](https://forum.liquibase.org/t/how-do-i-use-loglevel/3729 "2019-03-07T20:37:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Spokey](https://avatars.discourse-cdn.com/v4/letter/s/8baadc/32.png) [@Spokey](https://forum.liquibase.org/u/Spokey)\
**Post date:** [March 7, 2019, 8:37pm UTC](https://forum.liquibase.org/t/how-do-i-use-loglevel/3729/1 "2019-03-07T20:37:00Z")

</div>

It doesn’t seem to matter what I set it to, I don’t get anything that looks like additional information?

liquibase --url=“jdbc:informix-sqli:INFORMIXSERVER=informix01\_tcp;SQLH\_TYPE=FILE;SQLH\_FILE=/opt/informix/informix/etc/sqlhosts;DATABASE=wallet” --logLevel=debug --logFile=./lb.log --classpath=/opt/informix/informix/jdbc/lib/ifxjdbc.jar --changeLogFile ./test1ChangeLog.xml --includeTablespace=true generateChangeLog

Starting Liquibase at Thu, 07 Mar 2019 12:30:34 GMT (version 3.6.3 built at 2019-01-29 11:34:48)

Unexpected error running Liquibase: liquibase.exception.DatabaseException: liquibase.exception.DatabaseException: java.sql.SQLException: The cursor has been previously released and is unavailable.

liquibase.exception.LiquibaseException: liquibase.command.CommandExecutionException: liquibase.exception.DatabaseException: liquibase.exception.DatabaseException: java.sql.SQLException: The cursor has been previously released and is unavailable.

ls: ./lb.log: No such file or directory

---

<div class="post-metadata">

**Author:** ![un63453276661320211r](https://avatars.discourse-cdn.com/v4/letter/u/278dde/32.png) [@un63453276661320211r](https://forum.liquibase.org/u/un63453276661320211r)\
**Post date:** [March 7, 2019, 8:37pm UTC](https://forum.liquibase.org/t/how-do-i-use-loglevel/3729/2 "2019-03-07T20:37:00Z")

</div>

I have the same question.&nbsp; Unless I’m also using it incorrectly (which is hardly inconceivable), --logLevel seems to be a supported flag, with 0 functionality.

---

<div class="post-metadata">

**Author:** ![un1382561729492r88id](https://avatars.discourse-cdn.com/v4/letter/u/c4cdca/32.png) [@un1382561729492r88id](https://forum.liquibase.org/u/un1382561729492r88id)\
**Post date:** [March 7, 2019, 8:37pm UTC](https://forum.liquibase.org/t/how-do-i-use-loglevel/3729/3 "2019-03-07T20:37:00Z")

</div>

The built-in logger for liquibase is fairly basic. It outputs to the console (stderr stream, I think), not to a file. The different levels available are&nbsp;debug, info, warning, severe, and off. I think the default level is ‘severe’. So in Spokey’s example above, since the difference in commands was just to use --logLevel=severe, there was no difference in output. It is not clear to me why the --logFile=./lb.log option did not result in a file being created.&nbsp;

debug - most verbose. Show debug-level messages, chatty info messages, warnings, and severe errors.

If you want to get better logging, there is a plugin that enables the slf4j logging interface, which is far more configurable. Search the web for ‘liquibase slf4j’ for more details on how to do that.&nbsp;

Steve Donie  
Principal Software Engineer  
Datical, Inc. [http://www.datical.com/](http://www.datical.com/)

---

<div class="post-metadata">

**Author:** ![un1382561729492r88id](https://avatars.discourse-cdn.com/v4/letter/u/c4cdca/32.png) [@un1382561729492r88id](https://forum.liquibase.org/u/un1382561729492r88id)\
**Post date:** [March 7, 2019, 8:37pm UTC](https://forum.liquibase.org/t/how-do-i-use-loglevel/3729/4 "2019-03-07T20:37:00Z")

</div>

Follow up to this

There was actually a bug in Liquibase 3.6.x that prevented the --logLevel flag from working properly. That has been fixed in 3.8.1 and subsequent versions.&nbsp;

Steve Donie  
Principal Software Engineer  
Liquibase Community Engagement  
Datical, Inc. [http://www.datical.com/](http://www.datical.com/)