Visiblement il y a un bug … Slack essaye d’avoir accès a un fichier de logs, dont il n’a plus accès. Il tourne donc en boucle et par la même occasion il sature de logs syslog.

Misère.

Dans syslog en boucle:

Sep 23 07:47:19 XXXXXX kernel: [1541572.057366] audit: type=1400 audit(1663912039.268:1467395959):
apparmor="DENIED" operation="rename_src" profile="snap.slack.slack"
name="/home/XXXXX/snap/slack/64/.config/Slack/logs/default/webapp-console1.log"
pid=18282 comm="slack" requested_mask="wd" denied_mask="wd" fsuid=1000
ouid=1000

Quand je regarde la fin du fichier sur Slack :

tail -f /home/XXXXX/snap/slack/64/.config/Slack/logs/default/webapp-console1.log
[09/05/22, 11:39:35:001] info: [CHECK-UNREADS] (TJ5HTNKGB) Checking unreads after unread line became visible
[09/05/22, 11:39:35:001] info: [CHECK-UNREADS] (TJ5HTNKGB) Not marking C020NGCFJ7R because last_read >= latest && channel is read
[09/05/22, 11:39:37:301] info: Breadcrumb: ui.click: div.c-message__reply_bar_description > span.c-message__reply_bar_view_thread
[09/05/22, 11:39:37:320] info: [ROUTES] [ROUTE_FLEX_THREAD] navigateToRoute called with reason workspace-store/setSecondaryView
[09/05/22, 11:39:37:320] info: [ROUTES] [ROUTE_FLEX_THREAD] Attempting to navigate to new route {"teamId":"TJ5HTNKGB","entityId":"C020NGCFJ7R","memberId":"UKJ6492EP","threadId":"C020NGCFJ7R-1662365958.376179"}
[09/05/22, 11:39:37:320] info: [ROUTES] [ROUTE_FLEX_THREAD] About to run notifyRouteWillNavigateListeners to determine shouldNavigate
[09/05/22, 11:39:37:320] info: [ROUTES] [ROUTE_FLEX_THREAD] notifyRouteWillNavigateListeners finished, shouldNavigate is true
[09/05/22, 11:39:37:322] info: [HISTORY-NAVIGATION] Adding route to the history stack
[09/05/22, 11:39:37:322] info: [ROUTES] [ROUTE_FLEX_THREAD] Navigated to new route
[09/05/22, 11:39:37:340] info: [API-Q] (TJ5HTNKGB) e5b6d985-1662370777.339 conversations.replies called with reason: history-api/fetchReplies