Super Contributor.. JHarris941 Super Contributor..
Super Contributor..
1486 views

"Command Execution Error" message when trying to migrate using Object Types

Jump to solution

Hello All,

 

We just started to receive this error message when we try to migrate code in the workbench:

 

 

java.lang.NullPointerException
at com.kintana.core.util.LogFileWriter.flush(LogFileWriter.java:151)
at com.kintana.core.util.MultiWriter.flush(MultiWriter.java:161)
at com.kintana.core.util.HtmlFilterWriter.flush(HtmlFilterWriter.java:20

 

This happen before even a log is produced so I assume its something PPM does before migrations. Has anyone experienced this before? I included a screenshot of the package line status as well.

 

Thanks,

Jajcen

0 Likes
1 Solution

Accepted Solutions
Super Contributor.. JHarris941 Super Contributor..
Super Contributor..

Re: "Command Execution Error" message when trying to migrate using Object Types

Jump to solution

Thanks Utkarsh for your help..from your suggestion we were able to determine the issue.

 

Within our PPM_HOME/logs directory there were some directories owned by root.  They should have been owned  by our application user.  These directories
are the REQ_% and PKG_% ones.

The last modified date on all of them is July 11th.

We think PPM was restarted by someone as root on that day.

When our weekly maintenance ran the next day, the problem stopped expanding because PPM was correctly started by our application user.

So now in PPM when those affected directories are accessed we get execution errors. (The ones owned by root.)

 

Thanks again for your help.

 

Jajcen

0 Likes
5 Replies
Established Member.. Utkarsh_Mishra
Established Member..

Re: "Command Execution Error" message when trying to migrate using Object Types

Jump to solution

Every OS has a limit of number of sub directories within any directory, so quite possible that your log directory limit is reached. Try this

 

  • Delete some of the old request/package/report directory within <PPM_ROOT>/logs

 

If still issue persitis then check whether your have enough disk space for PPM application on your server.

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
0 Likes
Super Contributor.. JHarris941 Super Contributor..
Super Contributor..

Re: "Command Execution Error" message when trying to migrate using Object Types

Jump to solution

hey 

0 Likes
Established Member.. Utkarsh_Mishra
Established Member..

Re: "Command Execution Error" message when trying to migrate using Object Types

Jump to solution

It is getting error when closing the File Stream (flush); can you try again by shortening the name of object.

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
Super Contributor.. JHarris941 Super Contributor..
Super Contributor..

Re: "Command Execution Error" message when trying to migrate using Object Types

Jump to solution

Thanks Utkarsh for your help..from your suggestion we were able to determine the issue.

 

Within our PPM_HOME/logs directory there were some directories owned by root.  They should have been owned  by our application user.  These directories
are the REQ_% and PKG_% ones.

The last modified date on all of them is July 11th.

We think PPM was restarted by someone as root on that day.

When our weekly maintenance ran the next day, the problem stopped expanding because PPM was correctly started by our application user.

So now in PPM when those affected directories are accessed we get execution errors. (The ones owned by root.)

 

Thanks again for your help.

 

Jajcen

0 Likes
Established Member.. Utkarsh_Mishra
Established Member..

Re: "Command Execution Error" message when trying to migrate using Object Types

Jump to solution

Great, good to know this 🙂

Cheers..
Utkarsh Mishra

-- Remember to give Kudos to answers! (click the KUDOS star)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.