Data Fabric ERROR

[Mirza12332]

I got Systems/Process Cores are Present error as you see above and  implemented description commands.

What should ı write instead of these commands ? Can you explain meaning of this commands ?

Thank you.

[Dave Olker]

The default core file directory is typically /opt/cores.  Can you check if this directory exists on your system and whether there are any files in this directory?

[Mirza12332]

@Dave Olker 

[Dave Olker]

That certainly explains why the cores alarm is getting raised.  For now you can delete all of those files in /opt/cores to clear the alarm.  If the MFS continues to generate core files then that would need to be investigated by HPE support.  If this is a stable, working cluster then MFS should not be creating cores.  If this is a cluster you are still working to get stable then I would wait and resolve any other issues with the cluster and see if that stop MFS from ceating these core files before engaging with HPE support.

[Mirza12332]

Hello,  I solved other issues for now but,   still meet same problem.

[ldarby]

Hi @Mirza12332,

Did you delete the cores as @Dave Olker suggested?  (the 12m could just be when the alarm was first raised when CLDB started up with cores present).  The question is if these cores are from earlier, or if any were newly generated since getting everything configured properly?  You can check when they were last generated with this:

ls -ltr /opt/cores | tail

Yes the cores indicate something went wrong, and that could be investigated, but if it was caused by bad config from earlier, then there isn't much value in spending the time and effort on that investigation.  If the cores are new since fixing the config, then yes I think we should investigate further.

Regards,
Laurence Darby

[Mirza12332]

@ldarby @Dave Olker 

Even those dates shown as old dates , whet ı dismiss ERROR, it appear again on web service. 

NOTE THAT: Node Servers dates are up to date.