HOW TO REMOVE FILES JETTY***.DIR IN FOLDER .../BROKR/APACHE TO CA DA

[Cassio Pinheiro]

How can I remove/delete old files of type *.dir (dir extension) located in the folder .../PMDA/broker/apache-activemq-5.15.2 ?

Thanks

[Jeffrey Pinard]

You mind showing a directory listing under apache-activemq-5.15.2?

Not seeing any *.dir under my 5.15.2 directory.

[Cassio Pinheiro]

Sorry

part was missing. It is the TMP directory inside this folder. The contents of these folders are empty.

The strange thing is that it is saving daily, it is not cleaning automatically.

[root@PMDA tmp]# pwd
/produtos/PMDA/broker/apache-activemq-5.15.2/tmp
[root@PMDA tmp]# ll|more
total 1448888
drwx------ 3 root root 4096 Jun  1  2018 jetty-0.0.0.0-8161-admin-_admin-any-1000149037253136502.dir
drwx------ 3 root root 4096 Mar 12  2023 jetty-0.0.0.0-8161-admin-_admin-any-100019071664901757.dir
drwx------ 3 root root 4096 Apr 18  2023 jetty-0.0.0.0-8161-admin-_admin-any-1000290537734717566.dir
drwx------ 3 root root 4096 Jan  6  2023 jetty-0.0.0.0-8161-admin-_admin-any-1000291229509349798.dir
drwx------ 3 root root 4096 Apr 16  2023 jetty-0.0.0.0-8161-admin-_admin-any-1000324616843651273.dir
drwx------ 3 root root 4096 Apr 27  2018 jetty-0.0.0.0-8161-admin-_admin-any-1000357052820678860.dir
drwx------ 3 root root 4096 Aug 23  2023 jetty-0.0.0.0-8161-admin-_admin-any-1000439018587009283.dir
drwx------ 3 root root 4096 Mar 17  2023 jetty-0.0.0.0-8161-admin-_admin-any-1000488344700720431.dir
drwx------ 3 root root 4096 Mar  7  2019 jetty-0.0.0.0-8161-admin-_admin-any-1000489551616691578.dir
drwx------ 3 root root 4096 May  3  2019 jetty-0.0.0.0-8161-admin-_admin-any-1000643898883976532.dir
drwx------ 3 root root 4096 Jun 18  2020 jetty-0.0.0.0-8161-admin-_admin-any-1000682509956981946.dir
drwx------ 3 root root 4096 Jan 15 05:34 jetty-0.0.0.0-8161-admin-_admin-any-1000688677161293130.dir
drwx------ 3 root root 4096 Mar 29 19:55 jetty-0.0.0.0-8161-admin-_admin-any-1000832967763282693.dir
drwx------ 3 root root 4096 Jul 31  2018 jetty-0.0.0.0-8161-admin-_admin-any-1000841135355615940.dir
drwx------ 3 root root 4096 Jul 21  2020 jetty-0.0.0.0-8161-admin-_admin-any-100093919908084676.dir
drwx------ 3 root root 4096 Mar 18 11:06 jetty-0.0.0.0-8161-admin-_admin-any-1000944744665632811.dir
drwx------ 3 root root 4096 Sep  6  2023 jetty-0.0.0.0-8161-admin-_admin-any-1000961849246234836.dir
drwx------ 3 root root 4096 May 20  2019 jetty-0.0.0.0-8161-admin-_admin-any-1000978628802605041.dir
drwx------ 3 root root 4096 Oct 22  2023 jetty-0.0.0.0-8161-admin-_admin-any-1001000105846130338.dir
drwx------ 3 root root 4096 May 27  2019 jetty-0.0.0.0-8161-admin-_admin-any-1001019374988434360.dir
drwx------ 3 root root 4096 Dec 18  2018 jetty-0.0.0.0-8161-admin-_admin-any-100102104297315150.dir
drwx------ 3 root root 4096 May  3  2018 jetty-0.0.0.0-8161-admin-_admin-any-1001078833805401769.dir
drwx------ 3 root root 4096 Feb  6 06:50 jetty-0.0.0.0-8161-admin-_admin-any-1001088881643320814.dir
drwx------ 3 root root 4096 Mar 19  2018 jetty-0.0.0.0-8161-admin-_admin-any-1001107509846060106.dir
drwx------ 3 root root 4096 Dec 19  2018 jetty-0.0.0.0-8161-admin-_admin-any-1001126246793003973.dir
drwx------ 3 root root 4096 May 16  2018 jetty-0.0.0.0-8161-admin-_admin-any-1001143143543954979.dir
drwx------ 3 root root 4096 May 15  2018 jetty-0.0.0.0-8161-admin-_admin-any-1001154608955506084.dir
drwx------ 3 root root 4096 Nov 25 06:56 jetty-0.0.0.0-8161-admin-_admin-any-1001231806654111280.dir
drwx------ 3 root root 4096 Dec 24  2020 jetty-0.0.0.0-8161-admin-_admin-any-1001293311722048747.dir
drwx------ 3 root root 4096 May  5  2018 jetty-0.0.0.0-8161-admin-_admin-any-1001318416595995227.dir
drwx------ 3 root root 4096 Jul 30  2023 jetty-0.0.0.0-8161-admin-_admin-any-1001341160494382439.dir

[Jeffrey Pinard]

So AMQ does run a webserver (aka jetty) on 8161.

These appear to be the temp files it creates when it starts.  If AMQ doesn't shutdown cleanly, it won't clean up it's temp directory entry.

So yes, you can delete these, EXCEPT the one for the current running AMQ process (latest date probably).  if AMQ is not running, you can clean them all up.

[Cassio Pinheiro]

ok, there is a file there from 2018, very old
Thanks

[Cassio Pinheiro]

Hi Jeffrey,

After deleting these temporary files, I started receiving an HTTP 403 error
- failed to open stream: HTTP request failed! HTTP/1.1 403 Forbidden in /produtos/web/cmdb/pipaFinderExt/coletaPMCPUPIPAFinder.php on line 258

- for data collection using the script below on the PM API :

file_get_contents(http://...@10.???.???.???:8581/odata/api/memorymfs?$select=Timestamp,im_Utilization,max_im_Utilization,min_im_Utilization&$filter=((DeviceItemID%20eq %201079327))&starttime=2024-04-26T00:00:01&endtime=2024-04-27T00:00:01&resolution=Hourly&$top=24&$format=application/json):

Is the problem related?

How could I resolve this 403 error?

Thanks

[Jeffrey Pinard]

So you stopped the Data Aggregator, and ActiveMQ processes, then cleared out the broker/apache-activemq-5.15.2/tmp directory?

Then started ActiveMQ. and did you see a new *.dir get created under broker/apache-activemq-5.15.2/tmp ?  Sounds like it should.  Or maybe on first access to http://DA:8161/admin??

Anyway, the cleanup of AMQ should not cause odata to be throwing errors.  odata doesn't use AMQ at all.

403 is bad password or disabled acct.  Did the account password, for making odata calls to DA, expire?  or account get disabled?

[Cassio Pinheiro]

Hello,
good morning

yes the services were stopped

and started successfully, where new directories were created, but still empty and being stored in the area in question.

I will evaluate the expiration information, the account has not been deactivated.

..
The situation is strange, as there is API data available, we are just not getting it regarding the projection.

Thanks

[Jeffrey Pinard]

It will create a new .dir each time AMQ starts, but the key is AMQ stopping cleanly to delete the .dir directory.

As for the account, if someone tries too many times to login, we may disable the account in Portal.
It could also be disabled in ldap or password has been changed.

[Jeffrey Pinard]

Another thing, check the DA apache-karaf/data/log/AuthenticationLog.log for any issues connecting to Portal SSO service, which may also cause us to return 403.

Does odata work for other accounts or all?  if all, could be issue with DA->SSO communication.