RotherOSS / otobo

OTOBO is one of the most flexible web-based ticketing systems used for Customer Service, Help Desk, IT Service Management. https://otobo.io/
GNU General Public License v3.0
264 stars 75 forks source link

Daemon bloats the ssh terminal session with messages #596

Open wollmers opened 4 years ago

wollmers commented 4 years ago

OS: Debian 10.5 OTOBO: 10.0.5

Reproduce:

$ ssh w4
Linux w4 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) x86_64
helmut@w4:~$ su -
root@w4 ~ # su - otobo
otobo@w4:~$ bin/otobo.Daemon.pl status

Manage the OTOBO daemon process.

Daemon running
otobo@w4:~$ bin/otobo.Daemon.pl stop

Manage the OTOBO daemon process.

Daemon stopped
otobo@w4:~$ bin/otobo.Daemon.pl status

Manage the OTOBO daemon process.

Daemon not running
otobo@w4:~$ bin/otobo.Daemon.pl start

Manage the OTOBO daemon process.

Daemon started
otobo@w4:~$ No indexing needed! Skipping...
Done.

No messages available for sending.
Done.

otobo@w4:~$ 
otobo@w4:~$ No indexing needed! Skipping...
Done.

No messages available for sending.
Done.

No indexing needed! Skipping...
Done.

No messages available for sending.
Done.

otobo@w4:~$ exit
logout
root@w4 ~ # 
root@w4 ~ # No indexing needed! Skipping...
Done.

No messages available for sending.
Done.

root@w4 ~ # exit
logout
helmut@w4:~$ No indexing needed! Skipping...
Done.
Processing ticket escalation events ...
Done.

No messages available for sending.
Done.

Unlocking tickets that are past their unlock timeout...
Done.

helmut@w4:~$ exit
logout
Connection to 88.X.X.X closed.
bschmalhofer commented 6 months ago

This behavior observed by @wollmers is still the case. Here are the logs of six minutes in the daemon container:

$ docker logs otoelfnullrel-daemon-1 >logs1.out
$ sleep 370 ; docker logs otoelfnullrel-daemon-1 >logs2.out
$ diff logs1.out logs2.out > new_output.txt

new_output.txt

When running under Docker we also have the output from the Daemon checker every two minutes:

> Manage the OTOBO daemon process.
> 
> Daemon already running!