Skip to main content
12-Amethyst
May 27, 2022
Solved

Linux hidden file /dev/shm/.tomcat.ptc_p caused backup failed

  • May 27, 2022
  • 2 replies
  • 3554 views

Hello all,

 

There is a hidden Linux file /dev/shm/.tomcat.ptc_p after running Thingworx. The file's attribute is question mark "?". This file is still there even if Tomcat shutdown. And also cannot delete it by root user. It caused backup software failed.

 

jsvc service running mode, tomcat:tomcat user&group created and tomcat user is with nologin.

 

Any method to avoid creating, delete this hidden file, or change file attribute to normal?

 

Thanks.

Best answer by slangley

Hi @WilliamZhao.

 

As you know, a case was opened for this issue and subsequently the solution was documented in an article.  Please feel free to add any additional details of the case.

 

Regards.

 

--Sharon

 

2 replies

Support
May 31, 2022

Hi @ZHH.

 

That hidden file, among others, are necessary for ThingWorx to start.  It does not get removed upon shutdown and you should not try to delete it.

 

What is your driving your desire to remove this file?

 

Regards.

 

--Sharon

ZHH12-AmethystAuthor
12-Amethyst
June 1, 2022

Hello Sharon,

 

An application agent is running on the Linux server to backup the whole Linux system automatically, backup process will be broken if this file is there. 

 

Even root user cannot delete it, the file attribute of .tomcat.ptc_p likes "d??????????     ?       ? ", based on Google search results, it seems abnormal.

This case happens on Thingworx 9.1, 9.2 and 9.3.

 

What the customer expected is:

1, best if .tomcat.ptc_p can be removed after stopping Tomcat, so that backup can be done automatically.

2, if .tomcat.ptc_p cannot be removed, grant normal file attribute so that root user can delete it, then start backup manually.

 

Thanks.

 

Support
June 1, 2022

Hi @WilliamZhao.

 

After reading your response, I realized that the file you mentioned is not named correctly and is possibly a copy of the one created by ThingWorx--not the one actually in use.  To verify, please navigate to the $HOME directory of the Tomcat process owner.  Do you see a file there called ptc_p.0?

 

Are you running any other PTC products that may have created the file?  If not, you will need to find a way at the o/s level to remove it.  Have you tried changing the attributes in order to delete it?  You may have to use a 3rd party utility for getting rid of it.

 

I assume the backup is failing to run because of the invalid attributes.   If you're unable to remove the file, have you tried excluding it from the backup process?

 

Regards.

 

--Sharon

slangleyCommunity ManagerAnswer
Support
July 22, 2022

Hi @WilliamZhao.

 

As you know, a case was opened for this issue and subsequently the solution was documented in an article.  Please feel free to add any additional details of the case.

 

Regards.

 

--Sharon