Skip to content

Suppress "Welcome Screen" when using --silent #3278

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ghost opened this issue Nov 13, 2017 · 5 comments
Closed

Suppress "Welcome Screen" when using --silent #3278

ghost opened this issue Nov 13, 2017 · 5 comments

Comments

@ghost
Copy link

ghost commented Nov 13, 2017

What's going wrong?

The Welcome Screen (the big ASCII PM2) should respect the --silent option.

I use pm2 to launch node processes inside docker containers. When a new container is created then pm2 prints the welcome screen in the log. Therefore the first 35 lines of each container log look like this:

container.service-foo |
container.service-foo |                         -------------
container.service-foo |
container.service-foo |                       PM2 process manager
container.service-foo |
container.service-foo | __/\\\\\\\\\\\\\____/\\\\____________/\\\\____/\\\\\\\\\_____
container.service-foo |  _\/\\\/////////\\\_\/\\\\\\________/\\\\\\__/\\\///////\\\___
container.service-foo |   _\/\\\_______\/\\\_\/\\\//\\\____/\\\//\\\_\///______\//\\\__
container.service-foo |    _\/\\\\\\\\\\\\\/__\/\\\\///\\\/\\\/_\/\\\___________/\\\/___
container.service-foo |     _\/\\\/////////____\/\\\__\///\\\/___\/\\\________/\\\//_____
container.service-foo |      _\/\\\_____________\/\\\____\///_____\/\\\_____/\\\//________
container.service-foo |       _\/\\\_____________\/\\\_____________\/\\\___/\\\/___________
container.service-foo |        _\/\\\_____________\/\\\_____________\/\\\__/\\\\\\\\\\\\\\\_
container.service-foo |         _\///______________\///______________\///__\///////////////__
container.service-foo |
container.service-foo |
container.service-foo |                        Getting started
container.service-foo |
container.service-foo |                         Documentation
container.service-foo |                         http://pm2.io/
container.service-foo |
container.service-foo |                       Start PM2 at boot
container.service-foo |                         $ pm2 startup
container.service-foo |
container.service-foo |                      Daemonize Application
container.service-foo |                        $ pm2 start <app>
container.service-foo |
container.service-foo |                      Monitoring/APM solution
container.service-foo |                     https://app.keymetrics.io/
container.service-foo |
container.service-foo |                         -------------
container.service-foo |
container.service-foo | [PM2] Spawning PM2 daemon with pm2_home=/root/.pm2
container.service-foo | [PM2] PM2 Successfully daemonized

It would be nice if the Welcome Screen would respect the --silent option and not show itself in that case.

How could we reproduce this issue?

Start pm2 with the option "--silent" on a host where the folder ~/.pm2 does not exist yet.

Supporting information

Tested on pm2 2.4.6

@ghost
Copy link
Author

ghost commented Nov 13, 2017

As a workaround I added pm2 status > /dev/null to my startup file to "eat" the welcome screen.

@Unitech
Copy link
Owner

Unitech commented Dec 12, 2017

fixed, pending release

@Unitech
Copy link
Owner

Unitech commented Dec 14, 2017

Fixed.

Changelog: 2.9.0 CHANGELOG
Introduced in version: 2.9.0

Update procedure:

npm install pm2 -g
pm2 update

@Unitech Unitech closed this as completed Dec 14, 2017
@tjanson
Copy link

tjanson commented Nov 22, 2018

I’d appreciate if there was a way to silence the banner only (--no-banner or something). I’m in the same situation: lots of Docker container logs starting with the banner. But I’m actually interested in the regular output.

To be honest, as cool as the ASCII logo is, it’s pretty annoying in practice.

Edit: I see now that this is essentially #1658, though that doesn’t offer a solution.

inerc pushed a commit to inerc/pm2 that referenced this issue Feb 11, 2020
@OliverJAsh
Copy link

OliverJAsh commented Mar 3, 2021

PM2_DISCRETE_MODE=true does the job but it probably hides other things as well which might not be desired. We need a separate flag to just hide the banner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants