Logger error with OTP 21.0-rc1

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Logger error with OTP 21.0-rc1

Sébastien Merle
Hi,

I am porting the grisp software (grisp.org) to OTP 21.0-rc1.
Everything build and deploy just fine but when running Erlang on the board the console is swamped with error like:

  `(no logger present) unexpected logger message: {log,error,"Error in process ~p with exit value:~n~p~n",[<0.39.0>,{badarg,[{ets,lookup,[logger,proc_lib],[]},{logger_config,allow,3,[{file,"logger_config.erl"},{...`

I saw someone else complaining about this same error on the thread about 21.0-rc1 but the only response was to use a clean build, and I already built OTP from a fresh checkout.

Any idea what could be the cause ? Maybe this is a know issue or the new logger API requires some configuration or service to be started explicitly ?

Thank you very much.

Sebastien Merle,
Peer Stritzinger GmbH.

_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions
Reply | Threaded
Open this post in threaded view
|

Re: Logger error with OTP 21.0-rc1

Siri Hansen
Hi Sebastien,

which script/boot file do you use? Is it built with the new OTP version?

Kind Regards
/siri@otp

2018-05-28 23:42 GMT+02:00 Sébastien Merle <[hidden email]>:
Hi,

I am porting the grisp software (grisp.org) to OTP 21.0-rc1.
Everything build and deploy just fine but when running Erlang on the board the console is swamped with error like:

  `(no logger present) unexpected logger message: {log,error,"Error in process ~p with exit value:~n~p~n",[<0.39.0>,{badarg,[{ets,lookup,[logger,proc_lib],[]},{logger_config,allow,3,[{file,"logger_config.erl"},{...`

I saw someone else complaining about this same error on the thread about 21.0-rc1 but the only response was to use a clean build, and I already built OTP from a fresh checkout.

Any idea what could be the cause ? Maybe this is a know issue or the new logger API requires some configuration or service to be started explicitly ?

Thank you very much.

Sebastien Merle,
Peer Stritzinger GmbH.

_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions



_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions
Reply | Threaded
Open this post in threaded view
|

Re: Logger error with OTP 21.0-rc1

Sébastien Merle
The release is built using rebar3:

`{relx, [{release, {testproject, "0.1.0"}, [ testproject ]}]}.`

and erlang is started on the board with:

`erl.rtems -- -home . -pa . -root testproject -boot testproject/releases/0.1.0/testproject -kernel inetrc "./erl_inetrc"`

Thank you for your help.

Sebastien Merle,
Peer Stritzinger GmbH.


On Tue, May 29, 2018 at 11:21 AM, Siri Hansen <[hidden email]> wrote:
Hi Sebastien,

which script/boot file do you use? Is it built with the new OTP version?

Kind Regards
/siri@otp

2018-05-28 23:42 GMT+02:00 Sébastien Merle <[hidden email]>:
Hi,

I am porting the grisp software (grisp.org) to OTP 21.0-rc1.
Everything build and deploy just fine but when running Erlang on the board the console is swamped with error like:

  `(no logger present) unexpected logger message: {log,error,"Error in process ~p with exit value:~n~p~n",[<0.39.0>,{badarg,[{ets,lookup,[logger,proc_lib],[]},{logger_config,allow,3,[{file,"logger_config.erl"},{...`

I saw someone else complaining about this same error on the thread about 21.0-rc1 but the only response was to use a clean build, and I already built OTP from a fresh checkout.

Any idea what could be the cause ? Maybe this is a know issue or the new logger API requires some configuration or service to be started explicitly ?

Thank you very much.

Sebastien Merle,
Peer Stritzinger GmbH.

_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions




_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions
Reply | Threaded
Open this post in threaded view
|

Re: Logger error with OTP 21.0-rc1

Sébastien Merle
After some unsuccessful investigation I re-read your message I realized I was still using 20.2 to release my application !
This was the issue , everything seems to work fin when using 21.0-rc1 for everything.

Thank you very much.

On Tue, May 29, 2018 at 12:45 PM, Sébastien Merle <[hidden email]> wrote:
The release is built using rebar3:

`{relx, [{release, {testproject, "0.1.0"}, [ testproject ]}]}.`

and erlang is started on the board with:

`erl.rtems -- -home . -pa . -root testproject -boot testproject/releases/0.1.0/testproject -kernel inetrc "./erl_inetrc"`

Thank you for your help.

Sebastien Merle,
Peer Stritzinger GmbH.


On Tue, May 29, 2018 at 11:21 AM, Siri Hansen <[hidden email]> wrote:
Hi Sebastien,

which script/boot file do you use? Is it built with the new OTP version?

Kind Regards
/siri@otp

2018-05-28 23:42 GMT+02:00 Sébastien Merle <[hidden email]>:
Hi,

I am porting the grisp software (grisp.org) to OTP 21.0-rc1.
Everything build and deploy just fine but when running Erlang on the board the console is swamped with error like:

  `(no logger present) unexpected logger message: {log,error,"Error in process ~p with exit value:~n~p~n",[<0.39.0>,{badarg,[{ets,lookup,[logger,proc_lib],[]},{logger_config,allow,3,[{file,"logger_config.erl"},{...`

I saw someone else complaining about this same error on the thread about 21.0-rc1 but the only response was to use a clean build, and I already built OTP from a fresh checkout.

Any idea what could be the cause ? Maybe this is a know issue or the new logger API requires some configuration or service to be started explicitly ?

Thank you very much.

Sebastien Merle,
Peer Stritzinger GmbH.

_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions





_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions
Reply | Threaded
Open this post in threaded view
|

Re: Logger error with OTP 21.0-rc1

Siri Hansen
Hi again - sorry for the slow follow-up! 

The problem is that start script/boot built with older releases start the error_logger instead of logger. Good to see you solved it - thanks for letting me know!

/siri



2018-05-29 14:04 GMT+02:00 Sébastien Merle <[hidden email]>:
After some unsuccessful investigation I re-read your message I realized I was still using 20.2 to release my application !
This was the issue , everything seems to work fin when using 21.0-rc1 for everything.

Thank you very much.

On Tue, May 29, 2018 at 12:45 PM, Sébastien Merle <[hidden email]> wrote:
The release is built using rebar3:

`{relx, [{release, {testproject, "0.1.0"}, [ testproject ]}]}.`

and erlang is started on the board with:

`erl.rtems -- -home . -pa . -root testproject -boot testproject/releases/0.1.0/testproject -kernel inetrc "./erl_inetrc"`

Thank you for your help.

Sebastien Merle,
Peer Stritzinger GmbH.


On Tue, May 29, 2018 at 11:21 AM, Siri Hansen <[hidden email]> wrote:
Hi Sebastien,

which script/boot file do you use? Is it built with the new OTP version?

Kind Regards
/siri@otp

2018-05-28 23:42 GMT+02:00 Sébastien Merle <[hidden email]>:
Hi,

I am porting the grisp software (grisp.org) to OTP 21.0-rc1.
Everything build and deploy just fine but when running Erlang on the board the console is swamped with error like:

  `(no logger present) unexpected logger message: {log,error,"Error in process ~p with exit value:~n~p~n",[<0.39.0>,{badarg,[{ets,lookup,[logger,proc_lib],[]},{logger_config,allow,3,[{file,"logger_config.erl"},{...`

I saw someone else complaining about this same error on the thread about 21.0-rc1 but the only response was to use a clean build, and I already built OTP from a fresh checkout.

Any idea what could be the cause ? Maybe this is a know issue or the new logger API requires some configuration or service to be started explicitly ?

Thank you very much.

Sebastien Merle,
Peer Stritzinger GmbH.

_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions






_______________________________________________
erlang-questions mailing list
[hidden email]
http://erlang.org/mailman/listinfo/erlang-questions