WAPT Logrotate Modification

Questions about WAPT Server / Requests and help related to the WAPT server
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
User avatar
Aguay
Messages: 27
Registration: May 22, 2015 - 4:20 p.m.

January 4, 2017 - 9:25 AM

Hello TISman and TISwoman,

We appreciate the use of logrotate in the wapt server, however, there is a modification to be made.

In the wapt-server logrotate file (https://github.com/tranquilit/WAPT/blob ... -logrotate), line 7 should be changed:

`/etc/init.d/waptserver restart > /dev/null`

to

`/etc/init.d/waptserver restart &> /dev/null`.


Otherwise, we get a CRON email with the restart output:

`/etc/cron.daily/logrotate:
[uWSGI] getting INI configuration from /opt/wapt/conf/waptserver.ini`.

This could be unnecessary logging.
If necessary, I'm happy to submit a pull request, and you can merge it.

See you soon. ;)
High
gildasc
Messages: 1
Registration: August 30, 2017 - 12:47

August 30, 2017 - 12:55

With a Jessie/sid, applying the suggested modification, we get this in the email:
/etc/cron.daily/logrotate:
Restarting waptserver:
..
I think it's because

Code: Select all

&>
This is specific to bash, and cron jobs are executed in Dash since version 5. I suggest instead:

Code: Select all

service waptserver restart > /dev/null 2>&1
High
Locked

Return to "WAPT Server"


  • To go further with WAPT