You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perhaps this is no a bug, but a feature, but... I noticed selected Tableau Server / tabsvc / services / output folders (most probably result of running LogShark) are not cleaned up at all.
Steps to reproduce (in my case, install dir d:\Tableau Server)
run command for couple of days (each day = separate zip with different name)
check the below dirs as an example (each LogShark run seem to generate new dir here, which is next included in result of tsm backup). Tableau Server\data\tabsvc\services\vizportal_0.20214.21.1217.2252\bin\Output\ Tableau Server\data\tabsvc\services\clustercontroller_0.20214.21.1217.2252\bin\Output\
Same applies for other dirs like apigateway, backuprestore, flowminerva, hyper, licenseservice, siteimportexport, tabadmincontroller, tdsnativeservice
The conclusion that LogShark is causing these dirs to be created is because new items are there only for days when I run LogShark.
Also, the tsm maintenance cleanup -t -l --log-files-retention 4
does not cleanup that (not tried -a though yet).
The text was updated successfully, but these errors were encountered:
Perhaps this is no a bug, but a feature, but... I noticed selected Tableau Server / tabsvc / services / output folders (most probably result of running LogShark) are not cleaned up at all.
Steps to reproduce (in my case, install dir d:\Tableau Server)
LogShark.exe mydailylogs.zip--plugins "Art;Apache;Backgrounder;ClusterController;Filestore;Hyper;Postgres;ResourceManager;SearchServer;Tabadmin;VizPortal;VizqlDesktop" --publishworkbooks 1>"d:\Backup\LogSharkLogs\result.log"
Tableau Server\data\tabsvc\services\vizportal_0.20214.21.1217.2252\bin\Output\
Tableau Server\data\tabsvc\services\clustercontroller_0.20214.21.1217.2252\bin\Output\
Same applies for other dirs like apigateway, backuprestore, flowminerva, hyper, licenseservice, siteimportexport, tabadmincontroller, tdsnativeservice
The conclusion that LogShark is causing these dirs to be created is because new items are there only for days when I run LogShark.
Also, the
tsm maintenance cleanup -t -l --log-files-retention 4
does not cleanup that (not tried -a though yet).
The text was updated successfully, but these errors were encountered: